This morning I watched a really great key note from Uncle Bob about how test driven development is very important to a language, not just in terms of writing clean code but as part of an professional approach to project delivery and relations with the wider industry.

In summary, Smalltalk was an amazing language but its community built walls to keep out the rest of the industry and did not accept that they needed tools to keep their work maintainable through testing (TDD).

I hope you enjoy this 1 hour keynote as much as I did: RailsConf 09: Robert Martin, “What Killed Smalltalk Could Kill Ruby, Too”

Thank you
@jr0cket

---

This work is licensed under a Creative Commons Attribution 4.0 ShareAlike License, including custom images & stylesheets. Permissions beyond the scope of this license may be available at @jr0cket

Edward de Bono devised a simple thinking system called 6 thinking hats which defines how you can approach a problem without descending into argument. Here is a quick guide to using this very effective technique.

Read More

My notes from Confessions of a Kanban Virgin - Chris Pitts - Thirsty Bear Software - principle consultant and M.D.

Chris was coaching a team that was using scrum towards a leaner approach using Kanban.  At the time Chris had no experience with Kanban and learned to see the potential of the team as they tried it out.

When Chris arrived, something was not quite working right with the teams Scrum approach and kanban seemed a more relevant approach. Here is what Chris did to try support the team in their efforts.

Read More

A summary of the Acceptance-test driven development talk presented by John Smart, principal consultant at Wakaleo Consulting - held at Skills Matter by the Agile Testing user group on 11th February 2010.

Acceptance testing is a a key agile practice, especially in practices such as behaviour driven development (BDD) and test driven development (TDD).

Read More

For what is seen as a lightweight practice, there are a large number of techniques that help an agile team be successful.

Most people are aware of extreme programming, pairing, test driven development and more.  Very few teams I have worked with had experience of the more creative and collaborative practices that make an agile team successful.  Here are some examples of techniques I introduce that are often missed.

Read More

My current reading list is loaded with some highly recommended books on Lean System thinking and the theory of constraints. There are a lot of cross-concepts between these two areas and its been good to compare the ideas together.

Read More

Over the last few years I have learnt a number of techniques that introduce lean system thinking into running development projects. This is a summary of the techniques I have found useful and examples of how I have applied them.

Read More

It is not uncommon in IT projects that you are required to learn something on the fly or you see an opportunity to introduce a new technique or tool that would bring great benefits to a project.

How do you manage the learning curve required for something new without major impact to the project?

Read More

Having an inquisitive minds is a great thing but there can be a tenancy to be interested in too many things that you never learn something deeply enough. How do you stop the inquisitive monster in you mind and get on with just one thing?

Read More

In a Linked in post, someone asked if its possible to be both lean and agile. I think it is possible and this is what I replied:

If you are considering the value of the activities and your deliverables within your process, be that an agile process or not, you are starting to tend towards lean. How far you go towards lean depends on how much introspection you do and how much you act on the results.

Read More