iPhone Project Timeline (WIP)

I know better than to trust my own organic memory with this task, so here is an index of what has gone into the iPhone programming project thus far:

Stage One: Childish indiscretion

1. iPhone programming contest announced.
   
2. Ordered iPhone and Cocoa development books from The Pragmatic Programmers. Read a bit of the first in my spare time.
   
3. Contest start time arrived. Started reading in earnest, beginning on the basic tutorials once the development Mac was set up in the office (all while leaving time for my daily duties).
4. Brainstormed various project ideas.

Stage Two: Youthful vigor exerted and discovering the world at large

1. Researched the implementation details of said ideas, filtering out those which the technology and contest deadline made impractical.
2. Staunchly decided to go with a promising but time-pragmatic idea, expressly avoiding any thoughts of trying other projects in order to avoid a "paralysis of choice" situation.
3. Prepared multiple paper-based mockups of the layout and received coworker feedback on the now-visible idea.
4. Began coding a mockup in earnest.
5. Worked through the setup details necessary to load the app onto the developer iPhone hardware itself (as opposed to just the simulator).
6. Developed rudimentary implementations of the front-end GUI and online data-loading components, resulting in a presentable prototype.
7. With said prototype in hand, began demonstrating it eagerly to others and started soliciting coworkers as developer teammates while expanding and refactoring the prototype.

Stage Three: The college years

1. Met with a handful of coworkers over coffee, making a point of only inviting as many as I could hope to handle so as to avoid a "Too many cooks" scenario. Discovered just how nebulous of a project plan I had.
2. Assigned a high-level project component to each teammate, divided by functionality and with the hopes of avoiding unnecessary overlap (and the cross-coding that would result). The specific groupings: Backend GUI, Web-based data input, and Web-based data output.
3. Discovered the primary, extra-narrow purpose for the app, one with more personal value.
4. Worked out per-team member lists of actionable items. The early items represent comprehensible milestones that, with hope, elicit distinct actions on their owners' parts. Expressed the intent to further subdivide these actions as necessary.
5. Stayed on-hand one evening in case the Backend GUI developer needed any help with the initial iPhone tutorials. (He needed no such help, though, and knocked it right out.)
6. Wrote this blog post.

I'll add to this chronology in subsequent posts as the project progresses, especially as the contest deadline approaches.