Content deleted Content added
Improving language in the intro section |
|||
| (7 intermediate revisions by 6 users not shown) | |||
Line 1:
Of all the [[agile software development]] methodologies, '''outside–in software development''' takes a different approach to optimizing the software development process. Unlike other approaches, '''outside–in''' development focuses on satisfying the needs of stakeholders. The underlying theory is that to create successful software, the team must have a clear understanding of the goals and motivations of the stakeholders. The ultimate goal is to produce software that is highly
Outside–in software development is meant to primarily supplement existing software development methodologies. While it is suited for agile software development, it is possible to fit outside-in development into [[waterfall model|waterfall]]-based methodologies.
== The four stakeholder groups ==
What sets outside-in software development apart from other stakeholder-based approaches is the categorization of the four types of stakeholders. While the following four groups are unique however there can be and is usually a lot of interaction between them:
* '''Principals''': The people who buy your
* '''End users''': The people who interact with your product. They experience how your software works in the real world.
* '''Partners''': The people who make your product work in real life, such as operations teams and also business partners and system integrators.
Line 37 ⟶ 36:
* [[Carl Kessler]] and [[John Sweitzer]]. ''[[Outside-in Software Development: A Practical Approach to Building Successful Stakeholder-based Products]]'', IBM Press.
** First Edition, 2008. {{ISBN|0-13-157551-1}}. Pp. 1–3, 23–31, 183–195
*[[Craig Larman]] and [[Victor R. Basili]]. [https://web.archive.org/web/20080516194912/http://www2.umassd.edu/SWPI/xp/articles/r6047.pdf ''Iterative and Incremental Development:A Brief History '' IEEE Computer, June 2003]
{{DEFAULTSORT:Outside-in software development}}
| |||