Just a bit of a background, I am working to manage a big legacy system that has at least 32 branches for it's sub systems.
The challenge is how to manage and not miss required change points or defect fixes to be deployed to different branches. Currently the team has a 30% chance that the deployment is missed, and I am targeting to make this close to zero as much as possible.
I use JIRA for bug tracking and the process goes as follows:
- Fixed defect/completed implementation activity is reported by a technical leader in charge to PM
- PM asks for expert judgement from technical leader on which branches is it necessary to be deployed
Based on the expert Judgement PM reviews, creates the records and updates a deployment log similar to the following.
The created records are then assigned and processed to be implemented.
Current known problems with the said process are
- Some branch deployment implementation are past the deadline when a defect is detected and gets rejected for release. This causes some fixes to have been logged in the deployment log to have inconsistencies with them, saying they are deployed but not really deployed. I am thinking of creating an additional file where these items can be tracked.
- PM and technical leader gets very busy and this task of filling up for 32 branches take 4 hours (at least) to analyze and fill up. This yields rushing analysis work by technical leaders and further potential misses. Also it implies costs to the project's budget and development timeline.
My question is at what part of the process is it best to improve on? Or what points of this process needs improvement?