2019 Article Development Team Review Underperforming Technical Team 
Scrum.org
MARCH 22, 2021
Shall I notify you about articles like this one? Your Scrum team is consistently failing to meet commitments, and its velocity is volatile. How would you address this issue with the team? The team addressing unplanned priority bugs. So far, this Scrum Master interview guide has been downloaded more than 18,000 times. ??
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.’ And now in these four articles. . A new product had been developed to replace an older, third party solution that was no longer tenable. Background. The launch was less than satisfactory.
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
In this brief article, we will help you study some effective tools and techniques which can be used in different fields of the organizational culture that facilitate you in creating an efficient strategy and to successfully deliver a top-notch project. Agile Project Management.
Scrum.org
SEPTEMBER 13, 2021
Scrum has proven time and again to be the most popular framework for software development. Shall I notify you about articles like this one? Scrum Anti-Patterns: From Product Backlog to Sprint Review. Flow disruption : The Scrum Master allows stakeholders to disrupt the workflow of the Development Team during the Sprint.
Scrum.org
MARCH 2, 2020
Do you want to get this article in your inbox? 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. You can sign up here and join 25k other subscribers.
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.
228 
Let's personalize your content