PM Workshop # 3

1. PM Workshop # 3 05 July 2013 A.Bazovoy

2. Questions from the previous PM trainingscope of work / WO Task SSV activity 1) Pre-visits activity 2 h cost 3 h 2) on site activity passthrough cash revenew

3. what should be improved, changed? Share Best Practice (Case study, BD – Contracts/ Finance ) – CP-060 Alexey 5-10’ introduction Budget review …….

4. Activities to be done by PM Action/Decision Log => 2) SIF =>3) recruitment figures 058 => 4) annotated MV reports (SOP: PM is responsible for annotated SMVreport). Annotated SMVRs to be prepared by Vera and uploaded into - ? (Alexey to make a final decision) BD meeting – lessons learntTo inform Katja Ivantsova about Financial status Report update (done by end of month) – to make a reminder for PMS (AB)increase the number of SMVs planned SMVs

6. Risk Management

7. - Risk Metalanguage – Risk Management Process – Risk Management Plan – to accurately describe ‘Risks’ – various tools to identify and analyse Risks – importance of appropriate Risk Response Plans

8. Initial Thoughts on Risk –Risks are present in our everyday lives •Crossing the road •Journey to work •Going on vacation –Why is it that with our family we tend to take a different approach than in the work place? •We tell children not to go near the road •Teach them how to cross the road safely •Direct them to a pedestrian crossing point –We then assess if these steps are working or if we can improve These are the basic elements of Managing Risk

9. How Risk Management Integrates With Other Project Management Processes

10. BD (feedback) Out of Scope => Addendum (AM) -> invoicing (EI) Katja is in cc to BD (OoScope) Review – monthly To issue Adendum from 3000 $ Finance – Katja Iv FPM (invoicing) FSReport (monthly) 01. Contact Katja + Alexey in case of Out of Scope! - Client RA/ECs Stakeholder Map Ilja_feasibility Lead PM Vendor Project Team Lab Depot site AT_D,CO QA

11. What is a Project Risk? BD meeting

12. Risk & Opportunity vs. Amount at Stake

13. Cause? Risk? Effect? • The customer has chosen the sites to be used • We’ve never done a project like this before • We may not have enough patients enrolled • Samples may not get delivered to our Central lab in time • We do not have enough resources • Project communications may take too much time • We will be using a new I.T. system • We are going to be over budget • Database lock will not happen on time • We may not initiate enough sites

14. Risk Metalanguage “As a result of a <definite cause>, an <uncertain event> may occur, which would lead to <effect on project objective(s)>”* Cause -> Risk -> Effect Using this approach allows the project team to identifyreal risks, not causes or effects of risks Risks may become issues in the future Issuesarehappening now! –“An issue is a risk whose time has come!” The goal of Risk Management is to keep risks from becoming issues

15. What is Risk Management? A formal, systematic process to identify, analyze and respond to project risks, thereby removing or reducing their impact on the project –A proactive process –Done throughout the project lifecycle –An integral part of good project management Why Conduct Risk Management? Enables project team / management to: –Properly prepare for possible risk events “Known and Unknown” –Prevent / minimize surprises on the project –Prevent risks from becoming major issues –Minimise probability and effects of negative events –Enhance probability and effects of positive events –Increase the potential for project success