Menu
How significant are the differences between Visual Studio Scrum 1.0 & MSF for Agile Software Development v5.0 process templates?
Has anyone used one over the other?
We are currently using external tools (TRAC) for implementing Scrum in our development process, since MS came up with additional process guidance in TFS2010, these 2 things confuse me to the core!
Unsure, which one to adopt!
354
MSF for Agile Software Development is a scenario-driven, context-based, agile software development process that utilizes many of the ideas embodied in Team System. Version 4.1 provides new guidance for the Database Professionals to use Visual Studio Team Edition for Database Professionals.
Choose a Basic, Agile, Scrum, and CMMI process Basic is the most lightweight and is in a selective Preview. Scrum is the next most lightweight. Agile supports many Agile method terms, and CMMI, which stands for Capability Maturity Model Integration, provides the most support for formal processes and change management.
The framework was originally used for software development and a lot of the resources you will find online will speak to the use of it in software development. But it is not exclusively for software development.
Jira. Atlassian's Jira is a popular tool used in agile software development and a prevalent project management program. The agile software development tool, Jira, allows you to plan, track, and manage your agile as well as your software development projects.
You're not alone! We have used both, mistakenly starting with the MSF Agile 5.0 template. If you are using Scrum specifically, I would use the Scrum 1.0 template. The Scrum 1.0 template was created with Ken Schwaber, one of the founders of Scrum.
The MSF Agile 5.0 Template contains workbooks which allow a lot of control over reporting data using excel. But, there's many more disadvantages. It doesn't have a release burndown report. In order to produce a usable sprint burndown, you need to record actuals in your tasks. The product backlog is hard to keep groomed. The user story is the only backlog item, so tracking engineering spikes or non functional requirements are awkward.
The Sprint 1.0 uses a "Sprint" workitem type which makes velocity and burndowns a snap.
So, as far as tools go, it's pretty good.
73
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
