This presentation gives you a detailed look at what is in the out of the box templates available in TFS 2013, how they differ, and how that affects some of the ALM tooling.

1. Microsoft Visual Studio
Team Foundation Server
Process Templates
Angela Dugan
ALM Practice Manager
Polaris Solutions
Angela.Dugan@PolarisSolutions.com

2. Angela Dugan
Application
Lifecycle
Management
Project
Leadership
.NET
Solutions
Mobile
Solutions

4. AGENDA


What is a process template?
What process templates are available?
In the Box
 3 rd Party


What’s new in Team Foundation Server 2013?
Agile Planning Tools
 Reporting


5. AGENDA


What is a process template?
What process templates are available?
In the Box
 3 rd Party


Team Foundation Server 2013
Agile Planning Tools
 Reporting


6. WHAT DOES A PROCESS TEMPLATE LOOK LIKE?

7. WHAT DOES A PROCESS TEMPLATE LOOK LIKE?

Behind the scenes it’s just a bunch of XML

8. WHAT’S INCLUDED?










Work Item Type Definitions
Work Item Categories
Work Item Links
Queries
Repor ts
Lab Settings
Build Settings
Por tal Settings
Process Guidance
Source Control Settings

9. PROCESS CONFIGURATION OPTIONS
Backlog Work Item Types
Quick- Add Settings
Default Columns & Widths
Feedback Work item
attributes
Work Item Categories
Meta-states
Weekend days
Work Item Colors

10. AGENDA


What is a process template?
What process templates are available?
In the Box
 3rd Party


Team Foundation Server 2012?
Agile Planning Tools
 Reporting


11. PROCESS TEMPLATES – IN THE BOX
 Scrum 2013
 Extremely Lightweight
 Stretch to fit
 Targets teams implementing Scrum
 MSF for A gile Sof tware Development 2013
 Lightweight/Flat
 Stretch to fit
 Targets teams implementing Agile project management practices
 MSF for CMMI Process Improvement 2013
 Deeper hierarchy
 Stretch to fit
 Targeting teams interested in deep traceability/ auditablity

12. SCRUM
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

13. MSF FOR AGILE HIERARCHY
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

14. MSF FOR CMMI HIERARCHY
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

15. COMPARE & CONTRAST
Process area
Scrum 2013
Workflow states
•
•
•
•
•
New
Approved
Committed
Done
Removed
MSF for Agile 2013
•
•
•
•
•
New
Active
Resolved
Closed
Removed
MSF for CMMI 2013
•
•
•
•
Proposed
Active
Resolved
Closed
Product planning
• Bug (Scrum)
To customize the backlog pages,
• User Story (Agile)
• Product Backlog Item (Scrum)
see Customize the Backlog
• Agile backlogs
• Agile backlogs
Pages.
• Requirement (CMMI)
• Agile backlogs
Task and iteration planning
• Task (Scrum)
To customize the task board, see
• Agile task board
Customize the Task Board Page.
• Task (CMMI)
• Agile task board
• Task (Agile)
• Agile task board

16. COMPARE & CONTRAST
Process area
Scrum 2013
MSF for Agile 2013
MSF for CMMI 2013
Bug backlog management
Bug (Scrum)
• Bug (Agile)
• Triage Workbook
• Bug (CMMI)
• Triage 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
Not supported
Code Review Request
Code Review Response
Feedback Request
Feedback Response
•
•
•
•
Code Review Request
Code Review Response
Feedback Request
Feedback Response
Minimal
•
•
•
•
Issue (CMMI)
Risk (CMMI)
Review (CMMI)
Issues Workbook
Code Review Request
Code Review Response
Feedback Request
Feedback Response
Supported

17. PROCESS TEMPLATES – 3 RD PART Y
 Visual Studio Galler y
downloads
 Most FREE *
 Create Your Own with
Power Tools
*as in, ”FREE” like a puppy

18. AGENDA


What is a process template?
What process templates are available?
In the Box
 3 rd Party


Team Foundation Server 2012?
Agile Planning Tools
 Reporting


19. EVERYBODY GOT NEW TOOLS!
 “A gile” Planning Tools Work
for Any Template
 Quick Add Based on
