Scrum and Tfs

8/3/2019 Scrum and Tfs

1/36


2/36

Picis, Inc. All rights reserved.October 2009 SCRUM and TFS

Who is Jamie Phillips

Senior Software Engineer with over 10 yearsexperience in the Telecomm, e Commerce, Financeand Healthcare industries.

Passionate about working with the .NET framework

and related technologies (C# 3.5, WCF, EntityFramework, etc.)

Natural ability to adapt to change has lead to

becoming a practicing SCRUM Master andevangelist.

Blog: http://devblog.petrellyn.com


3/36


Who is Picis

Global provider of innovative information solutions thatenable rapid and sustained delivery of clinical, financial andoperational results in the acute care areas of the hospital the emergency department (ED), operating rooms (ORs),post-anesthesia care units (PACUs) and intensive care units(ICUs).

Locations include Wakefield, MA

Rosemont, IL

London, United Kingdom

Barcelona, Spain

Website: http://www.picis.com


4/36


The SCRUM framework

Product ownerScrum MasterTeam

Roles

Release planning

Sprint planningDaily scrum meetingSprint reviewSprint retrospective

Ceremonies

Product backlogSprint backlogBurndown charts

Artifacts

TFS facilitatesthese

Which contributesto these

And helpsthem


5/36


The SCRUM Framework


6/36


Product Backlog

Requirements / Defects

A list of all desired work onthe project(Product Backlog Item = Story)

Ideally expressed such that

each item has value to theusers or customers of theproduct

Prioritized by the productowner in collaboration with

team.

Reprioritized on an ad-hocbasis (typically done prior toSprint Planning and doesnot affect current Sprint)

Product BacklogProduct Backlog


7/36


Product Backlog Item (PBI)

Represents a userstory that has abusiness value.

Could also represent

a Defect (whichimplicitly hasbusiness value)


8/36


Sprint Backlog

Individuals sign up for work

of their own choosingWork is never assigned byany individual

Estimated work remaining is

updated daily.

If Product Backlog item isunclear, define aninvestigative story that will

generate more tasks/storiesin later sprints (known as a

spike).Sprint BacklogSprint Backlog


9/36


Sprint Backlog Item (SBI)

Represents a taskthat a teammember willperform to assistthe team incompleting a story.

Should always berelated to a ProductBacklog Item (PBI);otherwise, whatvalue is it adding tothe project?


10/36


Product Owner

Represents StakeholdersDefine the features of the product

Be responsible for the value added to the product

Prioritize features according to market value

Adjust features and priority every iteration, asneeded

Decide on release date and content

Accept or reject work results


11/36


SCRUM Master

Represents the project to management

Responsible for enforcing Scrum values and practices

Protects the team by making sure they do not over-committhemselves to what they can achieve during a sprint

Coaches rather than command and control

Acts as a facilitator to remove impediments

Ensure that the team is fully functional and productive

Enable close cooperation across all roles and functions

Shield the team from external interferences (interruptions)


12/36


The Team

Typically 5-9 people

Cross-functional (representation of different skill sets):

Developers, testers, documentation, requirements analyst,etc.

Members should be full-time May be exceptions (e.g., database administrator)

Teams are self-organizing

A sense of ownership / responsibility exists amongst theteam members

Free flowing communication across all functions

Membership should change only between sprints


13/36


14/36


15/36


Release Planning

Stories are created in QC using the Requirementsfunctionality

Story description is of the formatAs a I want so that

Conditions of acceptance contains sufficient detailfor the team to create tasks to deliver storyfeature.

Stories that cannot provide sufficient detail in theconditions of acceptance will need to be brokendown in to smaller stories


16/36


Release Planning (cont)

Sizing of stories takes place with involvement fromProduct Owners and the Team (or at a minimum,technical expertise from Development andSoftware Quality with sufficient

knowledge/experience to be able to size theassociated stories).

Meeting minutes take note of sizing results foreach story and serve as a record for decisions

made on story sizing.


17/36


Release Planning Tools

Quality Center utilizing

Requirements Functionalityfor story creation andsizing.

Planning Poker (as needed) online version available

(free):http://www.planningpoker.com


18/36


Sprint Planning

Product Owner is present to motivate and discussSprint goals at the beginning of the meeting.

Team capacity is taken.

High priority Defects take precedence over new

functionality.Stories or Defects are taken from QC and enteredinto TFS.

Tasks are created in TFS by the team using the

Done, Done list in order to prevent missing storytasks.

Tasks are created as Sprint Backlog Items and arerelated to a particular story.


19/36


Sprint Planning (cont)

Team estimates the tasks together, however taskestimates may be changed by the task assignee.

Capacity is continually updated.

Items are pulled from backlog in order of

importance/priority.

Other team members can, and are encouraged to,facilitate meetings (Sprint Planning, Daily SCRUM).

Product Owner is available for questions duringplanning.

Be conservative when estimating tasks.


20/36


21/36


Sprint Planning Tools

Quality Center for both

Stories and Defects

Team Foundation System

for creation of ProductBacklog items (Stories) andSprint Backlog Items(Tasks)

Excel for team capacity


22/36


Example of Sprint PlanningIn Release Defects

High priority In Release Defects are brought into TFS from Bug reporting system, representingthe teams commitment to fixing the defect.


23/36


24/36


Daily SCRUM (Stand-up)

SCRUM Master discusses current status of Sprint

Remote team members participate via phone andWeb-Ex. Typically they speak first.

Electronic task board is utilized for the display of

tasks, team members point to their tasksOther team members can, and are encouraged to,facilitate meetings (Sprint Planning, Daily SCRUM)

No Laptops (except for facilitator)


25/36


Daily SCRUM (Stand-up)

In-depth discussions must be deferred to anothertime, time is agreed on.

Each team members estimated work remaining(statistics) is reviewed to determine if action is

neededThe team decides whether a new build should betaken

Product Owner is involved, comes to the DailySCRUM however is not directly part of the DailySCRUM


26/36


Daily Standup Tools


for Sprint Burndown andProduct Burndown Charts.

Conchango TaskBoard foridentifying tasks associatedwith each team member.

Excel spreadsheet showingremaining hours (usingcustom Excel Add-In)


27/36


Example of Daily SCRUM

Teams progress through the Sprint Backlog isviewed and issues are highlighted.


28/36


The Sprint Review

Team presents what it accomplished during thesprint to the Product Owner and Stakeholders

Typically takes the form of a demo of new featuresor underlying architecture

Informal

Whole team participates


29/36


30/36


Sprint Retrospective Tools


for Sprint Reports, SprintBurndown Charts and SprintRetrospective Work Item.


31/36


The TFS Process Template

Process template is an integral part of TeamFoundation Server


32/36


Team System Process Templates

PBI and SBI are TFS Work Items with a range offields that can be used for reporting and recordkeeping.

Linking between Work Items is the strength of TFS

a PBI can be linked to a SBI, which can be linkedto a number of ChangeSets (each check-in createsa ChangeSet)


33/36


Working with a Process Template

TFS 2008 comes with two pre-configured ProcessTemplates:

Microsoft Solutions Framework (MSF) for Agile SoftwareDevelopment

Microsoft Solutions Framework (MSF) for CMMI ProcessImprovement.

Templates can be loaded in the Process Editor ofVisual Studio (Team Foundation Power Tools).

Add / Remove fields in the Work Item of choice. Upload the template to TFS server (for new projects)

Inject the changes in to an existing project.


34/36


Example of working with Process Template

Changes can be made to a Process Template or toan individual Work Item definition.


35/36


Questions and Answers


36/36


Resources

SCRUM for Team System & Task Board

(Conchango):http://scrumforteamsystem.com/en/default.aspx

Team Foundation Power Tools (Microsoft):

http://msdn.microsoft.com/en-us/teamsystem/bb980963.aspx

How Do I? Videos for Team System (Microsoft):http://msdn.microsoft.com/en-

us/teamsystem/bb507749.aspx

Scrum and Tfs

Documents

Transcript of Scrum and Tfs