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.

Presentation: Prioritizing Your Product Backlog

Posted by Geoffrey Wiseman on Oct 06, 2008

Sections
Process & Practices,
Architecture & Design
Topics
Agile ,
Delivering Value ,
Agile Techniques
Tags
agile2008 ,
Management ,
Planning
Choosing the right features can make the difference between the success and failure of a software product. Mike Cohn presented 'Prioritizing your Project Backlog' at Agile 2008 on how a project backlog should be organized and prioritized and non-financial techniques for prioritization such as kano analysis, theme screening/scoring, relative weighting and analytic hierarchy process.

Watch Prioritizing Your Product Backlog (75 minutes).

Pascal Van Cauwenberghe commented on the presentation:
Essentially, the process works on the theme level. Applying it to stories is too much work and is often meaningless to business users. When we work on a theme, we have to split them in stories and redo the exercise because not all stories in a high-scoring them have a lot of business value or are necessary to realize the theme’s business value. Overall an excellent presentation with good visuals, some exercises and practical advice.

If you'd like a hardcopy, Mike Cohn has released a PDF of his presentation.
hardcopy by Jesse Stockall Posted
Re: hardcopy by Ralph Poellath Posted
Re: hardcopy by Geoffrey Wiseman Posted
  1. Back to top

    hardcopy

    by Jesse Stockall

    Most of the links, including the PDF download are not functional

  2. Back to top

    Re: hardcopy

    by Ralph Poellath

    The PDF of Mike's presentation can be found
    on his website.

  3. Back to top

    Re: hardcopy

    by Geoffrey Wiseman

    Fixed.

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.