Why, If, and How to Transform your Organisation

Richard Cornelius


Half-day workshop - in English

Agile transformations** don’t have to be a based on a traditional framework. In fact every organisation will have a different context based around existing culture and the value proposition, so why should we state that a few frameworks can fit every scenario. Does this mean that these models are all wrong and should be discarded, or as famously stated by George Box “"All models are wrong, but some are useful".

During this workshop we will be using a structured approach to allow attendees to build and describe their own agile structures, asking such questions as “WHY or even IF we should be doing Agile?”; “What purposes do we want to achieve?”; “What are our limitations”; “How do we structure the work?”; “What are the risks and how do we minimise them?”.

As mentioned previously, agility is heavily context driven and so there is no intention of ‘teaching a single way’ rather attendees will be facilitated through their own personalised learning journeys. The outcome is to enable quality conversations and structure outside of the conference and back in the real world of work.

It doesn’t matter if you’re part of product development; delivery; compliance; security or a corporate CEO, everyone has a valid perspective as long as you have a desire to see and implement positive change.

** PS. Personally, I don’t like the word “transformation” as it denotes a fixed & known end scope of work (which also then has the assumption that this is easy, which it isn’t), however I have used it here as it’s currently more commonly understood than words such as “continual learning organisation”.



Primarily for: Developers, Tester/test leads, Project managers, Architects, UX specialists, Security professionals, Product developers, Managers, Scrum masters, Agile coaches, Designers, Others

Participant requirements: Just themselves