Extreme programming is great in that it recognizes that at any point there is *so much we don't know*.
-
-
Replying to @stubbornella
"What is the min we can do to measure what to do next?" Is a great question. So is, "how will we know if we're succeeding?"
1 reply 20 retweets 53 likes -
Replying to @stubbornella
But 100% pairing is FUCKING AWFUL. I need time to think & reflect to do my best work. Then answer to "I don't know" is not hands to keyboard
9 replies 55 retweets 196 likes -
Replying to @stubbornella
Some of extreme programming was born out of a consulting model and straight up doesn't work for product teams. eg 3 mo. rotation is insanity
7 replies 9 retweets 27 likes -
Replying to @stubbornella
100% of time spent working from a backlog is also horrid. People need breathing room. Engage creativity and not churn out keyboard monkeys.
9 replies 108 retweets 185 likes -
Replying to @stubbornella
I also think work actually needs planning (not just the next sprint).
8 replies 16 retweets 48 likes -
Replying to @stubbornella
The (not so dirty) secret of agile is that many PMs are actually planning out work in advance, they just pretend to constantly adjust.
5 replies 42 retweets 104 likes -
Replying to @stubbornella
I agree waterfall is terrible. It is best to get designers, engineers, etc collaborating to solve hard problems. But waterfall is a strawman
4 replies 7 retweets 36 likes -
Replying to @stubbornella
I also wish waterfall was just a strawman. I've seen it argued with a straight face in tech companies in 2016.
1 reply 0 retweets 1 like -
I thought so too. I won't tell-all on Twitter but some of the cases are shocking.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.