By Udayan Banerjee | Article Rating: |
|
June 18, 2009 01:02 AM EDT | Reads: |
1,382 |

Though I am a strong believer in Agile Methodologies and I very much subscribe to SCRUM, I always get a feeling that a product backlog does not give the full picture of the expected product and we need something more to define it.
Let us first look at how product backlog is prepared?
- You start with either a business problem or a product idea – and you decide to build a piece of software
- You probably write a very high level specification of what the software should do
- A product owner is identified who breaks up it up into multiple stories on how the user is going to use the software
- Stories are prioritized and build one by one
- At each stage the software is reviewed by product owner – and any required course correction incorporated
- Once all the stories are completed the product is ready
Essentially, what we are doing is:
- Define the problem
- Break it up into smaller parts
- Solve each one individually
- Put it together and hope that it solves the original problem
Yes, I know we iterate – and in theory iteration is suppose to reduce the gap between “is” and “should be”. But the big question is do we accurately know the “should be”?
That brings us to the debate between “Designed Solution” vs. “Emergent Solution”. We all know that Linux has emerged – that Wikipedia has emerged. However, what we forget is that for a good solution to emerge we need to try out many alternative and select the best. Here is an interesting quote from The Cathedral and the Bazaar by Eric Steven Raymond
“…you often don’t really understand the problem until after the first time you implement a solution. The second time, maybe you know enough to do it right. So if you want to get it right, be ready to start over at least once”
In a commercial situation, how often do you have this luxury? How often can you try out multiple ways of doing the same thing?
What is the alternative? To have somebody who understands the problem and understands what the solution should be. The product owner is supposed to be that person (see this).
However, this only means that the solution will be as good as the product owners understanding of the problem.
Does this not tilt the solution to “Designed Solution” rather than “Emergent Solution”? Does it not put too much responsibility of the shoulder of the product manager?

Published June 18, 2009 Reads 1,382
Copyright © 2009 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.
More Stories By Udayan Banerjee
Udayan Banerjee is CTO at NIIT Technologies Ltd, An IT industry veteran who started his career in 1977, he has 32 years' experience in the IT industry. He blogs at http://udayanbanerjee.ulitzer.com and has created open-source frameworks for Model-Driven Software Development and Rich Internet Applications. He has a special interest in collective intelligence arising out of self-organizing complex systems.
- The Essential Guide to Better Release Management & Deployment
- Who’s Gonna Buy Novell?
- Management Solutions for the Cloud
- Red Hat Strikes Deeper into Amazon
- Red Hat Enables Enterprise Cloud Usage by Leveraging Amazon Web Services
- NTT Powers Cloud Service with Red Hat Enterprise Virtualization
- Oracle Introduces Oracle Communications Data Model to Provide Actionable Insight for Communications Service Providers
- Spring Cleaning: Innovate, Validate, or Get Out of the Way!
- Hong Kong Broadband Network Enhances Data Warehouse System With Oracle Communications Data Model
- Surplus PC Power Yields Faster Cancer Research
- Cloud Expo, Inc. Names Carmen Gonzalez CEO
- Red Hat’s KVM Virtualization Steals Spotlight
- FalconStor Announces HyperFS™ File System for Media and Entertainment Market
- The Essential Guide to Better Release Management & Deployment
- Who’s Gonna Buy Novell?
- Adaptivity’s Mike Tardif to Discuss the Science Of IT Design in the Cloud
- Commercial Add Ons to Open Source Software: aheadWorks and Magento
- UEC: Bundling Linux Image
- links for 2010-04-07
- If You’re Saying Goodbye to Your Server, Bring Some Tissue
- Liquavista launches Display kits to enable customers to develop application & designs
- General Telecom Announces RouteNGN’s Expanded Least Cost Routing Capabilities
- Virtualization Conference Keynote Webcast Live on SYS-CON.TV
- Red Hat Drops Consumer Linux, Sponsors Community Led Fedora Project
- Citrix & Dell Partner on Server Virtualization
- The Top 250 Players in the Cloud Computing Ecosystem
- Red Hat Named "Platinum Sponsor" of Virtualization Conference & Expo
- Red Hat CTO Keynoting Today on The Future of the Virtual Enterprise
- Red Hat vs Sun Battle of Words Heats Up
- Forbes' "Red Hat = Linux" Spin Angers Sun Microsystems COO
- SOA, Virtualization and Web 2.0: BEA's Deputy CTO Connects the Dots
- Getting Started with Red Hat Linux
- Red Hat to Deploy "NX" vs Viruses
- AJAX in Enterprise Portals