You’ve experienced it. You’re handed a project with two hundred thousand lines of complicated undocumented code and a looming deadline. Where do you begin? How do you get familiar with the code? Finding and eliminating bugs is a good start, but how can you collect unbiased metrics on the system? How do you know when the system is “good enough” for launch? In this session we’ll use the rebirth of dotProject as web2project to demonstrate five key concepts that will help you measure, track, and triage your project from concept to the brink of failure to launch.

Comments

Comments are closed.

Nice talk! I love showcases ...

Didn't know what to aspect, but i reLly enjoyed your infos. To be honest, i did looked in it for some months

Well presented, but I have some doubts about relevance to real life projects. Open source projects are of a different nature and although many of the same things apply, I would be weary mapping this as-is on actual projects.

I'll see if I can introduce some of the mentioned tools into our internal development process. Nice talk!

Interesting talk, with an interesting approach. Very good presenter. Slides could be better.

Keith's talk was a true inspiration.
I have found a new earned respect for open source developers and maybe start triaging some projects myself.
The slides were plain horrible, but his presentation made everything ok.

In the end it went a bit to far into statistics for my taste. I'd rather have heard what he thought of the chosen approach in retrospect. Would he still hav chosen for triage instead of rebuilding. Would he have changed his approach to the recovery process? etc.

Keith's talk was a true inspiration.
I have found a new earned respect for open source developers and maybe start triaging some projects myself.
The slides were plain horrible, but his presentation made everything ok.

In the end it went a bit to far into statistics for my taste. I'd rather have heard what he thought of the chosen approach in retrospect. Would he still hav chosen for triage instead of rebuilding. Would he have changed his approach to the recovery process? etc.

for me this was the most valuable talk of the whole conference. Not only is Keith a fluent and engaged speaker but the way he explains how he tackled his problems makes you want to jump out of your seat and start working on getting your own projects out of the mud now!

Maybe not everything in his talk translates to non-OSS projects (getting good client/user feedback is a lot harder in a business environment that in OSS afaik) but in general this talk was really inspiring and holds some great value for people leading projects that are on the verge of failure!

TOP!

The slides were horrible. Fortunately, Keith is an excellent speaker.
I don't think it would work as good as it did for a non-OSS project. Maybe we just have to find it out.

the key point to me was: collect those metrics during/after each release

Great talk, but the data tables where almost unreadable.
Nice addition to the "Technical debt" talk.

My apologies on the slides. They were designed for 800x600 but the projector only showed them at 640x480 so they were screwy. If I'd realized how bad they were, I would have done the - apparently minor - adjustment that would have corrected it.

You can get the slides here:
http://caseysoftware.com/blog/phpbenelux-2011-recap

@ijansch and anonymous, I'd love to know your specific criticisms and/or weaknesses to address them next time around. Thanks :)

Nice talk with some very good points. I will implement some of the things said in my work process for sure.
Good showcase of you did things, was nice to see how "the-other-project" performed in the same time.
Most important for me was: don't wait with a release until all bugs are fixed, just fix the important ones!
Also had a great time! :P