The following is an excerpt from a recent presentation I did on Agile and Coldfusion - the subject of this excerpt is Vague Requirements.   more »

there are many teams who would say they run iterations or sprints when in fact they are running increments or phases and therefore missing out on the real benefit of iterations or sprints   more »

I hope this helps to convey that boundaries and structure do exist in the agile process. In order for it to work properly agile needs to be just as disciplined as any other software development process so as for those who feel “agile is a bit to ad-hoc” or “a bit too loose” – maybe they don’t understand it well enough.   more »

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

Once a User Story has been added its possible to start entering Confirmation notes immediately   more »

Once a User Story has been added its possible to start entering Conversation notes immediately   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 »

If a team wants to become agile it must have a reason for wanting to do so - there must be something not going to plan - something broken about the process - or just a desire to perform better - the team can only know if this is a success by measuring it - just a little.   more »

I would point out that the product backlog isn't much more than a list - and is only going to be as complicated as you make it   more »

I'll be planning to release the first full version in late June early July and this will contain the first deployment from the 'Add work flow basics to CCC' project. Before I start the development I'll post so that you can see what I've got in my sprint and why I left some things until later.   more »

A bux fix has been released on the beta version of CardConversationConfirmation.com today.   more »

Next comes Work Flow; the processes or the stages, indeed the lifecycle of a User Story from its initial conception to its deployment on the production platform.   more »

Using structured user stories in the form AS A, I WANT TO and SO THAT offers a greater agile benefit to the data that represents the requirements without adding in too much additional data to supply the structure - it gets the balance just right on ceremony.   more »

A new project can be be added at any point and there is no limit to the number of projects the user can create.   more »

This weekend I've released the first beta version of my new agile tool at CardConversationConfirmation.com - and its completely FREE to use.   more »

... a challenge when there are dependancies on another team, in another organisation, who are not running an agile project. How should these types of dependancies be managed effectively while maintaining an agile sprint orientated approach at home?   more »

There are many software development teams who are working in an ad-hoc way and are desperately looking for improvements in the processes that define their working lives and their business - here will be benefits for the developers, the management and the customer.   more »

Card Conversation Confirmation is described by Ron Jeffries as the three critical steps of User Stories. If there are any development teams looking for that magical balance between cycle and ceremony in their processes Card Conversation Confirmation is at the heart of the answer. Add into this Planning Poker and you've got all you need to implement a lean software development team - its a Software Development Lifecycle, in a nutshell. Hopefully this can be read as a journey of self discovery for the team and the individuals that make it up too.   more »