Every now and then every ScrumMaster or Agile Coach meets a team that doesn’t show any of the Scrum values in their day to day interactions. This can be frustrating to the agilist, but to the team it can be psychologically harmful and have a severe impact upon their performance. Taking a lead from professional coaching, I believe that the answer to this problem in the team exists within the team itself. I set to work creating a retrospective that would help this team create a charter that they own and buy into. Continue reading “The Journey to Creating a Team Charter”
How many meetings have you been in that you didn’t understand why you or someone else was there? Or perhaps you didn’t know why the meeting was happening or what the meeting was expected to deliver? On average, an hour meeting attended by ten people costs the business £500. Roll this out to a couple of meetings a week, and that team is burning through £4,000. For investment we better be getting a good return. Worse still, if that meeting didn’t come to a solid conclusion and setup another meeting, the cost of delay could be high. An easy to adopt meeting facilitation technique that can help to dramatically increase meeting output, increase ROI, and reduce the cost of delay is a POWER start. Continue reading “POWER Start Your Meetings”
I’ve been watching my team for a couple of sprints now, and I’ve generated some questions around how they groom stories. When stories are brought into sprint they are typically between 25% and 50% of the team’s average velocity. The ideal is that every story is around 6% to 10% of the average velocity. The Team and Product Owner have been telling that they cannot be made smaller. I didn’t believe this and so decided to explore a story that the Team claimed to be ready for the next sprint.
When I was a developer, I understood in theory that retrospectives were a good things and were there to help the team improve over time. The thing was, that isn’t how it worked in practice. Our ScrumMaster ran the same retro every time. He would walk in, draw three columns on a flip chart, and labelled them Positive, Negative, and Delta. The team would then sit quietly and write up the same things on stickies that we had written last time. Our ScrumMaster would then quickly read out the good things, let us spend half an hour whinging at each other about the negatives, and finally we would agree to change all the things that we hadn’t changed before. When I decided to become a ScrumMaster, I promised myself that I would never put a team through that.
Our team is comprised primarily of relatively new staters, with all but one being here between four months and four weeks. One developer (let’s call him Jack) has been here much longer and is very familiar with the product. As I’m sure we’ve all seen in this scenario the team has developed a level of reliance upon Jack that was understandable to start with, but needs tackling to avoid problems in the future. Continue reading “Addressing Team Reliance Upon One”
This week is my first week with the team I’m going to be working with for the next few months. I started on the last day of sprint 28, which was also my predecessor’s last day. This week we setup sprint 29 and I broke the golden rule of not changing anything in the first sprint. Continue reading “New Team, New Sprint, Tidier Board”
I’ve recently been working with a client who told me they had worked in an agile environment before, had found it valuable, and wanted to use it again. After running two or three grooming sessions of the product backlog with the development team and customer I was asked what I thought the point of writing user stories was. Many people who have worked in quasi-agile environments think that user stories are agile’s equivalent of requirements gathering. They’re wrong. Continue reading “What’s the Point of Writing User Stories?”
Agile is a term being used a lot in software development these days. From start-ups to international banks, everyone says they’re agile or they want to be. So, what is agile? Continue reading “What is Agile?”
The role of ScrumMaster is becoming more and more popular. As this popularity grows, so do the amount of people who are trying to break in. Here are five things I would advise any budding ScrumMaster to do.
Continue reading “Five Ways to Become a ScrumMaster”
I’ve worked in many organisations undergoing an agile transformation, both as part of the development team and as a ScrumMaster. Over the years I’ve seen the behaviour of the development team have an impact upon the agile journeys of organisations. Given agile was designed by and for developers, its they who have the most to gain from transformation. The development team needs to understand how they can help the transformation be successful. Here are the top ten things that the members of the development team can do to help ensure that success. Continue reading “Ten Things the Development Team Can Do to Help the Agile Transformation”