In stolen moments. Afternoons, weekends. Together, mostly.
So far, that’s about it. (And so far, so good.)
Sufficiently
One problem: we haven’t done sufficiently for one another to make it easy to work on Nudge in these stolen moments and weekly-ish meetings together. The whole stupid xp / agile thing doesn’t work, since none of us are embedded in the project on a steady, consistent basis. We don’t need to justify our rain-hungry expanses of time to some control tower, and then bail half-baked some fiscal quarters later. (We can bail half-baked without structure to enable that behavior, thanks.)
Nudge is important, but it’s not the first thing on anybody’s list.
So there’s this push towards a collection of stories goals designs objectives: a frontier of things that need to happen for Nudge to happen.
With some edges of this frontier scoped out sufficiently that we can peel off little one-hour-ish chunks of work to perform and commit.
Not the best
I wonder about quality of the work we do in this environment. I know it’s not my best. Part of that is because I am learning by doing (all this GP stuff is new to me; that’s why I’m grateful for this little black book PDF). Another part is that Nudge never gets the best of my time or energy. But software isn’t about quality, it’s about bringing light into the world. It just has to be something that wasn’t there before, with [1] decent test coverage and [2] reasons for being both plusses. And on that count, I’m pleased by what’s happened so far, since it’s more than we had before, and it seems in danger of becoming something genuinely, demonstrably useful.