...
- Keep the product in a constantly known state
- increasing rigor in the definition of "done"
- skilled use of TDD
- refactoring
- continuous integration
- Build/Test more than once per day
- New Scope discovery tends to outpace velocity
- Scrum teams ship
- the highest-value products they can within time constraints
- accepting that some requests must be delayed until future releases
- Scrum teams ship
- Role of Management Changes
- from telling people what to do
- to
- leading
- helping
- To become more adaptable
- development teams must learn engineering practices that reduce the cost of change, a kind of technical debt
- Re-prioritization should affect the Product Backlog not a Sprint in progress (except in real emergencies).
- Hold off decisions until the end of the meeting
- Give everyone a chance to offer their view.
- Keep the product in a constantly known state