Product & Engineering coach. Recovering software engineer, father, husband, home improver. Some skills better than others. Opinions are my own. He/Him.
This reminds me of a point brought up when writing our "Measuring Value" paper for @ITRevBooks last year... when an IT org considers itself and its goals distinct from its business peers...
"If IT wins but the business loses, is that still success?"
Answer here. 👇
Just heard of a utilities government company that is going bankrupt after their IT arm went all-in on Scrum and SAFe, rewrote a billing system, and that billing system got delayed long enough that they could not collect revenue, and ran out of money.
Oh man.
Just heard of a utilities government company that is going bankrupt after their IT arm went all-in on Scrum and SAFe, rewrote a billing system, and that billing system got delayed long enough that they could not collect revenue, and ran out of money.
Oh man.
@age_shulman@RealGeneKim This got me...
"these [issues] are operational implementation issues and not related to the overall Workday contract performance metrics."
The vendor project metrics look great. What? No, we weren't measuring whether the software solved an actual problem. That's crazy talk...
@dustinson I've not had this problem. But then again, I usually have a conversation with my manager first if I'm planning to submit a talk about something work-related to make sure it doesn't include sensitive IP.
"Once we understand the overall direction we are trying to go…as well as where we are today…we can then figure out the next target goal we want to reach. With this, we will focus on a couple of tools to help us: an Outcome Canvas and OKRs…"
Read more: https://t.co/X9KQqzxPqo
@scottsauber Apologies for the self-promotion, but I helped co-author a paper this year on this problem of articulating value in IT. Hope it helps others.
https://t.co/vgOYaV0Ayw
@editingemily This was an amazing talk @editingemily! A great combination of raw personal story, historical truth bombs, and an inspiring call to action. 👏
Thank you for sharing this with the rest of us.
@age_shulman There's definitely a time element to it, as well as an org culture element. (e.g., is cross-team collaboration discouraged, tolerated, or encouraged?)
https://t.co/csS1pKpXtP
@age_shulman I think COEs are useful for exploring or starting up a new capability (because that is their charge). But, as part of their charge, they should help stand up CoP(s) as soon as possible, owned by passionate advocates beyond the COE, to help make the new capability sustainable.
🚀 New 0800-DEVOPS #54 is out - I talked with 🎙️ @nathenharvey about the DORA community, the inaugural DORA Summit, and the freshly published 2023 State of DevOps Report!
https://t.co/HBn1b0GPQb
#DevOps#engineeringmanagement#leadership
@ikrnic@nathenharvey Great episode and insights @nathenharvey and @ikrnic! I loved the soundboard analogy and the double-click into the report insights this year!
I've been taking a break from work for the last few weeks, so missed much of the brouhaha over the McKinsey developer productivity article. But I'm sure that I could not write a better response than this one from @tastapod
https://t.co/3PlzZ37kgb