Ever thought of what you are going to do when you join a new Agile team?
I am sure you feel overwhelmed just thinking about it: all the positive changes that you need to bring, all the expectations the company has about you and your team...
Keep your cool. v(￣ｰ￣)v I have an action plan for you about what you should do first and foremost when joining a new team as a Scrum Master (and it does not start with 'make some changes').
It could take a while to understand how to approach your Scrum Master role, especially, if you are completely new to this.
Watch the video to know exactly what your should focus on in the first two weeks of joining a team.
I love writing about Retrospectives. I would even say that it is my favourite Sprint Ceremony. Interestingly enough, my mood often depends on the outcome of the Retrospective, because I really want the team to improve.
So when the Retrospective is a success and the team finds great experiments to run in the next sprint and leaves the room in high spirits and lots of hope, I feel good, I feel I succeeded as a Scrum Master.
Scrum Master is a misunderstood role in Scrum. Often people think that Scrum Masters are the Project Managers under another name. So it's quite common for some to be confused after realising that the above statement is incorrect.
One of the things that Scrum Master is responsible for is making progress visible. This is an important task but I think it should not only be about progress. There is a lot of information that should be visible to the team at all times in the spirit of transparency and I think it is also Scrum Master’s role to make it visible.
If you are still not sure what is a part of a Scrum Master role, you should download my free guide to a typical day of a Scrum Master where I cover visualisation in some more detail.
I’ve decided to make a list of things that should be easily accessible in your team area to help them be more Agile.
As part of a Hackathon project at Bluecat Networks, our team of Scrum Masters and Agile Coaches decided to make a leaning game.
The purpose of this project was to design a board game to teach teams difficult Agile topics, in this case, the backlog refinement.
In the spirit of being Agile we used iterative approach to make our game and improve it as we continued to work on it. Keep reading to know more.
Recently I've been working with a team responsible for triage. Though initially a medical terms, it explains quite well with what the team was doing - reviewing requests coming from customers and identifying whether issues reported are expected behavior, bugs or feature requests and how important they are
Bright individuals were working in this team, great developers and testers. But let's be honest, triage can be boring, especially, for prolonged periods of time. It's not that we don't care about our customers' requests, it's just we'd love to work on something more engaging and challenging.
At the same time we can't abandon triage completely - customers will be customers with requests. But how do we keep triage going fast and give everyone on the team an opportunity to shine?
It seems like the importance of having Retrospectives in Agile teams has been covered, and more and more teams understand the reasons behind it and believe in them. But the more Retrospectives you've completed, the more difficult it becomes to keep teams engaged.
For this reason I feel it is important to start discussing the importance of using various Retrospective techniques. If you are still not sure, why it's NOT ok to use the same technique every time, keep reading.