How little can I do to successfully reach this goal?
Continually asking youreself that questions is the best ways to minimize rework, reach goals quickly, guarantee sustainable solutions, and design for wear.
This approach creates a functional prototype quickly, keeps stress levels down, and keeps product teams lean.
Johanna Rothman has an excellent post highlighting other benefits of this approach from the product development perspective:
- Understanding the requirements is a scarce resource, and we should focus our energies towards delivering something that shows we understand the specific requirement and the value it has to our customer.
- Schedule is critical and we don’t have time to do it again, or build technical debt
- Project cost is important, and we need to manage it
and another on how this approach specifically addresses rework
See how little you can do, and deliver that much as quickly as possible. The technique I use most often is to break the pieces into groups of requirements/features and then perform iterations within whatever lifecycle the people are used to.
Thanks to NerdHerding for Beginners.