BT

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?

Agile Architecture - Oxymoron or Sensible Partnership?

by Shane Hastie on  May 14, 2010 9

A number of commentators have been talking about the perceived dichotomy between Agile techniques and architectural thinking. This post investigates some of the tensions between Big Up Front Design (BDUF) and You Aint Gonna Need It (YAGNI) thinking and looks at how the two approaches can in fact work together in complimentary ways.

Harmonizing Agile With "User-Centered Design"

by Mike Bria on  Mar 17, 2010 6

UX specialist Anthony Colfelt presents a case for how agile, alone, might not be sufficient and a thorough and engaging look into how User-Centered Design can, and should, be merged with it.

Emerging Industry SOA Best Practices

by Boris Lublinsky on  Mar 10, 2010 4

A new MITRE whitepaper documents a variety of best practices and key characteristics for a successful SOA implementation.

Continuous Deployment, In Practice

by Mike Bria on  Jan 27, 2010

Continuous deployment has gained a recent buzz in the Lean-slanted "eliminate work-in-progess" movement. But while many may find this an intriguing and logically worthwhile objective, many less can visualize how this might actually be achieved. Ash Maurya helps to fill this gap by describing his experience with making it happen at his company.

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.

Refactor or Rewrite?

by Vikas Hazrati on  Nov 24, 2009 10

The goal of refactoring and rewriting is to improve the sanity of the system by improving the code readability, structure and clarity. A clean code would be easier to maintain and enhance. However, on many occasions Agile teams have a tough time deciding between the two.

Forrester Releases Free Research Report on Lean for Business

by Deborah Hartmann Preuss on  Oct 01, 2009 1

Forrester Research, in preparation for their Business Technology Forum next week, has released an analyst report for free download, entitled "Lean: The New Business Technology Imperative." Aimed at management, it discusses Lean as a whole-business imperative, and its impact on IT, cautioning: "Don’t get so caught up in eliminating waste that you forget to create value and increase flexibility."

The Minimum Viable Product - a tool for exposing value

by Shane Hastie on  Aug 31, 2009 5

In a recent interview on Venture Hacks (Advice for Entrepreneurs) commentator Eric Ries discussed the concept of the Minimum Viable Product (MVP) – doing “just enough” to meet customer needs in order to get a product THAT PEOPLE WILL PAY FOR to market as soon as possible.

Comparing Value, Velocity and Value Velocity

by Vikas Hazrati on  Aug 04, 2009 1

An implicit assumption made by most Agile teams is that 'value' is directly proportional to the 'velocity' of the team. While this may be true in some cases, however mostly, the team velocity gives little indication on the true value delivered.

What is Velocity Good For?

by Amr Elssamadisy on  Jul 06, 2009 4

A recent discussion on the ScrumDevelopment Yahoo! group discussed the different uses and misuses for velocity. Should velocity be used a metric for productivity? Should it be used for iteration planning? What about longer term release planning?

Stop and Refactor?

by Amr Elssamadisy on  Jun 15, 2009 2

When should you refactor? There are times when you simply need to pay down technical debt - you should stop and refactor. No, you should only refactor when one is working on a User Story. Which advice is best? Is there, perhaps, a third option?

What does Quality Mean?

by Mark Levison on  Apr 22, 2009 5

Is quality supposed to mean a lack of defects that are holding us back? Mike Bria, Lisa Crispin, James Bach and JB Rainsberger debate the meaning of quality and the limitations our current definition is placing on us.

Achieving Agility Needed for Business Survival

by Shane Hastie on  Mar 06, 2009 1

An increasing number of organizations are embracing Agile development as a survival tactic in these turbulent economic times. This in turn has lead to a number of pundits examining what attitudes and attributes their teams need to be successful. Business agility is important, but how is this agility achieved?

Being A Better Product Owner

by Mike Bria on  Mar 04, 2009

Anyone who has spent any time on an effectively executed agile project can attest to the fact that the Product Owner's (or, in XP, the "Customer's") collaboration with the development team plays a key role in the success of a team. Peter Stevens offers a bit of advice to help people in these roles do this well.

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