...the word concentric assits the concept that all the processes in agile "have a common center" - that being quality and delivery...   more »

A problem that can often occur in planning poker is a stalemate situation - i.e. the same cards are played by each player for more than one round without a consensus being reached   more »

If you're involved in planning and managing software development read this book and it will alter your mind.   more »

If anyone plays a ? card this should be taken as an indication that they have something important to say and therefore should be given the floor first in that round...   more »

As a general rule in planning its good to employ practices that mitigate against presumption influencing reality and this is well illustrated by the success that Planning Poker can bring to the software development process.   more »

In previous articles in this series I’ve discussed how to pull together a simple agile approach based around Card Conversation Confirmation. In part 5 I want to illustrate how this can be introduced in a traditional lifecycle.   more »

The customer usually wants to see a plan as early as possible - it’s a reasonable request and its perfectly ok to do this providing the communication of the plan and its risks is carefully articulated and the pros and cons of the method are clearly understood by all. The key to mitigating the cons coming into play is to have a poker game with the senior management from both the customer and supplier.   more »

Clients who want to be confident about a schedule to deliver an agreed set of functionality on time and within budget will benefit from the development team implementing standard deviation buffers...   more »