Chapter 4: Integration Flashcards
C4 Integration: Terms and terminology
-
Integrated Change Control Process - особенности
- Если изменение затрагивает baseline, policies and procedures, charter, contracts, SOW, Proj Man plan - обычно нужно проходить через процесс Change Control, либо спонсора. В Agile это обычно аппрувится силами PO
- Osmotic Communication (agile!) - работает в co-located среде. Услышал что-то и смог если что передать кому-нибудь (полезные знания)
- Work authorization system - makes sure work is only started when a formal authorization is given (company-wide system). Part of PMIS
Change Requests Categories
Вызываются CR-ом
- Preventive action - deals with anticipated deviations from the performance management baseline
- Corrective action - deals with actual deviations, выправление ситуации
- Defect repair - modifies nonconformance to project req, rework. В отличие от Corrective action, это -> Rework
Approved CRs impemented in:
- Direct and Manage Project Work
- Control Quality
- Control Procurements
Integration Management Overview
Performance Measurement Baselines
Scope baseline
- Scope statement,
- WBS
- WBS dictionary
The creation of the project deliverable will be measured against the scope baseline to show any variances from what was expected and what the project team has created.
Schedule baseline
Schedule, including start/stop dates for each activity and schedulled milestones
Cost baseline
The time-phased cost budget (the spending plan indicating how much money is approved for the project and when the funds are required and will be available)
Two Types of Knowledge
- Explicit knowledge - конкретная информация, выражается цифрами и фактами
- Tacit knowledge (scarce knowledge?) - Knowledge that’s more difficult to express because it’s personal beliefs, values, knowledge gain from experience, and “know-how” when doing a task. Не всегда можно выразить через слова и символы, скорее через job shadowing
Types of lessons Learned
- Technical
- Project management
- Management
LL are best completed by stakeholder (не только team)!
Relationship between the process group and PM categories
.
Management plans
Project Management Plan
- The documented approach of how a project will be planned, executed, monitored and controlled, and then closed.
- This document is a collection of subsidiary management plans from all knowledge areas
- Have baseline
- Updated throughout the project
Такое впечатление, что в него входят все документы. Как общий репозиторий какой-то
Individual management plans
- Scope
- Schedule
- Cost
- Quality - what quality means for the project, how the project will achieve quality, and how the project will map to organizational procedures pertaining to quality.
- Resources
- Communications
- Risk
- Procurement
- SH engagement
Other Management Plans
- Configuration management plan - how PM will manage changes to documentation, including which orga tool to be used. Goal: all SH have access to the latest versions of the Proj Management plan components
-
Requirements Management Plan - how req will be gathered, analyzed, prioritized, evaluated, documented, managed and controlled. Типы требований:
- Business req - describe why the organization is undertaking the project
- Stakeholder req - user needs or user requirements, describe what users do with the system
- Change Management Plan - how changes will be managed and controlled и какого рода CR требуют какого уровня согласования и формализации. E.g. approvals levels, change procedures, creation of CCB, tool use to track and control changes
Process for Making Changes
Predictive
1. Prevent the root cause of changes
2. Evaluate the impact на project constraints
3. Identify options - придумать как минимизировать эффект (E.g. crashing, fast tracking etc.)
4. Get approval internally - through Change Control Board
5. Коммуницировать SH
Agile
- Daily changes - by PO
- Если влияют на Schedule, Cost - через стиринг
