Week in Review #2

My week in Agile practice and learning:
  • Abandoned Start with Why. Went back to The Coaching Habit.
  • Scheduled a vision meeting for the teams with the chief product owner; this was a pain point raised in our most recent retrospective. The message was received by the teams, I think, with well-deserved caution given our organizational history. Now I must ask myself how I can help them achieve their goals. 
  • Listened to the Agile for Humans 010 (great discussion of fast agile and extreme programming) and 011 (cross-over with Agile Coffee, so that's another one for me to check out, plus I was reminded about tastycupcakes.org. So many resources, only one me.). AND to meta-cast 121. Lot of podcasts this week.
  • Attempting to focus on active listening. 
  • Held a meeting with the product owners to discuss issues raised by the teams at last week's retrospectives. Not entirely pleased with how it went; too much agreement in principle, too few action items, too few voices in the conversation. Will have to think about the format next time.  
  • Manager commandeered the teams' daily scrum time for a status meeting. Three times.
  • Got to listen to half of a Scrum, Inc. webinar on addressing problems in Scrum before I got sucked into a meeting -- which was too bad, there were a lot of great questions up for discussion, and I was reminded of the existence of scrumplop.org. 
  • Podcast on psychological safety  which also introduced me to Conway's law 

We put out a release today, so the latter part of my week was mostly spent dealing with my other job in documentation. 

Comments

Post a Comment

Popular posts from this blog

Handling Meetings with Remote Attendees

This is the third session in my brown bag series. It's not an "agile" topic really, but it was one of the things people requested a session on.  I hoped that people would bring their questions and be willing to discuss them. There were four topics proposed, and some conversation although it was mostly people in the room. Here is the outline:  Day before, set up a Trello board as an option for people to raise topics and added a link to the invitation. Recruited a co-pilot who would watch the WebEx chat and bring up anything that came in through that.  Five minutes before the session, dial in to WebEx, start camera, ensure that screen sharing is set up and the projector is working.  Noon - official start time. 
Read more

Agile Transitions as Self-Sustaining Reaction

Weird confession time? I used to be a little dubious about the long-term role of coaches and even of Scrum Masters or equivalent in an Agile organization. Once you’ve taught people the rules, what else is there to do? People are smart, and Agile methods as a rule aren’t complicated. I wondered—how could it possibly take more than a year or so to get this thing going? Then I spent several years observing an Agile transition from its initial push phase through to a kind of equilibrium, and I have gained a different understanding of the roles and the process in such a transition. I’m going to call these roles Primary Agile, because their work centers on fostering agility— and nothing else . Agile transitions can be thought of as something like a chemical reaction. The system starts in one state, and by adding some ingredients and – most importantly – energy, the system changes into a different state. For most organizations, that end state is going to be very different from whe
Read more

Shu Ha Ri Skeptic

Last year it seemed like I couldn't turn around without hearing someone talking about shu ha ri and its applicability to Scrum (it was usually Scrum, probably because other Agile techniques are less ceremonial). There's a good summary here . Although I don't practice martial arts, I do meditate and practice yoga, which I feel gives me a way toward understanding how the idea is supposed to work. When you first start practicing, after all, it takes all of your attention just to get into the poses or to glimpse a moment of still attentiveness. Why you're supposed to do a specific pose or follow a particular sequence won't fit in there until you've been doing it for a while, until the physical part has become automatic. That said, something about that metaphorical connection, about the idea of "just do the Scrum ceremonies as prescribed, and why will come later" didn't sit well with me. After a fair amount of rumination I've finally identified wh
Read more