Scrum And Tfs

50 %
50 %
Information about Scrum And Tfs
Business

Published on January 13, 2010

Author: petrellyn

Source: slideshare.net

Description

SCRUM has grown in popularity and acceptance by many companies over the world with numbers of registered SCRUM Masters reaching 51,955 (11 March 2009 - Jeff Sutherland). Although SCRUM does not stipulate what tools to use to produce the necessary artifacts, Microsoft Team Foundation System provides a number of features via TFS Explorer that facilitate capturing the artifacts of SCRUM and is a useful tool for any SCRUM Master, Team and Product Owner. This presentation will highlight the SCRUM framework and show you practical use of TFS and other tools that facilitate the ceremonies and artifacts of SCRUM.

Presented by Jamie Phillips SCRUM and TFS

Who is Jamie Phillips Senior Software Engineer with over 10 years experience in the Telecomm, e Commerce, Finance and Healthcare industries. Passionate about working with the .NET framework and related technologies (C# 3.5, WCF, Entity Framework, etc.) Natural ability to adapt to change has lead to becoming a practicing SCRUM Master and evangelist. Blog: http://devblog.petrellyn.com

Senior Software Engineer with over 10 years experience in the Telecomm, e Commerce, Finance and Healthcare industries.

Passionate about working with the .NET framework and related technologies (C# 3.5, WCF, Entity Framework, etc.)

Natural ability to adapt to change has lead to becoming a practicing SCRUM Master and evangelist.

Blog: http://devblog.petrellyn.com

Who is Picis Global provider of innovative information solutions that enable rapid and sustained delivery of clinical, financial and operational 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 View slide

Global provider of innovative information solutions that enable rapid and sustained delivery of clinical, financial and operational 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

The SCRUM framework TFS facilitates these Which contributes to these And helps them Product owner Scrum Master Team Roles Release planning Sprint planning Daily scrum meeting Sprint review Sprint retrospective Ceremonies Product backlog Sprint backlog Burndown charts Artifacts View slide

Product owner

Scrum Master

Team

Release planning

Sprint planning

Daily scrum meeting

Sprint review

Sprint retrospective

Product backlog

Sprint backlog

Burndown charts

The SCRUM Framework

Product Backlog Requirements / Defects A list of all desired work on the project (Product Backlog Item = Story) Ideally expressed such that each item has value to the users or customers of the product Prioritized by the product owner in collaboration with team. Reprioritized on an ad-hoc basis (typically done prior to Sprint Planning and does not affect current Sprint) Product Backlog

Requirements / Defects

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

Ideally expressed such that each item has value to the users or customers of the product

Prioritized by the product owner in collaboration with team.

Reprioritized on an ad-hoc basis (typically done prior to Sprint Planning and does not affect current Sprint)

Product Backlog Item (PBI) Represents a user story that has a business value. Could also represent a Defect (which implicitly has business value)

Represents a user story that has a business value.

Could also represent a Defect (which implicitly has business value)

Sprint Backlog Individuals sign up for work of their own choosing Work is never assigned by any individual Estimated work remaining is updated daily. If Product Backlog item is unclear, define an investigative story that will generate more tasks/stories in later sprints (known as a “spike”). Sprint Backlog

Individuals sign up for work of their own choosing

Work is never assigned by any individual

Estimated work remaining is updated daily.

If Product Backlog item is unclear, define an investigative story that will generate more tasks/stories in later sprints (known as a “spike”).

Sprint Backlog Item (SBI) Represents a task that a team member will perform to assist the team in completing a story. Should always be related to a Product Backlog Item (PBI); otherwise, what value is it adding to the project?

Represents a task that a team member will perform to assist the team in completing a story.

Should always be related to a Product Backlog Item (PBI); otherwise, what value is it adding to the project?

Product Owner Represents Stakeholders Define 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, as needed  Decide on release date and content Accept or reject work results

Represents Stakeholders

Define 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, as needed 

Decide on release date and content

Accept or reject work results

SCRUM Master Represents the project to management Responsible for enforcing Scrum values and practices Protects the team by making sure they do not over-commit themselves 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)

Represents the project to management

Responsible for enforcing Scrum values and practices

Protects the team by making sure they do not over-commit themselves 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)

