Session 2 Flashcards
How do you manage organizational change impacts on projects?
• assess organizational culture
• evaluate impact of organizational change to project and determine required actions
• recommend options for changes to provide
• continually monitor external business environment for impacts to project scope/backlog
What do you need to know about organizational culture and style?
• leadership hierarchy and authority
• visions, beliefs and expectations
•diversity, equality and inclusion
• risk tolerance
• regulations, polices, procedures
• code of conduct
• operating environment
• motivation and reward system
What are the risk, culture and change in organizations?
Diverse values of:
• country/region
• industry/sector
• leadership
• project tran
The risk, culture and change in organization, must be understood to_________
•establish effective approaches for initiating and planning projects
• identify the accepted means for getting work done
Name a change management Framework?
ADKAR
Project Life cycle
The series of phases that a project passes through from its start to its completion
Name the five milestones from the change management framework ADKAR
- A- awareness of the need for change
- D- desire to support the change
- K- knowledge of how to change
- A- ability to demonstrate new skills and behaviors
- R- reinforcement to make the change stick
How do you plan for change?
• include an attitudinal survey to find out how people are feeling
• create an informational campaign to familiarize peoples changes
• be open and transparent about potential affects and changes
• consider creating a rollout plan ( not a project management component)
What is a North Star statement (template) used for?
To articulate the vision in strategic objectives for the organization to follow
What comes first in a project plan?
Identifying the key stakeholders
Project Governance Components/Process
• change
• communication
• documentation— i.e., project management plan
• decision- making
• internal stakeholder alignment with project process requirements
What can Governance In Adaptive Projects provide
• a clear view of project l status from:
• defined iteration/sprint exception
and outputs
• releases tied to specific dates
• Real time monitoring of project
output through daily standups
Does Adaptive and Predictive have the same governance methology?
Yes
What does Governance Board (Project Board or Steering Committee) provide?
• project oversight
• project sponsor, senior managers, and PMO resources as
• Maybbe responsible for:
• reviewing key deliverables
• providing guidance for project
decisions
What are the project Managment principles?
• recognize
• evaluate
• respond to system interactions
Predictive value delivery
Value delivery as product of life cycle
Adaptive value delivery
Value delivery embedded in life cycle
Predictive Goverance Checkpoints
(Kill Point)
• split work into phases
• review results as a phase gate- aka, goverance gate, kill point or tollgate
What does predictive Goverance Checkpoints decide?
• continue to the next phase
• continue with modifications, or
• end a project or program
Adaptive Governance Checkpoints
( Kill Point)
• split work into releases
• review results at end of iterations
• gather feedback and take action to improve value in next iteration
What does adaptive Goverance Checkpoint decide?
• continue until customers acceptance criteria— e.g. definition of done or MVP— is satisfied or project ends
When is the governance checkpoints
( Kill Point) discussed
• at the end of the project
What type of phases relationships can a project have (predictive)
They have sequential or overlapping relationships.
What should be applied to a governance project phase at the beginning?
• verify, invalidate project assumptions
• analyze risk
• provide detailed explanation of phase deliverables
What should be applied to a goverance predictive project phase at the end?
• key deliverables produced
• review to ensure completeness and acceptance
If huge risks occur during the goverance phase what will happen?
• deliverables are no longer needed or requirements change
• a phase or project will be terminated
What are the internal and external aspects of compliance?
• government regulations
• corporate policies
• product and project quality
• project risk
What level does PMO monitor compliance at?
Organizational level
Project team is also responsible for project activity-related compliance including:
• quality of processes and deliverables/products
• procurement and work vendors
What does legal or regulatory compliance requirements include:
• requirements of specific practices
• standards
• privacy laws
• handling of sensitive information
What are the compliance categories classification?
• environmental risks
• workplace health and safety
• ethical/ non - corrupt practices
• social responsibility
• quality
• process risks
What are compliance categories based on?
• industry and solution scope
• unique legal and regulatory exposure
How do you investigate compliance threats?
• where/ who in the organization handles compliance
• what legal regulatory requirements impact the organizations e.g. workplace safety, data protection, requirements for professional membership
• what is the organization quality policy
• are the team and stakeholders aware of compliance matters