Project deliverables
Project deliverables
Ethan Bolker
2004-2005
Here are the formal, dated deliverables. Of course there are
intermediate ones you will schedule individually, internally for the
team and externally with your customer. And of course
everything you do must be transparent - visible on the project web
page and subject to surprise inspection.
-
From first team meeting ...
- October ??:
Vision statement and project web page.
- October ??:
Looking for venture capital: project presentation.
- December ??: Requirements analysis (and more).
- Use cases (customer approved as appropriate, prioritized)
- Hardware and software requirements
- Risk analysis (update)
- Schedule (update)
- Development methodology
- Critique/analysis of work to date
(more information to follow).
-
Performance review
Since we
began the year with a simulated job interview we should finish with a
simulated performance review, so I can decide by what percent to
increase your salary. I will provide a signup sheet for these
meetings. You should provide
- An updated CV and web page (since you will be moving on ...)
- A sample of your work on your project (code, perhaps
documentation too). (This is in lieu of the code reviews we never got
around too. And it's something you may be asked for at a job interview.)
- A fair discussion of your sense of how your
strengths and weaknesses affected your team's performance.
- May ??: Production release (1.0). The principle that governs
the details of what you must do: leave the project in a state that the
customer is pleased with, and that you would be pleased to maintain.
-
Complete tested application, installed/installable by customer (as
appropriate).
-
Complete documentation (for users, installers, programmers) on web
page. Proofread, of course.
-
Web page (probably at sourceforge) up to date, including
sourceforge release and prominent pointer to list of
known bugs (of course a
production release should have no bugs - but this is real life ...)
-
Release flagged correctly in CVS tree.
-
Hard copy:
- Acceptance from customer.
-
Appropriate documentation.
- Bug list.
-
Your poster (framed, small format) for me to keep in my office to
impress future SE classes.
- May ??: Presentation to public - poster and demo - at annual
department Spring party.
- May ??: Maintenance release (1.1).
- June ?: Graduation.