1. AGILE PROJECT MANAGEMENT WITH TEAM FOUNDATION SERVER 2010 Brian Keller Microsoft

2. MANUAL TESTING WITH MICROSOFT TEST MANAGER 2010 Philosophy and Design Goals Microsoft Test Manager  Test Plans  Test Case Management  Authoring Tests  Running Tests  Fast-Forward for Manual Testing Introduction to Coded UI Tests Tuesday| 3:45 PM – 5:00 PM Mediteranea 2

3. TEST AUTOMATION WITH VISUAL STUDIO 2010: CODED UI TESTS AND LAB MANAGEMENT Advanced Coded UI Tests Lab Management  Build-Deploy-Test  Best Practices  Getting Started Wednesday | 9:45 AM – 11:00 AM Europa 2

4. AGILE PROJECT MANAGEMENT WITH TEAM FOUNDATION SERVER 2010 Backlog Management Iteration Planning Running the Sprint Project Server Integration Team Foundation Server vNext

5. I WORK HERE…

6. …ON THIS…

7. …AND THIS. http://bit.ly/ThisWeekC9

8. I BLOG HERE: HTTP://BLOGS.MSDN.COM/BRIANKEL HTTP://BLOGS.MSDN.COM/BRIANKEL

9. http://tinyurl.com/ALM2010Book http://tinyurl.com/TFSBook

11. INDIVIDUALS AND INTERACTIONS over processes and tools WORKING SOFTWARE over comprehensive documentation CUSTOMER COLLABORATION over contract negotiation RESPONDING TO CHANGE over following a plan THE AGILE MANIFESTO

12. Product Backlog Sprint Backlog Sprint Potentially Shippable Increment

13. 5 3 8 3 Product Backlog 1 8 Priority 5

14. 5 3 8 3 Product Backlog 1 8 55

15. Acceptance Criteria I can search for …. I can pay with a …. I can view and edit … Product Backlog

16. DEMO Backlog Management

17. Product Backlog Sprint Backlog Sprint Potentially Shippable Increment

18. 5 8 5 Product Backlog Sprint Backlog 3

19. Product Backlog Sprint Backlog

20. Product Backlog Sprint Backlog

21. Product Backlog Sprint Backlog TOO BIG!

22. Product Backlog Sprint Backlog COMMIT!

23. DEMO Iteration Planning

24. Product Backlog Sprint Backlog Sprint Potentially Shippable Increment

25. Product Backlog Sprint Backlog

26. Product Backlog Sprint Backlog

27. Product Backlog Sprint Backlog

28. Product Backlog Sprint Backlog

29. Product Backlog Sprint Backlog Sprint Potentially Shippable Increment

30. Product Backlog Sprint Backlog

31. Product Backlog Sprint Backlog What worked? What didn’t work? What should we change?

32. Product Backlog Velocity Sprint 1: Sprint 2: Sprint 3: Sprint 4: 13 15 12 18

33. Product Backlog Priority

34. Product Backlog Sprint Backlog Sprint Potentially Shippable Increment

37. Burndown chart tracks remaining and completed work

40. 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 stories…

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

42. Rich set of reports track progress

43. 1.Define done 2.Fail fast 3.Understand your team’s velocity 4.Write unit tests – always 5.Bugs are real work 6.Code with confidence 7. Always deliver value 8. Finish what you start 9. Autonomy, mastery, purpose 10. Do the right thing… at the right time 11. Plan until you need to learn 12. Quality is not a variable

61. QUESTIONS? After the session please fulfil the questionnaire. Questionnaires will be sent to you by e-mail and will be available in the profile section of the NT Conference website www.ntk.si.www.ntk.si Thank you!