DGC75 Status Chart

From Murray Wiki
Revision as of 21:13, 19 June 2004 by Murray (talk | contribs) (=Wiki Documentation=)
Jump to navigationJump to search

Caltech Project Management Toolset (CPMT) Status Chart

Updated: 19 Jun 04

CPMT Status 2004-06-19.jpg

Design Specification

Don't currently have any formal way of specifying system requirements or propogating them through the design. Need to think through how requirements will be specified at both project and team level.


  • GOTChA chart: requirements should be reflected in objectives
  • Design reviews: reviews should demonstrate requirements are met

Project/Team Meetings

We have a pretty good template in place for these: goals, agenda, notetaker. Need to create a document for proper meeting practices.


  • GOTChA charts: Meetings should start and end with GOTChA charts
  • Status charts: Meeting status updates should use status chart to organize discussion
  • Bugzilla: Meetings should review blocker items in bugzilla and new actions should be recorded in bugzila

GOTChA Chart

Need to copy over GOTChA chart info from TeamCaltech wiki.


  • Design Specification: objectives should reflect level 1 specifications
  • Status Chart: approach should correspond to status chart
  • Timeline Chart: objectives/approach should be reflected on timeline chart
  • Design Reviews: GOTChA charts for the basis for design review presentations

Status Chart

Need to write a description for what a status chart is and how to use it.


  • GOTChA chart: approach should be reflected on this chart
  • Timeline chart: status should be relative to timeline (milestones)
  • Bugzilla task lists: subsystem blocks should be represented as components in bugzilla.
  • Project/team meetings: status chart should be used in team meetings to guide discussion of current status

Timeline Chart

Need to create description of timeline chart. Should link to project meetings.


  • GOTChA chart: approach should be reflected in timeline
  • Project/team meetings: missing
  • Status chart: status should be reflected in timeline; arrow may be one way?

Design Reviews

Need to figure out how design reviews should be held. Probably having a couple of different types: working meetings, preliminary design review, critical design review.


  • Design specification: design specs should be the basis for the review
  • Technical Work: technical work should be driven by design reviews and new actions from design reviews should be reflected in technical work
  • Wiki documentation: not sure what the link is here yet. Define or delete.


Need to define some processes around tests and (field) demonstrations. These include pre-demo checklists, test matrices, test manager, etc.


  • Wiki Documentation: results of demos should be documented
  • Bugzilla task lists: action items from demos should be entered in Bugzilla
  • Technical work: technical work should be driven by demo milestones

Bugzilla Task Lists

Fairly well defined process here. Need to copy over information on how to use Bugzilla from Team Caltech Wiki


  • Status chart: products specified by teams, components specified by status chart blocks
  • Project/team meetings: use Bugzilla in team meetings to look at critical and blocker tasks. Team and project meeting action items should get entered into bugzilla by note taker
  • Design reviews: record design review action items in bugzilla
  • Demos/tests: record actions from demos and tests in bugzilla

Wiki Documentation

Need to write down how the Wiki is supposed to be structured and used. Can copy a lot of this from TeamCaltech site.


  • Technical work: only documented work will be graded
  • Design reviews: all work presented at reviewes should be documented
  • Tests/demos: all results from tests should be documented