Dev up 2016 Demystifying the scaled agile framework

I was invited by two product groups at Amdocs, Pune office to deliver a session on the overview of SAFe. This is the deck from the talk.

Presenter: Dr. Gail Ferreira, Agile Practice Leader, MATRIX Resources, San Francisco Center of Excellence Rapid scale directly impacts all levels of decision-making, planning, execution, culture, and communications for executives in hypergrowth companies. In this session, we will discuss how to organize, support, and tailor agile practices for teams and sub-teams in companies with a rapid growth cycle. We will share contemporary case studies of hypergrowth companies who have delivered agile at scale. Topics will include: • Basic agile and lean methods • Scrum of Scrums • SAFe • Disciplined Agile Delivery (DAD) • Agility at Scale (Ambler/Lines) • Spotify model (Tribes, Squads, Chapters & Guilds, DSDM).

The document discusses strategies for building a SAFe implementation, including defining the enterprise vision, creating an incremental rollout strategy, building a guiding coalition of leaders, organizing around value streams, executing the rollout incrementally, and addressing mindset and culture changes. It provides guidance on establishing a transformation team, training stakeholders, advocating for the changes, and focusing initially on the most important mindset issues.

What does it take to create a backlog, build software, release features, and finally deliver value to your customers? From estimation to prioritization, to understanding an end-state vision of an organization, this deck helps you understand the value you're delivering to your users. Learn more about the principles of Agile Product Management in this slide deck from LeadingAgile, Senior Vice President and Executive Consultant, Adam Asch.

The document provides an introduction to the Scaled Agile Framework (SAFe). It discusses that SAFe was developed to help agile scale for large organizations as traditional structures do not support innovation, speed and agility at scale. SAFe combines agile with systems thinking and lean product development. The core of SAFe is the Program level which revolves around Agile Release Trains (ARTs) consisting of cross-functional self-organizing teams that deliver working solutions every 2 weeks through planning events.

SAFe 6.0, a significant version of the Scaled Agile Framework, was released earlier this Spring. Join us for a deep dive into the newly released SAFe 6.0, where we'll explore the latest updates and improvements to the framework. In this session, we'll cover the following topics: Strengthening the Foundation for Business Agility - Foundational changes in SAFe Empowering Teams and Clarifying Responsibilities Accelerating Value Flow Enhancing Business Agility with SAFe across the business Delivering Better Outcomes with Measure and Grow and OKRs This session will provide valuable insights into the latest release and how it can help you and your organization improve business agility and deliver value to customers faster. Join us for an informative and engaging session with our expert speaker, SAFe Fellow/SPCT, and Scrum.org PST Yuval Yeret, who has extensive experience in implementing SAFe at scale. Yuval loves to answer questions, so review the “What’s new in SAFe 6.0” article and come up with concrete questions you want him to answer.

Large organizations face challenges scaling agile scrum practices across many teams due to issues like siloed teams losing overall product focus, fixed release dates encouraging a mini-waterfall model, and treating agile adoption as a project with an end rather than continuous improvement. The Large-Scale Scrum (LeSS) framework addresses these problems by organizing teams around customer-centric requirement areas rather than functions, empowering cross-functional feature teams to be self-managed and co-located, and viewing agile adoption as a continuous journey of inspection and adaptation. LeSS scales scrum without adding layers or processes in a non-prescriptive manner focused on continuous learning.

The document discusses the principles of Taylorism and how they are outdated for modern business needs. It argues that only by utilizing the intelligence of all employees, not just executives, can a company survive increasingly complex business environments. Konosuke Matsushita asserts that Japanese companies have moved beyond the Taylor model and will be more successful than Western companies still adhering to outdated Taylorist principles that separate thinking from doing work.

Discussed and summarized Scaled Agile Framework (SAFe@4.0) concept as an extension of Agile, together with Steve Ohnishi and two more people.

This document discusses enablers in the Scaled Agile Framework (SAFe). There are three types of enablers - exploration enablers which support learning what to develop in a feature, architectural enablers which help accelerate feature development through reusable architecture, and compliance enablers which support activities like validation and documentation for external compliance. Enablers can exist at the portfolio, program, and team levels and are broken down into smaller stories to implement at the team level. Teams allocate capacity at each program increment boundary to decide what percentage of work will go to developing enablers versus features, with more capacity initially going to enablers.

