Content tagged with: team
In a typical Scrum project, the ScrumMaster might have to fill many different roles simultaneously. He can be a technical expert, an evangelist, a mentor and a coach.
When you come to a Scrum or Agile conference, you pick up new ideas that you’d like to try when you get back to work. However, you may feel like you hit a brick wall when it comes persuading your team to try the idea out. Resistance is very common in organisations large and small.
Do you know situations where the team spirit and/or quality of results were decreasing? This might have been complex situations and maybe it took a lot of time to fix it. But did it change on a long term?
I suggest an easy to use way with all team members to get and stay in a continuous improvement loop.
The first value of the Agile Manifesto is ” Individuals and interactions over processes and tools”. Its third value is “Customer collaboration over contract negotiation”. In his book “Agile Analytics”, Ken Collier discusses the concepts of cooperation and collaboration in Agile.
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.