|
Of all the [[agile software development]] methodologies, '''outside-inoutside–in software development''' takes a different approach to optimizing the software development process. Unlike other approaches, '''outside-inoutside–in''' development focuses on satisfying the needs of [[stakeholder (corporate)|stakeholders]]. The underlying theory behind outside-inoutside–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-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
* '''Principals''': The people who buy your software--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.
* '''Insiders''': The people within your company that have some impact on how your team develops software.
It is crucial to speak with all stakeholders, even if they aren'tare not the primary audience of your software.
== Implementing outside-inoutside–in software development ==
The outside-inoutside–in approach does not require your entire development methodology to change. Outside-inOutside–in development can supplement the existing tools of developers.
Outside-inOutside–in development works particularly well in the context of agile/lean development. One of the major tenets of agile development is to program with the least amount of waste. Outside-in methodologies promote only developing according to stakeholder requirements. By identifying your stakeholders properly and soliciting helpful feedback early on in the development process, agile and outside-in methodologies can mesh together seamlessly.
Kessler and Sweitzer recommend that, no matter what kind of development methodology you employ, you incrementally introduce outside-inoutside–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-inOutside–in software development should not be introduced as a holistic development process. It is meant to supplement your current software development methodology.
== See also ==
| 