article thumbnail

Everything You Need to Know About Release Managers

Rebel’s Guide to PM

My software projects needed releasing, so we had to follow the formal process and engage with the release manager to make sure that the bug fixes and new features got pushed to the production environment in a controlled way. The role of a release manager is crucial in ensuring that software projects are completed on time and within budget.

article thumbnail

Getting started with a Definition of Done (DoD)

Scrum.org

In my last post about Professional software teams creating working software David Corbin made a good point. TL;DR; Your Developers are ultimately responsible for creating done increments of working software. Working Software is not specific to a PBI; it’s applied regardless of PBI to the entire delivery.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Estimate at Completion: A Complete Guide + Template

Rebel’s Guide to PM

You probably won’t be expected to use it without having the back up of decent spreadsheets (I have a basic template I share below, so scroll down for that) and the software to underpin the calculations. As the maths on this one is quite involved, it’s a better option to choose as part of an integrated earned value management system.

Estimate 450
article thumbnail

Release planning and predictable delivery

Scrum.org

TL;DR; Without working software, you can’t build trust and you don’t know when you will get the next piece of working software. Once you accept this, and quality becomes non-negotiable, your Dev e lopers can focus on creating usable increments of working software. Professional Developers create working software.

article thumbnail

How We Reduced Cycle Time from 164 Days to 8 Days in 6 Months

Scrum.org

Due to horrible time-management on my part, we could not answer all the questions in the webinar, so we are answering them in this blog instead. You might get more value from reading this blog if you watched the recording and reviewed the slides that are available on the webinar page - A Cycle Time Journey: 164 to 8 Days in 6 Months.

Cadence 222
article thumbnail

Beyond Mechanical Scrum

Scrum.org

The teams at his company had well established cadences for their Scrum events; well-oiled Daily Scrums that are done within 15 minutes and result in transparency of what the team will do for the next 24-hours. They are releasing software after every 2-week sprint. Visualising your work on a physical or electronic board? Kanban 101.

article thumbnail

Use MVIs for team improvements

Kiron Bondale

Whether a team uses a scheduled cadence for reviewing their WoW such as the use of retrospectives in Scrum, or they use a just-in-time approach they will come up with improvement ideas. Let’s say a software development team recognizes that they need to improve their code quality and to do this there are many options available.