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 Scrum. Starting from a “bad” ScrumMaster job description, Sam Laing discusses errors to avoid when you create such a 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.
In his book Agile Reflections, Robert Galen has aggregated multiple articles that he wrote about transitioning to Agile for the online publication PM Times. The book is based on his experience as in Agile coach helping companies in different phases of their transition to Agile software development.
This talk provides a is a reflection on what Michael De La Maza has learned as an Agile Coach about communication, emotional stress and team organization.