Embed Size (px)
DESCRIPTION
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).
Citation preview
Scrum with
TeamCompanion
Ognjen BajicAna Roje Ivancic
Based on Aaron Bjork: Scrum with Team Foundation Server 2010
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
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
Product Backlog
Sprint Backlog
Daily Standup
Sprint
Potentially Shippable Increment
TRANSPARENCY
INSPECTION
ADAPTATION
Scrum
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
TFS• Work Items• Work Item Queries• Reports• Builds• Documents
Outlook• Emails• Appointments• Reminders• Tasks
TeamCompanion
The Best TFS client for MS Outlook
Provides for better collaboration, efficient Agile Project Management and
increased productivity in daily tasks.
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
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
Demo
Demo
Working with TeamCompanion
TeamCompanion’s Look and Feel
Create Work Item from Mail
Sceduled Work Item Queries
Filtering and Grouping
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
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>.
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
Planning the Project
“As a new customer I want to register online so I can use
the services offered”
PBIs are listed on the backlog in priority order
New PBIs are added to the product backlog
The team estimates each PBI using story points
5
8
3
5
8
1
Prio
rity
Product Backlog
PBIs
Product Backlog
PBIs
Planning the Project
3
3
3
4
4
4
Sprint 3
The product owner re-prioritizes the backlog
Sprint 4
PBIs are planned for completion in upcoming
sprints
Prio
rity
Product Backlog
Sprint Backlog
Daily Standup
Sprint
Potentially Shippable Increment
•Product Backlog UI•Velocity Diagram•D’n’D ordering of PBIs
Scrum with TeamCompanion
Planning the Project with TeamCompanionTools 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
Demo
Demo
Planning the Project with TeamCompanion
Product Backlog
PM node
in Outlook tree
Product Backlog view
Product Backlog
Product Backlog
Velocity chart
Capacity per Sprint
PBIs estimated in Story Points
Quickly add new
PBIs
Product BacklogNew PBIs
created by Product Owner
New PBIs added on top with negative
ID
Save change
s
Product Backlog
New PBIs created
from Mails
Product Backlog
Drag’n’Drop support for reordering of PBIs
Each PBI is sorted by
priority and assigned a story point
value
Product Backlog
Edited PBI-s shown in
italics
Save or discard changes
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
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
Product Backlog
PBIs
Planning a Sprint
PBIs Tasks (hours)
Iteration Backlog
Commit!
Commit!3
3
3
Can’t Commit!
The team breaks down each PBI into tasks
The team thinks this PBI is more work than they can commit to…
Based on estimates the team commits to each PBI
During the sprint planning meeting, the product owner and the team add PBIs to the sprint
Product Backlog
PBIs PBIs Tasks (hours)
Iteration Backlog
Planning a Sprint
Tasks (hours)
3
3
3
3
Commit!
The larger PBI is removed from the sprint and the team considers a smaller PBI on the backlog
?Commit!
Commit!
The team can commit to this smaller PBI
The sprint is now planned and the team is ready to get started!
Product Backlog
Sprint Backlog
Daily Standup
Sprint
Potentially Shippable Increment
Scrum with TeamCompanion
•Sprint Backlog UI•Team Support•Capacity Planning•D’n’D assignment of PBIs and Tasks
• Product Backlog UI• Velocity Diagram• D’n’D ordering of PBIs
Planning a Sprint with TeamCompanionTools 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
Demo
Demo
Planning a Sprint with TeamCompanion
Sprint Backlog Select a Sprint
Sprint Backlo
g
Capacity per Team
Member
Capacity per Sprint
Team Settings
Manage Team Settings
Planning a Sprint
Set date range for the Sprint
Select a SprintSprint
settings related to Capacity
Set planned member and team interruptio
ns
Adjust capacity for each
team memberSave
changes
Planning a Sprint
Product Owner uses team
velocity to help plan for
upcoming sprints
Product Owner sets
capacity for the sprintSave
changes
Planning a Sprint
Plan top PBIs for the next Sprint
Drag’n’Drop PBIs on the
Sprint
Product Backlog view
Analyse sum of
planned story points
Planning a Sprint
Velocity graph is updated
Save changes
Changed PBI-s
shown in italics
Capacity per Sprint is updated
Planning a Sprint Sprint Backlog viewCapacit
y per team
member
PBIs in Sprint Backlog
Capacity per Sprint
Planning a Sprint
Team breaks PBIs into tasks
Each task is
estimated in hours
Capacity per Sprint is updated
Planning a Sprint
Assign tasks to
team members
Capacity per
member is updated
Drag’n’Drop Tasks on member
Planning a Sprint One team member has
too much work
assigned
Planning a Sprint Reassing some task to other team
member
Planning a Sprint
Assign all tasks to team members using
D’n’D
Save changes
Work load is now
balanced across the
team
Planning a Sprint
Team is comfortable with committing to this
plan
Sprint planning is complete!
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
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
Product Backlog
PBIs PBIs Tasks (hours)
Sprint Backlog
The team starts work on the tasks…
Running a Sprint
Product Backlog
PBIs PBIs Tasks (hours)
Sprint Backlog
Running a Sprint
Completed work is reported daily
2/1 2/4 2/72/1
02/1
32/1
62/1
92/2
22/2
52/2
8
0
20
40
60
80
100
Remaining Completed
Product Backlog
PBIs PBIs Tasks (hours)
Sprint Backlog
Running a Sprint
2/1 2/4 2/72/1
02/1
32/1
62/1
92/2
22/2
52/2
8
0
20
40
60
80
100
Remaining Completed
Each PBI has been implemented
All work for the sprint is “done-done”
Product Backlog
PBIs PBIs Tasks (hours)
Sprint Backlog
Running a Sprint
2/1 2/4 2/72/1
02/1
32/1
62/1
92/2
22/2
52/2
8
0
20
40
60
80
100
Remaining Completed
Product Backlog
PBIs PBIs Tasks (hours)
Sprint Backlog
Running a Sprint
The team holds a demo to show the value they have delivered
And the team has developed a “potentially shippable” increment
Running a Sprint
The latest increment is shipped to customers
Product Backlog
PBIs PBIs Tasks (hours)
Sprint Backlog
The team holds a retrospective…
PBIs and tasks are cleared from the backlog – the team delivered on its commitment
Product Backlog
PBIs PBIs Tasks (hours)
Sprint Backlog
What worked? What didn’t work? What can the team do to improve?
Running a Sprint
PBIs delivered in the last sprint are closed
New PBIs are added to the Product Backlog
Product Backlog
User Stories PBIs Tasks (hours)
Sprint Backlog
Running a Sprint
The backlog is prioritized and ready for the team to plan the next sprint
Product Backlog
PBIs PBIs Tasks (hours)
Sprint Backlog
Running a Sprint
Product Backlog
Sprint Backlog
Daily Standup
Sprint
Potentially Shippable Increment
• Product Backlog UI• Velocity Diagram• D’n’D ordering of PBIs
• Sprint Backlog UI• Team Support• Capacity Planning• D’n’D assignment of PBIs and Tasks
Scrum with TeamCompanion
•Burndown Chart•Remaining Capacity Charts•Full-text search for Work Items
Running a Sprint with TeamCompanionTools 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
Demo
Demo
Running a Sprint with TeamCompanion
Running a Sprint Burndown chart
refreshes in real time
Remaining capacity per team
member
Running a Sprint Burndown chart tracks remaining
and completed
work
Work is done
Remaining capacity is refreshed
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
Product Backlog
Sprint Backlog
Daily Standup
Sprint
Potentially Shippable Increment
TRANSPARENCY• Scheduled work item queries• Highlighted changes• Easy “Done” email• “One Click” Reports• Work Item Hierarchies• Work item Reminders
INSPECTION• Burndown Chart• Remaining Capacity Charts• Full-text search for Work
Items
ADAPTATION• Rich Work Item Management features• Email-Work Item Bridge• Offline Support and “What-If” Analysis
• Send Work Item Query as Email
Scrum with TeamCompanion
• Product Backlog UI• Velocity Diagram• D’n’D ordering of PBIs
• Sprint Backlog UI• Team Support• Capacity Planning• D’n’D assignment of PBIs and Tasks
![Comparing Communication Effort within the Scrum, Scrum with Kanban… · three agile processes (XP, Scrum, Scrum with Kanban) and in an unstructured process. [Method]: We designed](https://img.dokumen.tips/doc/110x75/60421a0d8961701f3d24c0f6/comparing-communication-eiort-within-the-scrum-scrum-with-three-agile-processes.jpg)
