DGC75 Status Chart: Difference between revisions
From Murray Wiki
Jump to navigationJump to search
(=Project/Team Meetings=) |
m (=Design Specification=) |
||
| Line 5: | Line 5: | ||
---- | ---- | ||
== Design Specification == | == [[DGC75_DesignSpec|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. | 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. | ||
Revision as of 20:46, 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
