This document discusses using Scrum for agile software development. It covers planning a project with a product backlog of prioritized user stories, planning sprints by committing to stories and tasks, running sprints with daily standups and a demo at the end, and reporting on burndowns, tests, bugs, and story progress. Visual Studio tools like work items and queries can help manage artifacts for Scrum projects. Iterative development with Scrum focuses on early delivery of valuable features.

1. Succeeding with Agile Software Development with Scrum Patrick Yong, MVP (SharePoint Server) http://patrickyong.net | i-payong@microsoft.com

2. Agenda Visual Studio ALM Scrum Planning a project Planning a sprint Running a sprint Reporting

3. Visual Studio ALM Plan and Track Design Develop Build Test Deploy

4. Plan and Track

5. Launching a new project

6. demo Creating a new Team Project

7. Agenda Visual Studio ALM Scrum Planning a project Planning a sprint Running a sprint Reporting

8. What is Scrum?

9. Roles Product owner Scrum Master Team role

10. Meetings

11. TFS Artifacts for Agile Development Work Items and Workflow Queries Dashboard Excel Reports Workbooks Reports

12. Why Scrum? Iterative Development Lots of small “product releases” over the project’s lifetime As opposed to one major product release at the end Bugs / Problems are found early Products are usable earlier in the process Involves the customer during each iteration Iterative Development lends itself to the Scrum modus operandi Scrum’s artifactpromote customer involvement They allow the customer to re-prioritise the order in which “development” work is done

13. A word of Warning Some project managers might not like the following slides. Viewerdiscretionis advised.

14. Waterfall vs. Iterative Development requirement gathering analysis & design development testing deployment Customer happy, early release? cost of change 80% of a product’s value comes from 20% of its features time Managing Iterative Development Using Scrum

15. Why focus on Iterative Development? Traditional, Waterfall profit & loss cost curve

16. Why focus on Iterative Development? Iterative Development, early release profit & loss cost curve

17. Agenda Visual Studio ALM Scrum Planning a project Planning a sprint Running a sprint Reporting

18. Planning the Project Product Backlog “As a new customer I want to register online so I can use the services offered” User Stories 5 8 Stories are listed on the backlog in priority order The team estimates each story using story points 5 Priority 3 New stories are added to the product backlog 8 1

19. Product Backlog User Stories Planning the Project Stories are planned for completion in upcoming sprints Sprint 3 3 3 3 Sprint 4 The product owner re-prioritizes the backlog Priority 4 4 4

20. Planning Product Backlog

21. What makes a good user story? INVEST Independent Negotiable Valuable Estimable Small Testable http://www.userstories.com/book

22. Start writing user story Does your user stories answer the following? Who the user is? What the user need to do? Why the user need to do that? “As a <user>, I need to <action> in order to <reason>”.

23. Before you rank user stories Small enough to be implemented in the sprint Just detailed enough to describe and estimate the work that is required to implement the story Acceptance criteria defined

24. Epic and Theme Epic Very large user stories that represent a significant amount of work Theme User stories that are fairly large, generally larger than you would implement in a sprint It must be broken down into smaller user stories.

25. Spikes Work that is not a direct implementation of a user story. Research Bug Process improvements

26. Prioritize your user stories First Things First: Prioritizing Requirements http://www.processimpact.com/articles/prioritizing.html

27. Story Points Story points are a unit of measure for expressing the overall size of a user story Do not translate directly into a specific number of hours Less precise = less effort to determine Do detailed estimation of hours of work later

28. Velocity Total story points in a sprint A starting point that you can use to determine how many user stories to implement in the sprint.

29. Estimate Release Plan Remember this: Each sprint, your team will complete an increment of the product that it could ship As such Identify groups of user stories that, together, provide enough business value to release Determine in which sprints the team expects to complete those groups of user stories Note: Its OK to remove/ add user stories to sprint

30. demo Project planning with MS Excel

31. Agenda Visual Studio ALM Scrum Planning a project Planning a sprint Running a sprint Reporting

32. Product Backlog User Stories Planning a Sprint Iteration Backlog User Stories Tasks (hours) Commit! Based on estimates the team commits to each story 3 3 The team thinks this story is more work than they can commit to… During the sprint planning meeting, the product owner and the team add User Stories to the sprint 3 The team breaks down each story into tasks Commit! Can’t Commit!

33. Product Backlog Iteration Backlog User Stories User Stories Tasks (hours) Planning a Sprint User Stories Tasks (hours) Commit! 3 3 3 The larger story is removed from the sprint and the team considers a smaller story on the backlog Commit! ? 3 The sprint is now planned and the team is ready to get started! The team can commit to this smaller story Commit!

34. Demo

35. Agenda Visual Studio ALM Scrum Planning a project Planning a sprint Running a sprint Reporting

36. How do you Run a Sprint? Track Progress Daily Sprint Meeting What work has been completed What work remains Deliver a “potentially shippable” increment Demo the value delivered Retrospective

37. Product Backlog Iteration Backlog User Stories User Stories Tasks (hours) Running a Sprint The team starts work on the tasks…

38. Running a Sprint Product Backlog Iteration Backlog User Stories User Stories Tasks (hours) Completed work is reported daily

39. Running a Sprint Product Backlog Iteration Backlog User Stories User Stories Tasks (hours)

40. Running a Sprint Product Backlog Iteration Backlog User Stories User Stories Tasks (hours) Each User Story has been implemented All work for the sprint is “done-done”

41. Product Backlog Iteration Backlog User Stories User Stories Tasks (hours) Running a Sprint And the team has developed a “potentially shippable” increment The team holds a demo to show the value they have delivered

42. Running a Sprint Product Backlog Iteration Backlog User Stories User Stories Tasks (hours) The latest increment is shipped to customers

43. Running a Sprint Product Backlog Iteration Backlog User Stories User Stories Tasks (hours) Stories and tasks are cleared from the backlog – the team delivered on its commitment Stories delivered in the last sprint are closed What worked? What didn’t work? What can the team do to improve? The team holds a retrospective…

44. Running a Sprint Product Backlog Iteration Backlog User Stories User Stories Tasks (hours) New Stories are added to the Product Backlog

45. Running a Sprint Product Backlog Iteration Backlog User Stories User Stories Tasks (hours) The backlog is prioritized and ready for the team to plan the next sprint

46. Agenda Visual Studio ALM Scrum Planning a project Planning a sprint Running a sprint Reporting

47. Burndown and Burn Rate

48. Build Quality Indicator

49. Test Plan Progress Unhealthy symptoms High no. of test failed No. of passed test remained flat

50. Bug Status

51. Bug Trend Healthy trend Bugs discovered early Fewer bugs towardsthe end Bugs resolved faster thanbeing discovered

52. Stories Overview Report

53. Story Progress Report

54. demo

55. Resources Brian Harry http://blogs.msdn.com/bharry Aaron Bjork http://blogs.msdn.com/aaronbjork/