At Crosstide, we recently hosted a live webinar on agentic software development, and a key question that came out was, what does all this actually mean for delivery management? AI is changing how fast teams can produce work - and that shift changes where delivery leaders need to focus their attention. David Titterton was joined by our Technical Director, Steve Thompson, and our Delivery Director, Paul, to dig into the wider topic of agentic engineering and delivery.
We had an engaged group of participants who took part in quick-fire polls and kept the chat buzzing with questions throughout. Here's a look back at the session through my delivery lens, with the key snippets, stats and takeaways.
We ran three quick-fire polls during the session:
The increased throughput of work from using AI tools, has resulted in a much higher cognitive load on all team members including Delivery Managers. This points back to the age-old challenge of too much work in progress, which has now amplified due to everyone’s concurrent AI chats!
"Those sort of delivery problems we tried to solve before - limiting work in progress and increasing throughput - I feel like that's shot through the roof now. So the context switching, the cognitive load, I think a lot of these things are contributing to some of that stall, some of that plateau." - Paul, Delivery Director
Whether AI adoption in your organisation is stalling or not, it’s a good time to remember the agile phrase, “stop starting and start finishing” to keep teams focused on sustainably delivering value.
"Engineering has been a very... easy, but a very direct way of implementing AI to get certain points of value. But it's everything that's around it - discovery, testing, release - that's the real opportunity now." - Steve Thompson, Technical Director
A core pillar of Delivery Management is connecting the dots between different aspects of the overall software development ecosystem. The use of agents increases the need for this facilitation and building the connective tissue between the stages, teams and individuals involved in the software development lifecycle.
A shared maturity model keeps everyone pointed the same way. From individual tool use, through team workflows with shared context, to systemic, governed value - knowing, objectively, where a team sits makes the next investment clearer. A consistent view on the maturity level of teams today, vs what advanced maturity looks like is key in showing a team where they can get to. This also allows key leadership and delivery roles to help progress the team along the maturity curve, by empowering them, creating opportunities and sourcing support and upskilling.
Measure as you go. 58% of attendees told us measuring AI's impact on their SDLC is still on the to-do list. A simple set of delivery metrics - cycle time, WIP by stage - often shows the balance between cognitive load and a sustainably higher work output.
Delivery Leads will generally be monitoring metrics anyway, to understand delivery flow and health. AI can have an impact on the delivery efficiency of a team. However, how much of an impact, whereabouts the impact is and whether the impact is long-lasting, will all be up to the team to decide and factor into their AI implementation. Delivery leads can increase the visibility of these metrics and share the responsibility for improving them with the wider team.
A big thank you to everyone who joined us live, asked questions, and took part in our polls - it made for an energising session.
If you'd like to talk through what AI and agentic delivery means for your software delivery lifecycle, or would like a copy of the full recording, I’d love to continue the conversation - just get in touch with me at anikh.subhan@crosstideconsulting.com.