Scrum.org

SEPTEMBER 23, 2019

The first article of this series will address the Scrum Master engagement with the Development Team. Scrum Master Engagement with the Development Team. Following this layout, there are three main scenarios for the Scrum Master’s support of the team: The Co-located, Stable Scrum Team Scenario.

Development Team Review 135

Development Team Review SCRUM Software Review Technical Review 135

Scrum.org

JUNE 14, 2019

The Sprint Burndown Chart that looks awesome but somehow there's still a lot of work dumped on testing towards the end of the Sprint and a scramble to try and get a Done Increment before the Sprint Review. . Some years ago (circa 2007) I found a secret weapon for fighting this sort of behavior.

Development Team Review 162

Development Team Review SCRUM 2007 Estimate 162

Scrum.org

APRIL 7, 2022

Team cognition is similar in the sense that the entire team can be thought of as a body, where each member (the limbs) has to learn how to coordinate their work effectively to move forward. This shared understanding is captured in the “team mental models” that drive team cognition. It takes time to develop teams.

Underperforming Technical Team 161

Underperforming Technical Team 2007 2006 2009 161

Leading Answers

JUNE 22, 2022

We must also be able to make the team feel capable and develop team members to their fullest potential. Instead, it recommends leaders build leadership teams that comprise all the necessary skills. This is another instance where having diversity on the team is helpful. Why pay twice for the same opinions?”.

Leadership 193

Leadership Underperforming Technical Team Development Team Review Energy 193

Digite

MARCH 12, 2018

Starting in 2007 when we moved from being a waterfall shop to 2011 when we adopted Kanban, we have ourselves mastered a number of challenges that the question above presents. Dev Lane for the main dev activity. The Dev board value stream follows a Test Driven Development flow. Our Kanban Journey.

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

Project Pulse Journal

APRIL 15, 2024

Limit Work in Progress (WIP) – By limiting WIP, Kanban encourages teams to complete current tasks before taking on new ones, thus reducing multitasking and focusing on quality and efficiency. Feedback Loops – Incorporate regular meetings to review and adapt your workflow based on feedback.

Software Review 52

Software Review Technical Review Agile SCRUM 52

Leading Agile

JANUARY 15, 2019

The title is based on a quote from the 2007 movie, Ghost Rider. Connection with Software Development. Software development teams often find themselves tangled up with more work than they can handle gracefully, if at all. The two fight briefly.

Software Review 68

Software Review Development Team Review 2007 Technical Review 68