Scaled Agile Framework

Editor's Notes

1. 5 mins
2. 5 mins
3. Mik kersten who wrote the very well known book project to product How to drive the product around the value Welcome to the software age—an interconnected, real-time world in which every industry is dependent on technology and every organization (at least in part) is a software company. To remain competitive, enterprises need to digitally transform their operations, business solutions, and customer experience. The larger challenge in many enterprises is that their current business models, organizational hierarchy, and technology infrastructure can’t keep pace with the rapid change required. Our discussion today is about competing in the age of software.  The creators of the Framework have been inspired by some new works in the field including Mik Kersten's new book Project to Product and John Kotter’s new book XLR8 (phonetic ‘accelerate’). Studying technological trends, Kersten concludes that those who master large scale software delivery will define the economic landscape of the 21st century. That's a bold statement. But when you look at the combined revenue of Facebook, Apple, Amazon, Netflix and Google, you’ll see that it’s equal to the gross domestic product of Japan. The economics of the world have changed, dramatically. If the Global 2000 doesn't get to the same level of competence that these unicorns have achieved, the balance of power will be eventually end up in the hands of these few companies and that’s not a healthy thing.
4. Managing growth Aligning men different level organization strategy to team execution Scale growth
5. Simplify on team level Squad for engineering That’s team level coaching Similar kind of deliverables /// HR or engineering Organization, targets like digitalization Team level output execution to strategy down the way
6. 5 mins
7. Timeline of raising …. Number of companies adopting Roles and team structure Level of details Spotify model
8. 15 mins
9. Introducing SAFe 5.0 the operating system for Business Agility Essential SAFe Large solution Different SAFe configurations in each slide Cadence
10. Trainer Guidance: Cover the 3 key train features 5-12 teams, synchronized, aligned. Key Message: The continuous delivery (CD) pipeline (also referred to as ‘pipeline’) represents the workflows, activities, and automation needed to provide a continuous release of value to the end user. The pipeline consists of four elements: continuous exploration (CE), continuous integration (CI), continuous deployment, and release on demand. Each Agile release train (ART) builds and maintains (or shares) a pipeline with the assets and technologies needed to deliver solution value as independently as possible. The first three elements of the pipeline work together to support delivery of small batches of new functionality, which are then released in accordance with market demand. References: Read more at: http://v5.scaledagileframework.com/continuous-delivery-pipeline/
11. Trainer Guidance: An Epic is a container for a significant solution development initiative that captures the more substantial investments that occur within a portfolio.  A Capability is a higher-level solution behavior that typically spans multiple ARTs. Capabilities are sized and split into multiple features to facilitate their implementation in a single PI. A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria and is sized or split as necessary to be delivered by a single agile release train (ART) in a program increment (PI). Stories are short descriptions of a small piece of desired functionality written in the user’s language. Agile teams implement small, vertical slices of system functionality and are sized so they can be completed in a single iteration. An Enabler supports the activities needed to extend the architectural runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. Enablers are captured in the various backlogs and occur throughout the Framework. The Portfolio Backlog is the highest-level backlog. It provides a holding area for upcoming business and enabler epics intended to create and evolve a comprehensive set of solutions. The Program Backlog is the holding area for upcoming features, which are intended to address user needs and deliver business benefits for a single Agile release train (ART) The Solution Backlog is the holding area for upcoming capabilities and enablers, each of which can span multiple ARTs and is intended to advance the solution.
12. Trainer Guidance: After PI planning, we take the top ten approximate features. Ten isn’t a mandatory number, but an approximate estimation of the ideal amount (i.e., 30 is too many and 2 is not enough). The vision answers the questions: “Why this feature? Why not this feature?” It helps organizations choose. Key Message: Developers will have to make thousands of decisions and will need this context to answer the questions. The developer now understands the thinking behind the decisions. Then we break features down into stories. Add then go to a program board to cross-check. The program board is a simple way to spot problems. After the planning process, we aggregate the output into PI planning objectives.
13. Very complex solution in enterprise solution Compliant always, involve all compliance ppl early
14. Lean portfolio configuration can be applied on essential version and large solution version Portfolio linking strategy to execution Requirements in SAFe Epic is a term Essential level features only
15. Lean portfolio configuration can be applied on essential version and large solution version Portfolio linking strategy to execution Requirements in SAFe Epic is a term Essential level features only
16. 15 min
17. 7 mins
18. While no two SAFe adoptions are identical, and they rarely follow a perfectly sequential step-by-step process, businesses typically get the best results when they follow a path similar to that shown in the SAFe Implementation Roadmap, which includes 12 steps. Each of the 12 steps is supported by a dedicated guidance article in the SAFe knowledgebase. Tipping point you’re lacking any of quality productivity, time to market
19. LPM