Being Agile with Any Process Template in TFS 2012
•
1 like•3,065 views
Using an Agile template does not MAKE you Agile. Using a CMMI template does not PREVENT you from being agile. In this talk, I compare and contrast the TFS process templates available out of the box, and relate the process template artifacts and features to the types of methodologies and practices they support.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (17)
Similar to Being Agile with Any Process Template in TFS 2012
Similar to Being Agile with Any Process Template in TFS 2012 (20)
More from Angela Dugan
More from Angela Dugan (20)
Recently uploaded
Recently uploaded (20)
Being Agile with Any Process Template in TFS 2012
- 1. Angela Dugan ALM Practice Manager Polaris Solutions Angela.Dugan@PolarisSolutions.com
- 3. Quick Review of Agile
- 6. SCRUM = Agile Agile <> Scrum
- 8. Activities Artifacts Sizing Product Backlog* Pre-Planning User Stories* Planning* Burn-down* Daily Standup Definition of Done* Sprints/Iterations* Sprint Backlog* Sprint Review/Demo Retrospective Deliverables Working Software*
- 9. Visual Studio ALM Ecosystem
- 13. Managing your product backlog as PBIs (and Bugs) Task, Test Case, & Bug Bugs are tracked during the iteration, added to backlog Execution PBIs are broken down into specific tasks Planning PBIs, Bugs
- 14. Managing your product backlog as User Stories User Story As a <> I want to <> so that I can <>. Bugs are tracked during the iteration Execution Task, Test Case, & Bug Stories are broken down into specific tasks Planning Epics & Themes
- 15. Feature Requirements are created at many levels and tracked as a hierarchy Tracking changes to features. Task Work during execution Test Case, & Bug Implementation verification Execution Change Request Planning Business Objective
- 16. Process area Visual Studio Scrum Bug backlog management Bug (Scrum) MSF for Agile MSF for CMMI • Bug (Agile) • Triage Workbook • Bug (CMMI) • Triage Workbook Issue (CMMI) Risk (CMMI) Review (CMMI) Issues Workbook Project management Impediment (Scrum) • Issue (Agile) • Issues Workbook • • • • Test management • Test Case • Shared Steps • Test Case • Shared Steps • Test Case • Shared Steps • • Code review and feedback • • Audit trail Code Review Request Code Review Response Feedback Request Feedback Response Not supported • • • • Code Review Request Code Review Response Feedback Request Feedback Response Minimal • • • • Code Review Request Code Review Response Feedback Request Feedback Response Supported
- 17. Tasks SCRUM Monitor bug activity, reactivations, and trends. • Build Success Over Time Report Monitor build activity, success, and trends. • Build Summary Report Track project health, team burn rate, and task completion. You can review this report daily or weekly to monitor the progress of the team during an iteration. Determine added work. (a.k.a. “Scope Creep”) Monitor testing activity. • Release Burndown (Scrum) • Sprint Burndown (Scrum) • Velocity (Scrum) Agile CMMI Bug Status Report Bug Trends Report Reactivations Report Build Quality Indicators Report • Build Success Over Time Report • Build Summary Report • • • • • • • • • Burndown and Burn Rate Report (Agile) • Remaining Work Report • Status on All Iterations Report • Stories Overview Report (Agile) • Stories Progress Report (Agile) • Unplanned Work • Test Case Readiness Report • Test Case Readiness Report • Test Plan Progress Report • Test Plan Progress Report • • • • • • • Bug Status Report Bug Trends Report Reactivations Report Build Quality Indicators Report Build Success Over Time Report Build Summary Report Burndown and Burn Rate Report (CMMI) Remaining Work Report Status on All Iterations Report Requirements Progress Report (CMMI) Requirements Overview Report (CMMI) • Unplanned Work • Test Case Readiness Report • Test Plan Progress Report
- 18. “Agile” Features in TFS 2012 Planning Tools Reporting
- 19. Supporting Features - Teams
- 20. “Agile” Planning Tools Work for Any Process Template Tools generated per Team Drag and Drop for Quick Prioritization and Assignment Real-time Repor ting Interactive Kanban Board Interactive Task Board Customizable
- 23. Ideal Trend = trend in which the team burns down all remaining effor t by the end of the sprint. Remaining Work = hours remaining for tasks that are marked as “ To Do” in a sprint
- 24. Track how much effor t your team has repor ted as complete for each sprint. Estimate how much backlog effor t your team can handle in future sprints. Answers the following questions: How much effor t has your team completed in each sprint? What is the maximum velocity of your team? What is the minimum velocity of your team? What is the average velocity of your team?
- 26. Making it “real”