1 / 37

Real World Scrum with TFS2013

Real World Scrum with TFS2013. Benjamin Day. Benjamin Day. Brookline, MA Consultant, Coach, & Trainer Microsoft MVP for Visual Studio ALM Team Foundation Server, Software Testing, Scrum , Software Architecture Scrum.org Classes Professional Scrum Developer (PSD)

emilia
Télécharger la présentation

Real World Scrum with TFS2013

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Real World Scrum with TFS2013 Benjamin Day

  2. Benjamin Day • Brookline, MA • Consultant, Coach, & Trainer • Microsoft MVP for Visual Studio ALM • Team Foundation Server, Software Testing, Scrum, Software Architecture • Scrum.org Classes • Professional Scrum Developer (PSD) • Professional Scrum Foundations (PSF) • www.benday.com, benday@benday.com, @benday

  3. Online courses at Pluralsight.com

  4. How many of you have heard ofScrum.org?

  5. (Warning: Shameless plug.)

  6. Professional Scrum Foundationsfor Teams training in Cambridge, MA on February 24th & 25th. http://bit.ly/186qR4y

  7. On with the show.

  8. The Goal: Show you how to use TFS to support Scrum.

  9. Disclaimer:TFS isn’t going to lead you toAgile/Scrum nirvana.

  10. TFS will help...

  11. …but TFS won’t just do it for you.

  12. Software is a human endeavor.

  13. There are actual people involved…

  14. …and (fortunately / unfortunately) you’re still going to need to talk to them.

  15. You’ll use TFS tostreamline the human automationand as the place of record.

  16. The Goal: Show you how to use TFS to support Scrum.

  17. Scrum in a nutshell.

  18. Scrum in a nutshell. • Team agrees to deliver working software in 30 days or less • Schedule a time to show that working software • Team creates the software • Team shows the software. Gathers feedback for next time.

  19. Scrum in a larger nutshell • There’s an idea for some software • Gather a Team • Team agrees to deliver working software in 30 days or less • Craft a Product Backlog • Schedule a time to show that working software • Team decides what they think they can do in a Sprint. • Team creates the softwareand assesses progress on a 24 hour interval • Team shows the Done software. Gathers feedback for next time. • Team conducts a Retrospective on how it went. • Repeat

  20. So how do you do that with Team Foundation Server 2013?

  21. Scrum  TFS2013 Demos • There’s an idea for some software • Create a Team Project in TFS • Gather a Team • Configure team(s) • Team agrees to deliver working software in 30 days or less • Configure Sprints

  22. Scrum  TFS2013 Demos • Craft a Product Backlog • Create a Product Backlog in TFS • Organize the Product Backlog using Features

  23. Does your team have a writtenDefinition of Done (DoD)?

  24. My ‘quickie’ sketch of a DoD for a PBI. • Checked in and merged/integrated with code for sprint • Unit tested without a shared database • Code Coverage of >75% • Compiles as part of an automated build • Code Reviewed by someone else • Test plan(s) in TFS • Tested by someone else • No P1 or P2 bugs • Demo’d and accepted by PO before Sprint Review • Database code & migration scripts checked in • Deployment script for feature • No undone work.

  25. “What does QA do at the start of a Sprint?”

  26. Scrum  TFS2013 Demos • Team decides what they think they can do in a Sprint • Sprint Planning in TFS • Capacity Planning • (…and don't forget QA testing in the DoD)

  27. Scrum  TFS2013 Demos • Team creates the software and assesses progress on a 24-hour interval. • Run your Daily Scrum using the Scrum Board • Maintain situational awareness using the Scrum Board • Use the Burndown Chart to determine if you’re on target

  28. Supporting your DoD Demos • Automated builds • Test plans in MTM & Test Hub • Manual Testing • Coded UI Tests • Code Reviews • Gather Feedback with Feedback Manager • Lab management deployment builds • Helps support your testing efforts • Helps prep for your Sprint Review meetings

  29. Streamline “Situational Awareness” • Use Team Rooms to help keep everyone aware of what’s going on.

  30. “What about planning for the next sprint?”

  31. “What are my BA’s doing?”

  32. Answer:PowerPoint Storyboarding* * = amongst other things

  33. Supporting planning • PowerPoint Storyboarding

  34. Scrum in a larger nutshell • There’s an idea for some software • Gather a Team • Team agrees to deliver working software in 30 days or less • Craft a Product Backlog • Schedule a time to show that working software • Team decides what they think they can do in a Sprint. • Team creates the softwareand assesses progress on a 24 hour interval • Team shows the Done software. Gathers feedback for next time. • Team conducts a Retrospective on how it went. • Repeat

  35. Any last questions?

  36. Thank you. www.benday.com | benday@benday.com

More Related