General Workflow of Issue in Project Management (Tool)

Here we are giving a general workflow for a support/maintenance/development project. It is quite elaborative process considering the scenario, when a product is in production and team is working on support/maintenance and for new development also. Of course it does not suit to everybody requirement, however it can be amended to suit the requirements.

• New Issue as a Feature or Enhancement
• Users will initiate the new requirements or defects for existing functionality in the system
• Alternatively Business Analysis team can log this on behalf of users, till user get familiar with the system.
• Business Analysis Team will also generate new requirements based on various requests from the users and log these in the system with the details. 
• BA team will discuss the requirements, put all of their views in the system
• Once requirements are freeze, the status will be changed to Finalized and the issue will be assigned to Development Team manager
• New Issue as Defect
• End user or UAT team can log any defect they found in the system with all the details, set it status to Finalized and can assign it to Development Team Manager.
• Development Manager will review the new assignment.
• She may come back to end user or Business Team for more clarifications
• She will set the status as Analysis Scheduled if it is a requirement or to Implementation Scheduled if it is a bug and schedule it for the team as per the discussed priorities in roadmap
• The issue will be assigned to any team member
• Developer will pick the issue as per the schedule and update the status as In Analysis
• She may assign this issue to Business team or users for more details
• She will put all her understanding for the requirement in system to avoid any gap
• Once she is done, she will update the status as Analyzed and assign it to concerned Business Analyst for Confirmation
• Business Analyst will review the understanding and will update its status as Confirmed, and assigned it to Development Manager
• Development Manager will schedule the activity with developer as per priorities and update the status as Implementation Scheduled
• Developer picks the issues as per the schedule and updates their status with their progress as in Progress. Once the issue is fixed, the status will be marked as Resolved.
• Development Quality team (developers currently) will test the solution and update the status as QA Approved.
• UAT team will pick the issues in QA Approved state and perform their testing on these.
• If there is any issue, defect can be logged and issues can be rejected with the status as Reopened
• If everything is fine, issue can be approved as QA Approved
• Now with the next release to production, this issue will be deployed to live server and the status will be updated by the concerned authority (Project Coordinator/Owner) as Deployed.
• Later if end user or UAT team found any issue, the process can be started again from first point.

This is just a sample process flow, however can be modified to fit to any requirement.

People who read this post also read :