TeamCompanion is a first class Team Foundation Server (TFS) client within Outlook. In addition to the standard TFS client features, TeamCompanion leverages Outlook features providing unique capabilities that lead to better collaboration and communication among project stakeholders.
TeamCompanion has rich support for Scrum. Here is the list of some of related features: Product/Sprint Backlog UI, Support for Teams, real time statistics and Burndown chart, Velocity chart, Drag-and-drop support for reordering and assignment, quick add PBI UI and many more.
Presentation is based on Aaron Bjorks “Scrum with TeamFoundation Server 2010” (http://www.slideshare.net/aaronbjork/scrum-with-tfs-2010).
Factors to Consider When Choosing Accounts Payable Services Providers.pptx
Scrum with TeamCompanion
1. Scrum
with
TeamCompanion
Ognjen Bajic
Based on
Ana Roje Ivancic Aaron Bjork: Scrum with Team Foundation Server 2010
2. Agenda
~ Scrum
~ TeamCompanion
~ Scrum with TeamCompanion
Product Backlog & Planning the Project
Sprint Backlog & Planning a Sprint
Running a Sprint
Burndown & Progress tracking
Transparency, Inspection, Adaptation
3. What is Scrum?
~ An agile, lightweight framework for Project
Management
~ Is used to manage and control software and
product development using iterative,
incremental practices
~ Wraps existing engineering practices
~ Is driven by daily and monthly feedback
loops
~ Is ideally suited for projects with rapidly
changing or highly emergent requirements
5. Agenda
~ Scrum
~ TeamCompanion
~ Scrum with TeamCompanion
Product Backlog & Planning the Project
Sprint Backlog & Planning a Sprint
Running a Sprint
Burndown & Progress tracking
Transparency, Inspection, Adaptation
6. TeamCompanion
The Best TFS client for MS Outlook
Outlook TFS
• Emails • Work Items
• Appointments • Work Item Queries
• Reminders • Reports
• Tasks • Builds
• Documents
Provides for better collaboration, efficient
Agile Project Management and increased
productivity in daily tasks.
7. Fully Featured TFS Client
~ Work Item Management
Add new/related WIs with one click
Embedded Work Item Form
~ Work Item Queries (flat/hierarchical)
~ Reports and Sharepoint Documents
~ Agile Project Management
~ Offline work and „What if” analysis
~ Clever graphical UI with Drag’n’Drop support
8. Deep integration of Outlook and TFS
~ Easy transition of data between Outlook object
and TFS artifacts
Create WI from Mail
Create Mail/Task/Meeting from WI
Send „Done” mails with one click
~ Scheduled execution of WI Queries
Outlook style notification of changed WIs
~ Show Queries and Reports in Favorites
~ Powerfull Searching, Filtering and Grouping
Full text search and search with custom expressions
eg. [Remaining work]>4
14. Agenda
~ Scrum
~ TeamCompanion
~ Scrum with TeamCompanion
Product Backlog & Planning the Project
Sprint Backlog & Planning a Sprint
Running a Sprint
Burndown & Progress tracking
Transparency, Inspection, Adaptation
15. How do you Plan the Project?
~ Product Backlog
Evolving ordered list of PBIs (Product Backlog
Items - Requirements)
Describes what users need and value
Owned by the Product Owner
Each PBI is written from the user’s perspective
As a <type of user> I want <some goal> so that
<some reason>.
16. Planning the Project
~ Done by Product Owner and Team
~ Product Backlog grooming
Backlog lists PBIs sorted by priority order
New PBIs added on end of Product Backlog
Product Owner re-prioritizes the Backlog
~ Team estimates PBIs in Story Points
~ PBIs are planned for upcoming Sprints
17. Planning the Project
Product Backlog
“As a new customer I want to
PBIs
register online so I can use
5 the services offered”
8
5
PBIs are listed on the
Priority
backlog in priority order each PBI
The team estimates
3
using story points
8
New PBIs are added to the
1 product backlog
18. Planning the Project
Product Backlog
PBIs are planned for
PBIs completion in upcoming
Sprint 3
3
sprints
3
3
Priority
Sprintproduct owner re-
The 4
4
prioritizes the backlog
4
4
20. Planning the Project with TeamCompanion
Tools and Features
~ Fully featured Product Backlog UI
Product Backlog list
Velocity Diagram
How many PBI-s were implemented in previous
sprints (measured in Story Points)?
Embedded real-time statistics
~ Actions
Quickly reorder PBIs using Drag’n’Drop
Easily add new PBIs with one click
26. Product Backlog
Each PBI is
sorted by priority
and assigned a
story point value
Drag’n’Drop support for reordering of PBIs
27. Product Backlog Save or discard changes
Edited PBI-s
shown in
italics
28. Agenda
~ Scrum
~ TeamCompanion
~ Scrum with TeamCompanion
Product Backlog & Planning the Project
Sprint Backlog & Planning a Sprint
Running a Sprint
Burndown & Progress tracking
Transparency, Inspection, Adaptation
29. What is Sprint Planning?
~ Sprint Planning meeting
~ Product Owner and Team add PBIs to Sprint
Backlog
~ Each PBI is decomposed into tasks and
estimated
~ Team commits to each PBI
If PBI can not be done, it is removed and
possibly replaced with smaller PBI
~ Team is ready ot start working
30. Planning a Sprint Based on estimates
the team commits to
each PBI
Product Backlog Iteration Backlog
PBIs PBIs Tasks (hours)
3
Commit!
3
3
The team breaks
During the sprint down each PBI into Commit!
planning meeting, the tasks
product owner and
the team add PBIs to
the sprint The team thinks
Can’t
this PBI is more
Commit!
work than they can
commit to…
31. The sprint is now
Planning a Sprint planned and the team
is ready to get
started!
Product Backlog Iteration Backlog
PBIs PBIs Tasks (hours)
3
Commit!
3
3
?
3
The larger PBI is Commit!
removed from the
sprint and the team
considers a smaller
PBI on the backlog
Commit!
The team can commit
to this smaller PBI
32. Sprint
Daily
Standup
Potentially
Shippable
Increment
Product Sprint
Backlog Backlog
•Sprint Backlog UI
•Team Support
•Capacity Planning
•D’n’D assignment of PBIs
and Tasks
• Product Backlog UI
• Velocity Diagram
Scrum with
• D’n’D ordering of PBIs TeamCompanion
33. Planning a Sprint with TeamCompanion
Tools and Features
~ Fully featured Sprint Backlog UI
Sprint Backlog list
Support for managing Teams
Capacity planning
Embedded real-time statistics
~ Actions
Quickly assign PBIs and Tasks using Drag’n’Drop
Easily decompose PBIs into Tasks with one click
37. Planning a Sprint Select a Sprint
Sprint settings
related to
Capacity
Set date range for the Sprint
Set planned
member and
team
interruptions
Adjust
capacity for
each team
member
Save changes
38. Planning a Sprint
Product Owner
uses team velocity
to help plan for
upcoming sprints
Product
Owner sets
capacity for
the sprint
Save changes
39. Planning a Sprint Product Backlog view
Analyse sum
of planned
story points
Plan top PBIs
Drag’n’Drop PBIs
for the next
on the Sprint
Sprint
40. Planning a Sprint Save changes
Velocity graph
is updated
Changed
PBI-s shown Capacity per
in italics Sprint is updated
41. Planning a Sprint Sprint Backlog view
Capacity
per team
member
PBIs in Sprint Capacity
Backlog per Sprint
42. Planning a Sprint
Each task is
estimated in
hours
Capacity
per Sprint is
Team breaks PBIs into tasks updated
43. Planning a Sprint
Drag’n’Drop
Tasks on
member
Assign tasks
to team
members Capacity per
member is
updated
46. Planning a Sprint Save changes
Work load is
now balanced
across the
team
Assign all tasks to team
members using D’n’D
47. Planning a Sprint Sprint planning is
complete!
Team is comfortable with
committing to this plan
48. Agenda
~ Scrum
~ TeamCompanion
~ Scrum with TeamCompanion
Product Backlog & Planning the Project
Sprint Backlog & Planning a Sprint
Running a Sprint
Burndown & Progress tracking
Transparency, Inspection, Adaptation
49. Running a Sprint
~ Tracking Progress
Daily Sprint meeting
Record completed work daily
How much work is completed
How much work needs still to be done
Use reports and dashboards
~ Preparation of “potentially shippable”
increment
~ Demonstration of delivered business value
~ Retrospective
50. Running a Sprint
Product Backlog Sprint Backlog
PBIs PBIs Tasks (hours)
The team starts
work on the tasks…
51. Running a Sprint
Product Backlog Sprint Backlog
PBIs PBIs Tasks (hours)
Remaining Completed
100
80
60
40
20
0
Completed work is 2/1 2/8 2/15 2/22
reported daily
53. Running a Sprint
Product Backlog Sprint Backlog
PBIs PBIs Tasks (hours)
Each PBI has been
implemented
Remaining Completed
100
80
60
40
20
0
2/1 2/8 2/15 2/22
All work for the sprint is
“done-done”
54. Running a Sprint
Product Backlog Sprint Backlog
PBIs PBIs Tasks (hours)
And the team has
developed a
“potentially
The team holds a demo
shippable”
to show the value they
increment
have delivered
55. Running a Sprint
Product Backlog Sprint Backlog
PBIs PBIs Tasks (hours)
The latest
increment is
shipped to
customers
56. Running a Sprint
Product Backlog Sprint Backlog
PBIs PBIs Tasks (hours)
PBIs and tasks are cleared
from the backlog – the team
delivered on its commitment
PBIs delivered in the last
The team holds a sprint are closed
retrospective…
What worked?
What didn’t work?
What can the team do to improve?
57. Running a Sprint
Product Backlog Sprint Backlog
User Stories PBIs Tasks (hours)
New PBIs are added
to the Product
Backlog
58. Running a Sprint
Product Backlog Sprint Backlog
PBIs PBIs Tasks (hours)
The backlog is prioritized
and ready for the team to
plan the next sprint
59. Sprint
Daily
Standup
Potentially
Shippable
Increment
Product Sprint
Backlog Backlog •Burndown Chart
•Remaining Capacity Charts
•Full-text search for Work Items
• Sprint Backlog UI
• Product Backlog UI
• Velocity Diagram
• Team Support Scrum with
• Capacity Planning
• D’n’D ordering of PBIs
• D’n’D assignment of PBIs and Tasks
TeamCompanion
60. Running a Sprint with TeamCompanion
Tools and Features
~ Integrated UI for burndown and progress
tracking
Sprint Backlog UI
Real-time Burndown chart
Real-time Remaining Capacity charts
Full-text search for Work Items
Various filtering options
~ Actions
Quickly reassign PBIs and Tasks using Drag’n’Drop
Update remaining/completed work