{"id":661,"date":"2014-06-12T01:24:48","date_gmt":"2014-06-12T01:24:48","guid":{"rendered":"https:\/\/agilestaffordshire.org\/?p=661"},"modified":"2014-06-12T01:24:48","modified_gmt":"2014-06-12T01:24:48","slug":"lean-code-retrospective","status":"publish","type":"post","link":"https:\/\/agilestaffordshire.org\/retrospectives\/lean-code-retrospective\/","title":{"rendered":"Lean Code Retrospective"},"content":{"rendered":"

It’s great to consider concepts around a practical challenge. Lean code is best considered with a working example. It doesn’t take a complex\/large problem to highlight the issues and this session hit home. Paul Williams<\/a> gave a ‘lightning talk’ on Lean Code based on slides by Chris Parsons<\/a>, and quickly got us in front of our IDE<\/abbr>s and started the ‘Fresco’ challenge. To briefly explain, the challenge comprises a\u00a0fast cycle of iterations (about 10 minutes each), where each pair delivers the requirements as per the specification and acceptance tests.<\/p>\n

One might say the challenge is intentionally trivial, but it’s a great exercise\u00a0because it neatly encapsulates many of the challenges in software development; especially in a rapidly changing context. Producing some code to address the problem was relatively simple, but how about the Lean principles? For convenience, I list the points that the group\u00a0considered:<\/p>\n