SCRUM The Art of Doing Twice the Work in Half the Time
Jeff, the CEO of scrum develop a system of doing more work in less time. In his book, he shares the principle behind this system. The principle is based on the art of checking in on your team regularly to see if the work is being done and if it is headed in the right direction while ensuring the goal remains constant. Jeff explains that the process requires thought, introspection, honesty, and discipline.
Jeff encourages the need to plan but disapprove the art of following plans blindly. When detailed plans meet reality, they fall apart. Therefore it is essential to give room for an assumption of change discovery and new ideas. When executing the plans, pause at every stage and review what has been done to know if you are on the right path or if there is something you can improve upon. Change is adept. It is constant; you have to be flexible with your predictions so that you will not be left behind by an organization that is willing to adopt change. The author moved on by describing the origin of Scrum.
Scrum was inspired by the Japanese through the HBR paper published in 1986: “The New Product Development Game” by Hirotaka Takeuchi & Ikujiro Nonaka which highlighted the importance of cross-functional teams and faster, flexible way of working. The next chapter opens up what scrum is base on. Scrum is based on Teams. More resources make the team go slower. It is preferable to have a team that has every skill needed to complete a project irrespective of the set mission. Remember small teams get work done faster than big teams. The author did not stop at that, he went ahead discourage the habit of waste in a project. He explained the types of waste which are MURI (waste through unreasonableness), MURA (waste through inconsistency) and MUDA (waste through outcome) and then summarize it all by saying “do one thing exclusively before moving on to the next project.”
What in the beginning you thought you needed was never what you actually needed. Scrum breakdown its role into three. These are the product owner (what the work should be). The Scrum master (how the work should be done) and the team member( does the work). The product vision serves as the intersection of what can be implemented, what you are passionate about and what can be sold. Jeff says ”figure out where the most value can be delivered for the least effort and do that right away. Then identify the next increment after and then the next” Scrum can be used un any endeavor to improve performance and result. It accelerates human effort irrespective of the project or the problem being analyzed.
Finally, T.E Lawrence said “all men dream but not equally. Those who dream by night in the dusty recesses of their minds wake up in the day to find that it was vanity: but the dreamers of the day are dangerous men for they may act their dreams with open eyes to make it possible”.
The Big Three – KEY POINTS
Key point #1: Don’t guess. Plan, Do, Check and Act. Plan what you are going to do. Do it. Check whether it did what you wanted to act on it and be flexible with how you do things. repeat the process in the regular cycle to achieve continuous improvement.
Key point #2: Small teams get work done faster than big teams.
Key point #3: Choose the smoothest, most struggle-free way to get things done. Scrum is about enabling the most flow possible.
One Last Thing
“Multitasking Makes You Stupid. Doing more than one thing at a time makes you slower and worse at both tasks. Don’t do it. If you think this doesn’t apply to you, you’re wrong—it does.”
―