2024 Public Training Schedule
December 9 – 12, 2024 – Agile Analysis and Design Patterns – Half-Day Sessions
2025 Public Training Schedule
January 14 – 17, 2025 – Agile Analysis and Design Patterns – Half-Day Sessions
Follow me on Twitter:
Blog Post Categories
- Announcements {19}
- Articles {2}
- Bits and Pieces {74}
- Blogosphere {1}
- Bonuses {2}
- Build in Small Batches {27}
- Collaborate {38}
- Create CLEAN Code {34}
- Implement the Design Last {11}
- Integrate Continuously {30}
- Off-Topic but Interesting {3}
- Rants {82}
- Refactor Legacy Code {24}
- Say What, Why, and for Whom Before How {22}
- Seven Strategies {38}
- Specify Behaviors with Tests {17}
- Write the Test First {27}
Archives
Privacy Policy
(c) 2024 To Be Agile
- May 11, 2016
- Bits and Pieces
A central benefit to Agile software development is breaking down tasks into the smallest component that can provide measurable feedback. When we do this we take complex tasks and simplify them by breaking them down into smaller, easier-to-handle tasks.
Smaller tasks have four essential benefits:
First, they’re easier to understand, which means they cost less to work with and are less risky.
Smaller tasks are also easier to estimate. More accurate estimates give projects a higher degree of predictability.
Smaller tasks are also easier to implement. When development is more highly focused, tasks get competed quicker.
Finally, smaller tasks are easier to test and verify. When we work with smaller tasks it means we get validation more frequently, which gives us more opportunities to adjust.
And that’s all I have to say about that.
Previous Post: « Dev.Cast
Next Post: The Single Wringable Neck »