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'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 »

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 »

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 »