I. Assign Secretery-General
Takes minutes at all group meetings.
II. Meeting Objectives
1) Devise Strategy for the Quarter
2) Assign Key Roles
3) Determine Activities/Goals/Schedule
4) Assess Risks
1) Strategy:
a) Probs: * hard to understand current code
* issue of which design platform to use
b) Suggestions?
c) Possible Solution
Parallel development of key funcitonality according to
Design Doc. on the Newton and one second language
(Delphi or Visual Basic on PC)
d) Strategy
- simultaneous design and platform analysis/learning language
- after design, begin implementation
- come together to test at end
2) Key Roles
Team Leader
(project plan, schedule, organizing final report, video)
|
----------------------------------------------------------------------
| | | |
Design Team Analysis Team Development Team Test Team
(design doc) (analysis doc) (code development) (test plan)
| (demo communication) | (test results)
| | | |
Design Leader ---------------- ------------------ ???????
| | | | |
Desigers (2) PC Newton PC Newton
/\ /\ | |
/ \ / \ CA CA
Chief Liason C.A. L. | |
Architect (L) Developers Developers
(CA)
Non-Technical Roles
* Secretery-General
* Equipment Manager
* Web Site Manager
3) Activities
* Meeting-Prep - preparing for meetings, typing minutes/outlines
* Group-Progress - preparing group progress reports
* Meeting - attending meetings
* research (specifically listed as Newton or PC) -
time spent reading and researching info specific to a platform
* Documents - (will be listed specifically)
time spent writing a document
* coding (newton/PC) - time spent coding and debugging
* Presentation-Prep - time spent preparing and rehearsing for
presentations
* Presentation- time spent in the presentation
* web - time spent maintaining web sit
Others???
4) Schedule
(talk about how long people want to spend on each phase)
5) Risks
a) personnel - minimize by having no single person groups
(ie if someone drops or is sick, we have another person
that theoretically knows the same material)
b) design doc --
we are depending on this to be done before we begin implementation
- minimize risk by having the most senior group members working
on it...
c) platform problems?
ie: learning, functionality, access to it...
functionality and access should be minimized because both
platforms have been shown functional by the existence of previous
prototypes (and accessible as well...)
learning probs are minimized by: the availibility of sample
cyberguide code for inspection and of people from previous
quarters for interrogation
d) implementation risks???
* Resources ?