Scrum and Control…What?
Scrum is all about NOT being in conventional control and still getting things done, fast and more effectively.
Today, Blogger, Author and a friend, Tanmay Vora wrote an interesting post that conveys a similar point – How NOT to be in control.
Tanmay talks about three important points:
- Positional Power.
- Staying on top of the information and
All the three points are nicely conveyed. Read Tanmay’s full post here.
An effective implementation of Scrum also touches upon all three points that Tanmay mentioned.
In Scrum, there is no positional power. People who get things done are in control of their own work and the software is developed collaboratively with the loosely defined guidelines that are based on tightly subscribed principles.
Staying on top of the information is the key success driver for a Scrum team. In Daily Scrum Meetings, this becomes evident.
Take any successful Scrum project and you will find a common thing – excellent communication among the team members. No communication, no Scrum. It is covered in the basics. Individuals and interactions over processes and tools.
Many a times, people ask me: Why is Scrum your favorite weapon in the world of software development? My answer is simple – It is the most logical, getting it done kinda framework that doesn’t depend on mere rules and controllers of those rules.
Scrum relies on principles more than rules…and I have always chosen principles over rules and have never regretted.
Scrum rocks. People doing right kind of Scrum also.