This document discusses software development best practices using an iterative approach called test-driven development (TDD). It recommends designing in small increments, writing tests before implementing code to verify it meets requirements, and continually refactoring code and re-testing. Diagrams show splitting projects into small user stories and tasks to deliver working software quickly in a predictable, sustainable way while avoiding bottlenecks.
Handle changing the requirements & prioritiesLower cost of changeProvide better visibility into project progressReduce riskMaximize return on investmentEncourage higher quality & simpler codeDeliver business value early & often
Some common reason make “waste”
Should have team meeting to discuss the plan, how to cut out delay, waste
- Realize purpose than conform to requirementIncrease feedback loops into development processLess document and more codingEncourage and accept immediately customer response to our yourRequire team planning
expertise
At the end of each iteration, ask team: - what’s slowing you down, or getting in your way of doing a good job? - make a list of good and bad practice => decide the best way to implement good practice
The developer should refactoring code by following these