Organizations that implement self-organized agile teams need managers who empowerer the teams by using servant leadership, and who coach and mentor them to learn and continuously improve themselves.
The 10th anniversary edition of the XP Days Benelux 2012 conference continues on the second day. An impression of the sessions about agile adoption, self organizing and managing technical debt.
Mike Cohn recently suggested that the Daily Standup (or Scrum) is not a status meeting for the Scrum Master, but a forum where team members are synchronising their work. Techniques such as breaking eye contact are helpful for Scrum Masters to fix this anti pattern in their teams.
A recent Harvard Business Review article highlights the importance of finishing one task at a time and hence getting more work done. Some of the core Agile practices help minimize context switching and bring a similar task focus while building software.
Esther Derby recently posted an article examining "Manager Think" and how the focus on having individuals work to their maximum capacity is detrimental to teamwork and the maximum delivery of value by teams. She tackles the common perception that teams need to appear to be struggling in order to actually be working hard. This item also examines the danger of excessive overtime on productivity.
For years Agile has been encouraging teams to work together collaboratively in open spaces and encouraging developers to pair program, but lately these types of practices have been coming under fire.
Tony Wong, a project management blackbelt, enumerates some practical points on individual procutivity. This article wonders how well these apply to software development and contrasts his list with that of other lists.
Rashina Hoda achieved her doctorate researching self-organizing Agile teams. She recently spoke to InfoQ about the work she's been doing and the results of her research. She discusses some of the factors that enable self-organization, looks at some of the risks and pitfalls that self-organizing teams face and provides some advice on how to create a culture that nurtures self-organization.
Glen Alleman describes the business management process they use and describes his discomfort with the idea of team accountability instead of having one person be accountable. He questions the effectiveness of having a team accountable and what that means when there is no single point that is responsible for success or failure.
Blog posts by Esther Derby and Mike Cohn focus on two different aspects of the staffing of Agile teams
A recent thread on the pmi-agile Yahoo! group discusses some frustrations of the Agile recommendations that seem on the verge of naivete.
Day two of the 2010 Scrum Gathering, packed full of a whirlwind of topics, talkers, activities, useful nuggets, and again (of course) healthy debates. Highlights including Harrison Owens, the creator of Open Space (as we know it), Jeff Patton's User Story Mapping, Jurgen Appello on self-organization and much, much more.
In response to a question about the Inherit Shortcomings of Scrum/Agile - Uncle Bob Martin penned (in the spirit of Martin Luther), 7 theses: No Technical Practices, 30 Day Sprints are too long, Scrum Master sometimes turns into Project Manager, Scrum carries an anti-management undercurrent, and others.
We often hear stories about daily standups that have become nothing more than long daily status meetings where team members tune out. What techniques do people have for avoiding this and other standup pitfalls?
Traditional management models don't tell leaders how to support their Agile teams without undermining their emerging self-organisation. Allusions to musical performance and "conducting the orchestra" abound - but not all are in agreement. Is the "conductor" model a good practice or an anti-pattern? In his TED talk, conductor Itay Talman shows that it may depend on what we think a conductor does.