During analysis, a lean business case is being developed for each epic, which among other aspects contains a description of the implementation strategy for the epic. In SAFe, epics go through the Kanban system where the necessary research and analysis activities are conducted, and a go/no-go decision is eventually made. The implementation needs to be aligned across all participants to be able to introduce meaningful milestones to the process and adjust the implementation based on the feedback. However, the way this works is not as simple as splitting an epic into a set of program epics and fully authorizing the programs to implement their portions the way they want.
Moreover, in the case of a portfolio epic, programs have certain flexibility and authority in implementing their own pieces. Incremental Decentralized ImplementationĮpics are defined as a single whole, but each epic undergoes incremental implementation. We assume that the reader is familiar with Epics, Business Epic, Architectural Epic and Epic Kanban System, and since we will be referring to some principles of Product Development Flow, the Lean-Agile Mindset article in SAFe also provides some important background. Portfolio Epic – involves more than one program. In this article we will discuss different strategies for incremental epic implementation dependent on the epic type:ĪRT Epic – an initiative that is constrained to a single program.
Moreover, once the technology, benefits, and economics are understood, some won’t deserve to be fully implemented, as the initial effort delivers most of the potential business value. While it’s easy to think of epics as big, binary, monolithic, committed blobs of work, the reality is they should be implemented incrementally to achieve the benefits of agility. It is a key capability of the agile enterprise to properly analyze and sequence business epics for implementation. Note: This article is part of the Community Contributions series, which provides additional points of view and guidance based on the experiences and opinions of the extended SAFe community of experts.īusiness epics are large initiatives in SAFe that drive business value and typically cross the organizational boundaries (release trains), time boundaries (PIs), or both. This cyclical process will roll data back into the next PI Planning when investments are re-analyzed.Implementation Strategies for Business Epics Making these decisions each quarter instead of each year as part of annual planning increases agility at the enterprise level. Based on the work's performance against projected delivery forecasts, persevere or pivot decisions will need to be made. Move work toward completion as underlying work is accomplished.Īs the organization goes through the cyclical process of delivering agile work through the underlying features and stories, the leading and lagging indicators will collect data. Even if epics were sequenced as part of investment and capacity planning, they will need to be put into the correct sprint in AgilePlace.ĭeliver agile work through underlying features and storiesīuild out the appropriate features and stories on the program and team program boards. Sync key prioritized work into AgilePlace, and make any adjustments if necessary. Sequence agile work into appropriate timeboxes (e.g., Program Increment)
0 kommentar(er)
