Week in Review #13

  • Monday - Spent most of the day on documentation as we come into the end of the sprint. Felt glum (again - Monday blahs?). It seems like my role transfer might actually become reality after all?
  • Tuesday - Went back to the CodeNewbies podcast (S1E2) and Base.cs (E2). There's so much good information out there, so many people doing neat things. Got a request from my mentor to take on a short-time coaching role for a team in a different product area. We have a release coming up at the end of this week, but it looks like after that I'll have some time to spend with this group, and hopefully I'll find a way to be useful to them. Also, we had backlog grooming. I should make one of my goals for next year to be "get this process to suck less."
  • Wednesday - Sprint planning was weird. There was a lot of carry-over from the previous sprint, one team is being reassigned to another product, and most of us are going to be on vacation for at least one week at the end of the year. This whole sprint is going to be cleaning up carried over tickets for a release early next week. I suppose that's a decent way to end the year, clearing the books of work in progress.
  • Thursday - Created a GitHub account and ran through their little tutorial. If I'm going to learn more about code next year, this toolkit seems like a necessary component. This is the time of year when I tend to get over-ambitious, but I suppose that's better than the reverse. 
  • Friday -  People have already started vanishing from the office; I suspect next week is going to be incredibly quiet here. I have documentation to finish up for Monday's release, and a post or two to work on.

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