Wednesday, December 22, 2010

SCRUM: A better method to manage Flux

You have an idea. You can only throw a few pages (say, less than 5) about the concept. You need to drive down but need a navigator help. You are sure it can succeed when you dive in deep to make the idea a better proposition collectively.

You need inspiration from like minded people, time to acquire intelligence from your sources and to have a notion of success, develop it to see some action.

You may want to cut down your losses at some point, change directions, move around pieces of your idea/work in a different sphere, or get a new idea that transforms the current work for a better scale.

You may want to pause, go for funding, travel for roadshows, be a change angel and find what your critics, cynics and competitors think, say and act. You would want to move down a feature and include a fresh and new thought to get it to marketplace early.

When you want to start small in a dream big project or divide work into smaller chunks, SCRUM is a great way to queue up work and get them moving to finish. All of the above is feasible due to possibilities with following SCRUM features.
  1. With Sprint planning and Timeboxed iterations, you can refine, rewrite, replay, re-configure and pay for what your immediate goals are. Not to stretch to touch the horizon.
  2. With Shared Stories (better to call it this way, because you are not the only one to write it) and Sprints, it is easy to see early outcomes and refine the language to promote them better. You get to see the linkages not previously envisioned and hence add it to a long list of shared stories written from users view. They leverage the past experience, existing products and licenses that can make your reach to idea transformation faster.
  3. With Burndown charts and impediment logs, you get to know the roadblocks and hold a tighter control on the investment purse.
  4. With Stakeholders meetings, Sprint stand ups  and Sprint Retrospectives, you continuously improve on the service, timeliness, productivity and product quality.
So isn't SCRUM a better way to manage Flux ?



Top Agile Blogs