Outside–in software development: Difference between revisions

Revision as of 17:04, 6 August 2022

Revision as of 23:39, 9 January 2023

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.