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 185

Underperforming Technical Team Risk 2012 Cadence 185

Henny Portman

MAY 30, 2019

The Agile Fluency model, developed by Diana Larsen and James Shore in 2012 and substantially updated in 2018, is a framework to help teams understand their current position and to help them develop an individual road map. Delivering teams deliver on the market cadence (agile sustainability).

Agile 85

Agile 2012 Cadence 2018 85

Agilemania

DECEMBER 13, 2021

Apply cadence and synchronize with cross-domain planning. Sustain and enhance. Spotify: Spotify came into being in 2012. Build Incrementally with quicker integrated cycles. Base milestones on an objective evaluation of working systems. Visualize and limit WIP, reduce batch sizes, and manage queue lengths. Organize around value.

Agile 98

Agile Lean Software Review Technical Review 98

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