Outside–in software development: Difference between revisions

Revision as of 04:24, 18 March 2013

Revision as of 20:18, 20 April 2013

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 behind outside–in software is that to create successful software, you must have a clear understanding of the goals and motivations of your stakeholders. Your ultimate goal is to produce software that is highly [[Consumability|consumable]] and meets/exceeds the needs of your client.

Outside-inOutside–in software development is meant to primarily supplement your existing software development methodology. While it does ideally work in more agile environments, it is possible

to fit outside-in development into [[waterfall model|waterfall]]-based or [[six sigma]] methodologies. Outside-inOutside–in software development is not a catchall solution, but a way to better your existing methodology.

== The four stakeholder groups ==

Line 8:

What sets outside-in software development apart from other stakeholder-based approaches is the categorization of the four types of stakeholders. The following four groups are unique, but there is a lot of interaction between all four:

* '''Principals''': The people who buy your software--thesoftware—the most important stakeholder to appease.

* '''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 24:

Kessler and Sweitzer recommend that, no matter what kind of development methodology you employ, you incrementally introduce outside–in development to your team. They cite the lack of enthusiasm by developers as the main reason to not implement sweeping, large scale change.

Outside–in software development should not be introduced as a holistic development process. It is meant to supplement your current software development methodology.

== See also ==

Line 38:

* [[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]]. [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}}

[[Category:Software development process]]

[[Category:Human–computer interaction]]