Agile & Retrospective

Steve Berczuk writes a short and succinct article on TechWell describing, “Why Agile Retrospectives are Important in Software Development.” I’m looking forward to reading the comments and responses he gets. More and more I think of Agile Retrospectives as an opportunity for the kind of learning that leads to real adaptive action in complex situations.

Agile Retrospectives

Working Agreements

Does your team have Working Agreements? (WA’s)

Effective teams think about how they will accomplish their work together before they begin working. They describe the levels of performance and professionalism they want to achieve, then record them in Working Agreements.

WA’s cover such areas as:

What does “done” mean for us?

What will meetings look like for us? (e.g., type, number, frequency, duration, attendance expectations, decision-making, etc.)

What Agile engineering and project management practices and methods will we incorporate?

What interactions, teamwork and collaboration will best support our work? (e.g., communication flows, conflict, feedback, continuous learning, social time, fun!)

Effective teams regularly take stock...