Change Requests
Change Requests
Using an iterative approach with frequent deliveries, customers often gain new insight and want to make alterations to functionality originally specified and agreed on by both parties. By providing a framework for customers to change the scope of their project, Metova can respond quickly to the changing scope and deliver a product that is more accurate to what our customers desire.
When an alteration or addition to the scope of work is required, Metova follows a change request process. The goals of this process are to:
- Provide flexibility
- Control project scope, time and cost
- Improve communication
- Maintain accountability
Change Request Process Steps
- The customer identifies a needed change by creating an issue as a Change Request issue type within Jira
- The customer assigns the Change Request to their Metova product manager
- Request Scoping will be performed by Metova
- The Change Request will then be reassigned back to the customer for approval of the tasks and their estimates
- The customer will resolve the Change Request with a resolution type of Approved or NOT Approved.
- If Approved, the issues may now be scheduled in an iteration
Search