Reminder: the Call for Sessions for next year's Agile Manchester conference in May is currently open: https://agilemanchester.net/call-for-sessions

/ @agilemanc.bsky.social #agilemanc

Call for Sessions

Our Agile Manchester 2026 Call for Sessions is open

Agile Manchester
Super Early-Bird tickets now on sale for May's Agile Manchester conference: https://agilemanchester.net/ - #agilemanc
Agile Manchester

Agile Manchester - practical agile, lean & flow programme – 13–14 May 2026

Agile Manchester

"...it's actually the sociotechnical aspects of delivering and operating software that are the most crucial, that the social and the technical cannot be easily separated." Sophie Weston

https://confluxhq.com/insight/social-and-technical-practices-for-fast-flow-insights-from-agile-manchester-2023

#agilemanc #FastFlow

Social and technical practices for fast flow - insights from Agile Manchester 2023 — Conflux

… it’s actually the sociotechnical aspects of delivering and operating software that are the most crucial, that the social and the technical cannot be easily separated. This was apparent even in Matthew’s opening keynote when talking about deployment pipelines and how often they mirror the team s

Conflux
Notes from Agile Manchester 2023 - Neil Vass dot com

I spent 3 days at the Agile Manchester conference, and had a great time – lots of interesting talks and workshops, plus lots of time to speak to people from all kinds of roles and companies. There’s plenty of ideas I’d like to think back over and put into practice. This post’s a prompt for […]

Neil Vass dot com

Notes from #AgileManc -- mostly to jog my own memory, but might be useful for others too

https://neil-vass.com/notes-from-agile-manchester-2023/

Notes from Agile Manchester 2023 - Neil Vass dot com

I spent 3 days at the Agile Manchester conference, and had a great time – lots of interesting talks and workshops, plus lots of time to speak to people from all kinds of roles and companies. There’s plenty of ideas I’d like to think back over and put into practice. This post’s a prompt for […]

Neil Vass dot com

Thank you to everyone who personally came to express their sympathy after my lightening and Meetup talk at #agilemanc 🙇😊

I truly appreciated that! Given I was shaking after the lightening talk.

That’s what I like about this community: vulnerability is valued.

The slides of my #agilemanc session

"From Bi-Annual to Fortnightly Releases in 4 months for 15 Teams and a Single Monolith"

Thanks to everyone attending the session. You were lovely! 😊

https://thinkinglabs.io/talks/2019/09/06/from-bi-annual-to-fortnightly-releases-in-4-months-for-15-teams-and-a-single-monolith.html

From bi-annual to fortnightly releases in 4 months for 15 teams and a single monolith

<p>15 teams, 1 shared monolith, 1 release every 6 months, and product demand for 1 release every 2 weeks. How do you know where to start with Continuous Delivery, when you’re surrounded by technology and organisational challenges?</p> <p>This is the journey of 15 teams and their 1 shared monolith, at a federal Belgian agency. They increased their throughput from bi-annual releases to fortnightly releases in under 4 months, achieving a state of Continuous Delivery.</p> <p>The cost and time for testing quality into the software product, stabilising and releasing the product during each bi-annual release were skyrocketing. The demand for Continuous Delivery was there, but the circumstances made it very difficult.</p> <p>I’ll cover how we used the Improvement Kata, Value Stream Mapping, and the Theory Of Constraints to choose which changes to apply first, and kickstart the organisational changes we needed to improve quality and drive down lead times.</p> <p>If you thought Continuous Delivery was just for the happy few having trendy microservices, think again!</p>

ThinkingLabs:: Thierry de Pauw

Time + Energy + Money = You give a fuck

Budget = limited amount of time, energy and money

What makes you happy? Keep in the budget

Be ruthless. Some things can be parked even though you like it.

Kindness is key!!!
So is honesty!!!

Sol Byambadorj (@SolByambadorj) #agilemanc

SmHarter insights Blog | Agile cross-team collaboration HOW-TOs (4-part)

SmHarter Blog

Continuous Improvement

1% per day is a 38 times improvement over a year
— James Clear

@WoodyZuill #agilemanc