Lesson 8 Flashcards
Issue-
• a condition or situation that may have an impact on the project objectives
~ Predictive teams use the term issue log
Impediment
• an obstacle that prevents the team from achieving its objectives- Also known as a blocker
~ Adaptive teams tend to use an impediment log
Risks- Predictive
• focused on the future
• can be positive or negative
• are documented in the risk register
• response is called a “risk response”
Issues- Predictive
• focused on the present
• will always be negative
• are documented in the issue log
• response is called a “workaround”
Issue Log- Predictive
• track problems, inconsistencies or conflicts and conduct investigation towards resolution
Steps to Discover & Solve Impediments Using Scrum- Adaptive
• discover the problem/ cause
• solve it. The scrum master is responsible for finding a resolution with concerned parties
~ often involves dealing with conflict somewhere in the organization
~ resolution can help the organization grow in agility
Removing Impediments- Adaptive
• track impediments
• reprioritize product backlog
• use daily standup meetings
• be a servant leader
Causes of Project Changes- Predictive
• inaccurate initial estimates
• new regulations
• missed requirements
• specification changes
Causes of Project Changes- Adaptive
• product backlog
• sprints
Product backlog
• Running To Do List
Monitor the External Business Environment
• change can bring negatives as well as positives, such as opportunities to add or extend value
~ monitor the external environment
~ remain vigilant for threats
~ constantly update the risk register and thresholds
~ use tools
~~ PESTLE (Political, Economic, Sociological, Technological, Legal Environmental)
~~ TECOP (Technical, Environmental, Commercial, Operational, Political)
~~ VUCA ( Volatility, Uncertainty, Complexity, Ambiguity)
Manage Change Overview and Controls- Predictive
Overview
• perform Integrared Change Control linear process
Control
• perform Integrated Change Control process
• change request process
• change control board (CCB)
• artifact management (updates)
Manage Change Overview and Controls- Adaptive
Overview
• feedback and development cycle
Controls
• product owner role- key decision maker and runs backlog
• everyone participates in backlog refinement
• use demos to understand requirements
• No changes allowed during a sprint
Manage Change Overview and Controls- Hybrid
Control and Overview
• use predictive or adaptive
Which Approach will utilize the Change Management Process Flowchart? Adaptive, Predictive or Hybrid
• Predictive
What are the 4 types of Change Request
• Corrective Action
• Preventive Action
• Defect Repair
• A Change
Correction Action- Change Request
• adjusts the performance of the project work with the project management plan
Prevention Action- Change Request
• ensures future performance of the project work with the project management plan
Defect Repair - Change Request
• modifies a nonconformance without the project
A Change - Change Request
• modifies a project baseline
Predictive Change Control Systems
Change Control Board
• forms tracking methods, processes and approval levels required for authorizing or rejecting requested change
Contract Change Control System- Predictive
• the system used to collect, track, adjudicate and communicate changes to a contract
What are the types of contract and changes
• administrative changes
• contract modifications
• supplemental agreement
• constructive changes
• termination of contract
Types of contract and changes - Administrative Changes
• non substantive changes, usually about contract administration method
Types of contract and changes - Contract Modifications
• substantive change to contract requirements or product requirements
Types of contract and changes - Supplemental Agreement
• an additional agreement related to the contract but negotiated separately
Types of contract and changes - Corrective Changes
• changes made by buyer through action or inaction
Types of contract and changes - Termination of Contract
• vendor defaults or buyers need changes
What are the legal concepts when managing disputes
• warranty
• waiver
• breach of contract
• cease and desist letter
Does Procurements need to be closed to close a Project?
T or F
• True
Warranty- Legal Concept
• a promise, explicit or implied, that goods or services will meet a pre- determined standard. The standard may cover reliability, fitness for use, and safety
Waiver- Legal Concept
• a legally binding provision in which one party in a contract agrees to forfeit a claim without the other party becoming liable, even inadvertently
Breach Of Contract- Legal Concept
• failure to meet some or all the obligations of a contract. It may result in damages paid to the injured party, litigation or other ramifications
Cease & Desist ( C& D) letter- Legal Concept
• a letter sent to an individual or a business to stop (cease) allegedly illegal activities and to not undertake them again (desist) . Often uses as a warning of impending legal action if it is ignored
Process, Asjudicate and Communicate Claims
• contested changes and potential constructive changes including
~ lack of agreement on compensation for change
~ lack of agreement that change occured
• if not resolved, handle through alternative dispute resolution (ADR) established in contract
• settlement through negotiation is preferred
• the “last resort” is litigation
Adaptive-Upfate Project Management Plan based on:
• the scope of changes, you may need to update
~ scope
~ time lines
~ work packages
~ team member assignments
Would an agile (adaptive) team might remove lower- value deliverables from the scope to make room for the change? T or F
• True
Predictive- Projects or Phase Close Fulfillment
• stakeholders accept deliverables based on acceptance criteria established at the beginning of the project management plan
• acceptance criteria may be modified during a project life cycle
• use the requirements traceability matrix to ensure completion and approval of all requirements
Adaptive- Projects or Phase Close Fulfillment
• at the end of an iteration, the tram and stakeholders assess the product/ service against their mutually agreed definition of done (DoD)
• final acceptance occurs prior to product release
Why Projects or Phases Close- Premature or Forced Closure
• requirements/needs change
• project/ deliverables is no longer feasible
~ internal- organization makes change to the business case
~ external- a legal or regulatory change prohibits progress
• project/ deliverables is no longer desirable
• impediment encountered
~ financial support is not available to complete the requirements
~ risks with significant consequences make successful completion impossible
Close Project or Phase Activities - Predictive
• acceptance of deliverables or product by customers
• transition of deliverables or product to customer
• notify enterprise and organizational functions; update and OPAs
• prepare final report
• conclude external obligations, including legal, regulatory, contractual— e.g. transfer of liability, closure of all accounts in financial system
• archive project information
• release resource la ( human, financial and physical assets)
Predictive- Transitions ( Handovers)
• deliverables are handed to the customer or owner. Transition/ handovers specifications for deliverables are in the project management plan
Hybrid- Transitions ( Handovers)
• a tailored solution that delivers value— most likely in an incremental way— to the organization
Adaptive- Transitions ( Handovers)
• every iteration output is handed to the product owner
Transition Readiness
•’readiness may require additional change management activities to ensure adoption and overcome resistance.
Assess the readiness of all parties
• end users
• the business
• project team
• support staff
