Why We Don't Do Daily Stand-Ups at Supercede An Article by Jezen Thomas jezenthomas.com Yesterday I worked on the widget. Today I will work on the widget. I have no blockers. Are you asleep yet? The developers are. You promise them an intellectually stimulating work environment and what they end up with is drudgery. What value can be had from these meetings anyway? Using “alignment” for justification is so nebulous that it is essentially meaningless. Engineers align themselves. They talk. Especially if you hire good ones (which, you know, you’ll struggle to if you have a culture of coercing them into this kind of busywork). Where does the real discussion happen? It’s written down. Why we stopped breaking down stories into tasks agile
Viability, usablity, feasibility In an empowered product team, the product manager is explicitly responsible for ensuring value and viability; the designer is responsible for ensuring usability; and the tech lead is responsible for ensuring feasibility. The team does this by truly collaborating in an intense, give and take, in order to discover a solution that work for all of us. However, in a feature team, you still (hopefully) have a designer to ensure usability, and you have engineers to ensure feasibility, but, and this is critical to understand: the value and business viability are the responsibility of the stakeholder or executive that requested the feature on the roadmap. Marty Cagan, Product vs. Feature Teams svpg.com What went wrong? teamwork