프로젝트 관리를 위해서 무엇을 모니터링 할 것인가?


출처: recommended approach

 

관찰하지 않는다면 엉망진창이 되어도 이를 통제할 방법이 없다고 생각하는 사람들의 의견에 동의하며…

아래는 프로젝트 진척에 대한 indicator이다.

INCOSE의 system engineering에 대한 indicator도 있는데, 그건 나중에 스터디를 해 봐야겠음

 

Phase MEASURE SOURCE FREQUENCY (COLLECT/ANALYZE) Data collection
Continued Begun
Requirement definition phase Staff hours (total and by activity) Requirements definition team and managers (time accounting) Weekly/monthly
Requirements status (percentage of completed specifications; number of requirements defined) Managers Biweekly/biweekly
Estimates of total requirements, total requirements definition effort, and schedule Managers Monthly/monthly
Requirement Analysis phase Staff hours (total and by activity) Developers and managers
(via Personnel Resources Forms (PRFs))
Weekly/monthly *
Requirements (changes and additions to baseline) Managers (via Development
Status Forms (DSFs))
Biweekly/biweekly *
Requirements (TBD specifications) Managers Biweekly/biweekly *
Requirements (Questions/answers) Managers (via DSFs) Biweekly/Biweekly *
Estimates of total SLOC, total effort,
schedule, and reuse
Managers (via Project Estimates Forms (PEFs)) Monthly/Monthly *
Preliminary Design Phase Staff hours (total and by activity) Developers and managers
(via PRFs)
Weekly/monthly *
Requirements (changes and additions to baseline) Managers (via Development
Status Forms (DSFs))
Biweekly/biweekly *
Requirements (TBD specifications) Managers (via DSFs) Biweekly/biweekly *
Requirements (Questions/answers) Managers (via DSFs) Biweekly/biweekly *
Estimates of total SLOC(new, modified, reused), total units, total effort, and
schedule
Managers (via PEFs) Monthly/Monthly * *
(total units)
Status (units p/designed/ certified) Managers (via DSFs) Biweekly/biweekly *
Detailed Design Phase Staff hours (total and by activity) Developers and managers (via PRFs) Weekly/monthly *
Computer use (CPU hours and runs) Automated tool Weekly/biweekly *
Requirements (changes and additions to baseline) Managers (via DSFs) Biweekly/biweekly *
Requirements (TBD specifications) Managers (via DSFs) Biweekly/biweekly *
Requirements (questions/answers) Managers (via DSFs) Biweekly/biweekly *
Estimates of total SLOC (new, modified, reused), total units, total effort, and schedule Managers (via PEFs) Monthly/monthly *
Status (units planned/ designed/ certified) Managers (via DSFs) Biweekly/biweekly *
Implementation Phase Staff hours (total and by activity) Developers and managers (via PRFs) Weekly/monthly *
Changes (by category) Developers (via CRFs) By event/monthly *
Changes (to source files) Automated tool Weekly/monthly *
Computer use (CPU hours and runs) Automated tool Weekly/biweekly *
Errors (by category) Developers (via CRFs) By event/monthly *
Requirements (changes and additions to baseline) Managers (via DSFs) Biweekly/biweekly *
Requirements (TBD specifications) Managers (via DSFs) Biweekly/biweekly *
Requirements (questions/answers) Managers (via DSFs) Biweekly/biweekly *
Estimates of total SLOC (new, modified, and reused), total units, total effort, and schedule Managers (via PEFs) Monthly/monthly *
SLOC in controlled libraries (cumulative) Automated tool Weekly/monthly *
Status (units identified/ coded/code-certified/ test-certified) Managers (via DSFs) (The number of completed units is also reported by developers
via COFs and by automated tools)
Weekly/biweekly (Status data differ from those collected during
design phases)
*
System Testing Phase Staff hours (total and by activity) Developers and managers (via PRFs) Weekly/monthly *
Changes (by category) Developers (via CRFs) By event/monthly *
Changes (to source files) Automated tool Weekly/monthly *
Computer use (CPU hours and runs) Automated tool Weekly/biweekly *
Errors (by category) Developers (via CRFs) By event/monthly *
Requirements (changes and additions to baseline) Managers (via DSFs) Biweekly/biweekly *
Requirements (TBD specifications) Managers (via DSFs) Biweekly/biweekly *
Requirements (questions/answers) Managers (via DSFs) Biweekly/biweekly *
Estimates of total SLOC (new, modified, and reused), total units, total effort, and schedule Managers (via PEFs) Monthly/monthly *
SLOC in controlled libraries (cumulative) Automated tool Weekly/monthly *
Status (tests planned/executed/passed) Managers (via DSFs) Weekly/biweekly *
Test discrepancies reported/resolved Managers (via DSFs) Weekly/biweekly *
Acceptance Testing Phase Staff hours (total and by activity) Developers and managers (via PRFs) Weekly/monthly *
Changes (by category) Developers (via CRFs) By event/monthly *
Changes (to source files) Automated tool Weekly/monthly *
Computer use (CPU hours and runs) Automated tool Weekly/biweekly *
Errors (by category) Developers (via CRFs) By event/monthly *
Requirements (changes and additions to baseline) Managers (via DSFs) Biweekly/biweekly *
Requirements (TBD specifications) Managers (via DSFs) Biweekly/biweekly *
Requirements (Questions/answers) Managers (via DSFs) Biweekly/biweekly *
Estimates of total SLOC (new, modified, and reused), total units, total effort , and schedule Managers (via PEFs) Monthly/monthly *
SLOC in controlled libraries (cumulative) Automated tool Weekly/monthly * Note: Test status is plotted separately for the system testing and the acceptance testing phases. Test discrepancies are also plotted separately for each phase
Status ( test items planned/ executed/ passed) Managers (via DSFs) Weekly/biweekly *
Test discrepancies reported/resolved Managers (via DSFs) Weekly/biweekly *
Advertisements

답글 남기기

아래 항목을 채우거나 오른쪽 아이콘 중 하나를 클릭하여 로그 인 하세요:

WordPress.com 로고

WordPress.com의 계정을 사용하여 댓글을 남깁니다. 로그아웃 / 변경 )

Twitter 사진

Twitter의 계정을 사용하여 댓글을 남깁니다. 로그아웃 / 변경 )

Facebook 사진

Facebook의 계정을 사용하여 댓글을 남깁니다. 로그아웃 / 변경 )

Google+ photo

Google+의 계정을 사용하여 댓글을 남깁니다. 로그아웃 / 변경 )

%s에 연결하는 중