The Team Typically 5-9 people Cross-functional (representation of different skill sets): Developers, testers, documentation, requirements analyst, etc. M embers should be full-time May be exceptions (e.g., database administrator) Teams are self-organizing A sense of ownership / responsibility exists amongst the team members Free flowing communication across all functions Membership should change only between sprints

Typically 5-9 people

Cross-functional (representation of different skill sets):

Developers, testers, documentation, requirements analyst, etc.

M embers should be full-time

May be exceptions (e.g., database administrator)

Teams are self-organizing

A sense of ownership / responsibility exists amongst the team members

Free flowing communication across all functions

Membership should change only between sprints

What is the role of a Manager in SCRUM? Creates business model that works Provides all resources that a team needs Removes impediments that the Team / Scrum Master cannot remove themselves (typically taken from the Impediments backlog) Encourages the team to move beyond mediocrity Can be seen as Invisible hand Oil in the enterprise “engine” Firefighter

Creates business model that works

Provides all resources that a team needs

Removes impediments that the Team / Scrum Master cannot remove themselves (typically taken from the Impediments backlog)

Encourages the team to move beyond mediocrity

Can be seen as

Invisible hand

Oil in the enterprise “engine”

Firefighter

Roles are not the same as Positions In SCRUM, roles are intended to serve as the definition of the interaction of particular individual(s) within the SCRUM framework. They are not intended to represent / replace the Positions defined in an organization. Theoretically a Scrum Master could be a Lead Developer or a Manager; just as a Product Owner could also be a Business Analyst. However; a Product Owner should never be a Scrum Master as it would lead to a conflict of interest for the team and the project.

In SCRUM, roles are intended to serve as the definition of the interaction of particular individual(s) within the SCRUM framework.

They are not intended to represent / replace the Positions defined in an organization.

Theoretically a Scrum Master could be a Lead Developer or a Manager; just as a Product Owner could also be a Business Analyst.

However; a Product Owner should never be a Scrum Master as it would lead to a conflict of interest for the team and the project.

Release Planning Stories are created in QC using the Requirements functionality Story description is of the format As a < role > I want < feature > so that < benefit > Conditions of acceptance contains sufficient detail for the team to create tasks to deliver story feature. Stories that cannot provide sufficient detail in the conditions of acceptance will need to be broken down in to smaller stories

Stories are created in QC using the Requirements functionality

Story description is of the format As a < role > I want < feature > so that < benefit >

Conditions of acceptance contains sufficient detail for the team to create tasks to deliver story feature.

Stories that cannot provide sufficient detail in the conditions of acceptance will need to be broken down in to smaller stories

Release Planning (cont) Sizing of stories takes place with involvement from Product Owners and the Team (or at a minimum, technical expertise from Development and Software Quality with sufficient knowledge/experience to be able to size the associated stories). Meeting minutes take note of sizing results for each story and serve as a record for decisions made on story sizing.

Sizing of stories takes place with involvement from Product Owners and the Team (or at a minimum, technical expertise from Development and Software Quality with sufficient knowledge/experience to be able to size the associated stories).

Meeting minutes take note of sizing results for each story and serve as a record for decisions made on story sizing.

Release Planning Tools Quality Center utilizing Requirements Functionality for story creation and sizing. Planning Poker (as needed) – online version available (free): http:// www.planningpoker.com

Quality Center utilizing Requirements Functionality for story creation and sizing.

Planning Poker (as needed) – online version available (free): http:// www.planningpoker.com

Sprint Planning Product Owner is present to motivate and discuss Sprint 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 entered into TFS. Tasks are created in TFS by the team using the “Done, Done” list in order to prevent missing story tasks. Tasks are created as Sprint Backlog Items and are related to a particular story.

Product Owner is present to motivate and discuss Sprint 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 entered into TFS.

Tasks are created in TFS by the team using the “Done, Done” list in order to prevent missing story tasks.

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

Sprint Planning (cont) Team estimates the tasks together, however task estimates 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 during planning. Be conservative when estimating tasks.

