Scribd
Upload
751 views3 pages

Lean Business Case For

This document outlines a lean business case for an epic, including an epic description and hypothesis, in-scope and out-of-scope features, minimum viable product features, potential implementation costs and returns, and a development strategy. It provides metrics to measure the hypothesis and considers potential impacts on customers, solutions, and sales/support. The document also evaluates sequencing, dependencies, and includes attachments for additional supporting data.

Uploaded by

vipulbhatt2003
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
751 views3 pages

Lean Business Case For

This document outlines a lean business case for an epic, including an epic description and hypothesis, in-scope and out-of-scope features, minimum viable product features, potential implementation costs and returns, and a development strategy. It provides metrics to measure the hypothesis and considers potential impacts on customers, solutions, and sales/support. The document also evaluates sequencing, dependencies, and includes attachments for additional supporting data.

Uploaded by

vipulbhatt2003
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Lean Business Case for <short name of epic>

Funnel Entry Date: Epic Owner: Key Stakeholders:

(Use for tracking, aging and (Who is the epic owner?) (List the names of key stakeholders)
analysis in the Kanban)

Epic Description:

(Consider using the epic Hypothesis Statement in the epic article as a starting point for a description of the
epic.)

Business Outcome Hypothesis: Leading Indicators:

(Describe how the success of the epic will be (Establish innovation accounting metrics to provide
measured: for example, 50% increase in shoppers leading indicators of the outcomes hypothesis: for
under 25; Availability increases from 95% to 99.7%, example, a measurable change in purchaser
etc. ) demographics within 30 days of feature release)

In Scope: Out of Scope: Nonfunctional Requirements:

 …  …  …
 …  …  …
 …  …  …

Minimum Viable Product (MVP) Features Additional Potential Features

 (Feature or Capability)  (Feature or Capability)


 …  …
 …  …

Analysis Summary: Go / No-Go:

(Brief summary of the analysis that has been formed to create (Go, or No-Go recommendation)
the business case.

1
Lean Business Case for <short name of epic>

Solution Analysis
Which Internal and/or external customers are affected, and how?

(Describe the user community and any markets affected)

What is the potential impact on solutions, programs and services?

(Identify solutions, programs, services, teams, departments, etc. that will may be impacted by this epic)

What is the potential impact on sales, distribution, deployment and support?

(For external solutions or products, describe any potential impact on how the product is sold, distributed, or
deployed)

Forecasted Costs
MVP Cost: Estimated Implementation Cost:

(What is the investment requested to fund the (What is the estimated investment (cost) of full
MVP (the MVP cost))? implementation of the epic if the MVP hypothesis is
proven true? This estimate is refined of over time)

Initial estimate: This can be expressed as a range

Refined estimate(s): Identify material updates to the


estimated implementation cost, usually informed from
experiments

Forecasted Returns
Type of Return:

(Market share, increased revenue, improved productivity, new markets served, etc.)

2
Lean Business Case for <short name of epic>

Development Strategy
In-house or Outsourced Development:

(Provide recommendations for where the epic should be developed)

Incremental Implementation Strategy:

(Epics are defined as a single whole, but each epic undergoes incremental implementation. Click here for
details on potential strategies.)

Sequencing and Dependencies:

(Describe any constraints for sequencing the epic and identify any potential dependencies with other epics
or solutions)

Additional Supporting Data


Attachments:

(Other supporting documentation, links to other data, feasibility or trade studies, models, market analysis,
etc., that were used in the creation of the business case)

Other Notes and Comments:

(Any additional miscellaneous Information relevant to LPM)

You might also like