DGC75 Status Chart: Difference between revisions
From Murray Wiki
Jump to navigationJump to search
m (=Project/Team Meetings=) |
(=Status Chart=) |
||
| Line 34: | Line 34: | ||
---- | ---- | ||
== Status Chart == | == [[DGC75_Status_Description|Status Chart]] == | ||
Need to write a description for what a status chart is and how to use it. | |||
Interfaces | |||
* 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 == | == Timeline Chart == | ||
Revision as of 20:56, 19 June 2004
Caltech Project Management Toolset (CPMT) Status Chart
Updated: 19 Jun 04
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.
Interfaces:
- 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.
Interfaces
- 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.
Interfaces
- 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.
Interfaces
- 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
