- We are frustrated because we are doing too many things at the same time (mostly felt by devs)
- We are frustrated because things get too long to be done (mostly felt by product team)
- limit work in progress
I dont think we are limiting work in progress enough in this project and that is slowing us down and creating the frustration mentioned above.
Very specific example:
- our #1 priority right now is the spree upgrade (WIKI - ordered delivery backlog (pipe-ready and in delivery)). if this is the case, we should have the full dev team on this one if possible until it is done. everyone.
the general rule is that if a team member is available and can help with #1 priority, that’s what she should do if she can help (it doesnt matter how many people are already “allocated” to the #1 priority, it only matters if the free dev can contribute positively to move #1 priority).
We have 2 devs that will have available capacity soon and it looks like as a group we are showing them priority #2 subscriptions and priority #5 mobile ready as possible tasks for them.
To action the opinion I share in this thread, all we have to do is to get both devs on to priority #1.
More specifically, we have to fix product import in v2 (https://github.com/openfoodfoundation/openfoodnetwork/issues/2791) and we have to fix subs in v2 (https://github.com/openfoodfoundation/openfoodnetwork/issues/2954)
Afterwards, we can go to the next priority items #2 and #5. but focusing on #1 is the most important, this way we become a lot more focused as a team, more knowledge is shared, we are less frustrated (see problem statement above), and velocity increases.
(this is not specific to any initiative in the list, this is applicable to any roadmap)