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
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
"...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
… 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
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 […]
Notes from #AgileManc -- mostly to jog my own memory, but might be useful for others too
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 […]
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! 😊
<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>
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
Links from Agile cross-team collaboration session @AgileManc #AgileManc:
-Collab Work https://www.smharter.com/blog/2022/08/08/agile-cross-team-collaboration-how-tos-long/
-Shared Work https://www.smharter.com/blog/2022/11/21/transcending-agile-cross-team-collaboration-with-shared-work/
-Feature Teams primer https://featureteams.org/
-Team topologies https://teamtopologies.com/
-Scaling XP: Dependencies, Kent Beck: https://tidyfirst.substack.com/p/scaling-extreme-programming-dependencies
-Taming dependencies, see point 2: http://p2.fed.wiki/view/practices-and-patterns-for-the-product-and-the-delivery-initiative
-Unwinding the dependency spiral, Principles 2) and 3) http://p2.fed.wiki/view/part-1-unwinding-the-dependencies-spiral
-Collaborating at scale, Principle 5)
http://p2.fed.wiki/view/part-2-collaborating-at-scale
Continuous Improvement
1% per day is a 38 times improvement over a year
— James Clear
@WoodyZuill #agilemanc