Project Infrastructure Usage Requirements

I kind of see this class as "playing house" for doing more serious project management on bigger projects in a professional setting. One difference is that most of us won't have to set up all the project management goo, we'll just have to use it. Using the term "playing house" is a little demeaning but it communicates some of the vibes I'm sensing from my group members (which might not actually be there, my group members have lots of other classwork to worry about, and this is the only class I'm taking).

One of these "vibes" is that it seems a little artificial to build up all this project management stuff and then actually use it, because we haven't had use for this stuff previously are we aren't forced to use it in this class. We'd probably be better initiated in to using this stuff if we had a standard set of tools that the whole class could play with, along with assignments like Using a Ticket System, or Using a Revision Control System. In the meantime, I don't know how usage the project infrastructure will see since their don't seem to be many hard requirements in the class to do so.

Mailing Lists and Project Management Documentation

Our new mailing list has been working swimmingly. At least until the whole engineering wing of UNM apparently lost power. Hopefully we'll be able to use our list again soon.

I didn't manage to make it to any classes this week, but I should have plenty of time to catch up on what I missed over spring break. Hopefully we'll also be able to hammer out more of the design stuff for our project so we can get started writing code.

While I wasn't going to class I contributed to the Project Managment document that we needed to write (which was due today at 5p), which outlined the basic project tasks, as well as (the part that I wrote) an outline of all the machinery we've set up the manage the project and how we intend to use it.