International Institute for Learning
APRIL 19, 2023
DA was developed in 2011 by Scott Ambler and Mark Lines and is based on Scott’s work at Rational Software and IBM. To coordinate the teams, SAFe applies cadence and synchronization. Cadence means all teams are aligned to a standard, two-week delivery cycle. They emerged about a decade after the Agile Manifesto.
Inloox
JULY 1, 2021
Origin and Basic idea The Scaled Agile Framework was introduced in 2011 by Dean Leffingwell with the goal of taking advantage of existing agile methodologies and scaling them across the entire organization. In this post, we start with the 7 core competencies and the 10 fundamental principles on which cross-enterprise agility is based on.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
International Institute for Learning
MAY 16, 2022
As we adopt a continuous planning cadence, the ability to manage uncertainty with incomplete data becomes much more tolerable because we know we will have the opportunity to inspect and adapt at more frequent intervals. Intuit’s innovation success was also featured in Eric Reis’ book The Lean Startup (Crown Business, 2011).
Agilemania
DECEMBER 6, 2021
It was circa 2011 when Dean Leffingwell decided to conceptualize the Scaled Agile Framework. Apply cadence, synchronize with cross-domain planning. But, is there a solution? Build Incrementally with fast, integrated learning cycles. Base milestones on the objective evaluation of working systems. Decentralize decision-making.
Agilemania
JANUARY 24, 2022
The cadence of development of multiple teams. In 2011, Dean Leffingwell codified SAFe, the Scaled Agile Framework , to help bring the success that small teams have enjoyed with various agile methodologies such as Scrum or XP but scaled to the enterprise. Facilitate teams of teams planning. Enable enterprise-wide visibility.
Agilemania
DECEMBER 2, 2021
The year was 2011 and there was a pressing need for a scaling framework that could help large organizations design efficient systems to build enterprise level products/solutions to cater to customer’s rapidly changing needs. Apply cadence and synchronize with cross-domain planning. Build Incrementally with quicker integrated cycles.
Scrum.org
FEBRUARY 22, 2021
Apparently, there is a difference in the inspect & adapt cadence when product strategy and Sprint Backlog are compared to each other. The product roadmap needs to be adapted to the learnings from running product experiments regularly in an appropriate cadence to meet that standard.
Expert insights. Personalized for you.
59 
Let's personalize your content