• 04Mar
    Categories: Agile Practices

    I’ve heard people say that scrum teams don’t have a heart.  We plow through backlogs with our heads down.  We finish a project.  We start another and plow through the next backlog.  Story, plan, task, sprint, demo, retrospect, repeat.  Story, plan, task, sprint, demo, retrospect, repeat.  Where’s the heart?  When do scrum teams look beyond these super focused iteration based tasks and think about innovation.  I agree with this assessment.  I think that agile and scrum teams can get stuck in this rut.  Well, we’ve all heard about the Google 20%…20% of time spent working on innovation.  I like that, but can most organizations really afford 20% of our time to do free thinking?  Probably not, we’re not all making billions of dollars like Google.  But that doesn’t mean we can’t do something about this dilemma.  Personally, I like something like a hackfest or hackathon.  Maybe after 6 weeks of focused development, your team gets a week to do some focused play.  A one week iteration…tell us what you’re going to work on…be innovative, do something cool and commit to it.  At the end of the week, same old same old…do a review.  Everyone DEMONSTRATES their cool idea.  Not a diagram, not a slideshow…demo something you can show us.

    I think that unless you’re completely dominant in your market space, you need to be doing something like this to keep you innovative and on the competitive edge.  It’s the old innovation curves again.  You want to always be anticipating or defining what the next thing is.  If you don’t, you slide down the laggard side of the innovation curve and risk becoming irrelevant.  If you slide down that curve, it’s very difficult to get back up to that next innovation curve.  So, give your teams time to innovate…it’s good for your organization’s future, it’s good for your customers, and it’s good for the professional growth and health of your development teams.

    image


    © Copyright 2007, ChrisSpagnuolo.com GeoScrum! by Chris Spagnuolo is licensed under a Creative Commons Attribution 3.0 United States License.

    Related posts:

    1. Mid-week Iterations A question I field frequently is “When should we start...
    2. The Daily Scrum: Scrum gratia totus I am the ScrumMaster on our current project, and...
    3. Scrum works, even for non-development GIS projects Try this: Go to Google and search on GIS Project...
    4. Agile/Scrum Elevator Speech This week I was asked to give an extremely brief...
    5. Scrum Basics Before I begin blogging about our Scrum journey, it is...

    Related posts brought to you by Yet Another Related Posts Plugin.

Leave a Comment

Please note: Comment moderation is enabled and may delay your comment. There is no need to resubmit your comment.