I think this section of the post could definitely be expanded on:
It’s important to have developer buy-in. Their passion for a feature can be a huge driver for velocity.
This is why I also appreciate PM tools that incorporate discussion threads: that back-and-forth communication really helps clarify what you're building. I also like using the 5 whys after the initial spec has been written: "Why are we building this feature?"
Yah if I understand why you want me to make this thing it makes it much easier to make said thing. It also helps alleviate the generally poor acceptance criteria because if you told me your intention I can fill in the grey area with my best guess on how that feature should work.
I think of all the stakeholders, the boss (CEO, chairman, etc.) is the only one who is higher than the developers on the list of who has to buy into the project.
3 comments
2 u/mijustin [OP] 12 Jul 2015 02:45
I think this section of the post could definitely be expanded on:
This is why I also appreciate PM tools that incorporate discussion threads: that back-and-forth communication really helps clarify what you're building. I also like using the 5 whys after the initial spec has been written: "Why are we building this feature?"
1 u/LargoUsagi 12 Jul 2015 04:18
Yah if I understand why you want me to make this thing it makes it much easier to make said thing. It also helps alleviate the generally poor acceptance criteria because if you told me your intention I can fill in the grey area with my best guess on how that feature should work.
0 u/jasotastic 12 Jul 2015 21:58
I think of all the stakeholders, the boss (CEO, chairman, etc.) is the only one who is higher than the developers on the list of who has to buy into the project.