scrum in the enterprise with microsoft visual studio 2010 l.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Scrum in the Enterprise with Microsoft Visual Studio 2010. PowerPoint Presentation
Download Presentation
Scrum in the Enterprise with Microsoft Visual Studio 2010.

Loading in 2 Seconds...

play fullscreen
1 / 54

Scrum in the Enterprise with Microsoft Visual Studio 2010. - PowerPoint PPT Presentation


  • 226 Views
  • Uploaded on

FT09. Scrum in the Enterprise with Microsoft Visual Studio 2010. Simon Bennett Managing Consultant, EMC Consulting Certified Scrum Trainer / Practitioner. Agenda. What is Scrum? What do we mean by “Enterprise Scrum”? Applying Scrum with VS 2010 Multi Team Configuration (Demo)

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Scrum in the Enterprise with Microsoft Visual Studio 2010.' - betty_james


Download Now An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
scrum in the enterprise with microsoft visual studio 2010
FT09

Scrum in the Enterprise with Microsoft Visual Studio 2010.

Simon Bennett

Managing Consultant, EMC Consulting

Certified Scrum Trainer / Practitioner

agenda
Agenda
  • What is Scrum?
  • What do we mean by “Enterprise Scrum”?
  • Applying Scrum with VS 2010
  • Multi Team Configuration (Demo)
  • Enterprise Bug Modelling
  • Process Template anatomy
  • Team Foundation Server extensibility
what is scrum
What is Scrum?
  • Scrum is a Project Delivery Framework
  • Both Iterative & Incremental
  • Based on the Agile Manifesto
    • Working Software is the measure of progress
    • Harnesses change for competitive advantage
    • Multiple “Inspect & Adapt” points
    • Promotes close customer collaboration
scrum was designed for small teams
Scrum was designed for small teams
  • 7 +/- 2 people per team
  • Single Product Owner
  • Scrum scales easily up to about 3 teams
  • Most standard process templates can support projects of this size
  • Scrum for Team System 2.2 (TFS 2008) is the most widely used template in this market
enterprise scrum
Enterprise Scrum
  • Larger Variation than in single team Scrum
    • Need to balance consistency & adaptability
    • By supporting varied project configurations without template modifications
  • Multiple indicators:
    • More than 30 developers on a single project
    • Multiple PO’s / Work Streams / BU’s
    • Inter woven cadence
supporting enterprise scrum in 2010
Supporting Enterprise Scrum in 2010
  • Acceptance Test Driven Development
  • Hundreds of Teams, dynamically adjustable
    • Working in different cadences
    • Starting on different days
    • Or in different time zones
  • Flexible Bug Modelling
    • Integrated with Test & Lab Manager
  • All integrated into one great ALM solution
enterprise friendly deployment
Enterprise Friendly Deployment
  • Install – drops the bits
  • Deploy – pushes the template to the Team Project Collections of your choice
  • Create – your empty project
  • Configure – set up the standard template to fit the project & Team Environment
tfs 2008
TFS 2008
  • We could link WIT’s
  • But in a “flat” structure
  • Relationships were implicit
forget flatland

Forget Flatland

Visual Studio 2010

work item hierarchy example
Work Item Hierarchy Example

Product Backlog Item

Sprint Backlog Task

Implemented By

Tested By

Impeded By

Acceptance Test

Impediment

relationships are bi directional
Relationships are bi-directional

Product Backlog Item

Sprint Backlog Task

Implements

Tests

Impedes

Acceptance Test

Impediment

adding a linked work item
Adding a Linked Work Item
  • You must select the correct Link Type and Work Item Type when adding a linked item.
planning scope
Planning Scope
  • Builds on the Iteration Path
  • Allows for complex multi-team projects
  • Supported with three Work Item Types
  • Uses an Event Service to collect metrics in real time to support Release Planning
planning scope work items
Planning Scope Work Items

Release

ImplementedBy

ImplementedBy

Sprint

Implements

Team

Implements

that looks hard complex
That looks hard & complex!
  • It is. (Well complex anyway)
  • But real life enterprise projects are complex
  • Thankfully there is help from the ScrumMaster’s workbench
    • Easier to create a project now than in 2.2
  • 3.0 Projects start empty
atdd in practice
ATDD in practice

Tested By

Failed By

AcceptanceTest

ProductBacklogItem

BugReport

Tested By

AcceptanceTest

after a pbi is done bugs are prioritised by the product owner not qa
After a PBI is “Done” Bugs are prioritised by the Product Owner not QA

BacklogItem

Highest

Priority

We need these done in 30 days!

Bugs are a normal part of the planning process, and are prioritised just like PBI’s.

Bug

BacklogItem

BacklogItem

These aren’tcritical, but it

would be nice.

Bug

Bug

BacklogItem

This bug isn’thurtinganybody.

BacklogItem

Lower

Priority

Bug

the implication is
The implication is...
  • That a lot of the time, developers can’t “fix” a bug
  • In many organisations, a bug only specifies an opinion on pre-existing incorrect behaviour
  • It follows that the PO must inspect and modify all bugs to ensure that they describe not just the problem, but also the desired behaviour.
