The biggest question looming at the start of a project is, what exactly are we
building? We know the general shape of the system to be built. We may know, for
example, that we are building a word processor. But there are always dark corners
yet to be explored or issues yet to be settled about how specific features will work.
Will our word processor include an interactive table design feature, or will tables
be designed by entering values into a series of screens?
Chapter Contents
- Shift from Documents to Discussions
- Don’t Throw the Baby Out with the Documentation
- Use User Stories for the Product Backlog
- Progressively Refine Requirements
- Emergent Requirements
- The Product Backlog Iceberg
- Why Progressively Refine Requirements?
- Progressive Refinement of User Stories
- Learn to Start Without a Specification
- Specify by Example
- Cross-Functional Teams Reduce Documentation Needs
- Make the Product Backlog DEEP
- Don’t Forget to Talk
- Additional Reading