Template, Customizable
 Real-time Repor ts Based on
Process Template

20. TASK BOARD FOR EVERYONE
 Task Board Automatically
Reflects:




WIT types
States
Meta-states
Transitions
 Supports ANY process
template

21. AGENDA


What is a process template?
What process templates are available?
In the Box
 3 rd Party


Team Foundation Server 2012?
Agile Planning Tools
 Reporting


22. REPORTING


Real-time embedded web reports, SSRS and Excel
Available Reports Based on Template
Scrum has very few reports
 Agile has more (almost same as CMMI)
 CMMI has the most


Cross Team Project Reporting is a Challenge is Using Dif ferent
Templates

23. REPORTS
Tasks
SCRUM
Monitor bug activity, reactivations, and trends. Track bugs that the
team is finding and the progress that the team is making toward
fixing them.
Monitor build activity, success, and trends. You can use build reports
to track the quality and success of your team's builds over time.
Agile
•
•
Build Success Over Time
Report
Build Summary Report
Bug Status Report
Bug Trends Report
Reactivations Report
•
•
Build Quality Indicators Report
•
Build Success Over Time
•
Report
•
Build Summary Report
•
Track project health, team burn rate, and task completion.
•
Use to review the level of effort that the team has spent on each
requirement type work items that the team is implementing. By
using this report, you can quickly determine whether any work was
recently completed on each item, what work is remaining and how
far each item has been implemented and tested.
CMMI
•
•
•
•
•
•
•
Release Burndown (Scrum)
•
Sprint Burndown (Scrum)
•
Velocity (Scrum)
•
You can review this report daily or weekly to monitor the progress of
the team during an iteration.
Determine added work. You can use the Unplanned Work report to
determine how much work the team added to an iteration after it
started.
Monitor testing activity. You can use the test reports to track the
•
team's progress toward developing test cases and to determine how
well they cover the requirement type work items.
•
Burndown and Burn Rate
Report (Agile)
Remaining Work Report
Status on All Iterations Report
Stories Overview Report
(Agile)
Stories Progress Report
(Agile)
•
•
•
•
•
•
•
•
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)
•
Test Case Readiness
Report
Test Plan Progress Report
Unplanned Work
•
Unplanned Work
•
•
Test Case Readiness Report
Test Plan Progress Report
•
•
Test Case Readiness Report
Test Plan Progress Report

24. SCRUM - RELEASE BURNDOWN
Understand how quickly your team has
delivered backlog items and track how much
work the team must still perform to complete
a product release.
Review the report to determine the progress
that your team has made in a release and to
answer the following questions:
 How much work remains in the release?
 How quickly is your team working through
the product backlog?

25. SCRUM - SPRINT BURNDOWN
Displays the following pieces of data:
 The Ideal Trend line indicates an ideal situation in
which the team burns down all of the effort that
remains at a constant rate by the end of the
sprint.
 The In Progress series shows how many hours
remain for tasks that are marked as In Progress in
a sprint.
 The To Do series shows how many hours remain
for tasks that are marked as To Do in a sprint.
Review the report to determine the progress that
your team has made in a release and answer the
following questions:
 How much work remains in the sprint?
 Is your team on track to finish all work for the
sprint?
 When will your team finish all work for the sprint?
 How much work for the sprint is in progress ?

26. SCRUM - VELOCIT Y
Based on the velocity of previous sprints that
the report illustrates, you can:
 Track how much effort your team has
reported as complete for each sprint.
 Estimate how much backlog effort your team
can handle in future sprints if your team
composition and sprint duration stay
constant.
Review the report to determine how much
progress your team has made and to answer the
following questions:
 How much effort 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?

27. AGILE - BURNDOWN
You can use this report to answer the following
questions:
 Is the team likely to finish the iteration on
time?
 Will the team complete the required work,
based on the current burn rate?
 When can the team finish the current iteration?
 How much work can the team complete in the
available time?
 How much work does each team member have?
 How fast is the team completing remaining
work?
 Is the team adding work during the iteration?
Is there scope creep?

How is the work distributed across the team?

