original by Bryan Alexander (CET) :: hacked by LRC Design Studio
grey = elements we choose not to, or have yet to, implement
italics = LRC additions
grey = elements we choose not to, or have yet to, implement
italics = LRC additions
- Create scope statement
- basic structure
- input: needs, requirements
- output: deliverables
- constraints: time, cost, quality criteria, personnel availability
- mechanisms: tools, staff, materials
- check with previous instances, history
- scope definition (subgroups, small tasks)
- scope modifications: tie to versioning. manage expectations (risk) by versioning
- Compose project plan Characteristics: clear, well-documented Elements:
- cost estimation
- resources (campus community; fiscal; hardware)
- control (PM; risk)
- requirements, or inputs
- tasks: outputs, minitasks
- time schedules
- durations, sequencing - tie back into scope definition
- control (PM; risk)
- communication environment: tool details; blog, wiki, email, morse code, smoke signals?
- quality assessment criteria
- KPI: Key Perfomance Indicator
- CSF: Critical Success Factor
- criteria for completion and success: feedback from client, project wrapup, peer assessment
- balance different p.o.v
- Generate responsibility matrix (PMI)
- Situate project in context
- consensus with supporting/supervising structures
- curricular reintegration
- promotion and seeking re-use options
- Ensure updating
- establish versioning schedule: soft deadlines, per semester basis, Spiral Model
- logic of emergence
