Jul
12

Lots of session proposals

Oh no! Right again…

Only a few session proposals had arrived a few days ago. Lots and lots and lots of proposals came in the day of the deadline. Student Syndrome in action. I sent in my proposals an hour or two before the deadline. Useful things, those arbitrary deadlines 🙂

Some people needed a little coercion before proposing a session. Hosting a session at a conference can be a bit scary the first time. The next times it’s still scary, but at least you know that you’ll survive… I hope that reassures all those who proposed their first session.

A community such as the “Agile community” or the “XP Days community” needs to spend time finding new people, new ideas, fresh blood. There is a danger that many of the sessions at the various XP Days (e.g. in the UK and in Germany) are given by a small group of “Usual Suspects”. And many attendees will be familiar faces too.

On the one hand, this is great: it’s always nice to meet these people from all over the world, to discuss the things we’re passionate about or have a drink and a chat. I feel as if we’re pulling eachother up by our bootstraps.

On the other hand, we risk becoming a “closed club” discussing weird, “touchy feely”, “arty farty”, “namby pamby” stuff like Systems Thinking, Cynefin, Appreciative Inquiry, Congruence, Theory of Constraints. “How will this help me write better software tomorrow?“.

That is one of the challenges the program committee for XP Day faces: how to create a program out of those many great session proposals, that satisfies the needs of both beginning, intermediate and advanced attendees? Each one with their own unique preferences, environment they work in, challenges they face, answers they seek.

In a workshop on “Communities of Practice (CoPs) at SPA2005, we discussed a few patterns for creating, sustaining and growing communities. One of these patterns (note to self and Laurent: we must write these up somewhere), is called “CoPs Pull You In“.

If a community is to thrive it needs an influx of new ideas, new people. And yet, a thriving community can seem “closed” and “unapproachable” from the outside, because those inside have developed their own rituals, protocols, language and trust. Therefore, CoPs need to “pull in” new people. “Pull In” can be understood in two senses:

  • People inside the CoP need to make a conscious effort to help people outside understand what the CoP does, how it works. They need to assist people who want to enter the CoP, to introduce them to others, to show them how things work. We see this in (session proposal) writing, where people act as “shepherds” to help newcomers. Or we can assign a “buddy” to a new hire to make the entry into the organisation smooth and productive.
  • There must be something in a CoP that is attractive to the newcomers. A strong “attractor” that pulls people into the core. As someone at the workshop noted: “one can’t be pushed into a CoP that one doesn’t find attractive

How do you help people get “pulled” into the community? I do it by bullying people into sending in session proposals 😉

Jul
11

XP Day Benelux session review

Sessions are gushing in for XP Day Benelux 2005. There’s still a little time left to send in your session proposal.

We’re now organizing them on the session review site. Session reviews start in a few days.

Session reviews for XP Days Benelux are unlike most other conferences’ reviews, they’re more akin to an “Open space” process. The review process as we use it now, was first applied by Vera Peeters as Workshop Chair for XP 2005. It goes something like this:

  • Session proposals are collected on a wiki. Session organizers get access to this site.
  • Each session organizer is expected to review 3 sessions, distributing reviews in such a way that each session is reviewed by 3 reviewers. You are not allowed to review your own session.
  • A first round of reviews is held
  • Session organizers can update their proposals, based on the feedback they receive from their reviewers.
  • A second round of reviews is held, after which the final session evaluation is given.

We apply ideas from Oscar Nierstrasz’ Identify the Champion pattern language (specifically the Make Champions Explicit pattern): a reviewer scores the proposal using the following categories:

  • A: Good proposal. I will champion it.
  • B: OK proposal, but I will not champion it.
  • C: Weak proposal, though I will not fight strongly against it.
  • D: Serious problems. I will argue to reject this proposal.

A set of acceptance criteria has been established beforehand. Session reviewers evaluate how well the session meets the criteria.


This process uses several agile components:

  • All work is done in an “Open Workspace”, a wiki where reviewers and session organizers can exchange ideas and “overhear” each other’s conversations.
  • The process is completely open: everyone sees what you write, you see what everyone writes. Organizers and reviewers can communicate (through the wiki or offline) about the sessions, to ask questions, clarify unclear elements…
  • The review process is not confrontational, but cooperative: reviewer and organizer work together to come to the best possible session.
  • The process is iterative: session organizers can improve their proposals based on the feedback of their reviewers and their new insights. There are two rounds of reviews, and there are plenty of opportunities for small, incremental improvements to the proposals as questions and reviews come in. Your session proposal doens’t have to be perfect first time, there’s room for improvement.
  • There is a constant reflection (Hansei) and improvement (Kaizen) of the review process, by suggestions from participants and in a retrospective at the end of the process.
  • Acceptance criteria are defined beforehand, a “customer” (here: the reviewer) determines if the criteria have been met sufficiently.
  • Maybe not “agile” per se, but important for me: the process only uses “low-tech” technology: a wiki, email and a simple web form to submit proposals. Nothing too complex or restrictive, just enough structure to enable participants to collaborate effectively; not so much to stifle their creativity and communication.
Jul
10

XPDay sessions and Student Syndrome

Tomorrow is the deadline to send in a proposal for the XP Days Benelux 2005 conference on 17-18 November 2005 in Rotterdam.

As usual, lots of the session proposals came in today. And I expect even more tomorrow. Typical “Student Syndrome”. Most students start to study when exams are frighteningly close

I’m not immune: I haven’t sent in my proposals yet, I’ll do it tomorrow. There’s always tomorrow…

Luckily, we took this into account in our planning: session proposal deadline is July 11th. Session reviews start on July 15th. This gives us a bit of time to deal with the glut of proposals coming in.

How do you deal with Student Syndrome in your project?

Jul
09

XP Day Benelux Call for Sessions closing

Don’t forget to send in your session proposal for the XP Days Benelux 2005 conference on 17-18 November 2005 in Rotterdam, The Netherlands.

The Call for Sessions closes on July 11th.

I’m just about ready to send in my session proposal. Are you?