Epics progress through several lifecycle columns, ranging from a proposed change, through retirement of legacy functionality. Similarly, they also rank higher or lower within each column. For those who understand how the board works, this provides a quick, insightful depiction of an overall Epic Roadmap.
The second of six (2 of 6) steps in Epic Lifecycle Management indicates a corresponding Request is being made "Ready" for subsequent Elaboration. Elaboration is the stage in which the TMO may establish new Epics, and/or new Solutions, thus altering the Solution Portfolio.
Epic Lifecycle - Step 2 of 6: Reviewing
What's Before
During ELM - Step 1 of 6: Intake Funnel, the TMO added a new Portfolio Epic to the Epic Lifecycle Board. In doing so, they conveyed to Owners and other stakeholders progress of the corresponding Request onto the Portfolio Roadmap. In similar fashion, this also signals the Portfolio Epic's addition to the Epic Roadmap.
Afterwards, the TMO assessed the Request for Portfolio value and risk. Then, a governing entity determined the proposed change warrants further evaluation. In due time, the Request moves on to 'In Analysis', triggering the Portfolio Epic's progression to this state.
What's Happening Now
The TMO identifies and obtains the resources necessary to gather initial information with which to define the Request. This is the next step along the Epic Roadmap.
When appropriate, the TMO facilitates development of Level 1 and Level 2 Process Definitions for each process the Request may affect. Specifically, these diagrams define the scope of each process, and describe business operations. Moreover, they provide an agreed upon, common reference, available to all. Indeed, they save a tremendous amount of time and effort later on when defining what is, and is not, in scope. They are also invaluable for later design and delivery.
Thereafter, the TMO facilitates the development of mid-level requirements. Generally, several sets are compiled, including requirements from Business, IT, and other sources.
Initial Epic Hypothesis
Using the diagrams and requirements, the TMO guides creation of the initial Solution Epic(s) hypothesis. Each describes a proposed Epic. Additionally, they identify a proposed Epic Owner. Moreover, the descriptions include the objective(s) the Epic would achieve, anticipated business outcomes, leading indicators and non-functional requirements.
The TMO presents the materials for architectural guidance. This may involve a Solution Architect, and/or an Enterprise Architect. Their review will seek to assess the proposed change for its impact to the Portfolio, IT, and Business strategy. It should also challenge assumptions and call out gaps or conflicts with how the change should fit into the organization's overall Portfolio.
After gathering all of the materials related to the Epic, the TMO presents the results to Sponsors, Epic Owners, Business / Process Owners and other key stakeholders. At this point, the Request is either signed-off for additional work, sent back for re-work, or stopped for whatever reason.
If approved for further work, the TMO then identifies and confirms the availability of resources needed to complete definition, and transition on to delivery. Those actions cover the remaining steps along the Epic Roadmap.
Step-by-Step
To Gain this State
While in this State
To Attain the Next State
- The TMO will progress a Portfolio Epic from 'Intake Funnel' to 'Reviewing' when they progress the corresponding Feature (Request) from 'On Roadmap' to 'In Analysis',
______________________________
- A Portfolio Epic may regress to this state if previously 'In Analysis', but is later de-prioritized, in favor of other, pending, Portfolio Epics.
- TMO will identify, obtain and guide resources to accomplish the tasks below.
- When appropriate, produce or update Level 1 & Level 2 Process Definitions for each process the Request may affect.
- Gather mid-level Business, IT, and Other requirements.
- Create the initial Solution Epic(s) hypothesis. Later on, if approved, these eventually replace the Portfolio Epic on the Epic Roadmap.
- Solicit architectural review of the requested change(s).
- Present Request-related materials to Sponsor(s), Epic Owner(s), Business / Process Owners, and other stakeholder(s) for consideration and commitment to continue the proposed change.
- Finally, upon receiving commitment, identify and confirm availability of appropriate resources, necessary to Elaborate upon the Request for Change.
- Sponsors and Owners sign-off on for further progress of the proposed change.
- Appropriate resources to conclude the Request's definition are available.
- The TMO selects the corresponding Feature (Request) into a Portfolio Release for further Elaboration.
Participation & Updates to the WMS
In general, Epics on this board summarize the progress of a Customer Request for Change to Sponsors, Epic Owners and other stakeholders. Indeed, these steps do not manage work. Rather, the TMO initially manages the Request using Portfolio Tasks. They do so until all aspects of the change align to an appropriate Solution Epic. Thereafter, Solution leadership becomes responsible to plan and implement the change. Accordingly, there is rarely additional work here, beyond that which updates to the WMS as follows.
The TMO will move the Portfolio Epic from 'Intake Funnel' to 'Reviewing' when they progress the related Feature (Request) from 'On Roadmap' to 'In Analysis'. That is, the Epic will continue along the Epic Roadmap.
What's Next
The TMO will progress a Portfolio Epic from this state when its corresponding Feature (Request) progresses from 'Ready' to 'Options' in PT3 - Step 2 of 6: Identify Options.
At that time, proceed to the next step, ELM - Step 3 of 6: Analyzing.