2012 Cadence SCRUM 
Scrum.org
JUNE 8, 2023
He worked at Spotify around 2012 when they were pushing the boundaries of scaling agile and experimenting with new organizational designs. Thanks to the work of Scrum Masters, many teams moved from A2 to A3, from incomplete teams with dependencies to (more) autonomous end-to-end teams. You've probably heard of Henrik Kniberg.
Agilemania
DECEMBER 13, 2021
SAFe contains a combination of principles, processes, and best practices that help large organizations in easy adoption of agile frameworks including Lean, Kanban, and Scrum. Apply cadence and synchronize with cross-domain planning. SAFe vs. Scrum@Scale. SAFe: SAFe is the most popular framework after Scrum. LeSS is Scrum.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
International Institute for Learning
APRIL 19, 2023
They build on lean-agile thinking, and standard Scrum, Kanban, and DevOps practices. Dean Leffingwell released the first version of SAFe in 2012. To coordinate the teams, SAFe applies cadence and synchronization. Cadence means all teams are aligned to a standard, two-week delivery cycle.
Herding Cats
APRIL 16, 2019
But each method needs to be based on 5 Immutable principles to be successful, no matter the domain or context, PMI Spring Seminar , 2012, Austin TX. Five Principles of Project Success - The recurring theme of 5 Immutable Principles , is the basis of this workshop at PMI, Northern Utah Chapter, Professional Development Day , 2012.
MPUG
MAY 18, 2022
So I just want to let you know that the only drawback, real life drawback, is that they really haven’t updated this since about 2012. A lot of people don’t like that, but whatever your scrum team decides to do is right for your team. So keep in mind, it might take you time to kind of clean that up.
Scrum.org
DECEMBER 8, 2023
This commercial product was built using traditional project management practices and delivered on a two-yearly cadence. From 2005 (first beta) until 2012 they worked, successfully delivering a new version every 2 years. Even before 2012 Leadership, and engineers, had noticed that things were getting bogged down.
Expert insights. Personalized for you.
170 
Let's personalize your content