Is customer value your mainline quest?
If your project were in an RPG, would your mainline quests be delivering value? Or do you have to do that on side quests?I was recently sharing a story about a project I was working on where there were many bureaucratic obstacles to delivering value.
“You can’t create a pull request until you have a Jira ticket.”
“You can’t get a Jira ticket assigned until the next Sprint.”
“You can’t get access to the service logs without special approval.”
And on and on.
Your project sounds like a complex RPG (Role-Playing Game) where you get insight into how most “average” development teams talk and work.
LOL.
The only problem?
The mainline quests have nothing to do with delivering value! They’re all about navegating bureaucracy. The side quests are where work is actually done!
How does your team fare in this regard? If you were in an RPG, would your mainline quests be delivering value? Or do you have to do that on side quests?
