Welcome to EMC Consulting Blogs

It’s always been possible to descope work in the Scrum for Team System template. But the method employed in Version 2.2 whilst functional, was quite fiddly, overly manual and not very “Scrummy”. When building 3.0 we took the opportunity to revamp the way in which it worked and better utilise the power of the Event Service (something you can see ...

The new bug model in Scrum for Team System 3.0 might look obvious at first, but it's taken a long while getting to where it is. Before I start delving into how the new bug model works, it's worth taking some time to describe what came before it. Almost by coincidence, each of the three major versions of Scrum for Team System have had a different ...

There has been some small amount of confusion around the Scrum for Team System version numbers, especially with the popularity of the 2010 TFS Beta.   This short post should help clarify things.   Version Latest Release TFS version Next version Expected 1.x 1.2 ...

To support the release of Beta 1 of Scrum for Team System 3.0 for 2010, this is the first in a series of blog posts that will help you prepare for the release of the template and better plan your adoption strategy. Scrum for Team System 3.0 (for TFS 2010) brings with it many changes, many of which work together to produce what I believe is our ...

Scrum for Team System version 2.2 was recently released. The most significant new project management report is the Velocity Report.   The velocity report tracks the historical "burn rate" for a team in such a manner to allow for truly accurate release planning. Throughout this post I'll use the term "Story Points" as ...

Recently I was sent an email asking me for some advice on using TFS with the scrum for team systems plug-in for managing testing tasks and defect tracking on an agile project. I thought the answers might be useful to others, so I have posted them here:Basically I want to use VSTS / TFS (with the Conchango template) to manage functional testing as ...