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.
Most ScrumMasters are quite fluent in “Scrum”, but they lack experience in System and Complexity Thinking. Most projects don’t fail because of the wrong tools, but because of people and a missing understanding about the system that we are all part of.
The Scrum Training Series is a series of screencasts available for free on the web. Its goal is to provide ae fun way to learn about Agile and Scrum, to prepare for Scrum or Agile certification (CSM, CSPO, PSM, or PMI-ACP) and to debunk popular misconceptions.
The ScrumMaster is a key element of the Scrum teams that need such a role for facilitating their work. In his book “Scrum Shortcuts without Cutting Corners”, Ilan Goldstein discusses the question if a ScrumMaster can be member of multiple Scrum teams.
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.
In a typical Scrum project, the ScrumMaster might have to fill many different roles simultaneously. He can be a technical expert, an evangelist, a mentor and a coach.
Knowing the basics of Scrum is essential for any team member, but out in the trenches, a good ScrumMaster must be ready to identify and deal with Agile Antipatterns quickly to help his team and organization move forward.