Team estimates the tasks together, however task estimates 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 during planning.

Be conservative when estimating tasks.

Sprint Planning (cont) Tasks for shared resources (Doc, RE) are created and estimated by the team.  Scrum Master follows up with resource at a later time. When Sprint Capacity is reached, Sprint Planning is complete. Scrum Master needs to be aware of each members capacity to be sure that no one on the team over commits to tasks in a sprint – capacity is continually updated .

Tasks for shared resources (Doc, RE) are created and estimated by the team.  Scrum Master follows up with resource at a later time.

When Sprint Capacity is reached, Sprint Planning is complete.

Scrum Master needs to be aware of each members capacity to be sure that no one on the team over commits to tasks in a sprint – capacity is continually updated .

Sprint Planning Tools Quality Center for both Stories and Defects Team Foundation System for creation of Product Backlog items (Stories) and Sprint Backlog Items (Tasks) Excel for team capacity

Quality Center for both Stories and Defects

Team Foundation System for creation of Product Backlog items (Stories) and Sprint Backlog Items (Tasks)

Excel for team capacity

Example of Sprint Planning “In Release Defects” High priority “In Release” Defects are “brought in” to TFS from Bug reporting system , representing the team’s commitment to fixing the defect.

High priority “In Release” Defects are “brought in” to TFS from Bug reporting system , representing the team’s commitment to fixing the defect.

Example of Sprint Planning Feature Story User Stories are “brought in” to TFS from Requirements repository , representing the team’s commitment to producing a functional solution to the Story.

User Stories are “brought in” to TFS from Requirements repository , representing the team’s commitment to producing a functional solution to the Story.

Daily SCRUM (Stand-up) SCRUM Master discusses current status of Sprint Remote team members participate via phone and Web-Ex.  Typically they speak first. Electronic task board is utilized for the display of tasks, team members point to their tasks Other team members can, and are encouraged to, facilitate meetings (Sprint Planning, Daily SCRUM) No Laptops (except for facilitator)

SCRUM Master discusses current status of Sprint

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

Electronic task board is utilized for the display of tasks, team members point to their tasks

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

No Laptops (except for facilitator)

Daily SCRUM (Stand-up) In-depth discussions must be deferred to another time, time is agreed on. Each team members estimated work remaining (statistics) is reviewed to determine if action is needed The team decides whether a new build should be taken Product Owner is involved, comes to the Daily SCRUM however is not directly part of the Daily SCRUM

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

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

The team decides whether a new build should be taken

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

Daily Standup Tools Team Foundation System for Sprint Burndown and Product Burndown Charts. Conchango TaskBoard for identifying tasks associated with each team member. Excel spreadsheet showing remaining hours (using custom Excel Add-In)

Team Foundation System for Sprint Burndown and Product Burndown Charts.

Conchango TaskBoard for identifying tasks associated with each team member.

Excel spreadsheet showing remaining hours (using custom Excel Add-In)

Example of Daily SCRUM Team’s progress through the Sprint Backlog is viewed and issues are highlighted.

Team’s progress through the Sprint Backlog is viewed and issues are highlighted.

The Sprint Review Team presents what it accomplished during the sprint to the Product Owner and Stakeholders Typically takes the form of a demo of new features or underlying architecture Informal Whole team participates

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

Typically takes the form of a demo of new features or underlying architecture

Informal

Whole team participates

The Sprint Retrospective Typically 30-60 minutes Done after every sprint Whole team participates Scrum Master Product owner Team Team discusses: What we did right? What we did wrong? How can we improve? (Select a few items to correct – do not try to commit to all)

Typically 30-60 minutes

Done after every sprint

Whole team participates

Scrum Master

Product owner

Team

Team discusses:

What we did right?

What we did wrong?

How can we improve? (Select a few items to correct – do not try to commit to all)

Sprint Retrospective Tools Team Foundation System for Sprint Reports, Sprint Burndown Charts and Sprint Retrospective Work Item.

Team Foundation System for Sprint Reports, Sprint Burndown Charts and Sprint Retrospective Work Item.

The TFS Process Template Process template is an integral part of Team Foundation Server

Process template is an integral part of Team Foundation Server

