Our overall approach follows the global standard of best practices set forth by the Project Management Institute. We recognize that the primary value of projects goes beyond delivering on-time and on-budget. For that reason our approach takes steps to understand the expected business outcomes.
Identify Stakeholders and SME’s
Create AS IS Process Flow
Identify Pain Points
Determine In Scope Use Cases
Develop Initial Project Plan
Hold Kick-Off Meeting
Elicit Business Requirements
Create TO BE Process Flow
Document Business Requirements
Break into Design Packages
Phase Gate I
Re-estimate Project Budget and Timeline
Baseline Project Plan
Approval of Business Requirements Approval of Project Plan
Develop Functional Design
Develop Technical Design
Develop Test Strategy
Phase Gate II
Approval of Functional Design
Develop Approved Design
Document Test Cases
Perform Test Cases
Perform Bug Tracking
Develop Bug Fixes
Retest Bug Fixes
Certify Package for Release
UAT (User Acceptance Testing)
Release Code to UAT Environment
Perform Smoke Testing
Client performs User Acceptance Testing
Perform Change Management
Gather Qualified Issues into Design Packages
End to End Testing
Client performs end to end system testing
Client makes Go/No go Decision
Provato supports Go Live activity
Provato’s proven approach to software development defines the solution scope early in the project. One of our consultants will kick start your project by leading your key stakeholders through a project scoping meeting to quickly define the initial scope, current process pain points, and expected business outcomes. The Scope Document, the deliverable of this activity which defines the scope of the project, becomes the foundation necessary for keeping the project on track. The scope of the project is broken down into in-scope use cases.
Our consultants will continue to work closely with your key stakeholders through a series of Requirements Elicitation sessions, where the future state of every use case is defined through successively lower levels of analysis. Care is taken during these sessions to improve business processes by eliminating the current pain points, and designing lean processes. The Business Requirements Document (BRD) defines the solution scope, and paves the way for designing the functional aspects of the solution. It is approved by your sponsor, and serves as the road map through the later phases of the project.
The use cases defined in the BRD will be divided into Design Packages. Then, the core team will begin to iterate through the remaining phases of the project for each of these packages. Your team will approve the Functional Design (FD), including models of the screens or process flows, before they are developed.
Following the same iterative approach, the tested software will be released for User Acceptance Testing (UAT). Feedback will be reviewed for scope through our Change Management process, and then divided into Design Packages that are treated the same as the initial project requirements.
After completion of the last work package, Provato will provide support while your team performs end to end testing, and implements the new system that is tailored to meet the specific needs of the business.