Prince2
6 varialbes/aspects (control)/Proj Performance
costs
timescales
quality
scope
risk
benefits
7 principles
business justication
experience
roles/respon
manage by stages
manage by exception
focus
tailor to suit
7 themes
business case
organisation
quality
plans
risk
change
progress
Proj Board = Senior supplied + Senior User + Executive
Structure - Principles, Themes, Processes, Tailoring
proj mgmt structure has 4 levels
Proj board 4 qualities - Authority, Credibility, Ability to delegate, Availability
7 process - which helps to direct, manage and deliver
startingup
directing
managaing stage boundary
Initiating project
controlling stage
managing product delivery
closing proj
Three; project, stages and quality --PRINCE2 document management structure, 3 types of file
7 of these are for customer’s quality expectations, Project Quality Plan, Configuration Management Plan, Configuration Item Records and Quality inspection records
Acceptance Criteria
3 plans - Project, Stage and Team Plans
planning focuses ---> descriptions, hierarchy, sequence
Manage by Exception principle sets tolerances for six areas -->Time, Cost and Qualities, Scope, Risk, Benefit
Identify, Assess, Plan, Implement <-- assess="" dentify="" implement="" nbsp="" p="" plan="">
Project interst - User Supplied Business
Proj Product description, WBS, Prod Desc & Flow diagram
Initiating project
-------------------
Issue register
Quality mgmt strategy
Quality register
risk register
Quality will be achieve/Plan
proj mgmt team structure
proj approach
business case
Benefit review plan by executive
The Executive and Project Manager are appointed
How the required quality will be achieved
Proj Quality Plan
Project Manager ask the Project Board where the authority for making change lies
scope what is to be done and the products to be delivered
progress will be monitored and controlled
Learn from experience
starting up of proj
-------------------
Quality expectation
Lesson log
Daily log
Project brief
project aproach
issue log
Plan the Initiation Stage
do we have a viable and worthwhile project
Ensuring that the prerequisites for initiating the project are in place
Directing starts --> Proj Board starts
Mandate
acceptance criteria
1) Setting up the project management team
2) Developing the Project Mandate into the Project Brief
3) Confirming the Project Approach
Process is used to design the Project Management Team
learn from experience
next is directing
issue register, quality mgmt st, config mgmt st, project plan, Business case, risk register, quality register --> End stage
Project Approach - decision inhouse/third party/off the shelf
Project breif=proj defn
Initiating = stage plan+Proj breif
risk mgmt strategy=pm
all risk=executive
handles day to day = control
decision making=directing
quality methods -In process methods, Appraisal methods, Inspection methods, Sampling methods
PID = Business Case, Quality Management Strategy/plan, Configuration Management Strategy, Communication Management Strategy/plan, Risk Management Strategy
the ‘contract’ between the Project Manager and the Project Board, no pm control, tolerance, updating the project plan as part of Managing a stage boundary
Project Product Description =customer’s quality expectations, outline business case,composition, purpose, project level tolerance
business option =Project Brief --> Authorise initiation
Project Brief =Project definition, Project approach, Role descriptions, Provides a firm basis on which to initiate the project, assist creating the Stage Plan
Project Brief=outline Business case+Proj Aproach+ PPD
project mandate=Corporate or programme management
Prod Descripition:
1. A breakdown of the individual parts that make up the product
3. Details of the individuals responsible for reviewing the product
3. Product Quality tolerance
4. Any allowable deviation from the specified quality criteria
5. Necessary abilities of the people needed to produce the product
6. Why the product is needed and what it will look like
7. Necessary abilities of the people needed to review the product
Prod purpose
composition
derivation
format
quality criteria/method
focus on products
nature
purpose
function
Project Board - Approve the Project Product Description
Confirm the required frequency of Highlight Reports
Transfer ownership of the Benefits Review Plan to corporate or programme management
Progamme - realization benefits
Progress = Authorising one stage at a time
initial Project Plan = Brief+QualityPlan+Approach
Acceptance for the completed products = Proj Delivery
PM --> Checkpoint Reports, Work Packages status and quality log
Porj Prod description, PBS, Prod Desc, Flow Diagram
ppd=Purpose of the product, Composition, Project level tolerances
quality responsibilities for the project-> Proj Quality Plan
Three-project, stage and quality --> 3 document management structure
Quality File has seven --> customer’s quality expectations, Project Quality Plan, Configuration Management Plan, Configuration Item Records and Quality inspection records, Acceptance Criteria
Directing a Project begin --> completion of Starting up a Project, stage tolerances be set
Senior User -responsible for providing the customers quality expectations and acceptance criteria for the project
Plan description - Process, Systems, Operating, Org model
3 mgmt products
baselines
records
reports
corp/prgm stnds
CCQR
Comm mgmt strategy
config mgmt strategy
Quality mgmt str
Risk mgmt str
Prince2 Plan
Proj Plan
Stage Plan
Team Plan
Exception Plan
Benefits Review Plan
http://baidy.com/view/e56745cc58f5f61fb7369969c.html?pn=39
Progress theme support the manage by exception
Change theme support the manage by exception
costs
timescales
quality
scope
risk
benefits
7 principles
business justication
experience
roles/respon
manage by stages
manage by exception
focus
tailor to suit
7 themes
business case
organisation
quality
plans
risk
change
progress
Proj Board = Senior supplied + Senior User + Executive
Structure - Principles, Themes, Processes, Tailoring
proj mgmt structure has 4 levels
Proj board 4 qualities - Authority, Credibility, Ability to delegate, Availability
7 process - which helps to direct, manage and deliver
startingup
directing
managaing stage boundary
Initiating project
controlling stage
managing product delivery
closing proj
Three; project, stages and quality --PRINCE2 document management structure, 3 types of file
7 of these are for customer’s quality expectations, Project Quality Plan, Configuration Management Plan, Configuration Item Records and Quality inspection records
Acceptance Criteria
3 plans - Project, Stage and Team Plans
planning focuses ---> descriptions, hierarchy, sequence
Manage by Exception principle sets tolerances for six areas -->Time, Cost and Qualities, Scope, Risk, Benefit
Identify, Assess, Plan, Implement <-- assess="" dentify="" implement="" nbsp="" p="" plan="">
Project interst - User Supplied Business
Proj Product description, WBS, Prod Desc & Flow diagram
Initiating project
-------------------
Issue register
Quality mgmt strategy
Quality register
risk register
Quality will be achieve/Plan
proj mgmt team structure
proj approach
business case
Benefit review plan by executive
The Executive and Project Manager are appointed
How the required quality will be achieved
Proj Quality Plan
Project Manager ask the Project Board where the authority for making change lies
scope what is to be done and the products to be delivered
progress will be monitored and controlled
Learn from experience
starting up of proj
-------------------
Quality expectation
Lesson log
Daily log
Project brief
project aproach
issue log
Plan the Initiation Stage
do we have a viable and worthwhile project
Ensuring that the prerequisites for initiating the project are in place
Directing starts --> Proj Board starts
Mandate
acceptance criteria
1) Setting up the project management team
2) Developing the Project Mandate into the Project Brief
3) Confirming the Project Approach
Process is used to design the Project Management Team
learn from experience
next is directing
issue register, quality mgmt st, config mgmt st, project plan, Business case, risk register, quality register --> End stage
Project Approach - decision inhouse/third party/off the shelf
Project breif=proj defn
Initiating = stage plan+Proj breif
risk mgmt strategy=pm
all risk=executive
handles day to day = control
decision making=directing
quality methods -In process methods, Appraisal methods, Inspection methods, Sampling methods
PID = Business Case, Quality Management Strategy/plan, Configuration Management Strategy, Communication Management Strategy/plan, Risk Management Strategy
the ‘contract’ between the Project Manager and the Project Board, no pm control, tolerance, updating the project plan as part of Managing a stage boundary
Project Product Description =customer’s quality expectations, outline business case,composition, purpose, project level tolerance
business option =Project Brief --> Authorise initiation
Project Brief =Project definition, Project approach, Role descriptions, Provides a firm basis on which to initiate the project, assist creating the Stage Plan
Project Brief=outline Business case+Proj Aproach+ PPD
project mandate=Corporate or programme management
Prod Descripition:
1. A breakdown of the individual parts that make up the product
3. Details of the individuals responsible for reviewing the product
3. Product Quality tolerance
4. Any allowable deviation from the specified quality criteria
5. Necessary abilities of the people needed to produce the product
6. Why the product is needed and what it will look like
7. Necessary abilities of the people needed to review the product
Prod purpose
composition
derivation
format
quality criteria/method
focus on products
nature
purpose
function
Project Board - Approve the Project Product Description
Confirm the required frequency of Highlight Reports
Transfer ownership of the Benefits Review Plan to corporate or programme management
Progamme - realization benefits
Progress = Authorising one stage at a time
initial Project Plan = Brief+QualityPlan+Approach
Acceptance for the completed products = Proj Delivery
PM --> Checkpoint Reports, Work Packages status and quality log
Porj Prod description, PBS, Prod Desc, Flow Diagram
ppd=Purpose of the product, Composition, Project level tolerances
quality responsibilities for the project-> Proj Quality Plan
Three-project, stage and quality --> 3 document management structure
Quality File has seven --> customer’s quality expectations, Project Quality Plan, Configuration Management Plan, Configuration Item Records and Quality inspection records, Acceptance Criteria
Directing a Project begin --> completion of Starting up a Project, stage tolerances be set
Senior User -responsible for providing the customers quality expectations and acceptance criteria for the project
Plan description - Process, Systems, Operating, Org model
3 mgmt products
baselines
records
reports
corp/prgm stnds
CCQR
Comm mgmt strategy
config mgmt strategy
Quality mgmt str
Risk mgmt str
Prince2 Plan
Proj Plan
Stage Plan
Team Plan
Exception Plan
Benefits Review Plan
http://baidy.com/view/e56745cc58f5f61fb7369969c.html?pn=39
Progress theme support the manage by exception
Change theme support the manage by exception
Comments