Scrum.org

DECEMBER 8, 2023

So why is so much of software opaque to the business? I hear the phrase “but not all debt is bad” a lot, usually coupled with “some level of debt is manageable” and, as a software developer, it makes me cringe. This commercial product was built using traditional project management practices and delivered on a two-yearly cadence.

Underperforming Technical Team 188

Underperforming Technical Team Risk 2012 Cadence 188

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. The team thinks and plans in terms of the benefits their sponsors, customers, and users will see from their software.

Agile 85

Agile 2012 Cadence 2018 85

Agilemania

DECEMBER 13, 2021

The groundwork for SAFe was formed in 4 knowledge areas – agile software development, lean product development, systems thinking, and DevOps. Apply cadence and synchronize with cross-domain planning. Sustain and enhance. Spotify: Spotify came into being in 2012. Build Incrementally with quicker integrated cycles.

Agile 98

Agile Lean Software Review Technical Review 98

Herding Cats

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Agile Software Development (#ASD). Enterprise IT and Embedded Systems (#EIT).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42