Strategy execution is complex. Too many programs and projects fail to fully deliver. Inconsistent requirements governance and standards continue to obscure awareness of the impact of poorly define outcomes and and how that impairs results.
The outcome analysis framework is a repeatable, outcome-focused, policy-based business analysis innovation that can front end any methodology or framework. The primary value of outcome analysis is improved requirements quality and project value. Projects are more likely to deliver desired outcomes and meet expectations with fewer obstacles.
The framework includes capturing
- business needs; as the problem and outcomes
- objectives; to achieve the outcomes
- the benefits; the measurements of the impact of the outcomes
in a way that traces business strategy to project value and improves requirements quality.
The framework includes guidance to achieve the full value.
See The Steps, below…
Why Outcome Analysis
Less than 30% of software projects are successful (Standish). 47% of projects that fail do so due to poor requirements (PMI). This innovative focus on requirement quality is an opportunity to improve results by as much as 70%.
Yet, most projects make the undocumented assumption that requirements will be fine. Only 20% of companies try to address this problem (IAG Consulting). Outcome analysis is an investment in techniques that execute strategy by eliciting and organizing project objectives and requirements based on the strategy’s business problems or opportunities and outcomes.
Projects are complex with internal and external constraints, dependencies, and integrations. It is well understood that analysis of current state, future state, and the objectives and requirements to get from one to the other must be planned and completed.
What is not well understood are effective, proven, and repeatable methods to guide analysts and stakeholders to successfully iterate the complex and challenging activities of developing and recording business needs then organizing, validating, and managing project requirements.
Outcome analysis describes the problem and solution scope in business terms and presents requirements hierarchically in concise, unambiguous, and outcome-focused terms that all stakeholders can see reflects the strategy and quickly validate.
The primary benefits of this framework are improving
- strategy execution; aligning project outcomes
- delivery results; requirements organization and quality
- decision making; requirements awareness and accuracy
- business value; keeping stakeholders and teams focused on the right things
- management of requirements change through the project life cycle
An Outcome Analysis Model
The Steps
Using the strategy as a guide, business analysts iterate through these steps to develop the outcome description and the objectives and benfits to be achieved
- Outcome analysis starts with documenting descriptions of the problem and the outcome, first as a single statement, then elaborating their details.
- Once the outcome is well formed and has sponsor approval, the business objectives to achieve the outcome can be developed.
- Business requirements are extended from the objectives.
- Benefits, measurement of the outcomes, are then noted.
- Sometimes, requirements, such as creating a base-line, must be met to measure benefits.
- A solution strategy can be utilized to govern the solution design.
- The first five steps are often iterative.
- It is hard to establish meaningful business needs. Taking the sponsor from “I need this shinny object” and eliciting and recording a business problem-oriented statement with actionable, traceable, and measurable outcomes is challenging.
- Outcome analysis should be eloquent. That is hard to explain. Examples are needed (coming soon), but these next statements try to elaborate: While recording and organizing the problem, outcome, and objectives content, expect change. Look for balance between too much and too little detail. Organize other project artifact content to find the right number of business needs for the initiative. There may only be one, but most have between three and five. However, this isn’t science either. Elements of the content will evolve and move. Remember, benefits are not things. Benefits are measurements of the impact of the outcome. If a thing is listed as a benefit, it is likely an outcome or an objective. Collaborate with other business analysts in addition to the business and project stakeholders.
Producing a business view of the outcome with well formed business needs at the beginning of each initiative is critical and hard to do. Outcome analysis is a structured, nimble approach to getting business needs defined quickly and using them to construct the right requirements while demonstrating tractability of project outcomes to business strategy.
Delivery teams are driven to produce results. The constraints of scope, budget, and time can challenge a project’s business value.
Well-intentioned analysts too often work with inappropriately limited information and collaboration opportunities and a lack of internal standards and proven guidance, which results in sub-standard requirements quality and therefore reduced success (IAG).
Here be innovation
Outcome analysis utilizes a repeatable, collaborative, and agile process to define and consistently present concise and complete business needs – the problem, outcome, objectives to achieve the outcomes, and the measurable benefits of outcome’s impact – in business stakeholder terms. The framework can increase business transformation and project success.
Visit Facebook or LinkedIn to join in the conversation.