Storage Informer
Storage Informer

Agile project management with Team Foundation Server (TFS)

by on May.27, 2009, under Storage

Agile project management with Team Foundation Server (TFS)

When we started our journey towards Agile SW Development, project management tool was a key challenge. We did analysis of few tools and decided TFS as the best fit, because it was easy to customize and integrates with Visual Studio which is our development tool. Also there was no additional cost for license & maintenance as we had the corporate license and support.

Our team won Intel Software Quality Award – 2009 and I realized using TFS for project management helped us tracking the metrics and taking corrective actions.

Following are the top 2 TFS work item which we have done customization and their benefits are as follows.

1. Iteration Metrics

We decided to track metrics on iteration level (1-2 weeks) which can rolls up to release level. TFS does not provide any capability for this need. So we created a customized Work Item to meet our requirement and following is how we use this work item

  • During Iteration planning, we capture the ¡§Available Business Days¡¨ and ¡§Available Resources¡¨. If you multiply, you will get the raw availability. We use this for our productivity calculation. We have provisions to capture other attributes like Team/Systematic efficiency which can be used to calculate the net availability for the iteration commitment.
  • We have added attributes like Team Temperature, Automated test count, Code Coverage etc. which we use to plan at the beginning of the iteration and compare with actual at the end of iteration. This gives us data to take further actions where actual does not meet the plan.
  • We have also added additional sections to capture retrospective notes and their action items for an iteration. It also helps us to go through the action items identified in previous iteration.

2. Scenario / Story

Though TFS has inbuilt Work Item for Scenario, it was not having all attributes what was needed for us. So we customized (Defined our story life cycle and customized the WI accordingly) to meet our need and following is theusage model.

  • Business analyst use this WI for authoring Business stories where as Developer use this for authoring technical & design stories. When the story is ready for review they change to "Ready to Play¡¨ status
  • Iteration manager review with team and update estimates (High Level / Low level), add notes in ¡§Engineering notes section, add queries in ¡§Queries¡¨ tab for business analyst to respond and finally change status to ¡§Iteration Backlog¡¨
  • Developer picks up a story which are in ¡§Iteration backlog¡¨ and changes status to ¡§Development¡¨
  • Developer completes development, unit testing and assign to QA and change status to ¡§Testing¡¨
  • QA validates and assign to Business analyst after successful testing and change status to ¡§Customer Review¡¨
  • Business analyst who works as a proxy customer, review the story and move to ¡§Done/Complete¡¨

Following are the other TFS features our team is currently using

  • Source control
  • "Bug" Work Item for Pre-Production & Post-Production issues Tracking
  • Continious Integration Build
  • Report
  • Sharepoint


:, , , , , , , , , , , ,

Leave a Reply

Powered by WP Hashcash

Looking for something?

Use the form below to search the site:

Still not finding what you're looking for? Drop a comment on a post or contact us so we can take care of it!

Visit our friends!

A few highly recommended friends...