The presentation demonstrates why SAFe (Scaled Agile Framework) is the most widely adopted agile scaling framework. SAFe’s practices have evolved from Agile practices and methods, Lean product development, systems thinking, and observation of successful enterprises. This presentation introduces the Scaled Agile Framework (SAFe version 4.5), including its core values, principles, and practices, along with a roadmap for implementation.
Resources on Scaling Agile frameworks like the Scaling Agile Framework (SAFe), LESS, Nexus, Disciplined Agile Delivery (DAD), Scrums of Scrums, etc.
Nexus is a framework for scaled Scrum developed by Scrum co-creator Ken Schwaber and Scrum.org community. It addresses the most painful problems of scaled development – dealing with dependencies and building ‘Done’ integrated software every iteration.
This presentation explains to leveraged UX practices, innovation games and design sprints in a the Scaled Agile Framework (SAFe) context to improve the maturation of the business needs and their prioritization to best fit what users want and deliver value in a continuous flow.
Should agile practitioners avoid large corporate clients? Are they just too hard to take on a progressive agile journey? Helping companies that think they are already agile to actually adopt agile is an interesting challenge, for a start, nobody likes to be told that they are doing it wrong. In this video, David Espley shares his experience of helping larger corporate clients to act more like Lean startups, discusses how you wean people off their agile washed legacy processes and let go of some of the big company baggage.
Learn how to succeed with large scale Agile. Implementing Agile in small, short lived projects is easy. The real challenge comes when the project becomes long-running, and it gets even harder when spanning into multiple large projects. Add the challenge of distribution of resources and different cultures and it becomes almost impossible.
Lear how to use the Theory of Constraints to scale Agile and Scrum development teams. The Theory of Constraints is a methodology for identifying the most important limiting factor (i.e. constraint) that stands in the way of achieving a goal and then systematically improving that constraint until it is no longer the limiting factor. While implementing Scrum and shortening Time To Market in large financial institution we were slowed down because of obstacles in planning and analysis. I came with the idea to use Theory of Constraints which helped us to calculate real TTM and gave us hints how to release faster and cheaper. Now they’re ready to change direction anytime and do releases more often. This presentation is suitable for people in organizations trying to lower workload of releases. Video producer: http://swanseacon.co.uk/
Developing large software systems automatically generate some technical dependency issues. If this is often managed by software architects in traditional projects, how do you communicate this technical dependencies when you are organized using an Agile approach? This is the topic discussed in the paper written by a Swedish research group.