2. Preparing for change Flashcards
Why is a procurement strategy needed?
- Not exceed budget
- Provide return or benefit intended
- Investment aligns with bigger picture of organisation
What does a procurement strategy include?
- Documents process for procuring goods and services
- Make or buy decision - can it be done in house?
- Supplier selection including
○ Selection process
○ Decisions to use one, integrated or multiple suppliers
○ Plan for negotiation - Decision on contractual relatnship
○ Conditions and forms of contract - type of contract, laws to comply with, industry standards
○ Supplier reimbursement terms - Types of contractual relationships
What determines a make or buy decision?
- Specifications required
- Capacity, speed and availability
- Required quality aspirations
- Internal and external stakeholder engagement
What is the process for ensuring a competetive tender?
- Reserach the market
- Pre-qualify suppliers
- Issue an ITT
- Respond to questions
- Recieve and evaluation bids
- Award contract. Agree terms
- Enter contract
What types of negotiation technique can be used when agreeing with suppliers?
- Best Alternative to the negotiated agreement (BATNA) - best fallback position - identify alternative positions if agreements aren’t made
- Zone of possible agreement - bargaining range where both parties set minimum targets for acceptable outcome overlap - actual outcome can be anywhere here
- Win-win - collaborative approach where both parties reach mutually beneficial agreement - problem solving, communication and strong relationships
What types of contractual relationships are there?
- Single contract
- Parallel contracts - several suppliers providing similar goods at same time. Multiple relationships
- Sequential contracts - activity dependent on completion of contract prior to this. Multiple relationships.
- Prime contracts - supplier sub-contracts to other suppliers of specific goods and/or services
What are the types of supplier reimbursement terms?
- Time and materials/ unit price
○ Client pays per unit
○ Risk of running over lies with client
○ Suitable for vague specification - allows scope to evolve- Cost plus
○ Client pays actual cost of work, plus agree for overhead and profit (% or fixed fee)
○ Suitable for when earlier start on site required and scope still being developed - emergency works - Contract target cost/ price
○ Incentivised collaboration - target cost or price agreed, both client and supplier work to achieve it
○ Suitable where collaborative relationship
○ Risk is shared - Fixed price
○ Pre-agreed price based on agreed scope
○ Risk or running over lies with supplier
○ Price may be higher due to higher risk for supplier
○ Suitable where scope clearly defined - where transactional relationship preferred
- Cost plus
- Why are project reviews important?
○ Independent perspective, ensuring details aren’t overlooked, and that plan is progressing as in line with original specification
○ May highlight where project needs to change if requirements fluid from senior stakeholders
Bring together a big picture view of the project combined detailed evidence gathering. It’s a collation of data to inform decision making and communication
- What are the different types of reviews and when do they happen?
○ Decision gates - linear: event driven and at end of each stage. Iterative: time-bound and held at end of each iteration
○ Benefits reviews - sponsor does during benefits realisation phase - 6-12 months after project handover
○ Audits - held regularly by independent individuals at set frequency or when certain issue identified
- What are the benefits of each type of review
○ Decision gates
§ Improves senior leadership involvement
§ Gains agreement from sponsor and governance board
§ Ensure project on track and delivering benefits originally set out in business case
○ Benefits review
§ Checks project achieving against benefits originally set out in business case
§ Determines what could be done to further enhance benefits
○ Audits
§ Third party confirmation of compliance with regulations etc
§ Supports confidence in robustness of project
§ Helps ensure project is following agreed governance and policies defined in quality management plans
- What are the key factors which should be reported on:
○ Progress against schedule
○ Spend - actual against spend
○ Earned value - spend and value it’s achieved
○ Audit findings including non-conformities
○ Risks and issues
- What are the key elements of information and data to make project centric decisions?
○ Status reporting - so the PM can understand status of project in relation to cost, schedule and quality against acceptance criteria
○ Estimating the project - so more realistic schedules and costs and be developed using past projects
○ Risk identification - so that need for corrective actions or escalation can be determined
○ Problem solving and options appraisal - so solutions to problems and issues can be generated using past projects
○ Availability of information - to inform decision making at key points by ensuring relevant info available in appropriate format
○ Knowledge and information management - to provide understanding on when to schedule QA and QC activities for the project, by assessing what was done on previous projects and understanding times in cycle to schedule activities to maximise findings
- Why might a project need to be re-planned following a review to ensure overall success?
○ Achieving identified scope doesn’t meet requirements
○ Motivation and satisfaction in the team are low
○ Performance of contractors or relationships with the supply chain are poor
○ Committed costs and cash flow exceed forecasts
○ Changes to risk profile or impact on time and cost are needed due to new risks
○ Communication with stakeholders is ineffective
- What does assurance do?
○ Objective and independent approach agree by sponsor and other stakeholders
○ Hand in glove with governance and risk management - any weakness in three areas will affect the project and each other element
○ It provides:
§ Confidence to the governance board that project’s on track
§ Supports decision making and change control
§ Improves risk assessment
§ Improves likelihood of project meeting objectives
- What are some example of assurance activities?
○ Controls - management system or policies, procedures, standards and procedures to control and minimise risks
○ Compliance - monitoring , audits and QA. Intend to confirm control of risks
○ Independent review - internal or external audits (eg NAO) - provide strategic overview of systems of control
- What criteria does an assurance plan need to meet?
○ Independent, objective and proportionate
○ Target greatest risks
○ Clear accountabilities for all assurance arrangements, activities and outputs
○ Timings of cycles and assurance are planned and coordinated
○ Must show governance and clear reporting routes
- What is transition management?
○ Planning and doing activities needed to shift outputs of a project into BAU
○ Considers coordination of resources comms and risk to transition with minimal disruption
Requires strategic approach and meticulous planning, and pragmatic approach to problem solving to address change and challenges when going to BAU
- What is needed to support a successful transition?
○ Managing stakeholder expectations from the offset to make outputs more likely to be accepted
○ Engaging with end users and sponsors throughout project
○ Aligning needs with outputs where possible
○ Setting path to handover and acceptance by working with stakeholders who will own outputs
○ Ensuring clear communication to reduce risk of PM misunderstanding requirements of end users
- What is change impact analysis and how can it be used to help transition management?
○ Method for analysing scope and change to new BAU state to understand impact on people, performance, processes, systems and culture
○ Helps support planning and communication of change
○ It involves the following steps:
1. Define the change and it’s purpose, objectives, scope etc
2. Identify organisational areas including people, performance, processses, culture etc
3. Evaluate the level of impact the change will have on each area
4. Develop an action plan to address the impacts of the change to align with shared vision and communicate reguarly
- What are the steps in progressive implementation (knowledge transfer)?
a. Launch - “what’s this”
b. Experimentation - “ i tried it once”
c. Practicing “i use it sometimes
d. Embedded “this is how we do things here”
- What are important things to consider in progressive implementation?
○ Relationship between project team and BAU people
○ Sponsor is key champion of this work and needs to take ownership of knowledge transfer etc
○ Extended life cycle approach makes project team accountable for change management - preventing knowledge boundaries between project and BAU teams
○ Learning and development needed to train BAU staff and to promote continuous improvement
- What is transition planning and what should it include?
○ Starts and the beginning of the project
○ May include:
§ Acceptance of pertient documentation
§ Acceptance certificates signed by sponsor - agreement that tasks to be completed and criteria to meet to get final approval
§ Transfer of responsibility for the deliverables
§ Formal transition of ownership
- What information is provided during handover for linear projects (or at different stages of iterative)?
○ Process maps
○ Project documents
○ Ownership of supplier relationships
○ Ongoing licensing agreements
○ Training on processes etc.
- Why is engagement important in handover?
○ Crucial to success of incorporating change as individuals will have vested interest in project’s outcomes
○ Early engagement with those stakeholders impacted important
○ Strategic alignment of goals and understanding of future state through collaborative approach to ensure shared ownership and vision
○ Communicating benefits helps support common understanding of the reason of the project. Benefits champion can support this communication with stakeholders