Friday, April 26, 2013
I had an interesting experience today with the help desk at the company I currently am trying to help. It was so interesting; it inspired me to write a small blog post on it!
One of the things I like about Agile is the core concept of asking WHY. Asking the "why" about everything is a critical first step on many Agile journeys, and it is a step that when skipped, will lead to interesting results. In addition to asking why, one of the things we want to try to be able to do is be helpful. I know I wrote about the negative side of this, but my experience deals with the exact opposite. In fact, if I could summarize the experience I would do so as being a victim of the Ticket mentality.
Wednesday, April 24, 2013
Today we have a guest Blogger, and this is his first try at this. I'd like to present +Todd Azbill and some thoughts on his current role change...
I am currently a Scrum Master for two teams on a short-term project. I am also new to Scrum Mastery. During my transition, my manager pulled me in to a meeting where he asked me if I was planning to continue coding…
…I’ve actually given this a lot of thought. On one hand, I don’t want to lose my technical skills. They've gotten me where I am. You could almost say I’m defined by them, right? At the same time, I don’t want to be the best Scrum Master I can be. Doesn't that mean the teams deserve my full attention?
Sunday, April 14, 2013
One thing I have noticed working with developers over the years is that they are very helpful people. So helpful, in fact, that sometimes they help themselves right into a corner. And in a modern organization, they have infinite possibilities to get in just such a bind and find themselves with no one to help them out of it!! This is only one of many ways people have found to work with Agile to be able to change the scope of the story/project/program they are working on. In this case, it is the face of friendship that can cause issues – in other cases; it is not quite as benign.