|
I think it solves a problem we have (if my understanding of your product is correct): We should focus less on the future and more on the present and past. That will save time and make for better progress evaluation. In our team, we're managing upcoming work by epics, features, user stories and tasks (TFS style), all ahead of time. For the latter two, ages are spent estimating, in the process having feelings about risks. We're left with a bunch of tasks that only partially describe what we eventually realize needs to be done, leading us to choose between sticking to the tasks, thus producing a nice burndown chart, or doing what's best for the project. For our team, the devs just want to know if we are spending our time in the best way possible: 1) What are we going to focus on today? Not completing, just focus on. That's mostly enough to align efforts.
2) What did we focus on yesterday, and can we evaluate progress? Steady? Slow? Stuck?
3) What did we actually end up focusing during the past week? Did we side track often or have to change direction? However, without the future aspect, management probably wont bite, making this a tough sell. So maybe consider something that marries the two: Some high level future planning, breaking work down to epics and features only, and some focus tracking for daily alignment and performance evaluation. |