This summer is been frantic! We're rearranging our dev team (one of them has already arrived and the other going to do it soon), released two games more (we can't say anything yet but you'll get news soon) and testing one new methodology for out project management: SCRUM.

It's a long time since we're using eXtreme Programming as development methodology, especially in our Battlewizard team, but planning, managent and tracking matters have been untidier than development side. So with Juan Palacio's help we're working out with SCRUM and now we're completing our sixth sprint (:

SCRUM is a auto-management team methodology, that is: there isn't a manager who cries commands and the others obey, but the team should be auto-managed.

Well, that's right and auto-management looks great but it's quite difficult to apply. Don't try to use this methodology at any company, because I know some of companies and people who will turn it in a true failure.
Just two days ago, Joel Spolsky has published a set of articles about team management, and he tells us there're three typical categories of management inside companies:

• Command and conquer: the boss tells what must be done and the others do it. This is the anti-SCRUM pattern. Team should be auto-managed, without external commands.

• External motivation: it's tried to motive people with rewards, bonuses, etc. It doesn't fit with SCRUM because we'll get people more concerned about getting prizes and bonuses instead of improve its own work.

• Indentity: it's tried to identify people with company's goals and philosofy, with a clear and fluent communication. When people understand whole company goals, it will be easy for them to make right decisions about their own work, without managers have to decide for them.

So first advice: do not try to apply SCRUM at any place. First obtain a good working environment and then everything will be easier.

Next, you have our experience about some SCRUM sides we're using here at Unkasoft:

• Product backlog
• Product owner
• Sprint
• Daily meeting
• Sprint backlog
• SCRUM and eXtreme Programming