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

Hello, World

This is a new blog I'm starting in order to keep track of my thoughts about Agile practices and philosophy, and the Scrum Master work I'm doing at my own place of employment. I began this work approximately one year ago, and if I've learned anything since then, it's that there's always more to learn....
Read more

Manifesto Musings #3

Working software over comprehensive documentation This line seems to me to be the least useful of the bunch, if only because it is so obvious as to seem unnecessary. Software without documentation may or may not be useful; documentation without software is always useless. This line causes technical writers a lot of angst, though, so maybe I will approach it from that perspective as a straddle the career boundary. Part of the angst seems to be rooted in a tendency for people to approach Agile stuff in a restrictive, black and white fashion. Most tech writers being in the business of providing customer-centric documentation of some kind, there's a tendency to think that Agile means getting rid of that wholesale, and I don't think that's what is actually meant. It is fairly common, though, to see "X has more value than y," morph into, "So you don't do y at all then. Good luck with that." Cue rolled eyes. This is of course a straw man; I've y...
Read more