in 99 words
Technical debt is code cruft; refactor to get rid of it. Iterations are a weekly timebox; timeboxes always end on time, even if the work isn't 100% done. Stories are how you plan (but they aren't requirements). Velocity counts what you did, so you can predict what you'll do.
Speaking of planning, strive to make decisions at the last reponsible moment. You'll have more information and make fewer mistakes. Use the Theory of Constraints to optimize whole systems by accepting waste in non-constraints.
Finally, be mindful in everything you do, so that you may learn, grow, and excel.
as haiku
before pulling weeds
perhaps I should remember
what the plants look like
Deleted Scene
Inside the Book
- XP Concepts
- Refactoring
- Technical Debt
- Timeboxing
- The Last Responsible Moment
- Stories
- Iterations
- Velocity
- Theory of Constraints
- Mindfulness
Subscribe (RSS)
Follow Me (Twitter)

Print

Loading comments...