Consulting
Services
Project Lifecycle
We start by understanding the opportunity and priorities using design thinking, focused on discovery and definition to arrive at some focused and meaningful outcomes which can be committed to for delivery. These are then taken through a truly design-led scaled agile approach of continuous iteration of discovery and delivery. We include the governance frameworks and processes to ensure that our largest and most complex customer engagements are delivered with rigor and governance.
Ensure that everyone understands the engagement by defining the vision and the benefits
WHY IS IT IMPORTANT?
Ensures there’s transparency, clarity, and alignment on what the engagement is about and what it’s due to deliver to the business.
KEY METHODS USED AND DELIVERABLES INCLUDE:
Agreeing on a Northstar Vision which defines and describes the overall vision of the engagement. This often includes:
- The business case
- Program Charter
- Program Roadmap
- Environmental assessment
- Risk assessment
Working with the customer to agree on Capabilities Mapping and Prioritization using techniques like
- Stakeholder interviews
- Journey mapping
- Benefits identification
Defining more details about the engagement, preparing the required plans, aligning strategies, and preparing the teams.
WHY IS IT IMPORTANT?
Allows the engagement teams to understand what the engagement involves, set the terms of the engagement, and determine how best to move forward.
KEY METHODS USED AND DELIVERABLES INCLUDE:
- Working with the customer to develop an achievable benefits management plan
- Focusing on outcomes such as creating a business process review
- Completing a readiness assessment
- Developing a program management plan
- Setting up reporting and required systems
- Running initial workshops
Gets teams ready to work together
Designs the output(s) of the engagement and plans to deliver the outputs
Defines roles and responsibilities as well as associated standards
WHY IS IT IMPORTANT?
Ensures holistic design aligned to business benefits, and establishes key responsibilities, roles, timeframes, and deadlines
KEY METHODS USED AND DELIVERABLES INCLUDE:
- Formulating the Solution design and reviewing where appropriate
- Creating a RASIC to clearly define who does what and when during the engagement
- Creating a work breakdown structure (WBS) to define the work to be done
- Developing baseline engagement plan and finances
- Determining code management standards and guidelines to ensure the entire team understands what the standards are
- Creating a quality assurance (QA) plan for accurate testing
- Implementing project tooling to provide consistency and clear understanding
- Designing a governance model and associated reporting to ensure complete transparency and accuracy of decision making
Build and iterate the agreed solution using agile best practices and ceremonies (stand-ups and sprint planning)
Tests delivery to ensure usable, high-quality solutions
Begins the change management initiative
WHY IS IT IMPORTANT?
Allows changes to be made during the build to accommodate business needs
Ensures everyone is ready for the solution delivery
KEY METHODS USED AND DELIVERABLES INCLUDE:
- Sprint planning and refinement to ensure all of the identified work can be done in the required and agreed timeframe
- Building and configuration of solution to best practices and agreed standards
- Acceptance of completed user stories by the customer ensuring we are delivering on the team’s commitments
- Component testing and resolution of associated defects and bugs for improved quality of delivery
- System integration and user acceptance testing led by the customer to ensure that the solution performs as expected
- Preparation for deployment which can be at the end of each sprint and/or the final deployment(s) into the production environment
Deploys the agreed delivery
Delivers data migration
Prepares for training
Moves application acceptance to “live”
WHY IS IT IMPORTANT?
Delivers business value when the application is live
Outlines lessons learned to ensure next phase or engagement iteratively improves
Onboards business as usual (BAU) processes
Ensures successful adoption of new technologies
KEY METHODS USED AND DELIVERABLES INCLUDE:
- Deployed solution, verified ready for use by the right users at the right time
- Final data migration – making sure everyone has the data they need
- Lessons learned – what should we start doing, what should we stop doing, and what should we do more of
- Training through train the trainer or directly to end-users to help adoption of the solution
- Help desk support plan — transition to BAU to ensure it becomes part of the customer’s normal activities and application “stack”
- Preparation of final deliverables package providing confirmation we’ve met our promises
- Documentation of feedback from the customer through a satisfaction survey (CSAT)
- Using success to help drive more success through
the publishing of Customer stories
