TastyCupcakes is a community-run site that presents games, techniques and approaches that could be used by Agile coaches and ScrumMasters.
When do you need to stop coaching an Agile team? In his blog post “An Exit Strategy for the Agile Coach”, Len Lagestee discusses this question and explains how he will gradually work to be ready to leave and let the Scrum team be ready to carry the Agile values on its own.
There might exist some lonely standalone software developers that create software without any other person involved, but my guess is that there are not many of them. Communication is an essential skill in software development, testing and project management… and life. As feedback is a key communication tool, I was therefore very interested when I stumble on this book about feedback written by an Agile coach.
The ScrumMaster role might be the more difficult to define among the three role involved in the Scrum team. Starting from a “bad” ScrumMaster job description, Sam Laing discusses in this article th errors to avoid when you create a Scrum Master role specification. As a bonus, she adds at the end a good ScrumMaster job description.
Henrik Kniberg goes through a handful of concrete steps for diagnosing and debugging Scrum problems. He talks about using the process wrong, blaming the messenger, being impatient, not adapting the process or using the wrong process. Henrik Kniberg also introduces some new Scrum terminology such as Scrumdamentalism, Sadoscrumism, and Scrumbutophobia.
As stated in the Agile Manifesto, Agile software development is about “Individuals and interactions”. The importance of having a performing team where individuals collaborate is an essential factor for the success of software development projects. In his “Forming Agile Teams Workbook”, Jesus Mendez provides some tools that offer an alternative-proven way to add more structure, transparency and visibility to formation of Agile teams.
Written by South African Agile coaches Samantha Laing and Karen Greaves, “Coach’s Guide to Agile Requirements” is a book on how to teach the concepts of Agile requirements. It provides a complete plan to run a workshop where people can learn how to elicit, refine and organize requirements in an Agile way.