Agile Estimating And Planning
Download as PPT, PDF3 likes1,543 views
This document discusses agile estimating and planning techniques. It explains that agile planning aims to reduce risk and uncertainty, support better decision making, and establish trust. Traditional planning can be problematic because work is prioritized for the convenience of developers rather than customer value. Agile techniques separate size from duration and use story points and velocity to estimate work. Iteration planning prioritizes stories until the team's bandwidth is full, while release planning is either feature-driven or time-driven based on defining velocity and forecasting points or length.
Agile Estimating And Planning
- 1. Agile Estimating and Planning Luca Grulla ESSAP Varese,Italy, 4/7/2008
- 2. Why planning and not plan ?
- 3. But what do we really want ? Reduce the risk Reduce uncertainty Support better decision making Establishing trust Conveying information
- 4. Problems with traditional planning Traditional plans are created with the assumptions that all the identified activities will be completed. This means that work is typically prioritized and sequenced for the convenience of the dev team. The work is not prioritized by the value to the customers.
- 5. Project phases Inception Release Planning Iteration Planning
- 6. Bank CMS: Story #1 As a Customer Relationship Manager I want to be able to send a welcome mail to every new customers in order to welcome them to our bank
- 7. Ideal Days Easy to communicate Don’t require bootstrapping But… Can be subjective Leads to questioning team’s productivity
- 8. Story Points Arbitrary unit that quantifies the 'difficulty' of a Story Story points encourage cross-functional behavior The conversion between Story Points and real time will change over time as the team become more familiar the project (Velocity) But… Difficult to get started Estimated Velocity as part of release planning has to be boot strapped in circumstances (at the start of projects) where there is nothing to use to judge the mapping between Story Points and effort
- 9. Velocity Number of story points completed per iteration Define the actual capacity of delivering of the team It’s the link between the size and the length of a project
- 10. Agile estimation techniques separate size from duration
- 11. Consistency vs Accuracy
- 12. Scale Powers of 2 (1, 2, 4, 8, 16…) Fibonacci (1, 2, 3, 5, 8, 13…) T-Shirt size (S, M, L, XL)
- 13. Bank CMS: Story #1 As a Customer Relationship Manager I want to be able to send a welcome mail to every new customers in order to welcome them to our bank
- 14. How to estimate The BA reads the story The team makes questions to understand the story better Every team member decides privately his estimate All the member show the estimate at the same time The higher and the lower discuss the reasons behind their decision Repeat until the estimate converge
- 15. What are we also doing ? Exploring the technical solution space Defining constraints Discussing the requirements Sharing different views of the problem
- 16. Iteration Planning According to the recent velocity (yesterday weather), the customer takes stories until the team bandwidth is full
- 17. Risk and Value Risk Value Low Risk High Value High Risk High Value Low Risk Low Value High Risk Low Value
- 18. Release Planning Can be feature-driven or time-driven Based on the requested approach, you define your velocity and then either your forecast the number of points (for a time-driven plan) or the length of the project (for a feature-driven plan)
- 19. Questions ?
- 20. References “Agile Estimating and Planning”, Mike Cohn