Remove Books Remove Cadence Remove Software Development Remove Software Review
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.

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.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Are These DevOps Obstacles Getting in the Way of Your Agile Transformation?

Leading Agile

As more and more companies scramble to untangle the code of their monolithic legacy software and get it into the cloud, strategic priorities are shifting. Want the Deck Text HIDDEN to 33777 Video Transcript We will run into times where packing software makes it harder for us to transform the skills of our staff and external vendors.

article thumbnail

Review People Over Process

Henny Portman

Levine wrote with People Over Process – Leadership for Agility a very pragmatic and down to earth book about leadership and agile projects. Furthermore, neither agile or scrum contemplates how the agile team should be connected to a larger organization and to external partners who will likely have differing development processes and cadences.

article thumbnail

A Review Of Scrum For Kanban Teams

Digite

It also encourages everyone to review/adopt the values (in Scrum language) that can help software development teams succeed in building software. Kanban teams are fully capable of doing everything that Scrum teams do, described as some sort of feedback meetings that happen on a cadence. You should go read it now.

article thumbnail

Kanban to manage Complex/ Quick Moving Situations

Digite

In my over 25+ years in the software industry, this has been an all too familiar situation! I have often wondered – doesn’t speak too well of us as software professionals! Far too many projects and teams are occupied by far too many crises all through the development/ implementation lifecycle.

article thumbnail

Adopting Agile Practices Isn’t Agile Transformation

Leading Agile

Third, how are we reproducing working tests in software? When people make such statements, they usually mean that they have trained product owners and a proficient Scrum master, and their team consistently follows the cadence of sprint planning, daily stand-ups, interviews, and retrospectives. First, how are we forming teams?

Agile 117