Friday, February 18, 2011

Pilot Projects Process

We recently rolled out Team Foundation Server Work Item Tracking at work to a pilot project. During the discussions we were asked what did we want from pilot project and this made me think about how pilot projects are created and what are the expectations.
To start with there has to always be a business statement or hypothesis. So here for TFS it was
  1. There will be more direct visibility for code change due to various work items related to the project.
  2. We will be eliminating various different tracking systems (Clear quest, SR System, worksheets, Quality Center Defect module, etc) and will save time from having to do duplicate entries.
One of our biggest goal was to consolidate different tracking systems. We had more than 5 tools and each project also had their own little system like worksheet or share point issues log. We wanted to make sure our tool would fit all these needs.

We then put a plan together for this project to make sure we had a time line and also set expectations for the pilot team.
  1. Project X will start using this for TFS work item to track bugs, change requests and tasks.
  2. The pilot will last 4 weeks after which a decision will be made on the roll out process for other projects within the organization.
  3. Support will be provided during these 4 weeks for questions regarding process, tool, and technology.
  4. Feedback will be gathered via emails, surveys and interviews.

We then had to tell the team on how the feedback will be gathered.
Feedback will be gathered during these 4 weeks around the following areas
  1. Training
  2. User guide and documentation
  3. Use of tool
  4. Technical adaptability
  5. Advantages and disadvantages
  6. Gaps in process within the tool
 Our final section for the plan was capturing and reporting findings.
  1. We will validate our hypothesis and present our reports to management
  2. The data gathered during the pilot will be presented at the end of 4 weeks with our findings
  3. If changes are proposed to workflow or tool, they will be presented to the steering committee to get approval for appropriate changes.
 So now we are busy gathering the feedback and data for reporting on our pilot project status.

Thursday, February 3, 2011

Updates and TFS WIT - Pilot Project

My projects at work have been keeping me away from blogging. This project that I was helping with during the month of Jan is finally wrapped up and I have caught up with my other project work that were on the back burner.
The thing that I am most excited about right now is the implementation and roll out of TFS Visual Studio Work Item Tracking (WIT). Yes we are going to pilot our new tracking system. Our goal with TFS is that it will eventually be a one stop show for all our software development activities (code, builds, work items, requirements, test cases).
Right now we are only moving our work item tracking (defects and change requests) to this system. We already have our code in TFS. Eventually we will be using it for requirements and test management. We are not there yet but moving WIT is like being one step closer.

This project is special to me because this has a lot of "firsts" for me. My first project
  1. I am leading the documentation process. I have a great team who is helping me put all the pieces together.
  2. We are doing a pilot for a process roll out. I will get a chance to learn pilot project processes including but not limited to gathering feedback, training and supporting users, gathering metrics, etc.
  3. I will be training teams outside of our core business unit. Its a great opportunity for me to learn about our other business units and their current/future processes.
I cant wait for the first pilot project to kick off. I will be back with more on pilot project implementation and process.