SAFe® - scaled agile framework in practice
•
21 gefällt mir•4,763 views
Learn more about the scaled Agile Framework + scaling Agile. After a short introduction to several frameworks that aim to support the scaling of Agile (DAD, LeSS, SAFe®), this power point presentation from our webinar dives deeper into the details of the Scaled Agile Framework (SAFe®). Find the truth behind the often cited sentence “As Scrum is to the Agile team, SAFe® is to the Agile enterprise.”
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (10)
Ähnlich wie SAFe® - scaled agile framework in practice
Ähnlich wie SAFe® - scaled agile framework in practice (20)
Mehr von Intland Software GmbH
Mehr von Intland Software GmbH (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
SAFe® - scaled agile framework in practice
- 1. SAFe – Scaled Agile Framework in practice Mai-Lan Tran 29 April 2015
- 2. 2 Agenda 1. Introduction of Intland Software 2. Agile frameworks • Scaled Agile Framework (SAFe) • Disciplined Agile Delivery (DAD) • Large-scale Scrum (LeSS) 3. SAFe in a nutshell 4. codeBeamer Agile Architecture 5. SAFe configuration example
- 3. 3 SAFe – Scaled Agile Framework in practice Webinar info o Live demonstration will be followed by a Q&A session o Webinar recording will be available at www.intland.com/webinars/ o Please register to our upcoming webinars o Continuous Delivery & DevOps: Integrated Test Management with codeBeamer
- 4. 4 o Founded in 1998 o Headquarters in Stuttgart, Germany o Office in Silicon Valley, USA o Partners in Korea & Taiwan o codeBeamer ALM with features including: • Requirements Management • Software Development Management • QA & Test Management • Demand Management • IT Operations (DevOps) Intland Software Who are we?
- 6. 6 What is Agile? “Agile is a time boxed, iterative approach to software delivery that builds software incrementally from the start of the project, instead of trying to deliver it all at once near the end.” (agilenuteshell.com) Intland Software Individuals and interactions over Processes and tools Customer collaboration over Contract negotiation Working software over Comprehensive documentation Responding to change over Following a plan “That is, while there is value in the items on the right, we value the items on the left more” (Agile Manifesto) The Agile Maniesto
- 7. 7 Intland Software Developer, Tester PI PI PI Sprint 1 Project Backlog Scrum Master Product Owner Product Manager Agile Team Agile Team Team Backlog Team Backlog Sprint 2 Sprint 3 Sprint 1 Sprint 2 Sprint 3 What to we mean by scaling?
- 8. 8 o Hybrid approach, which extends SCRUM with tailored strategies o Building off of Scrum, XP, Kanban, Lean approaches and other methods o „The Disciplined Agile Delivery (DAD) process decision framework is a people-first, learning-oriented hybrid agile approach to IT solution delivery. It has a risk-value delivery lifecycle, is goal-driven, is enterprise aware and is scalable“ Source: www.disciplinedagiledelivery.com/ Agile Frameworks Disciplined Agile Delivery (DAD)
- 9. 9 o LeSS is a simple framework o Not too different from basic Scrum o The option for small but rapidly growing organizations o LeSS is more: considered thought over rules or policy o No project manager roles or organization-wide standard processes o Framework-1: under approx. 10 teams (with one Product Owner overseeing development) o Framework-2: 10+ teams Agile Frameworks Large-scale Scrum (LeSS)
- 10. 10 SAFe® Agile Frameworks SAFe® and LeSS classification Low High High Effectiveness Doingtherightthing Efficiency Doing the thing right Lean, Agile, Scrum Requirements Demand Goal LeSS
- 11. 11 o What is Agile and Scrum for teams, that is SAFe® for companies o Well defined and proven knowledge base for implementing Agile practices at enterprise scale o Building off of Scrum, XP and Lean Agile development approaches o Describes three levels of scale: Team, Program, and Portfolio levels o Aligns team level development with business strategy o Provides Program Increments (PI) and Release Planning Agile Frameworks SAFe® in a nutshell Origin © Dean Leffingwell scaledagileframework.com
- 12. 12 SAFe ® Portfolio & Demand Management - Kanban System Workflow Epic Epic Demand Management Business Epics Architectural Epics Architectural Epics Investment Themes/ Demands Epic Business Epics Architectural Epics Portfolio Backlog Business Epics Business Epics Business Epics Portfolio Agile Release Train Agile Release Train Agile Release Train Agile Release Train
- 13. 13 SAFe ® SAFe ® configuration example
- 14. 14 SAFe ® Scale to all levels Team 1 Team 2 Team 3 Portfolio Level Program Level Team Level Team 1 Team 2 Team 3 Team 1 Team 2 Team 3 Portfolio Agile Release Train Social Media advertisment strategy Prototype an Electric City car Prototype Bluetooth Audio Device S.M.A. Agile Release Train E. C. Agile Release Train B. A. Agile Release Train
- 15. 15 Watch our live demo now!
- 17. Thank you for your attention! Any questions? sales@intland.com We are looking forward to hearing from you!
Hinweis der Redaktion
- This slide shall give you an overview on what is agile and what are the principals behind agile development. Per definition from the agilenuteshell.com, agile is a time boxed, iterative approach to software delivery that builds software incrementally from the start of the project, instead of trying to deliver it all at once near the end. But the agile approach can and is being applied more and more to the development of products. It works by breaking projects down into little bits of user functionality called user stories, prioritizing them, and then continuously delivering them in short two week cycles called iterations. User stories are features which the clients might one day like to see in their software. Therefore the agile manifesto was created by a group of experienced people who just wanted to create better methods to create software. These are the following four fundamental main concepts in the agile manifesto: Individuals and interactions over processes and tools Customer collaboration over contract negotiation Working software over comprehensive documentation Responding to change over following a plan One of the myths of the Agile movement is that documentation is not required or useful. It is true that one of the core values within the Agile Manifesto is "Working Software over Comprehensive Documentation." However, note the word "over" in this statement. The Manifesto is not saying no to any kind of documentation; it's saying there is a preference for working software over documentation. The goal is to remove barriers and defects from the system and leave things that add value. If your organization is creating lengthy documents to produce any kind of products and you're still struggling to release them on time and also within your budget, then ask of what it will take to drive value to the client. Also, the agile manifesto focuses on self-organizing and self-correcting teams to drive quality and efficiency in the system. So this manifesto, who was created by that group of people, is already part of their organisation and they say that the value in the items on the left handside are much more than on the left side. Basically there are also values in the items on the right handside, but in order to reach much more value, there is more need to put effort into the key concepts to achieve these values.
- - Scalable Agile is an agile development process which refers to the ability to manage large projects with multiple teams and how they can work toghether. Agile methodology is great for smaller teams aiming to work fast and efficiently, and to deliver software early and often. Since Agile builds on self-organizing interdisciplinary teams, it inherently lacks the structure and organizational guarantees that large enterprises usually need in order to be able to authorize, plan and monitor the implementation of such a framework. Also, there are a few elements (such as the standup meeting etc) that simply don’t work for large / global enterprises with distributed teams. The challenge is again, to carry the qualitative and desireable agile benefits from small teams to multiple agile teams and large enterprises but still do so in an agile, lean and coordinated manner. Consequently, scaling Agile isn’t really that simple. That’s why experts have come up with solutions (or frameworks) for scaling agile, such as LeSS, DAD, and SAFe, of which the Scaled Agile Framework (or SAFe) seems to be gaining prominence. They offer ideas or techniques which can help organisazions with anywhere from small to hundreds of agile teams which needs to work together. Let me quickly walk you through each of these, before moving on to discussing SAFe, the main topic of today‘s webinar, in detail. Product Owner: decides doing right things, Scrum Master: doing the things right
- The Disciplined Agile Delivery process framework or briefly DAD is a hybrid framework to scale agile which builds up and extends on Scrum with other existing and proven foundation and methods such as Extreme Programming (XP), Unified Process (UP), Kanban, Lean, Outside in Development (OID) and agile Modeling (AD) and other methods as well. The DAD provides advice for who and when to use these strategies together. Per definition by the framework’s hompeage, the Disciplined Agile Delivery (DAD) process decision framework is a people-first, learning-oriented hybrid agile approach to IT solution delivery. It has a risk-value delivery lifecycle, is goal-driven, is enterprise aware and is scalable. In DAD, the team members shall be self-disciplined and self-organized as well. They collaborate closely to improve their effectiveness by investing efforts to learn from the experiences and also evolving the approach to reach their goals. DAD splits the process of development into three different phases, which are „Inception“, „Construction“ and „Transition“, and recommends to appoint an Architecture Owner. DAD recommends to chose a prioritization strategy and also adopts a risk-value lifecycle.
- LeSS is the most simple of these 3 frameworks, since it builds on Scrume directly: in fact, it is really not that different from basic Scrum. It is a great choice for small organizations that are growing quickly, and are looking for a framework that helps scale Scrum along with their organization. LeSS is true to the basic Agile discipline of flexibility and valuing interactions and efficient work over rules, processes, policy. Consequently, LeSS doesn‘t offer organization-wide standard processes. Instead, it lets each team figure out what‘s best for them. These teams are self-governing and crossfunctional, so there is just one defined role. LeSS wants to eliminate overhead on team level. So, there are no project managers for each team. Under about 10 teams, there‘s one product owner to oversee development. Once a single PO can‘t handle the volume, you‘ll switch over to framework 2, which is a set of parallel framework 1 sprint executions, divided by requirement areas, with one PO per requirement area.
- With the SAFe Framework a high level of effectiveness by doing the right things can be managed within the Demand Management capabilities in codeBeamer. Different approaches and methodologies can be used and combined within SAFe e.g. V-Model, Lean, Agile or Scrum to achieve a high efficiency by doing the things right. LeSS framework supports how to do the things right with the basics, which aren‘t too different from Scrum. Focus nur auf die zwei frameworks (nur damit beschäftigt)
- In this webinar, we want to focus on the SAFE framework as it is probably the most well-known of these three methods. The Scaled agile framework was created by Dean Leffingwell in 2012, which is also known briefly as SAFE. As I already mentioned before, companies have to face the challenge how to coordinate multiple agile development teams get them work for a common release objective and let them create a bidirectional line working both on business and development. The SAFe framework offers a good solution for that. That said, SAFe® is in fact an increasingly popular framework that is successfully and efficiently used by companies in various industries. Let‘s have a quick insight into SAFe: What Agile and Scrum are to teams, SAFe is for companies. Dean Leffingwell describes SAFe as an agile development knowledge base for implementing agile practices at enterprise scale. The Scaled Agile Framework differentiates between three different levels of scale: Team, Program, and Portfolio levels. SAFe describes how to interconnect lean business strategy to the agile development execution. At the Team level, SAFe® is not that different from simple Scrum extended with a few XP practices. Also the teams of five to nine members each, delivers a working software in two weeks periods, which is fully tested as well. SAFe also defines an artifact hierarchy of Epics, Features and also User Stories The Program level aligns the teams to form an Agile Release Train, while the Portfolio level aligns the Agile Release Train with the strategic goals of higher management. The program backlog contains a prioritized list of features to implement. Features can come from the Program level, or they can be derived from Epics at the Portfolio level. Features are being divided to User Stories which flows to Team-level backlogs afterwards. Also, what is iteration to team, the train is to the program. The Agile Release Train in the Program Level delivers the value stream and every 5 iterations and such a train delivers a Potentially Shippable Increment (also known as PSI)
- In the portfolio level, business activities, strategy and determination what epics, initiatives and demands are involved. This level helps to give instructions for the directions in the portfolio agile release train to underline agile release trains in the program level by allocation budget along investment themes. Also a backlog of portfolio level epics that needs to be adressed by the portfolio product managers in the upcoming PSIs is being created. To ensure cohesiveness at that level, Dean Leffingwell describes the so-called „Business Epic Kanban System Workflow“ to limit the amount of portfolio level inititives and make sure the trains are focused on those initiatives together. After that the epics needs to be analysed. In the analysis you have to measure work and track work through the analysis process with Business Analysts and System/Enterprise Architects to unterstand what the impact of such an initiatives might be. CodeBeamer‘s capabilies and feature on Demand management assists you in identifying, visualizing and understanding work. You can easily vote and rate on each epic before it becomes implemented. Demand Management in cB is essential for tracking demands and prioritizing requirements across departments. It provides valuable functionality and features that supports collaboration and helps forecast demand, meet consumers‘ expectations and also align the teams which form the Agile Release Train. Developers on the Team level will benefit from its integrated requirements management, development management, and QA & test management features. After that you can easily move on to the implementation of the winner and most valuable initiatives in the portfolio backlog, that can be measured easily through all levels, which are also interconnected through the Agile Release Trains.
- cB is the first implementation of SAFe in the Agile world. It sets itself apart from its competitors in that it enables Agile planning and scheduling while maintaining an established discipline of requirements, tests and development management tools. Another key differentiator is that cB provides versioning (baslines) and traceability for all artifacts, so vital for quality assurance (QA) and compliance (especially in the medical, automotive and aviation industries). As, one of our customer in the industry sector tried to successfully integrate Demand Management with the Program and Team level, they had like over 2000 slides for the visualisation of their processes. This simple BPMN process should just give you an overview of the whole SAFe framework that we tried to implement with codeBeamer.
- Fokus on one example (e.g blue string which represents the epic for Electric City Car Prototype) In the portfolio level, the most valuable and winner epics are collected which shall be implemented by the teams. One epic can be interconnected with a release train in the program Level
- In this webinar, we want to focus on the SAFE framework as it is probably the most well-known of these three methods. The Scaled agile framework was created by Dean Leffingwell in 2012, which is also known briefly as SAFE. As I already mentioned before, companies have to face the challenge how to coordinate multiple agile development teams get them work for a common release objective and let them create a bidirectional line working both on business and development. The SAFe framework offers a good solution for that. That said, SAFe® is in fact an increasingly popular framework that is successfully and efficiently used by companies in various industries. Let‘s have a quick insight into SAFe: What Agile and Scrum are to teams, SAFe is for companies. Dean Leffingwell describes SAFe as an agile development knowledge base for implementing agile practices at enterprise scale. The Scaled Agile Framework differentiates between three different levels of scale: Team, Program, and Portfolio levels. SAFe describes how to interconnect lean business strategy to the agile development execution. At the Team level, SAFe® is not that different from simple Scrum extended with a few XP practices. Also the teams of five to nine members each, delivers a working software in two weeks periods, which is fully tested as well. SAFe also defines an artifact hierarchy of Epics, Features and also User Stories The Program level aligns the teams to form an Agile Release Train, while the Portfolio level aligns the Agile Release Train with the strategic goals of higher management. The program backlog contains a prioritized list of features to implement. Features can come from the Program level, or they can be derived from Epics at the Portfolio level. Features are being divided to User Stories which flows to Team-level backlogs afterwards. Also, what is iteration to team, the train is to the program. The Agile Release Train in the Program Level delivers the value stream and every 5 iterations and such a train delivers a Potentially Shippable Increment (also known as PSI)