Content deleted Content added
m WP:CHECKWIKI error fixes - Replaced endash with hyphen in sortkey per WP:MCSTJR using AWB (9100) |
m Remove blank line(s) between list items per WP:LISTGAP to fix an accessibility issue for users of screen readers. Do WP:GENFIXES and cleanup if needed. Discuss this at... using AWB |
||
Line 11:
* '''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.
Line 18 ⟶ 17:
== Implementing outside–in software development ==
The outside–in approach does not require your entire development methodology to change. Outside–in development can supplement the existing tools of developers.
Outside–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–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.
| |||