I spent 12 years at Amazon in leadership, and I spent 12 years repeatedly fighting off efforts to measure (and improve) our engineer's efficiency.
Below is my general view.
One of the main misapplications of Agile is jumping to the implementation part of the old SDLC ("waterfall") and breaking it into iterations, rather than condensing the whole SDLC into short iterative cycles.
Why do many modern teams & companies fail to achieve the clarity, progress, and results they so badly seek?
5 cognitive biases of modern organizations, a thread:
"We need to shift from a mindset where we design everything all at once and move toward a mindset of designing the smallest possible thing that can deliver value to our users."
— @lauraklein
https://t.co/R2vvuHcsrV
Newsflash: Monoliths aren’t bad. Poorly architected software is bad.
Newsflash #2: If you thought poorly architected monoliths were bad, just wait until you see poorly architected microservice meshes.
If you're looking for a product management refresher, check out this thread with the best quotes from the book 'Inspired: How to Create Tech Products Customers Love' by @cagan:
Most teams in business work to create a defined output. But just because we’ve finished making a thing doesn’t mean that thing is going to create economic value for us.
https://t.co/aszJIfDEfg
In the darker shadowland of agile, a user story has become nothing more than a numbered token for scheduling permission.
If you write what you want to do as a "story" then it will be assigned a number and might eventually be assigned back to you as work to be done.
Organizations are Agile, not teams or departments. The metric that matters is the rate at which you get value into your users hands. That involves the entire "value stream," which encompasses every step an idea goes through from conception to delivery (& maybe after). 1/4
Pair with your mentees, not to show what an expert you are, but for them to see how vulnerable we all truly are, that it is OK to struggle, to not know, and, in spite of all our flaws, to have the perseverance to figure things out.
Here's a thing I find weird in the monoliths VS. microservices discussion:
1. We get told monoliths are naturally badly structured (hint: they aren't, *naturally*). This allegedly is due to the fact that it's so easy to introduce unwanted dependencies between modules. 1/5
Agile transformations tend to make agile skeuomorphic, like fake kitchen drawers that don't actually open. Here's why.
#agile#design#strategy
https://t.co/wgJWFHPes3