I personally prefer a more fundamental implementation of Scrum compared to MSF, and I am fully aware that this is a personal preference. However, we are already using Scrum as a de-facto methodology and using MSF templates in TFS.
At the moment, we use “Iterations” instead of “Sprints” and the iterations have no start and end date and therefore cannot calculate burn-down charts as well as when using “Sprints” in the TFS template.
New burn-down charts:
I also like the ability to add retrospectives directly to the sprint items.
On the list of other improvements:
- Ability to track impediments. Works well when the scrum master is located away from the entire delivery team.
- Full integration with test cases as with MSF (compared to the Scrum template in 2007)
- Better backlog priority organization
Overview
Quoted from http://blogs.msdn.com/b/somasegar/archive/2010/07/20/visual-studio-scrum-1-0.aspx
“Yesterday we announced the release of Microsoft Visual Studio Scrum 1.0, a new process template for Team Foundation Server 2010. The template can be downloaded from the Visual Studio Gallery or through the Visual Studio Extension Manager. This new template is the first new process template introduced by Microsoft since the MSF Agile and MSF CMMI templates first shipped with Team Foundation Server 2005.”
Installation
For a guide on template deployment, see Inside TFS: Installing the Visual Studio Scrum 1.0 Process Template.
0 comments:
Post a Comment
Feel free to add your comment to this post. All comments are moderated and may not appear immediately within the page.