Scrum.org

MARCH 11, 2020

TL; DR: Development Team Anti-Patterns. After covering the Scrum Master and the Product Owner, this article addresses Development Team anti-patterns, covering all Scrum Events as well as the Product Backlog artifact. The Role of the Development Team in Scrum. Source : Scrum Guide 2017. .

Development Team Review 214

Development Team Review Underperforming Technical Team Software Review Technical Review 214

Scrum.org

FEBRUARY 4, 2020

Hence, if you recognize some anti-patterns in your daily work, why don’t you ask the rest of the Scrum Team for support? The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.” Source : Scrum Guide 2017. Remember: user story creation is a team exercise.).

Development Team Review 184

Development Team Review Underperforming Technical Team SCRUM Technical Review 184

Scrum.org

FEBRUARY 8, 2020

Our Business Lending product is being developed by more than 20 teams spread across 3 sites. Each team contains business, IT and operations skills. Previously, I was involved in setting up a retail bank from scratch and in the development of mortgages solutions. My talk was about programmers in large scale development.

Underperforming Technical Team 149

Underperforming Technical Team Software Review SCRUM Technical Review 149

Herding Cats

APRIL 16, 2019

Product Development (#ProdDev). Agile Software Development (#ASD). The following material comes from conferences, workshop, materials developed for clients. The overarching theme is focused on defining what Done looks like, assessing progress toward Done in units of measure meaningful to the decision makers.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

MPUG

JUNE 28, 2021

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. And in this particular year, which was 2017, they found that 47% of unsuccessful projects failed to meet original goals due to poor requirements.

Underperforming Technical Team 52

Underperforming Technical Team Technical Review Defining Project Life Cycle 52

Scrum.org

NOVEMBER 2, 2018

When we started back in July 2017 it was a standard ‘task radiator’ borrowed straight from the boards at work: The columns on this were: Product Backlog, Sprint Backlog, In Progress, Needs Review (I think that was the first to go!), They’re less a way of estimating a task and more a way of keeping score. reluctance (i.e.

SCRUM 122

SCRUM 2018 Underperforming Technical Team Software Review 122