This rant has been building up for weeks, so here goes..
It is my experience that XP does not scale, yeah, you can go through the motions but for large teams, say 10 developers upwards, all the practices make less sense and have to have more ceremony added onto them.
Once your project gets so large you need a dedicated project manager, think twice about using XP.
For me, XP is all about a team focussing around a their iteration plan and getting stuff done. Project managers are used to owning tracking progress against the plan and in trying to help they take it away from the team. The smells are that there is no up-to-date plan visible in the standup, progress updates start being gathered on a one-to-one basis and suddenly complex tracking appears and scope creep of the project becomes an issue.
Yes, this might be what you need to do to scale a project team up but it is not XP. It makes me sad to see people working on this type of project thinking this is what XP is like because XP should empower the developer team not be used to stomp on them
And I guess that's the end of my rant.
I have reviewed 80+ tutorial submissions for conference since Xmas and so would be glad not to see any more for a while!
Submitters often miss vital info from their proposals. They forget to explain how they are going to deliver the tutorial and leave their process description too vague to be able to assess if it can be done in the time. If you are planning a lecture style presentation then say so. Some interactive exercises may help but reviewers need details of these to assess their practicality and impact on timings. Saying "the tutorial is mostly hands-on" for developer topics is not enough, you need to say how this is going to be arranged (what computing equipment and software is assumed).
The best proposal I have seen this year was from a user-interaction specialist who had actually thought about what a reviewer of the proposal needs to be able to assess suitabilityfor the conference program.
News heard from Mike Cohn, the IEEE has announced they are starting development of an “Agile Software Standard.” see press release and the actual program is described here
Well, whatever will they think of next?