Scrum.org

AUGUST 9, 2022

Once you have a goal, it is crucial to measure the progress on cadence. Remember about cadences. 1 Patrick Lencioni, Overcoming the Five Dysfunction of a Team, 2005. For more about setting up Product Goals you can read here. Evidence-Based Management (EBM) – shared measures toward the common. Measuring gives you a chance.

Technical Review 215

Technical Review Cadence 2005 Initiating 215

Herding Cats

APRIL 16, 2019

RFETS was a nuclear bomb manufacturing plant, built in 1951, operating until 1989, and closed in 2005. Probabilistic Schedule and Cost Analysis , prepared for NNJ051R, NASA Crew Exploration Vehicle, 2005. Rocky Flats Environmental Technology Site (RFETS) was the marketing term for the 3rd worst toxic waste site on the planet.

Technical Review 42

Technical Review Performance Measurement 2003 Underperforming Technical Team 42

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. On a two-yearly cadence, it takes four years to deliver on feature requests.

Underperforming Technical Team 202

Underperforming Technical Team Risk 2012 Cadence 202