Kyiv Project Management Day 2016 Анна Мамаєва: When SAFe is safe. Agile для дорослих компаній Сайт конференції: http://pmday.org/ Спільнота в мережі Linkedin: http://bit.ly/PMDayLin Спільнота в мережі facebook: http://bit.ly/PMDayKyivFB Twitter конференції: https://twitter.com/LvivPMDay
This document discusses implementing DevOps flow by leveraging lean/agile practices across development, deployment, and operations. It emphasizes establishing continuous integration and delivery workflows to enable frequent, reliable releases through automation. Kanban techniques are presented as a way to visualize work and limit work-in-progress to improve collaboration between teams.
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.
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
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.
Discussed and summarized Scaled Agile Framework (SAFe@4.0) concept as an extension of Agile, together with Steve Ohnishi and two more people.
Sans doute vous identifiez vous dans une ou plusieurs des situations suivantes: - plusieurs équipes Scrum travaillent dans votre entreprise, parfois sur un même projet ou des projets connexes - la coordination entre équipes Scrum n'est pas optimale - vous-même, ou certains stakeholders, ont besoin d'une vue plus long terme sur vos projets Agile, plus que "juste le prochain sprint" - sur base du succès de Scrum dans votre entreprise, vous voulez allez plus loin et vous voulez rendre plus agile l'entièreté de votre entreprise Si c'est le cas, venez découvrir le framework SAFe. Après une présentation du framework et de ses fondements, vous serez en mesure de mieux le comprendre, et de voir ce qu'il peut apporter ou non à votre entreprise.
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
Kumar Rajasekaran presented learnings from scaled agile implementations. Key topics included transitioning from a business process to an execution process, implementing a release train with focus on tools, metrics, user experience, agile coaching, trainings and workshops, and conducting agility assessments from team to program level. Challenges included priority/scope change management, sprint cycle duration, acceptance criteria, dependencies, capacity planning and standardization. Opportunities included delivering working software, aligning delivery to business value, and improving test practices.
Many organizations have achieved agility at the team level only to be unable to achieve it across teams. The Scaled Agile Framework (SAFe) provides both a vision and method for how to achieve this. SAFe is the first documented framework that can be used to scale agile throughout an organization. It is a combination of lean, kanban, and Scrum—lean to provide a context for an organization, kanban to manage the flow of projects, and Scrum to provide agile at the team level. Beginning with an introduction to lean and kanban, Ken Pugh explains why they are required for agile at scale. Ken then describes the framework of SAFe—specifically how it creates a structure to manifest the behaviors required for agile at scale. In particular, learn how to coordinate your organization’s portfolio, programs, and projects. Ken concludes by discussing when it is advisable to use the framework and when a more emergent method is preferable.
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.
Actual is a relative term when it comes to business value delivered by a SAFe PI Objective. In this talk we will explore techniques for validating the actual value delivered by SAFe Teams and ARTs based on real-world outcomes that can be evaluated post-release. RTEs, Product Management and Lean/Agile Leaders will be able to assess their current ability to validate value and learn specific practices they could add to their artifacts and events. Finally, we will take a deeper look at optionality and hypothesis-driven thinking in SAFe and challenge the comfort zone on how to properly use some of SAFe’s essential elements in this context. Learning Objectives: Assess their competency level of their ART/Program when it comes to ability to validate value Evolve their Inspect and Adapt events to enable validation value based on real outcomes Extend their Program and Portfolio Kanbans to help manage the flow of learning and validation.
This document discusses using "pull-based" and invitation-driven techniques to implement SAFe in an organization. It recommends: 1. Treating implementation like marketing different value streams, using techniques like training, workshops, and demonstrations to generate interest. 2. Inviting people to opt-in to SAFe training to identify champions and gauge acceptance. 3. Hosting open spaces to discuss SAFe and have groups decide how to apply it in their context. 4. Combining SAFe workshops with open-space discussions and experiments to help value streams commit to and customize their SAFe approach.
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
SAFe’s home turf is product/systems/applications development. Let’s talk about challenging this comfort zone by applying it in one of the core business functions – Marketing. Why? Because the marketing operating system is being disrupted and the larger the marketing organization the more it struggles to maintain relevancy and impact. More and more marketing organizations are seeing the impact of Agile and want to benefit as well. How should an organization using SAFe in R&D/IT look at Agile in Marketing? Is SAFe the right choice? Does it work “as is”? Are there any changes needed to support this new context? What are some lessons learned from trying this in the field? Learning Objectives and Key Takeaways: At some point in your enterprise transformation you should consider applying SAFe outside of Product Development/IT. Marketing is a great candidate for a next Value Stream to implement SAFe in. Agile Marketing is possible not just for small nimble companies but also for large organizations with hundreds of marketers and several legacy silos. SAFe provides a blueprint for how to achieve this. Understand the differences in applying SAFe outside of Product Development/IT and how to adjust the Big Picture / Implementation Roadmap to accommodate these differences. The ideal “Business Agility” state is actually to bring together Marketing, Product Management/Development, Sales into one Value Stream. This talk was delivered in the global SAFe Summit in DC in October 2018
Why assess the level of Agile Marketing? Teams, Managers and Coaches can quickly evaluate the current capability of a team/group, in order to: See how the capability measures against the recommended level for benefiting from marketing agility Guide the team/group on what to improve next See, over time, the evolution of agility (positive or negative trend) See the impact of the team/group improvement work See the impact of organizational/structural changes that are outside the team/group’s control (costs reductions, distributed, etc.) Motivate! Get acheivements and recognition for reaching higher agility levels (Emphasize intrinsic motivation!) Contact AgileSparks at http://www.agilesparks.com/services/agile-marketing for a downloadable version (and an excel sheet coming soon!)
This conference paper will be interesting to those who faced the problems team interactions and looks for success experience of solving these problems. You will get to know work sync up of over 20 Agile team. 5 present cases will illustrate solutions to 5 common problems such as: eliminating dependences between teams, increasing transparency and work effectiveness.
The Scaled Agile Framework (SAFe) is an agile framework for enterprise-scale organizations. It addresses challenges of architecture, integration, funding, and roles at scale. SAFe has three levels - portfolio, program, and team. At the portfolio level, investment themes drive budget allocations. The program level uses Agile Release Trains of 5-10 teams to deliver value in 10 week iterations. Teams use Scrum or Kanban with 2 week iterations. SAFe aims to apply lean-agile principles at an enterprise scale.
The document discusses how to implement agile practices in an enterprise setting. It describes using a combination of Scrum, XP techniques, lean practices, and traditional project management adapted to the enterprise context called "Adaptive". Key aspects include architectural planning, risk management, integration testing, continuous delivery, and working with complex requirements and stakeholder needs across multiple releases. The goal is to deliver working software in short iterations while managing the increased complexity of enterprise projects.
Kyiv Project Management Day 2016 Іванна Заєць: Основи ПМа (PM’s Essentials) Сайт конференції: http://pmday.org/ Спільнота в мережі Linkedin: http://bit.ly/PMDayLin Спільнота в мережі facebook: http://bit.ly/PMDayKyivFB Twitter конференції: https://twitter.com/LvivPMDay
Kyiv Project Management Day 2016 Олексій Кривицький: Чому масштабування agile – це не правильне рішення не тієї проблеми. Або як повернути молодість своєї організації Сайт конференції: http://pmday.org/ Спільнота в мережі Linkedin: http://bit.ly/PMDayLin Спільнота в мережі facebook: http://bit.ly/PMDayKyivFB Twitter конференції: https://twitter.com/LvivPMDay
This document discusses motivation in the workplace. It begins by looking at what motivation is and some of the basic human needs that motivate people, such as financial stability, love, and personal growth. It then examines the spectrum of motivation from disinterested to inherent enjoyment of a task. The core of motivation is said to be the three psychological needs of autonomy, relatedness, and competence. It explores how fulfilling these needs through empathy, meaningful social connections, and developing new skills can increase motivation. The document concludes by emphasizing self-awareness and shifting one's own motivation to a more integrated level.