We have 3690 guests and 24 members online

Video Spotlight

Home > Blogs > Featured Blogs > Plan and Deliver > Agile Anti-Practice: Delegating Product Ownership without the Vision

Agile Anti-Practice: Delegating Product Ownership without the Vision

Written by Peter Schuh   
Monday, 23 February 2009 11:02

Vision - or the lack of communicated vision - is a problem I’ve been trying to tackle on multiple teams for the last several months. The specific problem is caused by Product Owners (or Customers) who do not have a vision for the system they own.

It’s not that there isn’t anyone in the organization who has a vision for the system–that’s often the Product Owner’s boss. Rather, the troubles start when the boss delegates responsibility for product ownership but doesn’t take the time to instill that same individual with his or her desires and dreams for the system.

And what is the result of this failure to delegate vision with product ownership?

  1. Teams focusing on less, and even unimportant, features such as sophisticated admin functionality that only benefits Product Owner.
  2. An undercurrent of doubt within that team that the development path is not directed toward an overarching, understood, and meaningful goal. (This undercurrent will, at best, draw away productivity and, at worst, foster team-wide infighting over the development direction.)
  3. A completed system that does not deliver business value.

In one word, it’s waste.

Agile Anti-Practice: Delegating Product Ownership without the Vision

Read Full Article
Author:Peter Schuh

Comments (0)Add Comment


Write comment

You must be logged in to post a comment. Please register if you do not have an account yet.

busy
 

Agile Marketplace - Announcements and Special Offers

Webcast:  Moving Build and Code Quality Upstream
This interactive panel discussion moderated by Bob Aiello, Editor-in-Chief fo the CM Journal brings industry experts Anders Wallgren, CTO of Electric Cloud and Gwyn Fisher, CTO of Klocwork together for a candid discussion of the cost savings, productivity and quality benefits that can be achieved by stabilizing builds and code quality as early in the development cycle as possible.
Register Now!

Collabnet -TeamForge 5.3
CollabNet TeamForge 5.3 includes Dynamic Planning—providing flexibility to model release scope and timeline in a single view. Now, you can easily manipulate/adjust release data.
Download Your Free Trial

Requirements-based testing (RBT) can help to ensure comprehensive test coverage, reducing the risk of failure and improving software quality. This white paper details how application lifecycle management can be used to more effectively implement RBT processes, offering greater collaboration, traceability and control.can help you increase efficiency, reduce project risk, and improve overall software quality. Learn how MKS Integrity for application lifecycle management enables RBT, delivering full lifecycle traceability to help ensure that project requirements have complete test planning and execution coverage.
Download the Requirements-Based Testing whitepaper

PureCM –SCM for Agile Teams
PureCM helps you to manage development in short iterations: keeping track of changes, supporting automated builds and preserving frequent snapshots of your projects.
Get the free trial now