Abstract The primary purpose of PI planning in SAFe is to gain alignment between business owners and program teams on a common, committed set of Program Objectives and Team Objectives for the next release (PI) time-box. This workshop is to experience PI planning in action. Key Takeaways 1. Understanding of the importance of PI planning 2. Good practices for an effective PI planning 3. Preparatory work required for a PI planning

Scaled Agile Framework® PI Plannings in a distributed environment are challenging. Get ideas to be more effective with the right measures and tools for distributed collaboration.

The document discusses product backlog refinement and the definition of done in agile software development. It emphasizes that product backlog refinement is an important meeting to clarify and estimate user stories and work items to have a ready backlog for iteration planning. It also stresses that having a clear definition of done helps improve team quality, transparency for stakeholders, better release planning, and minimizing risks. Regular product backlog refinement coupled with a well-defined definition of done are key practices for achieving agility.

Scrum is an agile software development methodology where self-organizing teams work in short development cycles called sprints to build software incrementally. It focuses on collaboration, flexibility, and delivering working software frequently. Key components of Scrum include roles like the product owner and scrum master, a product backlog to track requirements, sprints for incremental development, and daily stand-up meetings. Scrum aims to be flexible and adaptive to changing requirements while maximizing productivity through its empirical process control methods.

This document discusses definitions of done at the sprint and release levels in Scrum. It provides examples of what could be included in a definition of done at the sprint level, such as code being complete, passing unit tests, and product owner acceptance. It distinguishes acceptance criteria, which ensures the right functionality is built, from the definition of done, which ensures quality. The document concludes by providing instructions for an exercise where a team discusses and creates their own definition of done, capturing deliverables needed at each level.

When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there. UPDATE VERSION : https://www.slideshare.net/pmengal/scrum-in-ten-slides-v20-2018

To compete in today’s application economy, organizations have adopted agile execution techniques. But is that enough? Learn about SAFe and how to leverage this methodology to elevate your agile teams to deliver quality outcomes and align at the enterprise level. For more information, please visit http://cainc.to/Nv2VOe

Deconstructing the Scaled Agile Framework - boiling down the "big diagram" and talking about when and how SAFe *might* be an appropriate direction for you or your team. Also covers practices from SAFe that could be useful regardless of the size and complexity of your organization

Delivered at the QAI Quest conference as a 90 minute workshop - With so many software delivery process frameworks and methodologies out there, it’s hard to know where to begin. And just when the industry seems to be warming up to agile, here comes SCALED agile with frameworks like SAFe, LESS, and a host of others. Should we all just be SAFe? But then maybe SAFe is just a glorified waterfall process for companies that “can’t handle real Agile”. SAFe, the Scaled Agile Framework, leverages the best of several well-established frameworks, including Lean, Kanban, and scrum. While SAFe is certainly intended for large, enterprise organizations delivering extremely complex and interdependent systems, many SAFe principles and practices can be used to improve much smaller teams. Join Angela in this workshop to gain a better understanding of the SAFe, and how teams can adopt SAFe principles and practices to improve the development, testing, and delivery of products.

The document introduces the Scaled Agile Framework (SAFe) for helping organizations adopt agile practices at scale. It discusses how SAFe addresses the needs of large software enterprises by drawing from agile, lean principles and practices. SAFe provides a proven framework for synchronizing alignment, collaboration and delivery across multiple agile teams working on large programs and portfolios. It emphasizes values like continuous delivery of value, transparency, quality code and respect for individuals.

This document introduces the Scaled Agile Framework (SAFe) as an approach for applying Agile and Lean principles at an enterprise scale. It discusses how traditional development methods are not keeping pace with increasing software complexity. SAFe is presented as a proven framework that harnesses the power of Agile for large software enterprises through elements like Agile teams, program execution, alignment, code quality, and scaling practices up to the portfolio level. The document advocates for SAFe's ability to accelerate value delivery, make money faster, deliver better customer fit, and reduce risk through approaches like continuous delivery, cadenced development, and synchronizing teams.

