BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Self-organizing Team Content on InfoQ

  • Using Lessons Learned as a Dungeon Master on Roleplaying and Games in Agile Coaching

    Guillaume Duquesnay uses his experience with games and roleplaying in his work as an agile coach. At the Agile Tour Brussels he talked about leadership, facilitation and management styles where no authority was involved. InfoQ interviewed Guillaume on his coaching, facilitation and leadership skills, and asked him if playing games gives happiness and fun to people, and make them more productive?

  • Agile Retrospectives, Can You Skip Them?

    Teams sometimes consider to skip a retrospective meeting, when they feel time pressure, or do not see direct benefits of doing one. Next they question themselves if they have to keep doing retrospectives? Agile retrospectives help teams to learn and improve continuously, and there are valid reasons to keep doing them also with mature teams.

  • Why Do Teams Find It Difficult to Do Agile Retrospectives?

    Retrospectives are often considered to be a valuable agile technique, but sometimes teams have difficulties doing them: insufficient control of things, thinking that they can’t improve, difficulties defining good actions, or much complaining. Teams may find retrospectives boring, and a waste of their time. How to deal with this, and help teams to discover better ways to do retrospectives?

  • Martin Fowler at GOTO Amsterdam 2013 about Agile Essence and Fluency

    Martin Fowler talked about software development in the 21st century, discussing agile essence and how teams adopt agile. He presented at the GOTO Amsterdam 2013 conference how teams can increase their agile fluency, from a first star level up to four stars.

  • Finding Ways to Improve Business – IT Collaboration

    Collaboration between business and IT can be a problem in enterprises. People are finding ways to better support the business needs and increase the business value of IT, using business IT fusion, DevOps or sociocracy.

  • How a Scrum Master Can Handle Impediments with a Team

    Impediments are used to discuss issues take actions when a team becomes blocked. Impediments are handled in different ways, a look at how some scrum masters do it.

  • Leadership for Self-Organized Agile Teams

    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.

  • XP Days Benelux 2012, second day sessions

    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.

  • The Daily Standup/Scrum is not for the Scrum Master

    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.

  • Achieving More By Doing One Thing at A Time

    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.

  • Are they Working Hard?

    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.

  • Is Agile Stifling Introverts?

    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.

  • Individual Yield

    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.

  • Nurturing Self-organizing Teams

    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.

  • Questioning Team Accountability

    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.

BT