Digite

MAY 15, 2018

This article is the fourth in a series of “Kanban and Scrum – Stronger Together”. In the most recent post in Steve Porter’s series, Yuval Yuret presents Scrum in a manner that is intended to educate Kanban teams. Values shouldn’t be expressed as goals like they are in the Scrum Guide. Disclaimer.

Development Team Review 93

Development Team Review Software Review Underperforming Technical Team SCRUM 93

Scrum.org

NOVEMBER 24, 2021

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. How much time should they spend with their team or with stakeholders? From our own quantitative research with 1.200 Scrum Teams , we know that teams are more effective when they are more aware of the needs of their stakeholders.

2014 204

2014 2008 Technical Review 2019 204

Scrum.org

MARCH 31, 2020

Despite the rapidness of the change, moving to remote worked surprisingly well for many teams, because they were used to some degree of remote work before. Especially development teams and technology firms in general have many years of experience with allowing their workforce to do their jobs from wherever and whenever they like.

Underperforming Technical Team 149

Underperforming Technical Team 2020 Technical Review 2016 149

Gunther Verheyen

DECEMBER 22, 2017

Driven by the prospect of an Italian translation of my book “ Scrum – A Pocket Guide ” I decided to revise it slightly; minor tweaks of words and terms, although a lot of them. Daily Scrum : a daily event, time-boxed to 15 minutes or less, to re-plan the development work during a Sprint.

SCRUM 44

SCRUM Development Team Review 2013 2016 44

Herding Cats

APRIL 16, 2019

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. Project Success Assessment - A checklist for assessing the processes for project success.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

International Institute for Learning

SEPTEMBER 20, 2022

Regarding the right size of a team, it has been experienced that a good number is around 10. For instance in the Agile Scrum Methodology [4] it is recommended to have 10 or fewer people in a team. Jeff Bezos, founder of Amazon, likes to use the “two-pizza rule” for strategy and development teams.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52