Whether we're writing code, manufacturing a product, or providing a service, most of us are contributing to the production of work whose completion may become dependent on others from time to time. While Lean-Agile frameworks seek to address this challenge in many ways (which include best practices around work breakdown structure and the creation of fully cross-functional teams), dependencies will remain a pragmatic reality for many complex environments.

Dependencies will often manifest themselves most clearly when we somebody shares they are unable to finish a task for piece of work "until my teammate (or some outside area) gets to their part.”

ScrumDo allows users to easily signal and capture metrics around work that becomes blocked from within a work card.  

How Do I Block a Card in ScrumDo?

Just open the card that is currently being blocked. Click the “block” icon along the top menu bar.  This will open a new window asking you to provide a reason for the blocked designation. 

Click on the "Block" button after entering your reason and the card will now be flagged as blocked within the system.  

Upon closing the card and returning to the board, you will now see an orange border around the blocked card. 

Once the block is resolved, either you or one of your teammates can remove the blocked designation by opening the card and clicking on “Resolve” within the Blocker area.  The system will again prompt you for a reason as to why the block designation is being removed.  Enter your reason and click on the “Resolve” button to remove the signal.  Three things will happen: the original blocker will be crossed out, the resolution will be detailed on the card, and the orange border will disappear. 

Blocker Clustering Report

While it's great to have the ability to create visual signals around your blocked work, what's even more powerful is the insights that can be gained from analyzing your “Blocker Clustering” report in ScrumDo.  This report will produce data related to all the blockers that satisfy your report criteria, how often they happen, and their average impact.  This data will be most meaningful if you establish and follow some standard conventions around the details your enter for reasons and resolutions.

Did this answer your question?