Home Of The Kanban Jedi
Beyond Agile Software Development

Posts Tagged ‘Lean

User Stories Don’t Deliver Business Value

April 17, 2009

User stories tend to focus on the user not on the business value. I think it’s largely to do with the popular “As a <insert type of user> I want to <insert thing to do here> so that <insert reason here>” format. This more formal wording of user stories takes longer to think about and […]

Never Let The Customer Forget

April 9, 2009

So no matter how hard you work and how much stuff you deliver I’ve always been amazed at how easily the customer forgets what you’ve done when things aren’t going so well or they can’t get what they want (*enter customer stomping feet and throwing tantrum*). So one thing I’ve had teams doing over the […]

Whole Team Stand-up

April 9, 2009

I’ve lost track of what people are saying is best practise for stand-ups nowadays. I know what works for me and the teams I’m working with and one of these things is including your stakeholders/customer. Don’t just include them but actually have them answer the same questions as the team. My experience has been they […]

Software Development is a Team Sport

April 8, 2009

So recently I heard of a team that is using Scrum and their manager had decided to have a “Person of the Iteration” award for the person that completes the most points in a Iteration. I think this totally misses the point of Agile being a team of people working together to get as much […]

Scrum & Kanban – Compare and Contrast

April 8, 2009

Henrik Kniberg has put together a good article on the similarities and differences of Scrum & Kanban here: http://blog.crisp.se/henrikkniberg/2009/04/03/1238795520000.html On the whole a pretty good article. I don’t fully agree with the section that talks about using estimates if you need predictability. Estimates are simply a prediction of the future but real predictability comes from […]

Priority Tokens

March 25, 2008

I met up with Karl Scotland just before Easter for a chat about our experiences with Kanban systems and whilst reviewing his information radiator we talked about the idea of having numbered priority tokens for each of the WIP limit slots as a way of keeping teams focussed on priority, even for the work actually […]