Week in Review #1

One reason I started this blog was in order to make sure that my own work is visible to me. I recently explained to one of our coaches that I find it difficult to feel like I'm getting anything done in this job. I come from a role in which I could at the end of the day point to milestones met and deliverables done -- could print out my day's work on actual paper. Scrum Mastering is not amenable to that, and it's one reason I have hesitated to leap into the role full-time. Will I be able to cope with the lack of concrete achievement?

He suggested that a blog would make a useful record, so I am going to experiment with this.
  • Sprint retrospectives - turned up a ton of impassioned feedback
  • Raised awareness with dev manager - teams feel a lack of strategic information (he came through, and I filled out a thank-you card)
  • Raised awareness with release coordinator - current deadline is not feasible (or fair) 
  • Encouraged team members to prioritize their health over unrealistic commitments they had no part in making
  • Planned a meeting with the product owners (had to move to next week)
  • Got 1/3 through Start with Why and am underwhelmed. 
  • Reviewed proposal from outside consultant re: team building work, for which there is unfortunately no budget. Boo. 
So that's it for this week. I'm going to try to post three times a week, I think. We'll see how it goes. 


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