3 ms·
Oh day to day blockers, especially when working on multiple things in parallel and you wait on someone else for some tasks. From our logs, some of our last few
by saidinesh5 4y ago
Oh day to day blockers, especially when working on multiple things in parallel and you wait on someone else for some tasks. From our logs, some of our last few blockers were:
1) Waiting for someone review and merge a pull request so something else that depends on that can be sent for a release.
2) Some architectural code changes that needed to be discussed with the person responsible for the module before i go ahead with the implementation.
3) Someone waiting on me to finish the CI setup so they can deploy their project
4) Us waiting on external client for more input, so our CEO can go nag them for more requirement updates.
5) Me hoping the someone can fix the frontend code because i was frustrated with my (lack of) CSS knowledge the previous day...
- randomdata 4y agoNone of those will come up at the beginning of the day. They are impediments that will only be revealed during the course of the work. Are people refraining from sharing important knowledge as it comes available so that they can grasp at something to share the next day, perhaps because reciting "no blockers" each day grows incredibly tiring? If so, how is that beneficial to the team being left in the dark for longer than necessary?