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.

Underperforming Technical Team 169

Underperforming Technical Team Risk 2012 Cadence 169

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.

2012 126

2012 Cadence Retail 2016 126

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.

Agile 59

Agile Cadence Certification Lean 59

Agilemania

DECEMBER 13, 2021

41% proclaimed absence of leadership to be the main problem. 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. Leadership: SAFe inculcates the Lean-Agile mindset which is necessary to become a Lean-Agile leader.

Agile 98

Agile Lean Software Review Technical Review 98

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.

Agile 59

Agile Underperforming Technical Team Software Review Cadence 59

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.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42