Definition of Solution Delivery Strategy

Solution Planning Series

Solution planning is a collaborative process that entails engaging with relevant business and technology stakeholders in order to determine the solution, and delivery approach that is best suited for solution implementation. A solution approach to solving business problems ensures that consideration is given to all the pieces that the solution will be composed of.

We have spent the last few weeks exploring the concept of solution planning. In the first post in the series, we recommended a 4-step process for carrying out a solution planning exercise. The steps of the solution planning process are listed below:

• Confirmation of Scope,

• Assessment of Capabilities and Constraints,

• Definition of Solution Blueprint, and

• Definition of a Solution Delivery Strategy

This post, the fifth in the series; discusses the fourth and final step of the solution planning process: definition of a solution delivery strategy.

The solution delivery strategy is a document that articulates the considerations and critical decisions made during the earlier stages of the solution planning process into a coherent and holistic plan for how the solution will be implemented. The outcomes of scope confirmation, assessment of capabilities and constraints, and definition of a solution blueprint serve as inputs into the solution delivery strategy.

The entire solution planning effort is led by a Solution Architect. The Solution Architect is responsible for documenting the solution delivery strategy, with input and validation from key business and technical stakeholders. As with all the other steps of the solution planning process, the solution delivery strategy should be documented before solution implementation commences.

A solution delivery strategy may address the topics discussed below:

• Scope: what are the high-level requirements? What is the scope of the solution? How will changes to requirements/ scope be managed?

• Business Process Blueprint: what are the high-level processes for in-scope areas? What are the high-level future state processes?

• Current Applications: what does the current application landscape look like? What would the future application landscape look like?

• Development: what development methodology or framework will be adopted?

• Technology Blueprint and Environments: what does the current technical environment look like? What will the future technical environment look like?

• Integrations: would there be a need for integration? How easy is it to integrate to existing applications? What is the planned approach for integration?

• Sourcing: what is the planned sourcing approach for resources? Will the solution be delivered in-house or outsourced to solution implementation partners?

• Governance: how will solution implementation be governed? What are the roles and responsibilities required to provide adequate governance for the solution implementation effort?

• Change Enablement Blueprint: what change enablement activities will be required to support change during solution implementation?

• Testing: what is the plan to test the solution during implementation?

• Release and Deployment: what is the preferred release schedule? Will releases be phased or will the solution be deployed all at once? How will the chances of successful deployment be maximized? Under what circumstances would a system rollback be permitted?

The overarching benefit of proceeding into solution implementation with a solution delivery strategy is that the chances of successful solution implementation are increased. Additional benefits include:

• A holistic view of all solution inputs,

• Clear understanding of in-scope and out-of-scope items,

• Business-driven prioritization of in-scope items,

• A thorough understanding of current and future business processes,

• An understanding of dependencies, current capabilities and constraints,

• Clear definition of a blueprint of the solution, including business process, applications, infrastructure and change management,

• Agreement on an approach or strategy for solution implementation, etc.

Is solution planning applicable to agile delivery? Join us next week for the next post in the series where we explore this topic.

Have you had any experience where there were challenges on a solution implementation project due to poor solutioning? Please share your thoughts and comments below. Follow Virtro on Social Media