Posts Tagged lean

This is not a manifesto: Valuing Throughput over Utilisation

In a previous article, This is not a manifesto, I expressed the values I hold as a software development team member. Today, I’m going to talk about the first of these values. Before I do, I’d like to say what I mean by “software development team”. I mean a cross-discipline team with the combined skills [...]

, , , , , , , , , , ,

2 Comments

This is not a manifesto

Recently, I had cause to ponder the values I hold as a member of a software development team. Values that, alongside other values I hold, drive my choices and behaviours. They sit behind the things I do and how I do them. They underly my thinking when considering how we can improve as a team [...]

, , , , ,

4 Comments

To hack, or not to hack

Recently, Engadget reported that Nokia had decided to abandon MeeGo in favour of Windows Mobile. What was interesting is the reported process used to make this decision: Elop drew out what he knew about the plans for MeeGo on a whiteboard, with a different color marker for the products being developed, their target date for [...]

, , , , , ,

1 Comment

A bit of UCD for BDD & ATDD: Goals -> Tasks -> Actions

There’s something wrong with many behaviour specs (or acceptance tests). It’s been this way for some time. I’ve written about this once or twice before, referencing this post by Kevin Lawrence from 2007. So, first things first, I want to take this opportunity to update the terminology I use… Goals -> Tasks -> Actions A [...]

, , , , ,

2 Comments

From Scrum to Kanban – good and bad reasons to switch…

This originally appeared on my old blog in February 2009. There are, IMHO, some good reasons and some bad reasons to consider switching from Scrum to Kanban… or for considering Kanban over Scrum as a starting point for ‘going Agile’ (so to speak)… ‘Good’ reasons for considering Kanban are… Wanting/needing more visibility of specific development [...]

, , , , , ,

1 Comment