Baseline7's methodology to deliver business-critical software solutions consists of 8 steps which are clustered in 3 phases.
Phase 1 "Start": Prepare, Initiate, Plan
Phase 2 "Act": Design, Execute, Train
Phase 3 "Finish": Handoff, Live
The basis for a successful delivery is the first phase and in particular the Preparation step. This is where the core of the "Value-based" project management approach is defined. Even if we follow our Customer's processes and designs, Baseline7 will include many of the aspects covered in this step to make sure that each change initiative that we are involved with is indeed successful.
Step 1 Prepare
This step sets the tone for the complete project. Not spending enough time in and focus on this step will break up at a later point in time. It is all about understanding what the solution means for the specific customer and/or organization and how to ensure that will be delivered. As not one organization is the same (culture, structure, urgency etc.), the outcome will always be different.
During this step we will amongst others formulate project values, clarify project objectives, create project vision, define approach (agile vs waterfall vs hybrid), identify transformational leadership, develop stakeholder & sponsor dialogue, define user involvement and short-term wins.
Step 2 Initiate
Setup the framework, logistics, infrastructure, tooling and team structure.
Step 3 Plan
Define the phases and rough timeline as well as initial resource allocation based on available information and documentation.
Step 4 Design
Review requirements, create the functional and technical designs as well as the formulation of the architecture. Following this step the Plan as defined in Step 3 will need to be evaluated and adjusted as needed.
Step 5 Execute
This step is about the development, configuration, integration and validation of the solution. This can follow agile, waterfall or hybrid approach (as initially defined during the Prepare phase.
Here will be an important link/relation with the change leadership program. As part of that, it is important to identify and delivery 'short term wins'. This could be for example the prioritization of a demo of some critical functionality, delivery of highly expected features for small group to 'play around' with.
Step 6 Train
The rollout of a new solution will require that users will be trained. This not only includes the end-users, but also those managing, monitoring and maintaining the solution moving forward.
Step 7 Handoff
During this step the solution will be formally handed off from the project/program team to the standing organization.
Step 8 Live
The final step is taking the solution live. This could be big-bang approach or could be gradual phase in over days or even weeks. Typically a warranty period is included which will require specific processes and procedures to be in place between the outgoing project organization and the standing organization.