Hi there,
We are working on a Desktop solution developing on Microsoft .NET (3.5) Platform. This is a product that we are developing for our company - A Manufacturing Resource Planning System. Our developing environment comprised of following tools:
- Visual Studio 2008 (Enterprise Edition) with SP1
- Team Foundation Server 2008
- SQL Server 2005
- MS Office 2007
- Mercury Quality Center (formerly TestDirector)
- Beyond Compare 3
- Greenshot
- RedGate Developer Bundle
We are now providing releases to QC (Quality Control). The release come out every weekend having fixes which they reported on Mercury Quality Center. We target defects based on their status. Our first priority is to fixed all Urgent, Very High and High status issues. On Monday, I shot an e-mail listed all the issues which have been fixed in this release. The QC department looks into the list and discuss in case if they require more updates which they found later in the testing otherwise the release gets the acceptance and they move on to this release version after they complete their testing on previous release.
From now on, we will be releasing build with new modules which will be like Purchasing, Stock Control, Accounting. I'm planning to release them after QC establish a statement on previous module that they are 'stable'.
Here, I don't have any release management mechanism. I would like to keep check on releases and like to monitor the progress in individual releases. How much error (re)produce (in Mercury QC we call it 'Reopen') in this release which were 'Closed' in previous one. With collective statistics, I would like to create something that would help me to manage things (defects updates, feature updates, etc). As a Team Lead, I would like to show my managers in weekly status e-mail something that gives them a detailed of our work.
I don't want to keep a paper that doesn't help me to see the problem? I prepare to write papers, maintain excel sheets but it should gives me back something that helps me to be productive and problem solving solutions.
I'd be more happy if there is something already featured in TFS which I can use for this purpose. Anything new would require to learn and I can't afford to learn 'cause of heavily engage in development and managing.
I don't want to make this conversation too long but I think before you suggesting me any solution you should have a picture of where I'm and what I can do or can't do.
If I cut down to a line this question will be: What are those practices which you are following before giving releases (having fixes or feature updates) to your QC department?
Please, suggest me a better practice - a checklist, release management; which you are being following and found effective in day to day planning.
Thanks.