Outside–in software development: Difference between revisions

Revision as of 05:32, 8 March 2018

Latest revision as of 10:16, 16 January 2025

(6 intermediate revisions by 5 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 [[Consumability|consumable]] and meets or exceeds the needs of the intended client.

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 software—thesoftware. This is the most important stakeholder group 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.