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.
Our experience thus far has been that while self-organizing teams may enable the organization to operate from day to day without active management, a more integrated organization and more productive teams make the value-add of managers highly transparent and place a premium on specific leadership skills.
From Adam Light, Chris Vike and Diana Larsen. "Teamwork Required: Managing Agile Application Delivery in a Matrix Organization", Cutter Agile Product & Project Management Executive Update, Vol. 12, No. 19. October 2011.
For a free download of the article pdf, register at the Cutter site. You can also order reprints from Cutter to use...
December 12 & 13 8:30 am – 5:30 pm Hotel Vintage Plaza 422 SW Broadway, Portland, OR 97205
Price: $1750 per participant* Group Rate: Register 3 or more participants at $1550 per person
The workshop is limited to 18 participants, so make sure to reserve your spot soon!
Course Overview Managers have a unique role to fulfill in an Agile world. Whether leading a shift to Agile methods or guiding a newly Agile organization, effective managers join their current skills with strategic tools learned in this course to keep people and teams on track. This course gives you the hands-on experience and builds the...
Over at her “Insights You Can Use” blog Esther Derby has posted two pieces on how teams can benefit from the lens of Double Loop Learning in their retrospectives.
Team member: How will we know when we've found an impediment? What do they look like?
Sponsor: How can I know what impediments block our teams' productivity?
Scrum Master: How can I get the team to mention impediments in our daily meeting and retrospectives?
Product Owner: Why is everyone whining about impediments? Why don't we just get the work done?
It's all fine and well to say identify and remove impediments but often we bump up against a stumbling block, find a way around, and make things work anyway without further thought. It's second nature. Moving forward is what's important. And,...
Martin Jul writes about a retrospective activity in the post “Retrospectives - Adapting to Reality.” He describes an interesting process for highlighting issues in the Generating Insights part of a retrospective session.
I’ve used “Park Bench” at the end of workshops as a way of reflecting on the day or as a debriefing technique after a training exercise to uncover group discoveries. You may be surprised that I hadn’t thought of it for retrospectives. I was. Luckily, Michael thought of it.
Today I invented a phrase (at least I think I invented it because I haven't heard anyone else say it): "Avoidable Heroism."
I invented it in response to a question, "Should my team work on the weekend to meet a commitment made under their control?"
Now, I don't know the background behind this question. Maybe it's perfectly reasonable for them to work on the weekend. Maybe they have no agreement about sustainable pace. And, it raises a few questions in my mind. How often does this happen? How far from the commitment are they? When was the first, best opportunity to...
Sometimes teams get stuck at the point of “deciding what to do” in retrospectives. Team members may begin to point fingers and describe things that the ubiquitous “they” must do before the team can move forward or make improvements,. This may lead to a team-as-victim, “poor us, we’re stuck” syndrome, or blame and finger-pointing. “It’s their fault we’re in this mess!” Blame kills retrospectives and the perception of persecution stalls any hope of forward motion, so the retrospective leader has to shift this conversation, and fast! Team members also may perceive so much room for improvement they become paralyzed and can’t decide where to start improving their lot.
When victim-talk, blaming or overwhelm surfaces, I reach into my retrospective leaders toolbox and pull out a technique to help teams identify the kinds of action the team can take.
In a comment on an article about Pixar in The Economist, Tom Agan from the Nielsen Company, writes:
"At The Nielsen Company we have just completed a study of the major consumer packaged goods (CPG) companies operating in the U.S. and those with standardized post mortems for new products, like Pixar, average almost 100% more revenue from new products compared to those that don't...I think through articles like this and new research that quantifies the impact, we are coming much closer to uncovering the universal truths of innovation."
I'm willing to put up with The Economist (and Pixar)...
While in Washington D.C. last month, for the first time I visited the U.S. Library of Congress. Guided by writer and experienced LoC researcher David Schmaltz, I received a temporary library card to research early management thought.
In the glorious reading room under its amazing dome, I held two precious books. One, an (out of print) copy of Mary Parker Follett’s Creative Experience is so old it didn’t have publication date or place data printed in it. However, a little diligent searching told me the edition I held was published in 1924. The book contains ideas offered...
In Agile Retrospectives: Making Good Teams Great!, Esther Derby and I include a collection of activities we called, “Short Subjects.”
After Gathering Data, these useful activities provide relatively quick ways to review event, effort, and response data; reflect on the implications of the data; and Generate Insights about team experiences.
Lately I’ve reinforced my interest in learning to learn. I get several benefits from it. First, I learn how to learn better for my own purposes. Second, I learn more about how other people learn. Third, if I apply what I learn about how other people learn, I can become a better consultant/coach/trainer. And, magically, fourth, I am liberated from needing to find a teacher to learn the things I’m interested in learning.
The reinforcement for my learning to learn comes in the form of “Where Are Your Keys?” or The Fluency Game. (Full disclosure: My son introduced me...
For some time, I’ve been ruminating on how to answer folks who query, “How do I convince people that Agile is better?”
Values vs. Principles vs. Practices in the Iron Cage of Death*: Three Go in, One Comes Out
Discussions about where to start with Agile approaches tend to devolve into “you got your practices in my values”...”no, you got your values in my practices.” Trying to bridge the gap, some folks say, “look at the principles for guidance.” None of these works.
In reality, we have to have it all. We need values to use as filters for our decisions. We need principles to give us ideas about what values look like when they come out of the clouds and into actual...