Team System Process Templates PBI and SBI are TFS Work Items with a range of fields that can be used for reporting and record keeping. Linking between Work Items is the strength of TFS – a PBI can be linked to a SBI, which can be linked to a number of ChangeSets (each check-in creates a ChangeSet)

PBI and SBI are TFS Work Items with a range of fields that can be used for reporting and record keeping.

Linking between Work Items is the strength of TFS – a PBI can be linked to a SBI, which can be linked to a number of ChangeSets (each check-in creates a ChangeSet)

Working with a Process Template TFS 2008 comes with two pre-configured Process Templates: Microsoft Solutions Framework (MSF) for Agile Software Development Microsoft Solutions Framework (MSF) for CMMI Process Improvement. Templates can be loaded in the Process Editor of Visual 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.

TFS 2008 comes with two pre-configured Process Templates:

Microsoft Solutions Framework (MSF) for Agile Software Development

Microsoft Solutions Framework (MSF) for CMMI Process Improvement.

Templates can be loaded in the Process Editor of Visual 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.

Example of working with Process Template Changes can be made to a Process Template or to an individual Work Item definition.

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

Questions and Answers

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 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

Add a comment

Related presentations

Boat chandlery

Boat chandlery

October 26, 2014

http://ecommerce-for-business.com/shackles-boats-theboatonlinestore/ We offer a ...

http://vendere-su-internet.com/shackles-for-boats-from-theboatonlinestore/ Moori...

Silver bar!

Silver bar!

October 21, 2014

Pretty similar to gold bars are these silver slabs. Silver is considered as the mo...

Gold coin prices!

Gold coin prices!

October 21, 2014

If you are an investor of gold bars and coins, one of the major things that you ou...

CyberSecurity's social media stats for one week as of Oct 21st 2014

CyberSecurity's social media stats for one week as of Oct 28th 2014

Related pages

Scrum process | Team Services & TFS - Visual Studio

Scrum process objects used to plan and track work, monitor progress, and trends when connecting to Visual Studio Team Services (VSTS) or Team Foundation Server
Read more

Agile Project Management using TFS 2012 - msdn.microsoft.com

Issues and downloads 2013 March 2013 Team Foundation Server - Agile Project Management using TFS 2012. March 2013. Volume 28 Number 03. ... specifically Scrum.
Read more

Sprint planning | Team Services & TFS - Visual Studio

Work with Scrum methods to plan a sprint or iteration in Visual Studio Team Services (VSTS) or the web portal for Team Foundation Server (TFS)
Read more

TFS as perfect tool for Scrum (Part 1) – Introduction in ...

7 Responses to “TFS as perfect tool for Scrum (Part 1) – Introduction in Scrum and TFS”
Read more

Microsoft Visual Studio Scrum 1.0 extension

Microsoft Visual Studio Scrum 1.0 Free A new Team Foundation Server process template for Scrum teams. ... Import Scrum Project back into TFS 4.
Read more

Scrum – Wikipedia

Scrum ist ein Vorgehensmodell des Projekt-und Produktmanagements und ist insbesondere ein Vorgehensmodell zur agilen Softwareentwicklung. Scrum wurde ...
Read more

SDX AG - Agil mit Scrum und TFS

Unsere bevorzugte Vorgehensweise im Projekt ist agil mit Scrum und TFS. Selbstverständlich beherrschen unsere eXperts aber auch sowohl andere Projekt ...
Read more

TFS 2013 Prozess Templates im Vergleich | Karsten Kempe ...

Visual Studio Scrum 2013 vs. MSF Agile 2013. Jedes TFS Team Projekt basiert auf einem Prozess Template, das die einzelnen Artefakte und Workflows für das ...
Read more

Scrum.org | The home of Scrum > Home

Scrum.org online assessments are tools to help you examine, enhance and improve your knowledge of Scrum. Those passing the Professional Scrum assessments ...
Read more

Scrum-Prozessvorlage

Durch die Verwendung der in der Scrum-Prozessvorlage enthaltenen Arbeitsaufgabentypen (WIT), Berichte und Dashboards können Teams Projekte ...
Read more