article thumbnail

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

Scrum.org

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.

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
Insiders

Sign Up for our Newsletter

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

article thumbnail

Building bonds: A founder’s take on our annual team retreat

Resource Guru

Since Resource Guru launched in 2012, our mission has always been crystal clear— to be a magical and insightful guru, helping teams do their best work in a happier, healthier way. Our engineering team had a break-out session to discuss how they could increase the cadence of feature releases. The result?

2012 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

Creating a Risk-Adjusted Backlog

Leading Answers

That could take two weeks and cost $100,000 when factoring in the new software license, the team's burn rate, and the cost of delay to the organization. Then, in 2012 I presented a collection of Collaborative Games for Risk Management  at the Agile 2012 Conference in Dallas and PMI Global Congress in Vancouver. After

Risk 145
article thumbnail

Project Boards and Project Steering Groups: An Introduction

Rebel’s Guide to PM

It’s fine to have a different cadence at different points in the project lifecycle. The compliance manager will make his team available to help if he understands how the new software tracking system will monitor license usage across the company. Parts of this article first appeared on The ICPM website in 2008 and on this site in 2012.

article thumbnail

How do you implement SAFe agile in your organization?

Agilemania

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. Spotify: Spotify came into being in 2012. SAFe endorses alignment, collaboration, delivery among large agile teams.

Agile 98