Only one specialist can change the parking-meter firmware, so every firmware story waits on that person. What should the Scrum Master/Team Coach coach?
Select an answer to reveal the explanation.
Short Explanation
One meter tech with the only key is a single point of failure downtown. Pair, share the key, grow collective ownership. Queuing a month of firmware or hiding it on a private board just makes the line longer.
Full Explanation
Knowledge silos are both a quality risk and a flow bottleneck: parking-meter firmware that only one specialist can change waits whenever that person is busy. Pairing and collective ownership spread the skill and reduce single-threaded delay. Queuing work, outsourcing without learning, or a private specialist board preserve the silo. The Scrum Master/Team Coach should treat knowledge sharing as built-in quality work.