Content tagged with: team
The Product Owner is a very important role in Scrum. He has the key responsibility to create, manage and prioritize the product development backlog. Can this responsibility always be to a unique person or is there situations where you could have a team of product owners? Kenneth Rubin discusses this topic in his “Essential Scrum” book.
Agile is founded on people and interactions. This presentation will explain a model to align teams for high performance and give you practical techniques, adapted from clinical hypnosis, that have proven successful with project visioning, goal setting, improved team communication and business collaboration.
The daily stand-up meeting is an important moment in Scrum project. Team members meet to know about potential challenges as well as to coordinate efforts to resolve issues. They usullay discuss the three following questions: What did I accomplish yesterday? What will I do today? What obstacles are impeding my progress? In this blog post, Derek Huether describes 10 types of persons that create trouble in the Scrum daily stand-up meeting.
How often did you meet a situation when everybody knows about an issue, at retrospective everybody agrees that it should be resolved, but next retrospective brings the same issue and the same action items? Why team of mature developers cannot change a situation on a project, cannot apply new practices or fail to apply innovations? Let me explain it on real project example and get you to the root cause, go from best practices to basic principles and back.
One of the principles of the Manifesto for Agile Software Development is that you should “Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.” Mickey Mantle and Ron Lichty give some advice in their book on how to facilitate when you are the manager of a self-organized Scrum team.
This highly-interactive talk shows typical communication patterns and behaviors in Agile teams. It also provides eye-opening insights into the ways communication can be improved in Scrum. It features some practical games that include the whole audience.
The board game Othello has the slogan: “A minute to learn, a lifetime to master.” This applies really well to a team that’s learning Scrum. The basic practices and mechanics of Scrum are straightforward, and not difficult to adopt.
This article by Tim Dahmen introduces a notation is based on a metaphor for software development, which is fantasy role-playing games. It explains a graphical and symbolic notation that allows to communicate about several Scrum phenomena.
How will an organization that is already truly self-organized before Agile changes its process to adopt a framework like Scum? In this blog post, the Lomio team, a worker-owned cooperative company with no bosses, discusses how they embrace Scrum.
In this article, Craig Larman and Ahmad Fahmy discuss how long does it take an organization to reorganize in order to adopt Scrum. This article is based on the transition done at Bank of America’s Merrill Lynch Global Securities Operations Technology where the software development teams went from a traditional activity based organisation (business analysts, developers, …) to Scrum.