I Hired a Certified ScrumMaster

June 26th, 2007 by Hal

Why would a lean projects guy hire a Scrum software development ScrumMaster? Short answer: it seemed like a good idea at the time. Seriously, I'm doing some work for an architectural engineering firm. The company focuses on designing technically sophisticated manufacturing facilities. We are developing for them a responsibility-based planning approach. It's starting out as a Scrum adaptation of the Last Planner System® (LPS). I thought…what better way to understand how Scrum can inform the changes to LPS than to perform our own development effort as a Scrum project.

Scrum is unlike the usual construction project.

We just started. We are almost done with the planning session. I'm the Product Owner, so I've been describing what it is that I want done in the first sprint of the project. While I've been following Scrum for five years, working on a project with a ScrumMaster has been challenging. So far, I really like the self-organizing aspect. The team negotiates with the product owner what will be included in the coming sprint. Then, the team decided who will do the work. But not all the work. Some of it stays in backlog until the first work is finished. One things for certain: Scrum is unlike the usual construction project.

The first sprint is 15 workdays. I'll continue to share my experiences as the project progresses.

Related Posts

Social Bookmarking
Add to: Folkd Add to: Linkarena Add to: Digg Add to: Del.icio.us Add to: Reddit Add to: Simpy Add to: StumbleUpon Add to: Slashdot Add to: Netscape Add to: Furl Add to: Yahoo Add to: Spurl Add to: Google Add to: Blinklist Add to: Blogmarks Add to: Diigo Add to: Technorati Add to: Newsvine Add to: Blinkbits Add to: Ma.Gnolia Add to: Smarking Add to: Netvouz Information

3 Responses to “I Hired a Certified ScrumMaster”

  1. Kevin Rutherford Says:

    Hi Hal, This is a really interesting article. I believe this is the kind of application for which Scrum is ideally suited. It brings a clear and simple structure to the process of developing something, and expects the application’s domain to provide the tools and techniques that will deliver value each iteration.

    I’ll be watching with interest as the experiment unfolds.

  2. Josh Nankivel Says:

    Keep us posted! My development team just starting using SCRUM, and so we’re working through the initial pains of it now.

  3. Hal Says:

    I will keep writing about this. Our Sprint is 15 workdays. With the holidays we finish sometime around July 19 or 20. The (building) architect on our team is quite enthusiastic about Scrum.

Comment On This

Note: This post is over a year old. You may want to check later in this blog to see if there is new information relevant to your comment.