Dan North, Agile troublemaker, developer, originator of BDD

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.

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.

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:

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