News for hackers. Stuff that matters.
Re:How to Build Deep Focus Into Your Organizational Culture by lockedoutwhoops on Saturday October 01, 2016 @07:26PM (#12620364)
Interesting. Who puts the tasks in? How do engineering and product work together to prioritize short term business value vs long term business value?
Re:How to Build Deep Focus Into Your Organizational Culture by wpietri on Saturday October 01, 2016 @11:45PM (#12620965)
I'm sure people do it many ways, but here's my approach:

Anybody can put a story in. (A story is some shippable unit of work that creates business value or otherwise improves things for some user.) Once a week, the team (by which I mean a cross-functional group of people committed to delivering value together, in the Balanced Team style [1]) sits down and talks about what should happen next.

This happens in the context of some agreed-upon set of long-term goals. In a startup, that's usually clear. In larger companies, a process like OKR [2] is a good way to make sure that a team has a clear purpose that meshes with the rest of the org.

The only hard rule is that the product manager has the final say on backlog order. But that's a power that should be rarely used; disagreement is usually a sign that people understand things differently, and that's worth sorting out. Often disagreements are worked out by proposing experiments. Questions of short- and long-term get worked out dynamically; in sane environments people are pretty good at striking that balance.

[1] http://www.balancedteam.org/

[2] e.g.:http://eleganthack.com/radical-focus-is-here/