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

Manifesto Musings #1

We are uncovering better ways of developing software by doing it and helping others do it. What is a manifesto? Literally, it is a list, in this case a list of guidelines. What does the first line of the manifesto communicate? That the subject is not abstract, but is based in lived experience (doing it). It is pragmatic rather than hypothetical (better as opposed to best, perfect, etc.). Being rooted in experience and individual context, it will not look exactly alike to any two people.  Agile practice is subject to change and growth (uncovering is an unbounded process). I am confident that 20 other people would not have reached the same conclusions as these did, and that even if those same people were to meet again now, they might easily reach a different place.  It is rooted in the exercise of creating software. Application to other environments should be approached with caution, and should be guided by empiricism rather than attempting to fit one solution as-is...
Read more

Week in Review #4

I came down with a cold this week, and have been busy preparing for a week on half-time to cover for the spouse's trip. Things might be a bit sparse here. (Indeed, I forgot to post this until Monday.) Team member contributed funds for the candy basket I keep on my desk. (Because Agile = food, as far as I can tell.)  Backlog grooming! This has been a big subject in our retrospectives lately. Unfortunately due to being sick, my energy level wasn't what it could have been for this significant meeting. The stories are not challenging, the business value is frequently unclear (and the teams get tired of asking product owners to provide it), and people are too invested (IMO) in the estimation exercise while at the same time having an unclear sense of how to achieve agreement about those -- or what to do if we can't agree, so as to keep the meeting going. Followed up on a few more items from last week's retrospective.  
Read more

Week in Review #27

Total fail this week as far as keeping track of what I've been doing. It was a sprint boundary week, and I feel like I spent most of it running. The good news is that I finally feeling physically better, which has been a boost in terms of the energy I can bring to my work. I'm trying to sell people on some practices I believe in, like team charters; we'll see how it goes.
Read more