If you’re not familiar with SCRUM, it is a very powerful set of principles and methods that empower teams to deliver increments of a product in a more reliable and productive way. This means using short cycles of development while gathering constant feedback and adapting to eventual changes in product vision or customer needs.
This article is a sum of terms and concepts about SCRUM, extracted from Jeff Sutherland‘s book Scrum: The Art of Doing Twice the Work in Half the Time, to help beginner users to solidify the key parts of SCRUM in an summarized way. If you’re already a pro user, skip to the end! There is a nice SCRUM joke there 😉
#1 – Teams
When it comes to speed, most of the time, manpower is not the answer. If you’re not moving fast enough, focus on developing your team and your system instead of adding more people to the project.
One famous term in software development is the Brooks’s Law (book “The Mythical Man-Month”):
Adding manpower to a late software project makes it later
– Small teams get work done faster than big teams (Magic number is seven people with plus or minus two)
– Teams must be cross-functional and independent (They must have all the resources needed in the team and be autonomous to make decisions and move fast)
– Focus on team performance instead of individual performance
– Blaming is stupid. Look for the bad systems instead of looking for the bad people (Sometimes bad systems reward bad behaviors)