Articles and videos on creating and managing cross-functional Scrum teams: scrum master, product owner and development team.
When properly implemented, the Scrum framework enforces simple constraints that lead a team to self-organize into a state that achieves 5 to 10 times performance improvement versus traditional approaches. However, the majority of Scrum teams is unable achieve this objective.
This short video looks at some of the roles played in an Agile Team with a particular focus on Project Manager and Iteration Manager.
How do you know if you are developing and maturing as a team? How do you know you are getting good at this agile stuff? Typically agile talks about the soft side of things with a focus on the less tangible aspects such as individuals and interactions. Are there things that teams can tangibly work towards and measure their progress against? This video presents metrics that will help you assess the agile maturity of your team.
This article presents the changes needed to create collaborative agile teams. It explains that you need to modify in your traditional project management team both the process, the way people get work done, and how people work together.
“An adequate ScrumMaster can handle two or three teams at a time. If you’re content to limit your role to organizing meetings, enforcing timeboxes, and responding to the impediments people explicitly report, you can get by with part time attention to this role. The team will probably still exceed the baseline, pre-Scrum expectation at your organization, and probably nothing catastrophic will happen.
in this blog post, John Piekos explains how the ScrumMaster and Product Owner roles in Scrum are much more demanding than the Project and Product Manager roles of traditional project approaches. With frequent “potentially shippable product increments”, he believes that full-time effort is required from all members in order to be successful.
The five stories presented in this article, mostly based on real life, might help you see how Agile can become mechanical and what you should do about this. You will also learn some solutions that could help to solve all five symptoms. We need to allow people to act like people and not try to force them into a machine model that we have created for them.
Scrum Expert Copyright © 2009-2025 Martinig & Associates