A field study of the software design process for large systems
Communications of the ACM
Agile software development
Microsoft Secrets: How the World's Most Powerful Software Company Creates Technology, Shapes Markets, and Manages People
Internet Software Engineering: A Different Class of Processes
Annals of Software Engineering
Balancing Agility and Discipline: A Guide for the Perplexed
Balancing Agility and Discipline: A Guide for the Perplexed
Distributed Scrum: Agile Project Management with Outsourced Development Teams
HICSS '07 Proceedings of the 40th Annual Hawaii International Conference on System Sciences
A Design Science Research Methodology for Information Systems Research
Journal of Management Information Systems
Building theory in the sciences of the artificial
Proceedings of the 4th International Conference on Design Science Research in Information Systems and Technology
Information Systems Research
Post-agility: What follows a decade of agility?
Information and Software Technology
Design science in information systems research
MIS Quarterly
Design science research post hevner et al.: criteria, standards, guidelines, and expectations
DESRIST'10 Proceedings of the 5th international conference on Global Perspectives on Design Science Research
| Hi-index | 0.00 |
Design theory is often an outcome of Design Science Research (DSR) and kernel theories provide explanatory justification of design principles. But like an iceberg, many of the design principles lie hidden under the surface or inadequately specified. Ascertaining the completeness of the design principles requires additional design process steps to surface underlying assumptions and to abstract design principles which emerge during secondary design. We follow the development of a project management decision support artifact and describe the primary design, based on literature on agile systems development, and the subsequent secondary design that took place in a financial company. Analysis reveals an "iceberg phenomenon"; only a partial design justification was initially apparent, and underlying design assumptions are only revealed through deeper reflection and analysis. We conclude by providing guidelines for making design justification more explicit in both the design and the evaluation phases.