jducoeur

One of my major projects for umpty months now has been to tame the process management at work. As Memento moves from being a platform-centric company to a more product-centric one, I've been working with my VP of Engineering to make the slow and painful transition to something a bit more agile. Part of that, for the past couple of months, has been to do a pretty deep dig into the available agile process tools, evaluating them both in terms of quality and how well they would work for us.

Today I got a note from the CTO of ScrumNinja, one of the ones I've played with a little bit, just checking in to see if we had questions for them. I sent a nice reply, explaining that we probably weren't going to be able to use them, pretty much entirely for reasons extrinsic to the product (company is a little too small and new, and not Windows-focused enough for us). But it did succeed in reminding me that they were one of the better-looking options in general, not least because they seem to be actively engaged with their user community, not just listening to but soliciting suggestions and ideas.

So now I'm thinking of trying them out for one of my open-source projects -- the Querki semantic-wiki projects, perhaps, or the Scala implementation of Wave. My quick kick of ScrumNinja's tires impressed me, so let's see how they do with something real. And points to them: little things like that feeler email are how you build your user base...