28. AGILE – REMAINING WORK
Number of Hours vs. Number of Work Items
Review the report to determine the progress
within an iteration or over time. Specifically, you
can find answers to these questions:
 How fast is the team burning down remaining
work?
 Is work being added during the iteration? Is the
team expanding the scope of the work?
 How much progress can the team make in the
available time?
 Approximately when can the team finish the
work?
 Is too much work in progress?
 Is the flow of work being impeded or blocked?
 When will the team finish the current iteration?

29. AGILE – ITERATIONS STATUS
This report displays the following information:
 Stories Closed: number of user stories that have
been closed; derived from the current values
specified for the iteration and the state of each
user story.
 Progress (Hours) : represents the values for Original
Estimate (grey), Completed (green) and Remaining
(light blue) based on the rollup of hours that are
defined for all tasks; derived from the current
values that are specified for the iteration and the
hours for each task.
 Bugs: representation for all bugs, grouped by their
current states of Active (blue), Resolved (gold) and
Closed (green); derived from the current values that
are specified for the iteration and the state of each
bug.

30. AGILE– ITERATIONS STATUS
This is BAD!!!
Review the report to determine how many stories are
ready to release and to better understand the rate of
the team's progress. For example, you can find
answers to the following questions:
 Did the scope of work for each iteration closely
match the team capacity?
 Does the number of stories closed in each iteration
correspond to your expectations?
 Is the team resolving and closing more bugs with
successive iterations?
 How many stories can the team ship today?

31. CMMI– BURNDOWN AND BURN RATE
Burndown shows the trend of completed and
remaining work over a specified time period.
Burndown
 How fast is the team completing remaining
work?
 Is the team adding work during the iteration? Is
there scope creep?
 How much work can the team complete in the
available time?
 When can the team finish the work?
 When can the team finish the current iteration?

32. CMMI– BURNDOWN AND BURN RATE
Burn rate provides calculations of the completed
and required rate of work based on the specified
time period.
Burn Rate
 Is the team working quickly enough to finish the
remaining work on time?
Work Assignment
 How is the work distributed across the team?
 Should the team balance the remaining work
load?

33. CMMI– REMAINING WORK
Number of Hours vs. Number of Work Items
Questions That the Report Answers
 Review the report to determine the progress
within an iteration or over time. Specifically,
you can find answers to these questions:
 How fast is the team burning down remaining
work?
 Is work being added during the iteration? Is the
team expanding the scope of the work?
 How much progress can the team make in the
available time?
 Approximately when can the team finish the
work?
 Is too much work in progress?
 Is the flow of work being impeded or blocked?
 When will the team finish the current iteration?

34. RESOURCES
P r o c e s s Te m p l a t e s a n d To o l s H o m e : h t t p : / / m s d n . m i c r o s o f t . c o m / e n - u s / v s t u d i o / a a 71 87 9 5 . a s p x
P r o c e s s Te m p l a t e s O v e r v i e w : h t t p : / / m s d n . m i c r o s o f t . c o m / e n - u s / l i b r a r y / v s t u d i o / m s 4 0 07 5 2 . a s p x
T F S Po we r To o l s : h t t p : / / b l o g s . m s d n . c o m / b / b h a r r y / a r c h i v e / 2 01 3 / 0 9 / 2 2 / t f s - 2 01 3 - p o w e r - to o l s a r e - av a i l a b l e . a s p x C u s t o m i z i n g
P r o c e s s Te m p l a t e s : h t t p : / / m s d n . m i c r o s o f t . c o m / e n - u s / l i b r a r y / m s 24 37 8 2 % 2 8 v = v s . 1 1 0 % 2 9 . a s p x
Te m p l a t e C o m p a r e To o l s :
Team Project Manager Tool: http://teamprojectmanager.codeplex.com/
TFS Rangers Integration Platform Mapping Tool: http://tfsintegrationmapper.codeplex.com/releases/view/59309
Re p o r t s a n d A r t i f a c t s :
Scrum: http://msdn.microsoft.com/en -us/library/vstudio/ff731587.aspx#monitoring
Agile: http://msdn.microsoft.com/en -us/library/vstudio/dd997580.aspx
CMMI: http://msdn.microsoft.com/en -us/library/vstudio/ee332487.aspx