InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

An Agile PM Walks a Mile in a Customer's Shoes

Posted by Deborah Hartmann Preuss on Nov 02, 2007

Sections
Process & Practices,
Architecture & Design
Topics
Customers & Requirements ,
Stories & Case Studies ,
Delivering Value ,
Agile
Tags
Contracts & Negotiation ,
Business/IT Alignment ,
Agile2006
Alexia Bowers, COO of Ternary Software, has lead numerous projects at Ternary, including managing and implementing custom e-commerce sites in Java and JSP, developing applicant tracking systems for Fortune-100 clients, and managing and developing large-scale web applications within the pharmaceutical industry. For a change, last year she played the role of customer (a.k.a. Product Owner), and told us how it felt in this Agile2006 Leadership Summit presentation, entitled Leading From A Position Of No Power: A Customer’s Perspective of an Agile Team.

Her lessons learned included: to clearly maintain the customer role, i.e. carry the vision and the "why" of things; not to shy away from conflict, but to use it constructively; and to be actively involved in the project, even though the customer has no real "power" over execution. She emphasised that the inevitable conflict between product and development should be channelled into finding better, faster ways to do things - instead of just a war over In-scope or out-of-scope.

The presentation sums up with advice for project participants:

Advice for Customers:
  • Be involved, not just present
    • Work with the rest of the team to get business value met
       
  • Expect good customer service
    • Ask for it if you aren’t getting it
       
  • Treat the rest of the team with respect
    • We are all working together
       
  • Ask your technical folks to tone down “techno-babble”
    • Get them to learn the business value vocabulary
Advice for Programmers:
  • Keep customer involved (but not micromanaging)
    • Give the updates & high quality info for decision making
    • Ask about business value, remember business value!
       
  • Avoid “techno-babble,” talk in terms of business value
     
  • Expect respect & provide good customer service
    • Remember where they are coming from
    • Help them get what they need
       
  • Encourage your customer to maintain the business value focus
    • Be sure to understand the business value of a solution.
View this 30-minute InfoQ exclusive presentation: Leading From A Position Of No Power: A Customer’s Perspective of an Agile Team with Alexia Bowers.
  • This article is part of a featured topic series on Agile

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.