Microsoft Singapore Developer Days Event - August 2011

1. 19th August 2011 Microsoft Singapore ALM Event Scrum withMicrosoftVisual Studio Team Foundation Server 2010 Adrian Dunne | Microsoft Singapore

2. Team Foundation Server 2010

3. An Open Platform

4. Source: Forrester Reasearch, Inc.

5. Why is Agile Catching On? 5

6. Business Needs Demand It “Firms today experience a much higher velocity of business change. Market opportunities appear or dissolve in months or weeks instead of years. This increased business velocity demands much greater agility from business systems.” Diego Lo Giudice and Dave West, Forrester February 2011 Transforming Application Delivery

8. Regular discussions with stakeholders

10. Planning the Project

11. Planning a Sprint

14. Evolving backlog of Product Backlog Items

15. Describes what users need and value

16. Owned by the Product Owner

17. Prioritized by business value

20. Creating new PBIs

21. Prioritizing

24. Planning the Project

25. Planning a Sprint

28. Each PBI is decomposed into tasks

30. Product Backlog Iteration Backlog PBIs Tasks (Points) Planning a Sprint PBIs 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!

32. Team members Sign up for tasks

33. Commit

36. Planning the Project

37. Planning a Sprint

40. What was done

41. What will be done

42. Impediments

43. Sprint Burn-down

44. Deliver a “potentially shippable” increment

45. Demo the value delivered

47. Running a Sprint Product Backlog Iteration Backlog PBIs PBIs Tasks (hours) Completed work is reported daily

48. Running a Sprint Product Backlog Iteration Backlog PBIs PBIs Tasks (hours)

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

50. Product Backlog Iteration Backlog PBIs PBIs 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

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

52. Running a Sprint Product Backlog Iteration Backlog PBIs PBIs Tasks (Points) PBIs and tasks are cleared from the backlog – the team delivered on its commitment PBIs 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…

53. Running a Sprint Product Backlog Iteration Backlog PBIs PBIs Tasks (Points) New PBIs are added to the Product Backlog

54. Running a Sprint Product Backlog Iteration Backlog PBIs PBIs Tasks (Points) The backlog is prioritized and ready for the team to plan the next sprint

56. Track and Resolve Impediments

57. Track progress with reports and dashboards

59. Tracking Progress - Development Burndown chart tracks remaining and completed work

60. Tracking Progress - Development

61. Tracking Progress - Development

62. Tracking Progress - Development Detailed sprint progress is tracked on the project portal The burndown shows the team on track… And almost half of the tasks remain open But the team hasn’t closed any of the three PBIs…

63. Tracking Progress - Development The Scrum Master opens an issue to track the problem the portal has identified

64. Tracking Progress - Development The issue is opened and tracked in TFS

65. Tracking Progress – QA The portal brings data together so it can be analyzed to ensure success on a sprint Test are passing… But bugs are climbing steadily

66. Tracking Progress - QA Rich set of reports track progress

67. Product Backlog Daily Sprint Sprint Backlog Potentially Shippable Increment

68. vNextA few agile driven features coming to TFS

70. Tool pre-populates required data

71. Streamlines the association and update process.

72. Effectively allocate work balancing load with available capacity

73. Real-time feedback on the updates to the planTeam capacity at a glance

74. Task Board in Team Web Accessupdate the status of work items visually Burndown progress Easily move tasks around

76. Packages all the open work

77. Save entire environment settings

78. Fix urgent bugs

79. Recall task, work is instantly restored in context and error-free.