It is usually far less expensive to start fast and learn fast that we were wrong than to spend a substantial amount of time and money up front to ensure that we make the “right” decision, only to find out eventually that we were wrong.
Fail Fast
It is usually far less expensive to start fast and learn fast that we were wrong than to spend a substantial amount of time and money up front to ensure that we make the “right” decision, only to find out eventually that we were wrong.
[…]the ScrumMaster observes how the team is using Scrum and does anything possible to help it get to the next level of performance. When problems arise that the team can and should be able to solve, the ScrumMaster’s attitude, like that of any good coach, is “I’m not here to solve your problems for you; instead, I’m here to help you solve your own problems.”
The ScrumMaster doesn’t hire and fire and cannot dictate to the team what tasks it should do or how to do them. The ScrumMaster is also not responsible for making sure the work gets done.
Managers need to foster an environment where people are constantly learning and adding to their skill sets. They need to make it clear that learning is not only encouraged, but is in fact a priority at the individual, team and organizational levels.
Idle work is work that we want to do (such as building or testing something) but can’t do because something is preventing us. […] Many product development organizations focus more on eliminating the waste of idle workers than on the waste of idle work. […] In Scrum, we are acutely aware that finding the bottlenecks in the flow of work and focusing our efforts on eliminating them is a far more economically sensible activity than trying to keep everyone 100% busy.