Week in Review #5

As expected, this week has been pretty challenging.
  • Monday - Got some unexpected news regarding career planning. That's going to take some thinking about. More candy contributions arrived! I'm happy to see this -- not because of the benefit to me (I would stock the stuff regardless), but because it indicates a level of consciousness about others' efforts that will hopefully manifest within their teams as well.
  • Tuesday - Sprint review and retrospective. I wasn't able to be involved in the individual team retrospectives this time, but one team member approached me to raise some concerns about communication on his (distributed) team. I have some ideas for a few of them, and will probably also discuss them with our coach. My Twitter feed was highlighted in a departmental mailing today, which was a little nerve-wracking to anticipate; however, while a few people responded with positive comments, on the whole it was a non-event. Lesson: Don't sweat.
  • Wednesday - Sent out the notes from yesterday's cross-team conversation. Velocity is down for two teams (way down for one), when it had finally stabilized for the previous few sprints. This is a concern. Sprint planning was frustrating; there was uncertainty over which stories were going into an upcoming release, and other stories had not been fleshed out well enough for the team to accept them.
  •  Thursday - A valuable lesson in how sometimes things work themselves out without me needing to pitch a fit about them. Not thrilled with how that new project is being organized, but we'll see how it goes. Communication remains a challenge with our distributed group.
  • Friday -  Coming to the end of a notebook, threw out a lot of notes that have passed their useful period, moved some items to a backlog.
Hopefully next week I'll have time to get back to reading and research. It hasn't been all bad, but I'm very tired.

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