<<< Previous speaker next speaker >>>

Dan North, Agile troublemaker, developer, originator of BDD

 Dan  North
Dan writes software and coaches teams in agile and lean methods. He believes in putting people first and writing simple, pragmatic software. He believes that most problems that teams face are about communication, and all the others are too. This is why he puts so much emphasis on "getting the words right", and why he is so passionate about behaviour-driven development, communication and how people learn. He has been working in the IT industry since he graduated in 1991, and he occasionally blogs at dannorth.net.

Presentation: "From months to minutes - upping the stakes"

Time: Wednesday 10:35 - 11:35

Location: Elizabeth Windsor, Fifth Floor


So you've made the shift from thinking in multi-year project delivery to releasing every quarter, or even every few weeks. You rock! Then you meet a team that delivers enterprise-grade software every few days, sometimes even several times in the same day, to delighted and engaged users. 

What's their secret? Is it the team? Their leadership? Their technology choices? Their methodology? Is it the organisational culture? Or is it just a massive fluke?

Find out what makes a genuinely hyper-performing team tick (and how to survive in one!) and pick up some tips to move your teams towards one day delivery cycles.

Presentation: "Agile Operations - optimising the business one shell script at a time"

Time: Wednesday 15:35 - 16:35

Location: St James’s Suite, Fourth Floor


Building software used to be the bottleneck. The delays and hand-offs between groups meant you could go literally years without any delivery. Then came Agile with its co-located teams, automation, feedback and collaboration, which meant we could deliver quickly and respond to changes in business direction.

For a lot of firms freeing this bottleneck exposes the next constraint: getting things done across the organisation. They are structured according to a hierarchy which directly opposes the flow of value through the organisation, meaning more hand-offs and more delays.

Agile Operations combines Lean thinking and Agile development practices to addressing this constraint. In this talk, Dan introduces Agile Operations using real examples of refactoring business processes to achieve dramatic improvements, and describes techniques you can apply to your own situation. There will be shell scripts.

Tags: lean, agile, operations, automation, continuous-delivery, process

Training: "Secrets of Agile Architecture"

Time: Tuesday 09:00 - 16:00

Location: Elizabeth Windsor, Fifth Floor


We architects love a good framework. We like our abstractions, we like to design "enterprise" solutions, we like to mandate complex algorithms, or better yet to prescribe toolkits to enable other teams to implement complex algorithms under our expert guidance. If it looks like a good idea we slap the label "pattern" on it and tell everyone to do it.

Ok, maybe that isn't you. But it's likely you work in an organisation where the other guys do. So what can you do about it? Is this the only way to do architecture?

This tutorial looks at strategies and techniques to incrementally architect your way out of a legacy mess, and to set up new applications for success.

During this one day tutorial you will learn, among other things:

* the joys of a strong domain model, and how to evolve one.
* how to use an anti-corruption layer as a border guard.
* to get over your dependence on dependency injection frameworks.
* not to have interfaces for everything.
* that you can incrementally replace legacy apps more often than you realise.
* how to successfully decouple subsystems.
* the value of getting into production early.
* not to fear integrating with third party libraries.
* the courage to automate the things you should, the serenity to accept the things you can't and the wisdom to know the difference.
* why "transfer object" is an oxymoron, and how to do remoting properly.

More importantly, you will learn to doubt what your experience is telling you, and instead to focus what's really there. Maybe.