Development Team Review SCRUM Survey Underperforming Technical Team 
The IIL Blog
AUGUST 2, 2023
The development team was devastated. In my consulting practice, I see development teams struggling with their users. A primary reason is poor stakeholder engagement. Poor alignment with project objectives and expectations. Develop mitigation strategies. Regularly survey the environment.
Scrum.org
JULY 10, 2018
Often I hear people say that Scrum does not take care of risk: there is no risk log, risk is not on the agenda of the Sprint Review or Retrospective as a standard agenda-item. The Development Teams need to be accountable for the quality of the product and how it's made. How is risk managed in Scrum? Financial risk.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Scrum.org
AUGUST 25, 2022
How sustainable is your pace as a developer? This has always been a huge struggle for us and most of the teams we’ve been part of. Unfortunately, many developers and development teams still burn more hours than are probably good for them. The initial practice was for developers to work no more than 40 hours a week.
MPUG
MAY 6, 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. Individual contributor team, lead section, lead project manager, program manager, director of engineering. That is a huge amount. You can’t influence that project.
Leading Answers
NOVEMBER 1, 2020
Demos – Having the team demonstrate increments of functionality at the end of every iteration shows what the project has achieved to date. Instead, the team regularly surfaces from work to show where they are with progress and discuss what should come next. Information radiators can show any data the team wants to display.
Herding Cats
JUNE 12, 2018
This is simply good process development and management. This, of course, is simply poor process improvement and a fallacy since without the root cause the symptom cannot be fixed and will return. We assess physical percent complete at close business every single day, with the update of the TO DO field in Rally at the Task level.
Herding Cats
JUNE 12, 2018
This is simply good process development and business management. This, of course, is simply poor process improvement and a fallacy, since without the root cause the symptom cannot be fixed and will return. The notion of waterfall development on slide 9 as actually prohibited in our domain. Have you done a Root Cause Analysis?
Expert insights. Personalized for you.
78 
Let's personalize your content