Week in Review #11

It was a lovely long weekend. I wrote, did some knitting, went on a hike with the family, and ate a great deal, as one does.
  • Monday - Hurry Slowly 04. I'm not about to go for any long ocean swims, er, ever, but it's interesting to think about what kind of risks I may be more likely to take, and how to prepare for them. Last day of the sprint. Three releases this week. *sigh* Studied Python (thanks CodeAcademy), wrote release notes, interviewed a tech writer candidate, plunged back into EDI document format hell.
  • Tuesday -Sprint review went as well as it ever does. As usual, no customers showed, which resulted in some commentary about how we format the meeting and whether it is necessary at all. Given our upcoming reorg, the discussion seemed beside the point.

    This was probably the penultimate meeting for the current team structure; no one knows when or how the teams might end up being restructured -- let alone how the details will fall out -- but the idea is in the air that it will be early next year. No one had anything to bring up at the cross-team retrospective, and my one team retrospective was canceled or at least postponed because half the team had taken the day off (update: they never proposed a time for another meeting). These no doubt contributed to a glum cast over the afternoon.

    Also, Hurry Slowly 05. I really enjoy Austin Kleon's way of thinking, and his experience with analog vs digital creation matches my own.
  • Wednesday - Sprint planning. Last minute tickets that no one had seen before that morning, and an even more last minute ticket that showed up in the afternoon; yay?

    People keep asking me if I know anything about the upcoming reorg, to which my response is generally, "I know fuck-all." So transparent. *sigh* 
  • Thursday - Another day spent mostly on documentation; the teams put out our two releases. 
  • Friday - Another "have you heard anything about what's going on with the reorg?" conversation. Watched some Modern Agile videos on Youtube, thought about trust and what, exactly, I would like my theoretical new company to do, and worked on my Codeacademy stuff (still on Python).

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