2019 Defining Development Team Review Underperforming Technical Team 
Scrum.org
MARCH 18, 2020
On November 22nd, 2019, I gave the closing keynote at Scrum Deutschland, a talk called ‘The Four Things You Do To Prevent Value Delivery.’ Such a study is holistic; it involves looking at the organizational design, technical capabilities, culture and knowledge, and type of control and metrics used to define success. Background.
Scrum.org
NOVEMBER 22, 2019
The Project Manager is typically concerned with day-to-day progress of the Development Team. They rarely (or never) miss a Daily Scrum, they’re involved during the Daily Scrum and it might just be that they’re asking individual team members what they’ve done, what they’re going to do and if there’s anything blocking them.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Scrum.org
JULY 29, 2019
In my role as an Agile coach and Scrum trainer, I get the chance to talk to a lot of Scrum Masters and teams. When I ask them about what their team is measuring, the most common answers I hear are velocity, story points, and burn-down charts. Team health? I often failed to help developers understand its true purpose.
nTask
SEPTEMBER 26, 2019
Your decision about which one to choose should arise from the project specifics that the brief contained, the complexity level that project boasts, the nature and qualification of the team involved in the development and countless other factors. Agile Project Management.
Scrum.org
SEPTEMBER 13, 2021
Scrum has proven time and again to be the most popular framework for software development. Scrum Anti-Patterns: From Product Backlog to Sprint Review. More critical, however, is when the Scrum Master decides to keep the team in the dark about principles and practices to secure his or her job.
Scrum.org
MARCH 2, 2020
InfoQ’s recent ‘ Culture & Methods – the State of Practice in 2019 ’ edition found that new converts to Scrum, for example, will recruit themselves mostly from the late majority and laggards. Copyright notice : InfoQ, 2019. After defining the context, let us consider some Scrum stakeholder anti-patterns in detail.
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!), In a team of two, we no longer need to consult very much about how much something should be worth.
Expert insights. Personalized for you.
145 
Let's personalize your content