BT
x Your opinion matters! Please fill in the InfoQ Survey about your reading habits!
rss

Knowing if You Are Building the Right Product

by Ben Linders on  Jul 10, 2014

Developing and delivering products which customers don’t want and for which there is no market can be costly. Agile can help you to efficiently develop products, but you need to know what to build. How can you find out which products your customers need?

Balancing Experiments and Deliveries in Product Development

by Ben Linders on  Feb 06, 2014

Experimentation using for instance lean startup can help you learn about your customers and find out which features and product would be valuable. The value however comes from building products and actually delivering them to customers. You need to find ways to balance between experimentation and delivery.

Remove Waste From Your Backlog with the Priority Game

by Ben Linders on  Jun 24, 2013

The priority game is an exercise which Michael Franken did at the GOTO Amsterdam 2013 conference, to make large backlogs manageable. He showed how Scrum can help you to focus and remove waste by not making things that are probably never used by customers.

Should You Create User Stories for Technical Debt?

by Ben Linders on  Mar 21, 2013 11

Agile teams sometimes struggle with the planning of pure technical tasks that have no direct value for the user of a system, but have to be done to deliver working software. Should you create user stories to handle such technical tasks and technical debt, or not?

Survey Confirms Biggest Agile Challenges Are Communication and Continuous Improvement

by Craig Smith on  Oct 13, 2012 3

A new survey, conducted by Serena Software at the recent Agile 2012 conference in Dallas, Texas has confirmed that whilst projects using Agile are working well, they could be much better and some of the biggest challenges include upsteam and downstream communication.

How to prioritize tasks based on their value

by Marta Jasinska on  May 18, 2012 2

Bob Marshall in his new blog post, "The Value", summarises his research on different methods of prioritisation. Together with Grant Rule he developed a new way of understanding team and company goals.

Individual Yield

by Christopher Goldsbury on  Dec 28, 2011 6

Tony Wong, a project management blackbelt, enumerates some practical points on individual procutivity. This article wonders how well these apply to software development and contrasts his list with that of other lists.

Application Lifecycle Management in Team Foundation Server 11

by Jonathan Allen on  Sep 15, 2011 1

Team Foundation Server 11 has added many features in the area of Application Lifecycle Management. Some of the highlights include support for code reviews, iterations/sprints, resource allocation, third part testing frameworks, and a much more capable dependency graph.

How to Convince the Product Owner to Prioritize the Backlog?

by Dan Puckett on  Dec 13, 2010 4

Scrum works most effectively with a prioritized product backlog. Prioritizing the backlog is part of the product owner role, but what can you do when your product owner won't prioritize the backlog because he or she doesn't see the value in prioritization?

Estimating Business Value

by Chris Sims on  Jan 04, 2010 2

The traditional agile approach to prioritization is that user stories of higher business value should be implemented before ones of lower business value. The concept is simple, but implementing it well relies on having a mechanism to assess business value. Pascal Van Cauwenberghe has recently described an approach to defining business value, called "Business Value Modeling", which may help.

Story Mapping Gives Context to User Stories

by Chris Sims on  Mar 23, 2009

The Scrum notion of 'backlog' is a single, prioritized list of user stories for the team to implement. This works well for organizing what the team should work on in the near term, e.g. during sprint planning. At the Orlando Scrum Gathering, Jeff Patton described story mapping. This is a way of organizing stories that provides richer context and can help with release planning.

Presentation: Extremely Short Iterations as a Catalyst for Effective Prioritization of Work

by Abel Avram on  Sep 24, 2008 1

Mishkin Berteig presents a situation where he proposed to a software development team, which just started to experiment with Scrum, to accept 2-days iterations. The approach was trying to tackle their organizational lack of prioritization resulting in constant crisis. Their decision led to a bigger crisis which exposed the need for task prioritization.

General Feedback
Bugs
Advertising
Editorial
InfoQ.com and all content copyright © 2006-2014 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT