Digite

MAY 15, 2018

It also encourages everyone to review/adopt the values (in Scrum language) that can help software development teams succeed in building software. As I wrote in 2013, Scrum and Kanban both share a use of values to encourage users of the methods to behave a certain way. You should go read it now.

Development Team Review 93

Development Team Review Software Review Underperforming Technical Team SCRUM 93

Digite

JUNE 13, 2018

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. Creating Your First Kanban Board.

Agile 110

Agile Technical Review Cadence Software Review 110

Project Management Essentials

AUGUST 3, 2019

In 2013, Mike Cohn coined the term scrum smells to describe the signs that a scrum team is in trouble. Poorly coded features may be technically complete, but not acceptable. Create cycles where the product owner periodically reviews the product and provides feedback. Story points can be inflated. Inexperienced Scrum Master.

Underperforming Technical Team 40

Underperforming Technical Team Agile Technical Review Software Review 40

Herding Cats

APRIL 16, 2019

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. Agile Software Development (#ASD). Enterprise IT and Embedded Systems (#EIT).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42