Remove 2012 Remove Cadence Remove Risk Remove Software
article thumbnail

All technical debt is a risk to the product and to your business

Scrum.org

All technical debt is a risk to the product and to your business. So why is so much of software opaque to the business? All technical debt is risk to the product and to your business. There is no asset securing that risk, no insurance for it. Technical debt is 100% risk. Technical debt is like an unhedged fund!

article thumbnail

Creating a Risk-Adjusted Backlog

Leading Answers

This article explains what a risk-adjusted backlog is, why they are useful, how to create one and how teams work with them. What is a Risk-Adjusted Backlog? A risk-adjusted backlog is a backlog that contains activities relating to managing risk in addition to the usual features associated with delivering value.

Risk 145
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Project Boards and Project Steering Groups: An Introduction

Rebel’s Guide to PM

They let you know whether you can go overspent or what risk mitigation actions are the right ones for this point in the project. It was a much smaller group, and focused on strategic decision making instead of day-to-day problem solving and risk management. Risks and issues. They should help guide you to project success.

article thumbnail

Disciplined Agile & SAFe

International Institute for Learning

DA was developed in 2011 by Scott Ambler and Mark Lines and is based on Scott’s work at Rational Software and IBM. 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
article thumbnail

The Agile Fluency model

Henny Portman

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
article thumbnail

Compendium of Works to Increase Probability of Project Success

Herding Cats

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. Business, Technical, Systems, Risk, and Project Management Briefings and Presentations.

article thumbnail

Use Agile Project Management with MS Project – Transcription

MPUG

He has lead projects that introduce durable goods, create hardware and software, integrate hardware and software and he’s brought up manufacturing facilities globally. 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.

Agile 59