Remove Books Remove Cadence Remove Software Developers
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

Once you accept this, and quality becomes non-negotiable, your Dev e lopers can focus on creating usable increments of working software. Once you have usable increments of working software, you can then start to look with interest at the progress being made on features and goals. 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

Kanban to manage Complex/ Quick Moving Situations

Digite

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. However, the fact is that software development is a complex activity – perhaps more so than any other type of projects?

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

Beginner’s Guide to Kanban for Agile Marketing

Digite

Anderson best articulated its application to software development, in 2013, in the foundational book Kanban: Successful Evolutionary Change for Your Technology Business, and its adoption hasn’t been as universal as Scrum’s during the early days of Agile software development.

Agile 110
article thumbnail

The Customer Representative (A Preferred Product Owner Stance)

Scrum.org

The term is most often applied to a representative of a company, or proxy, who works closely with a producer or developer to clarify specifications for a product or service. The term is used in software engineering; especially in development methodology Extreme Programming and Agile software development. — Wikipedia , Oktober 2019?—?.

Cadence 62