SAFe. Flow of Epics and Epic Owners

Now that we are no longer discussing about project management, multiannual planning, work breakdown-structures, fixed plans, fixed scope and so on, how are the big initiatives being pushed to implementation and who takes care of their lifecycle?

Now that we are no longer discussing about project management, multiannual planning, work breakdown-structures, fixed plans, fixed scope and so on, how are the big initiatives being pushed to implementation and who takes care of their lifecycle?

When you think about Agile processes you might think they cannot be applied to big companies with big needs — implemented in terms of volume of work, cost and resources. Well, this is the third topic in our SAFe article series.

Like we talked about in an earlier section, in SAFe there are multiple available configurations. One of them is the Portfolio configuration, aimed at organizations that deliver a portfolio of solutions and/or services to their customers. At the top most layer of this configuration, which is called “Portfolio layer”, the framework describes a set of artefacts called Epics and the role that manages them throughout their life span is called Epic Owner. It also includes the tools and processes that can be used.

The Epics are designed specifically to express those big initiatives requiring a huge investment in implementing them. They can be split into “functional” and “enabling” Epics depending on whether they are directly delivering new features or just preparing the ground for future functionalities. There can be Epics impacting only one of the portfolio products or a set of products. The definition of an Epic contains all the details needed to support the implementation of that specific idea. An epic contains a Lean Business Case which has a pragmatically chosen quantity of information needed for supporting its implementation. A very important section describes the minimum set of Features which once implemented will be creating an MVP (minimum viable product).

Structuring Epics through Portfolio Kanban

A Kanban board is used to structure all the steps needed for the definition and implementation of epics. Steps like analyzing, prioritization, estimation, go/no-go decision, planning, forecasting, implementation and deployment. This is a very well-known Agile tool, which in this case is called the Portfolio Kanban. Using a Kanban board has a lot of advantages:

• Makes all the work visible
• Provides context for economic decision making
• Brings all the perspectives together in one place
• Provides support for creating a constant and sustainable flow of value by using WIP limits for instance
• Brings a lot of transparency to the whole process
• Supports the continuous improvement effort

Read the rest of the article at — http://bit.ly/2leA2NT

Originally published at https://www.luxoft-training.com.