Although Scrum was intended for management of software development projects, it can be used to run software maintenance teams, or as a general project/program management approach.

Scrum is a “process skeleton,” which contains sets of practices and predefined roles. The main roles in Scrum are:

1. the “ScrumMaster”, who maintains the processes (typically in lieu of a project manager);
2. the “Product Owner”, who represents the stakeholders;
3. the “Team”, a cross-functional group of about 7 people who do the actual analysis, design, implementation, testing, etc.

Here is my collection of Scrum resources in the world wide web:

• Scrum (development) @Wikipedia – (that’s where my Scrum introduction text is basically from )
• Scrum 4 You — Scrum, Thoughts and more by Boris Gloger – one of the european Scrum Guru’s
• Scrum Alliance – as official as it can get

Here are some articles I find very interesting:

• 10 Things about ScrumMasters
• 10 Things about Product Owners

Next week I will attend the Certified ScrumMaster training in Munich, done by Boris Gloger. So more posts about Scrum are about the follow this one.