The Scrum team has improved, progress has slowed. How to analyze and identify the bottlenecks between Product Development and Deployment.
A company adds teams but wants to keep the same number of ScrumMasters. Smart move or disaster? This case study examines how to handle such a situation.
A case study of why overtime in an Agile environment doesn’t work. What pitfalls result, and how ScrumMaster and Product Owner can help the team avoid them.
#GOAT13 is now but a fond memory. As promised to the attendees I’m posting the presentation slides including presenter’s notes: and handout. I’m also doing a bit of a retrospective to reflect on how to improve for next time. Many of the comments in my Perfection game are based on attendee’s feedback after the session. […]
A study from Rally Software explores dedicated stable teams, what contributes to them, and what Scrum Practices they implement.
There is a common misconception that the Product Owner is just a Business Analyst with a new suit and a better title. While the two share many skills in common, the roles are really quite different. According to the Agile Atlas: “The Product Owner is the single individual who is responsible for drawing out the most valuable […]
Hiring, adding, or changing a Team member in Scrum means the whole Scrum team has to adjust. How a ScrumMaster can help during transition, and problems to avoid.
At Agile 2007, I attended Jean Tabaka’s session “Why I don’t like Mondays.” She recommended establishing ground rules for team meetings. We came up with these.