Friday, January 25, 2008

Attributes of a true Scrum Master

As per Tao Te Ching
The worst leader is who people despise, a good leader is who people worship. A great leader is he who makes people say "we overselves did it"

If you really look at the responsibilities of a true Scrum Master, he is supposed to be a great leader. One of the key responsibilities of a Scrum Master is to create a Self organizing team, where team is empowered to make decisions, lead the project towards the goal.
* A true Scrum Master(SM) won't spend time micro managing activities of the team and instead, he/she would be working towards creating a space for the team to express themselves.
* SM steps out observing the team, coaching them to move in the right direction. This process of empowerment ultimately makes the team feel possessive about the project and creates an image that "they" did everything.
* A true Scrum Master would stay as an angel not in the view of the team, but keeping a watchful eye on every movement of the team.

So, going back to the quote from Tao Te Ching, the Scrum Masters should not consider themselves as "transformed project managers" but work towards becoming great leaders, satisfying the true meaning of "Scrum Master".

Even though no body is born as a leader, I firmly beleive that some of the leadership skills could be developed by observing other leaders.

Tuesday, January 08, 2008

Agile world in the Top 20 Blogs

Agile Daily has rated my blog Agile blog in the top 20 list as the most recommended blogs on Agile development.

Here is what they say:
Sorted by Fastest Gain in SocialRank. These blogs had the biggest increase in attention today.

  1. Geek Noise
  2. ASP.Net
  3. James Shore
  4. Agile Advice
  5. Agile Game Development
  6. Jason Yip - Blog
  7. George Dinwiddie - Blog
  8. Agile .NET CT
  9. Agile Programmer
  10. Agile Israel
  11. Agile Software Process Improvement
  12. Me.Andering
  13. Diana Larsen - Blog
  14. Jeff Sutherland - Blog
  15. Agile Artisans
  16. Agile Blog
  17. TargetProcess
  18. Agile Project Planning
  19. Better Ways of Developing Software
  20. Agile Software Development blogs

Accountability and Productivity

I have been reading one of my favorite books Slack, and in one of the chapters on schedules, Tom brings up a good point about accountability and productivity. He mentions that

When a schedule is not met, those inclined to pass out blame are quick to
point at the lowest-level workers; they reason that performance is the domain
entirely of those who perform the work. They ask plaintively, "why can't these
guys ever meet their schedules" ? the answer that the schedule might have been
wrong in the first place only befuddles them.

He continues to say

There is such a thing as a bad schedule. A bad schedule is one that sets a date that is subsequently missed. .... If the date is missed, the schedule was wrong. ... The purpose of schedule was planning, not goal-setting. Work that is not performed according to a plan invalidates the plan.