Please join us on Wednesday January 27 in Burlington MA starting at 6:30 pm as senior enterprise agility coach Yuval Yeret describes several techniques that can be used to produce a lasting and productive adoption of the Scaled Agile Framework. The Scaled Agile Framework (SAFe) is a powerful and popular framework for implementing agile at large scale across the enterprise. However many organizations see their implementation of SAFe stall and even backfire since the adoption is mandated from its organizational leaders, instead of engaged teams participating and choosing their SAFe. In this talk we will examine some dangerous implementation anti-patterns as well as healthier alternatives. You will learn some concrete techniques that help live up to the Lean/SAFe principles of respecting and engaging people. We will discuss field-proven ideas such as pull-based crossing the chasm approach to implementation, use of open space as part of the different SAFe ceremonies, and how Open Space Agility can combine with SAFe.

This document summarizes a webinar on introducing the Scaled Agile Framework (SAFe). It discusses scaling agile from the team, program, and portfolio levels. It introduces SAFe values and how it draws from agile, lean, and product development flow principles. It also outlines the SAFe framework at each level including elements like Agile Release Trains, program increments, and upcoming SAFe training events.

Discover the foundations of the Scaled Agile Framework® Values, Principles, Practices and Implementation. For more information, please visit http://cainc.to/Nv2VOe

This document provides an overview of the Scaled Agile Framework (SAF), which is a proven knowledge base for implementing agile practices at an enterprise scale. The SAF combines agile methodologies like Lean, Scrum, and Kanban. It has been successfully applied in programs with 50-100 people and in large enterprises with thousands of developers. The document discusses SAF roles, responsibilities, artifacts, and the Jira workflow used. It provides various resources for learning more about the SAF methodology.

Today’s successful companies are recognizing that software is increasingly a competitive advantage for their business. Real, tangible software development value occurs only when end-users are successfully operating the software in their environment. To ensure a faster flow of value to the business, the Scaled Agile Framework helps teams successfully deliver a differentiated and engaging customer experience, achieve quicker time to value, and gain increased capacity to innovate. The process of deploying software builds to production is no less important than developing and testing the new functionality. As an industry, we are currently mastering more Agile, better and faster methods for incrementally developing potential user value. In practice, however, these achievements are jeopardized by poorly managed deployments that happen too late in the lifecycle and delays value delivery. Bringing deployment operations (DevOps) onboard the Agile Release Train, engaging them in the PSI planning and other program level events, and establishing environments, practices and disciplined procedures in support of a continuous deployment pipeline helps the enterprise enable faster feedback and a more predictable value delivery rhythm. Join Michael Stump (Principal Contributor to SAFe), Thought Leader from Scaled Agile Inc. and software industry veteran to get an in-depth overview of how SAFe together with DevOps can provide the most customer value and quality in the sustainable shortest lead time.

Why Scale? When choose each scaling approach? SAFe? LeSS? Enterprise Kanban? Other? Scaling experts will compare the different approaches, share from their experience and answer questions from the audience This is the SAFe section presented by Roni Tamari

Understanding and visualizing the flow of value in your organization is one of the first steps for implementing the Scaled Agile Framework (SAFe) successfully. We align Agile Release Trains (ARTs) around value streams. In this webinar we will look at understanding what a value stream is, why it is important and how to align agile release trains to value streams.

Do you have highly functional scrum teams but are wondering how to get them to work in sync with each other, or wondering how get "start-up" efficiency in a large enterprise? Or maybe you just heard that the Scaled Agile Framework for the Enterprise (SAFe®) is gaining traction and you want to find out more about it. Before the year is out, we want to give you a primer on SAFe, so you can decide if it should be on your list of resolutions for the new year! We continue to see that Agile and Scrum deliver value and are catching the eyes of leadership individuals. But how does a large enterprise thrive with a Scrum framework that was made for 5-9 individuals? SAFe has garnered a lot of attention as a potential framework for enterprises with large product teams (5 or more scrum teams on a product line). It calls for the overall alignment throughout the organization so that the Scrum teams making up a large product development team can deliver valuable, high quality product increments with transparency and technical excellence. The program execution is achieved by leveraging the existing Scrum Team practices and interfacing with the higher Program and Portfolio layers in the organization. cPrime SAFe coach, Sri will provide an overview of the SAFe framework and show why it appeals not only to the engineers and architects, but also to the product management, customer support and the executive team.

