From 7f35a41f1dc9977802a241b43da25888a4965dc0 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Mon, 1 Jun 2026 12:48:20 +1000 Subject: [PATCH] Update a_shield_or_a_cudgel.mdx --- src/routes/posts/a_shield_or_a_cudgel.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/routes/posts/a_shield_or_a_cudgel.mdx b/src/routes/posts/a_shield_or_a_cudgel.mdx index 7e036f9..1609228 100644 --- a/src/routes/posts/a_shield_or_a_cudgel.mdx +++ b/src/routes/posts/a_shield_or_a_cudgel.mdx @@ -17,7 +17,7 @@ Using the scrum model, which nobody seems to talk about any more but was very po - to serve as an arbiter between the developers and the product owner - to serve as an unblocker for the developers, in terms of getting access to systems/resources, making sure the developers' dependencies are fulfilled etc. -In this later sense the delivery lead is on the side of the developers. The idealised picture of this is that the developers have a clear picture of what they're trying build, and what the problem they are solving (because the product owner has done their job), they've created a plan to get there, and now they can sic the delivery lead onto whatever impediments get in their way. The delivery lead hassles whatever admin needed to approve an access request, runs interference when a different part of the organisation tries to get this team to prioritise their piece of work, and resists external stakeholders expanding the agreed scope of work. +This latter sense has delivery lead being on the side of the developers. The idealised picture of this is that the developers have a clear picture of what they're trying build, and of the problem they are solving (because the product owner has done their job), they've created a plan to get there, and now they can sic the delivery lead onto whatever impediments get in their way. The delivery lead hassles whatever admin needed to approve an access request, runs interference when a different part of the organisation tries to get this team to prioritise their piece of work, and resists external stakeholders expanding the agreed scope of work. However, what I have seen more commonly is that the delivery lead becomes a cudgel against the developers. The reason this happens I think is obvious - the role of 'delivery lead' involves a good deal of stakeholder managment, with stakeholders outside of the feature team, and often senior stakeholders at that. It's likely a lot better for someone's professional reputation to be that person who can say 'yes' to these external stakeholders, than to resist them. It's likely also better for their own performance appraisal to be seen as someone who can be getting things done, rather than someone who is constantly saying 'no'.