Iteration planning and user story definition

software engineering

1. Presented by Jobin joy Roll no-23 Iteration planning And User story-definition

2. Iteration planning is the process of discussing and planning the next cycle, phase or iteration of a software application that is under development. It is conducted through a meeting of the entire software development team at the starting point of each iteration to formally plan technical and non-technical processes.

3. Iteration planning

4. The purpose of iteration planning is for the team to complete the set of top ranked product backlog items. The commitment is time boxed based on the length of iteration and team velocity

5. Who Is Involved??? Scrum Master − The scrum master acts as a facilitator for the agile delivery team. Product Owner − The product owner deals with the detailed view of the product backlog and their acceptance criteria. Agile Team − Agile delivery defines their tasks and sets the effort estimates required to fulfill the commitment.

6. Agile Iteration Planning

7. Planning Process Following are the steps involved in iteration planning − Determine how many stories can fit in an iteration Break these stories into tasks and assign each task to their owners. Each task is given estimates in hours.

8. Planning process These estimates help team members to check how many task hours each member have for the iteration.

9. 9 Iteration Planning Characteristics of iterations to consider when planning: Generally 1 to 3 weeks long. More developer-focused than they are customer / product-owner focused. More precise than releases in terms of their planning focus. Have a specified length of time based on fixed dates. Start by holding an iteration planning meeting. © 2014 Intelliware Development Inc .

10. Velocity calculations An agile team calculates velocity based on past iterations. Velocity is an average number of units required to finish user stories in an iteration. For example, if a team took 12, 14, 10 story points in each iteration for the last three iterations, the team can take 12 as velocity for the next iteration.

11. Project Velocity Planned velocity tells the team how many user stories can be completed in the current iteration. If the team quickly finishes the tasks assigned, then more user stories can be pulled in. Otherwise, stories can be moved out too to the next iteration.

12. Task Capacity The capacity of a team is derived from the following three facts − Number of ideal working hours in a day Available days of person in the iteration Percentage of time a member is exclusively available for the team.

13. Planning Steps Product Owner describes the highest ranked item of product backlog. Team describes the tasks required to complete the item. Team members own the tasks. Team members estimate the time to finish each task.

14. Planning Steps These steps are repeated for all the items in the iteration. If any individual is overloaded with tasks, then his/her task is distributed among other team members

15. 15 Iteration Planning Meeting Objectives: Acknowledge accomplishments of last iteration. Determine the level of overall progress. Review problems and issues. Establish objectives for next iteration. Task planning for target stories (optional). © 2014 Intelliware Development Inc .

16. A user story is a tool used in Agile software development to capture a description of a software feature from an end-user perspective. The user story describes the type of user what they want and why. A user story helps to create a simplified dscription of a requirement.

17. 17 What is a User Story? There are numerous definitions for stories. A common definition: A short description of a function that an end-user would want. From Kent Beck: “ One thing the customer wants the system to do…(it) should be testable . ” 5 From Ron Jeffries: “ Stories are promises for…the series of conversations that will take place between the customer and the programmers . ” 6 © 2014 Intelliware Development Inc . 5 Beck, Kent, 2000. “Extreme Programming: Embrace Change”, (Addison-Wesley, Boston, MA) 6 Jeffries, Ron, Anderson, Ann and Hendrickson, Chet, 2001. “Extreme Programming Installed”, (Addison-Wesley, Boston, MA)

18. 18 Why User Stories? Stories have many advantages. Easy to understand Written in non-technical language that customers / product owners can relate to. Work at the right level Not too detailed, are easy to manipulate and move around, like a deck of cards. Relatively easy to create Writing stories takes some skill, but experts can define entire systems for planning purposes in a matter of hours. © 2014 Intelliware Development Inc .

19. 19 User Story Components At minimum, a user story has: A card to write the story on. A name that the customers and developers understand. A description (should be limited to one or two sentences). Acceptance criteria to define when the story will be considered completed. A size estimate for time management. © 2014 Intelliware Development Inc . A typical story card.

20. Advantages of User story A user story provides light-weight approach for managing requirements for the system. A short statement of function captured on an index card/tool. The details are figured out n the future conversations between the team and product owner or customers. This approach facilitates Just In Time requirement gathering. We can write a user story to cover large amounts of functionality. These large user stories are generally known as epics .