scheduling bug fixes
Scheduling Bug Fixes

Fails

Scheduled

BugReport

ProductBacklogItem

AcceptanceTest

Test for a class of desirable behaviour

Container for Scheduling + Statement of Value to the Business

Description of an instance of Negative Application Behaviour

building an incremental regression suite
Building an incremental regression suite
  • The Product Backlog Item Lifecycle

Done

Not Started

In Progress

Broken

Deprecated

in summary
In Summary
  • Enterprise Scrum Solution
  • Multiple PO / Workstream support
  • Supports Vast Numbers of teams
    • Starting on different days
    • Working to different cadences
    • All supported by standard reports
  • Support for ATDD & Regression Testing
  • “Always Accurate” Historical Backlog
agenda34
Agenda
  • Process Template anatomy
  • Implementing Link Hierarchy
  • Team Foundation Server extensibility
  • Summary
process template anatomy
Process Template Anatomy

Microsoft Visual Studio Team Foundation Server 2008

Sharepoint/WSS

Version Control

Reports

Work Item Tracking

process template anatomy36
Process Template Anatomy

Microsoft Visual Studio Team Foundation Server 2010

Sharepoint/WSS

Version Control

Reports

Work Item Tracking

Lab Management

Hierarchical Link Types

Build

Test Management

process template anatomy37
Process Template Anatomy

Microsoft Visual Studio Team Foundation Server 2010

Work Item Tracking

Hierarchical Link Types

inside the template work item tracking
Inside The Template: Work Item Tracking

TypeDefinitions

LinkTypes

Queries

implementedby xml
ImplementedBy.xml

Product Backlog Item

  • <?xmlversion="1.0" encoding="utf-8"?>
  • <LinkTypes>
  • <LinkTypeReferenceName="Scrum.ImplementedBy"
  • Topology="Tree"
  • ForwardName="Implemented By"
  • ReverseName="Implements“ />
  • </LinkTypes>

Implemented By

Sprint Backlog Task

Implements

Tree = Parent/Child relationship

implementedby xml40
ImplementedBy.xml

?

  • <?xmlversion="1.0" encoding="utf-8"?>
  • <LinkTypes>
  • <LinkTypeReferenceName="Scrum.ImplementedBy"
  • Topology="Tree"
  • ForwardName="Implemented By"
  • ReverseName="Implements“ />
  • </LinkTypes>

Implemented By

?

Implements

how to only show specific links
How to only show specific links
  • <TabLabel="Implements">
  • [...]
  • <WorkItemLinkFiltersFilterType="include">
  • <FilterLinkType="Scrum.ImplementedBy" FilterOn="reversename" />
  • </WorkItemLinkFilters>
  • <WorkItemTypeFiltersFilterType="include">
  • <FilterWorkItemType="Product Backlog Item" />
  • </WorkItemTypeFilters>
  • <ExternalLinkFiltersFilterType="excludeAll"/>
  • [...]
team foundation server extensibility
Team Foundation Server extensibility
  • TFS notifications can be Plain Text email, HTML email or a SOAP message.
  • Scrum for Team System installs an ASP.NET web service to handle the message generated when a work item is saved.
team foundation server notifications
demo

Team Foundation Server notifications

what did we cover
What did we cover?
  • Used the Alerts Editor to create a subscription
  • Set the endpoint to be a ASP.NET web service with a Notify web method
  • “Do something” with the inbound message
    • Text message when a Work Item is saved with a certain state.
    • Send a tweet through the Twitter API when your build completes.
scrum for team system calculated fields
Scrum for Team System calculated fields
  • Rules stored in customizable XML files
  • Default rules allow cover common scenarios
    • Set “parent” Product Backlog Item state to “Done” when all Acceptance Tests pass.
    • Sum the work remaining for a Product Backlog Item based on linked Sprint Backlog Items.
    • Divide two fields on the same form to calculate the Return on Investment field.
  • Modify the XML rules yourself and even write a Custom Processor. See http://consultingblogs.emc.com/crispinparker
in conclusion
In Conclusion
  • With Scrum for Team System 3.0. You can easily manage multi team Enterprise Scrum projects using Visual Studio 2010
  • Integrates with Test & Lab Manager
  • A richer experience was created by:
    • Leveraging the TFS notification mechanism
    • Customising Link Types
    • User Centric design in Team Explorer elements
references
References
  • Scrum for Team Systemwww.scrumforteamsystem.com
  • Simon’s blog consultingblogs.emc.com/simonbennett
  • Stuart’s blogstuartpreston.net/blog
  • Microsoft Visual Studio 2010 Beta 2 websitemsdn.microsoft.com/en-us/vstudio/dd582936.aspx
slide51

YOUR FEEDBACK IS IMPORTANT TO US!

Please fill out session evaluation forms online at

MicrosoftPDC.com

learn more on channel 9
Learn More On Channel 9
  • Expand your PDC experience through Channel 9
  • Explore videos, hands-on labs, sample code and demos through the new Channel 9 training courses

channel9.msdn.com/learn

Built by Developers for Developers….