October 29, 2004

Iteration 1: Retrospective

Outcome:
Small first iteration, but I have managed to post a few things, so, take a look at the release 1 stuff, and leave your comments:

Measured Velocity: 7.5 points
Business Value Released: 15

What worked well:

  1. I found that I had quite a bit of time to do all the tasks I had to do
  2. Posted a few things (hope they are good)
  3. There are quite a few areas around XP that I find I have things to say about
What did not work so well:

  1. did not get any comments so far - the blog has been up and running for 2 days only!
  2. editing the posts is quite time consuming 'cause service is slow...
Puzzles:

  1. how can I publicise this blog to a widder audience without being uber-spammed to death? (ideas welcome!)
Actions:

  1. Go home for the week end ;-)

Release 1: XP is not mainstream... no sir!

Hey, that's not new either!

Nope, just wanted to say that I have heard this for quite some time now, and franckly, what's the point...

Mainstream methodologies have one thing that XP does not have yet: a process that certifies that people have attended courses, used them (to some extend, if you have not used them, you can say what you would have done if you had to use it) or would be ready to use them.

In the end, you get a certification in the form of a nice (sometimes not so nice) diploma that you can put away in a drawer and forget until you are looking for another job. What else, you don't even have to use what you've learnt!

Look at SCRUM, there are a growing number of Scrum Masters around: I predict that SCRUM will become Mainstream before XP! Why? Because when you get certified for something, you put it on your CV, you make it visible for people to see it, you raise there awareness of what it is, you generate interest for what it delivers, you belong to a group and can prove some sort of power from above ("thee" who certified you).

But once again, what's the point? The point is, what is the point?

what would being part of the Mainstream methodologies bring to XP anyway?
XP practitioners would be recognised? they would be paid a lot more money? Managers would listen to them more? They would have better tools? They would be happier in their jobs? Or is just that we believe that it is the only way for companies to take XP values and practices seriously?

Utlimately, becoming mainstream may result in a complete halt to the entire XP community thinking about improving how XP works and delivers. Not being mainstream is the trademark of something evolving, avant-garde, and some organisations are looking for these.
Maybe we should be looking at which organisations are in the XP stream instead ;-)

Release 1: XP and Business Value...

Recurring subject indeed.. But is XP really addressing Business Value delivered through technical change?

The answer is no, not on its own.

What XP does is that it allows the maximisation of the Business Value which is in the customer story pot, that's all it does.

If you have a set of customer stories that together carry 0 in terms of business value, then XP (or any other methodology for that matter) will deliver 0. XP will only do it its own particular way, which I happen to believe is one of the best approach for producing and releasing software.

So, how can we ensure that XP maximises business value? Simple, ensure that the story pot carries maximised business value itself.

Anybody done that yet? Come along to XP Day (London, November 2004, http://www.xpday.org/) and we'll discuss this. I will presenting a case study of a project where I think we have managed to do that.

If you can't make it, no worry, this blog is open for questions and comments ;-)

Release 1: The MATRIX(P), it's everywhere!

What do I mean by this?
Well, I have been using some XP principles for the major part of two years now, and I must admit that these principles, especially the Management Practices are pretty generic and not only valid for the IT geeks (apart from the technical practices...).

In fact, I see these principles working everywhere, just like Neo in "Matrix" sees the Matrix world as it is (that green slime of numbers) after he has been shot by Smith ;-)

OK, OK, I am not saying I am the one here! Everybody can see the same thing as me, and it is very unlikely that I will start flying tomorrow and be able to kick butts in a variety of martial arts.

However, my life is now heavily tinted by reflexes that XP has given me, even outside the context of managing the production of software, 'cause at the end of the day, everything we do requires capacity monitoring, planning, delivery, integration, testing and aims at generating value.
"There is no waste of time, there are just different ways to use it"

October 28, 2004

Iteration 1: Planning Game

As mentioned in the introduction, this blog will be managed as an XP project.

I will not use the technical practices (I am not coding here!), but will try and stick to the management practices (writing stories, acceptance criteria, tasks, having planning games, stand ups - ie: this page is now my startup page on my browser - retrospectives, releases). By this, I want to check/demonstrate that these practices can be used to deliver a wide variety of outcomes.

So far, here are the user stories:

Story ID: 1
Estimate: 6.4
Type: Minimum Marketable Feature
Status: Complete
Value: 10
Description:
As an individual... I want the ability to share my experience and discuss XP and any other Agile methodology with the rest of the World... in order for me to enrich my knowledge on the subject as well as possibly enriching others.

Acceptance criteria:

  1. The communication medium must be available to the entire World
  2. There is no restriction concerning who can contribute as long as it is about XP/Agile
  3. There is no restriction concerning what can be posted as long as it touches XP/Agile
  4. Discussions/thoughts will be kept for future reference (Archive)
Tasks:

  1. Create blog (Estimate: .2) (Status: done)
  2. Publish blog (Estimate: .2) (Status: done)
  3. Communicate blog address to trusted contacts (Estimate: 1) (Status: done)
  4. Publicise blog (Estimate: 5) (Status: done)

Story ID: 2
Estimate: 1.1
Type: Minimum Marketable Feature
Status: Complete
Value: 5

Description: As the blog master...I want at least one release per week in order to keep this blog alive and people to want to come back and contribute.

Acceptance criteria:

  1. There is at least 1 new blog entry per week
  2. Each blog entry is relevant to subject
  3. Each blog entries are open for comments

Tasks:

  1. Record week's experience (Estimate: .5) (Status: done)
  2. Write to blog (Estimate: .5) (Status: done)
  3. publish (Estimate: .1) (Status: done)

Overall Iteration Value: 15

Let me know if you think of any additional acceptance criteria for this story.