A common practice among teams in IT companies adopting the latest trends, Agile can be scaled to enterprise level once applied properly. In this Innovation Session, Maduri Senadheera from the Project Management team talks about the Agile mindset, the need for scaling and the benefits of a Scaled Agile Framework for better aligning business processes.

Recording of this presentation: http://youtu.be/H_752O8P_Bs More info DevOps Community: http://bit.ly/DevOpsSAFe

The adoption of Agile is spreading across various industries, in organizations of all sizes. However, most experts agree that scaling Agile for enterprise use is a challenge. SAFe®, the Scaled Agile Framework, was created to resolve this problem. SAFe® provides a fully controlled way to adopt and scale Agile across large companies, and to align Agile processes to business strategy. The Scaled Agile Framework's latest edition 4.0 introduces the optional Value Stream level to synchronize all the Agile Release Trains, as well as other updates compared to SAFe® 3.0. Our webinar helps you to learn more about implementing enterprise Agile with the Scaled Agile Framework, and the differences between SAFe®'s previous versions and its recently released 4.0.

Scaled Agile Framework in 10 minutes (SAFe 3.0) - Scaled: SAFe is designed for large-scale software development ecosystems of 50-125 people who need to resolve inter-dependencies - Agile: SAFe is based on 9 Lean-Agile principles - Framework: SAFe is a collection of a proven efficacy tools, and you only have to use what you need https://www.youtube.com/watch?v=vysQQx7pQzg El objetivo de la Lightning Talk es dar una visión "light" pero completa de lo que propone Scaled Agile Framework 3.0 como marco de referencia para el escalado de Agile. Scaled Agile Framework es uno de los marcos de referencia para escalado de Agile que mayor aceptación está teniendo a día de hoy, sobre todo cuando hablamos de grandes organizaciones. El marco SAFe parte de las capas de abstracción clásicas de una organización para estructurar un cambio de perspectiva y de cultura basándose en los 4 valores y 9 principios Lean-Agile, apoyándose además en las prácticas Scrum-XP de desarrollo de productos. En la charla descubriremos de manera rápida los roles, artefactos y ceremonias que plantea el marco para conseguir un cambio de paradigma sostenible en las organizaciones. Unai Roldán UST Global

Presentation given at Dallas Agile Leadership Network Meetup on 24th October 2013. http://www.meetup.com/Dallas-ALN/events/144390642/

The document discusses the Scaled Agile Framework (SAFe) for implementing agile practices in complex enterprise projects. It presents SAFe as an option for organizations that have multiple Scrum teams or one team with independent threads. The core values and principles of SAFe are described, including the release train, program increment planning, and that it focuses on Lean-Agile leadership. Some limitations are that SAFe requires Scrum practices within teams and training for both teams and management to understand and apply the framework effectively.

A quick overview of some of the techniques and roles that help making the scaling of agile efforts across a large and/or complex organization more successful

Discussion in fishbowl format to find out how Scrum and DevOps should more power-full if we use it together and properly, then validating with data and convergence of CEO Scrum.org and CEO DevOps Institute.

Presentation from SAFE@Space conference on 2018.11.06. Some differences between SAFe and LeSS framework. Some difficult questions.

Talk on how scrum masters can avoid becoming impediments to their agile teams. Presented at SDEC 2015.

Mark Mzyk Engineering Manager with Chef Find more by Mark Mzyk: https://speakerdeck.com/mmzyk All Things Open October 26-27, 2016 Raleigh, North Carolina

The document discusses Lean-Agile maturity assessment (LAMA) framework. It provides an overview of LAMA and describes it as an integrated framework that combines proven Agile and Lean principles with a focus on leadership mindset and behavior. LAMA is presented as a methodology to assess teams' agility through methods and practices. The summary also outlines LAMA implementation steps and how teams can use results from assessments to identify focus areas and take action to continuously improve their agility.

This document discusses how to effectively adopt an agile mindset and practices. It begins by looking at the original goals of going agile but finds that in reality, many agile adoptions face problems and challenges. It discusses the "broken windows theory" - how small issues can lead to bigger ones if not addressed. However, instead of focusing on problems, it recommends taking an Appreciative Inquiry approach through retrospective meetings. This focuses the team on successes and strengths, envisioning future improvements through positive dialogue to act as a continuous engine for agile transformation.