ITPM - 04. Project Integration Management
What is Project Integration Management
- Project Integration Management is not the same thing as SW Integration
7 Main Activities(processes)
Initiating
1. Develop Project Charter
Planning
2. Develop Project Management Plan
Executing
3. Direct and Manage Project Work
4. Manage Project Knowledge
Monitoring and Controlling
5. Monitor and Control Project Work
6. Perform Interated Change Control
Closing
7. Close Project or Phase
Best Practice
- organization's strategic plan should guide the IT project selection process. (전략적 계획이 IT 프로젝트 선정 기준이 되어야한다.)
Strategic Planning and Project Selection
Strategic planing involves determining long-term objectives
-> SWOT 분석이 핵심 도구로 사용됨
IT 전략은 비즈니스 전략과 일치해야함
Project initiation 단계:
1) Identifying potential projects (프로젝트 후보 식별)
2) Using realistic methods to select which projects to work on (현실적 방법을 사용해 프로젝트 선택)
3) Formalizing their initiation by issuing a project charter (프로젝트 발행으로 공식화)
Project Selection 단계
1) IT Strategy Planning
2) Business Area Analysis
3) Project Planning
4) Resource Allocation
1. Developing a Project Charter
Input
- Business documents -> Business case
- Agreements
Output - Project charter, Assumption log
1-1. Project Charter
- formally recognizes the existence of a project
- Key project stakeholders should sign a project charter
- 쓰는 건 어렵지 않음, But 적당한 사람들 모으는게 더 어려운 작업임
1-2. Assumption log
포함 항목 (adscds)
1) assumption ID
2) date
3) source
4) category
5) description
6) status
2. Development a Project Management Plan
Input
- Project Charter
- Ouputs from other processes
Output
- Project management plan
Document used for:
- Coordinating all project planning documents
- Guiding a project's execution and control in the future
특징
- overall scope, schedule, cost baselines
- Flexible
- Progressive Elaboration(점진적 정교화) : specified as the project continues
3. Directing and Managing Project Work
Input
- Project management plan -> any component
- Project documents
- Approved change requests
Output
- Deliverables
- Work performance data
- Issue log
- Change Requests
- Proect management plan updates
- Project documents updates
- Organizational process assets updates
특징
- Executing the planned tasks by the project members
- The majority of time and money is uaually spent on execution
이 stage에서 PM의 주요 역할 두 가지:
1) leading the project team
2) managing stakeholder relationships
Coordinating Planning and Execution
- Project planning and execution are interwined and inseparable.(계획과 실행은 서로 얽혀있고 분리될 수 없다)
- "Those who will do the work should help planning the work" -> 실제 작업을 할 사람들은 계획 수립에도 참여해야한다.
- All project members need to develop both planning skills and executing skills
- Domain knowledge and experience is important
Providing Strong Leadership and a Supportive Culture
- PM must lead by example -> 행동으로 보여줘야 한다.
- Demonstrate the importance of creating good project plans and following them in project execution -> 좋은 계획을 세우는 것 + 그 계획을 실제로 따르는 것의 중요성 보여주기
- Oranizational culture can help proper project execution.
-> Provideing guidelines and templates
-> Tracking performance based on plans
Capitalizing on Product, Business, and Application Area Knowledge
-
PM의 필요한 역량
1) Strong leadership, Communication and political skills
2) Product, business and application area knowledge -
이전에 Technical experience가 있으면 도움이 된다.
-
Small project 에서는 PM 이 직접 기술 업무를 하거나 mentor 하는 경우가 있음
-
Big project 에서는 직접 기술 작업을 하지 않는게 좋음.
Project Execution Tools and Tech
- Expert Judgement
- Meetings
- Project Management Information Systems
4. Managing Project Knowledge
Tools & Techniques
1) Expert jedgment
2) Knowledge management
3) Information management
4) Interpersonal and team skills
Outputs
1) Lessons learned register
Basic two types of knowledge :
1) Explicit knowledge
- Easily explained using words, pictures, or numbers and is easy to communicate, store, and distribute
2) Tacit knowledge (i.e., informal knowledge or implicit knowledge)
- Difficult to express and hightly personal
Knowledge management is on-going process
1. Culture of trust 신뢰 문화
2. Culture of sharing 공유 문화
5. Monitoring and Controlling Project Work
- Baseline 과 actual performance comparison
6. Performing Integrated Change Control
- It is important that projects have a formal change control system.
- It involves identifying, evaluating, managing changes
Change Control System
- Formal and documented process that describes when and how official project documents and work may be changed.(공식적인 프로젝트 문서나 작업 내용이 언제, 어떻게 변경될 수 있는지를 규정한 절차)
- Describes who is authorized to make changes / Which paperwork is required for these changes / How the project will use an tracking systems
- Change Control Board(CCB) : 프로젝트 내에서 변경 요청을 승인 혹은 거절 권한을 가진 사람들 모임
- Configuration Management : 제품이 정확하게 정의되었고, 문서화되었으며, 변경도 추적되며, 요구사항에 맞는지 확인하는 역할
- Communication and Negotiation
7. Closing Projects or Phases
Output
- Project Documents Updates : should be reviewed and marked as final version
- Final Product, service, or result transition
- Final Report
