Wed. 9th Aug: Ian Carroll on How long will it take? How much will it cost? + John Le Drew and The product owner is an agile anti-pattern + Ian Lister with Cynefin A Gentle Introduction

Post date: Jul 26, 2017 8:44:31 AM

One of the nice things to have witnessed over the last few years is the growing number of people regularly speaking on lean / agile topics across and based in the north of England. With a slight change to our normal format this months gathering is a showcase of talent with three speakers all from our region. Ian Carroll runs Lean Agile Manchester and we've been trying to coax him along for some time, John Le Drew ran an excellent session at Agile Yorkshire on safety a few months and hosts the Agile Path podcast and Ian Lister is making his debut appearance. Hope everyone is having a great summer and see you in a couple of weeks.

Bio: Ian Carroll is a consultant, coach, and speaker on all topics related to Lean, Kanban and Agile software development. Using his 25 years of hands-on experience he helps clients transform their organisations using Agile & Lean techniques to lower costs while increasing their ability to respond to changing market demands and outperform competitors. Ian has trained and coached hundreds of software development teams in Agile, Lean and Kanban techniques.

Twitter: @IanCarrollUK Website:

Ian Carroll - How long will it take? How much will it cost?

The two questions that have haunted development teams since the beginning of 01/01/1970. In this session we explore the fear associated with deadlines, milestones, and commitments and how to turn this fear into positive focus to embrace the constraint. We introduce a new estimation technique to help you to manage expectations more effectively.

We will discuss questions like:

- What is actually the role of the product owner?

- Why do we discourage 'hero' developers but encourage 'hero' product owners?

- How do we know what the right thing to do is?

- Can the whole team engage in product ownership?

See John's website for more details of John's talk.

Bio: John has spent most of the last 2 decades working in the software industry, with a focus on web technologies. After 10 years as a software engineer John moved into consultancy where he quickly learned the value of team dynamics and how most technical challenges are projecting underlying issues with collaboration. So his focus shifted, while still being very involved technically, his first focus is on facilitating a safe, creative, collaborative environment. John also produces The Agile Path podcast

Twitter: @antz29 Website:

Ian Lister - Cynefin A Gentle Introduction "Ever wondered why the world works the way that it does?

This is gentle wander through the foothills of Cynefin the complexity framework, which has recently gathered a lot of momentum in the Agile and lean communities.

Remember Context is King!

Bio: Ian has been in IT since last centenary, its indoor work without heavy lifting so coming from a family of Durham miners he counts himself very lucky.

He has worked in a variety of roles in that time, from Support Analyst to Oracle DBA, from Developer to Development Manager, before settling on being an Agile Coach and Scrum Master as a way of being able to do what he loves doing outside work, as an FA and ECB coach as his day job.

Ian has worked for a variety of organisations such as, HBOS, Bankwest, Close Brothers, NHS Digital and Vodafone to mention a but few.

He spent 7 happy years working for Bankwest in Perth, Western Australia, which is where he started his Agile Journey and learnt to surf before his wife made him come home, he’s over it now though.

Twitter: @idlister Website:

John Le Drew - The product owner is an agile anti-pattern

While business knowledge and domain expertise is useful and essential, is this only achievable with a 'single wringable neck'? What would happen if the whole team could be encouraged to take ownership of product direction?

This session looks at how we have often created dysfunctional relationships with our product owners through both the way we collaborate (or don't) with them and the language we use to talk about the role itself.