Previous PIs had a lot of "blocker" churn. A team would mark soemthign as blocked but not say what it was on or who was to fix the issues. generalvisbility into dependencies/blocks was poor and led to delays.
The Aggressive timeline for production deployment means delays will add up.
We should utilize hackathons/meetings to make sure we're moving forward or communicating effectively where the blockers are.
Blocked items are added to the dependency board to ensure they get visibility.
Actions
[ ] Link to issues or list of actions to take to mitigate the risk.
Service areas and venue dependencies
Previous PIs had a lot of "blocker" churn. A team would mark soemthign as blocked but not say what it was on or who was to fix the issues. generalvisbility into dependencies/blocks was poor and led to delays.
The Aggressive timeline for production deployment means delays will add up.
Actions
Associated Objectives