The (not so dirty) secret of agile is that many PMs are actually planning out work in advance, they just pretend to constantly adjust.
-
-
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
Just because waterfall is bad doesn't mean all aspects of Agile/Extreme are healthy.
3 replies 26 retweets 79 likes -
Replying to @stubbornella
Pure agile finds local maxima. If that's all you need, pure agile is all you need!
6 replies 14 retweets 35 likes -
Replying to @stubbornella
Good code is architected. It is NOT enough to just TDD. Writing a failing test doesn't substitute for having a good think before you begin.
30 replies 496 retweets 678 likes -
Replying to @stubbornella
What works from extreme programming? Feedback loops. Retros, every damn week. If you don't talk about what worked/didn't, you won't improve.
3 replies 50 retweets 110 likes -
Replying to @stubbornella
What else works from Agile/extreme? Really clear product requirements for eng, delivering small chunks of functionality. Defining success.
4 replies 23 retweets 77 likes -
Replying to @stubbornella
what works from non-agile techniques? Trusting engineers and designers to solve problems/deliver business value without micromanaging.
12 replies 32 retweets 98 likes -
Replying to @stubbornella
So maybe we need a backlog of clearly defined stories, but anyone on the team can request other stories or ask to go off roading. ;)
7 replies 7 retweets 30 likes -
Replying to @stubbornella
still figuring it out... & with that, the baby woke up. To be continued... (my research/thoughts about this, perhaps not the tweet storm)
7 replies 0 retweets 14 likes
thanks for sharing! 
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.