1. Projmgmt-1/35 DePaul University Project Management I - Getting Started Instructor: David A. Lash

2. Projmgmt-2/35 Project Management Key Success Factors 1. Agreement Among Project Team, Customer(s) and Management 2. A Plan That Shows Overall Clear Path 3. Constant Effective Communication Among Everyone In Project 4. Scope Management - Defensive Measures Against Growing Scope 5. Management Support -

3. Projmgmt-3/35 Project Definition & Critical Success Factors Project Definition Effects 3 of the 5 CSFs Agreement, Scope, Management Support Tools of Project Definition Include 1. Charter 2. SOW 3. Responsibility Matrix 4. Communication Plan

4. Projmgmt-4/35 Purpose Of the Charter A Straightforward Announcement Of The Project A One-Time Announcement That States 1. Name Of The Project 2. Project Purpose 3. Project Manager Name 4. Perhaps The Goal & Responsibilities of the PM 5. Anything else to ensure responsibility is well defined Charter is reviewed and issued by sponsor.

5. Projmgmt-5/35 Project Definition & Critical Success Factors Tools of Project Definition Include 1. Charter 2. SOW 3. Responsibility Matrix 4. Communication Plan

6. Projmgmt-6/35 Statement Of Work Clarifies with stakeholders the goals, scope, and deliverables of project Sometimes may be a contract (E.g., an outsourcing arrangement for SOW) Other times a project clarification device Reviewed by project board/sponsor (sometimes with team member input).

7. Projmgmt-7/35 Elements of SOW Purpose Of The Project - Why are we doing it? - Be Specific Goal statement of the project - SMART Scope statement of project - what is in or out of scope Deliverables of project - definition of what the project will produce Cost and schedule estimates - Order of magnitude costs Formal Stakeholder definition - Chain of command - who reports to who

8. Projmgmt-8/35 Defining The Goal Need to clearly think out the goal and define it in writing Should spell out the criteria for success Entire team should agree to the goal

9. Projmgmt-9/35 Criteria for Defining Goals Goals Must be: 1. S pecific - clear enough so everyone can understand it from the written form only. 2. M easurable - identify the objective criteria will be used to judge the success of the project 3. A greed Upon - must achieve consensus form everyone on the project. 4. R ealistic - must be something have a reasonable chance of doing. (e.g., build a house for 1 dollar) 5. T ime component - Need definite termination date

10. Projmgmt-10/35 Goal Example Consider this goal: Roll out a new version of XXX software Or reword it to this: Deploy Version YYY of XXX software to ZZZ users - fully deployed by 4/22/00

11. Projmgmt-11/35 Another Goal Example Consider this goal: Deploy new release of Windows 2000 to all our desktop machines Or reword it to this: Deploy Windows 2000 to all machines by 4/22/00 - runs the application XYZ with 4000 transactions per hour

12. Projmgmt-12/35 A Real Life Goal Example This paper presents the objective, scope and high level plans for implementing the items outlined in the XXXX Disaster Recovery Technical Assessment. The two main objectives are to provide protection of data by ensuring nightly copies of key databases for all products are made to an off-site location and identify and set in place an appropriate recovery strategy for the server environments. While these steps will not completely achieve our recovery objectives, they will significantly reduce our exposure. The goal is to provide the capability to rebuild current product code within Y days of a catastrophic failure in either the XXXX or YYY environments.

13. Projmgmt-13/35 Elements of SOW Purpose Of The Project - Why are we doing it? Goal statement of the project - SMART Scope statement of project - what is in or out of scope Deliverables of project - definition of what the project will produce Cost and schedule estimates - Order of magnitude costs Formal Stakeholder definition - Chain of command - who reports to who

14. Projmgmt-14/35 Scope Purpose: Define project boundaries Should describe major activities in such a way that its impossible to add activities without adding to the scope statement Clarify: What is relationship to this project and other related ones What is within the scope What is beyond the scope What are the major deliverables

15. Projmgmt-15/35 Items Within Scope The following items are within scope of this project  Development and documentation of a Reciprocal Recovery Strategy between sites.  Development of requirements, procedures to create a nightly copy of key data.  Determine the network capacity to complete the nightly transfer and to allow user access to it once it is established in sister site.  Cross-training of staff on a common set of backup, restoration and recovery policies and procedures.  Rebuild of base within X days in event that either the XXXX or YYYYY server environments encounter a catastrophic failure.

16. Projmgmt-16/35 Items Outside Of Scope The following items are outside the scope of this project  Ensuring business continuity for an entire department  Creation of full Disaster Recovery Plan meeting the Recovery Time Objectives outlined in the Technical Assessment.  Ensuring building and building service D/R

17. Projmgmt-17/35 Elements of SOW Purpose Of The Project - Why are we doing it? Goal statement of the project - SMART Scope statement of project - what is in or out of scope Deliverables of project - definition of what the project will produce Cost and schedule estimates - Order of magnitude costs Formal Stakeholder definition - Chain of command - who reports to who

18. Projmgmt-18/35 Deliverables A. Development of requirements and procedures to create a nightly copy of the key data..Define the precise data needing replication with XXXX and YYYY..Quantify WAN traffic and get related equipment..Successful access of D/R of data.Documentation of all processes and procedures B. Development and documentation of an Internal Reciprocal Recovery Strategy to recover Environment - Determine what needs to be similar - Implement it

19. Projmgmt-19/35 Elements of SOW Purpose Of The Project - Why are we doing it? Goal statement of the project - SMART Scope statement of project - what is in or out of scope Deliverables of project - definition of what the project will produce Cost and schedule estimates - Order of magnitude costs Formal Stakeholder definition - Chain of command - who reports to who

20. Projmgmt-20/35 More on Charter/SOW. Cost and Schedule Estimates - What are the budget concerns? - How fixed is the budget it? - How good of an estimate can you make? - Can a reliable estimate be made?

21. Projmgmt-21/35 Elements of SOW Purpose Of The Project - Why are we doing it? Goal statement of the project - SMART Scope statement of project - what is in or out of scope Deliverables of project - definition of what the project will produce Cost and schedule estimates - Order of magnitude costs Formal Stakeholder definition - Chain of command - who reports to who

22. Projmgmt-22/35 Formal Stakeholder Definition Using Definitions from Chapt 3, create a table with at least the following Role Description Who Percent Involvement Estimated Duration

23. Projmgmt-23/35 Formal Stakeholder Definition - Example Planner Jane PM 100% 5 Weeks IT Admin Joe Sets up systems 50% 2 Weeks configures them Ap “A” Hans Identifies key data 50% 3 weeks Owner Ap “B” Mike Identifies key data 50% 3 weeks Owner Sponsor Jean Project Champion & <5% Monthly review Sponsor App Janet Project Board of < 5% Monthly Review Mgmt Directors Admin Frank Copies data & 100% 4 weeks. programs

24. Projmgmt-24/35 Elements of SOW Purpose Of The Project - Why are we doing it? Goal statement of the project - SMART Scope statement of project - what is in or out of scope Deliverables of project - definition of what the project will produce Cost and schedule estimates - Order of magnitude costs Formal Stakeholder definition - Chain of command - who reports to who

25. Projmgmt-25/35 Chain Of Command Create a chart similar to page 62 figure 4.1 Depends on how clear these roles are to the project.

26. Projmgmt-26/35 Other SOW Items Can include information about the phases of the project. What methods will the project follow? Incremental VS waterfall? Is there a phased approach? E.g., Phased - D/R plan Phase 1 - Plan for vital data Phase 2 - Plan for all business data Phase 3 - Building Facilities recovery

27. Projmgmt-27/35 Next Exercise For your select project, start to develop a Charter and SOW. - Write the charter - Develop the essential items of the SOW.

28. Projmgmt-28/35 Project Definition & Critical Success Factors Tools of Project Definition Include 1. Charter 2. SOW 3. Responsibility Matrix 4. Communication Plan

29. Projmgmt-29/35 Responsibility Matrix Defines key groups and their responsibilities. Help define cross organization responsibilities E.g., change in tool design requires work in another department. Will other department have a role in decisions? Can be done for each major task or for specific areas Best if done up-front before turf wars develop

30. Projmgmt-30/35 Responsibility Matrix List the major activities of project on vertical axis (see page 63 table 4.2) List the stakeholder groups on horizontal axis Code the responsibility matrix E - Execution responsibility (get work done) C - Must be consulted I - Must be informed A - Approval authority Review matrix

31. Projmgmt-31/35 Project Definition & Critical Success Factors Tools of Project Definition Include 1. Charter 2. SOW 3. Responsibility Matrix 4. Communication Plan

32. Projmgmt-32/35 Communication Plan u A written strategy for getting the right info to the right people – Sponsors - Probably a formal mechanism – Project Review Board - Separate from sponsor? – Functional management - as providers of resources may need to know – Customers - Make ultimate decisions, likely different levels of customer involvement – Project team - probably needs regular communication

33. Projmgmt-33/35 Communication Plan u What needs to be communicated? – Authorizations - major document agreements, such as project plans, SOW, product specifications – Regular Status Updates - Cost and status updates. – Coordination - General coordination generally among team members.

34. Projmgmt-34/35 Sample Communication Plan

35. Projmgmt-35/35 PM Should Be Defined Process u Charter – Purpose – review and publish u SOW – A. Document goals, scope deliverables HL budget estimate – Review with Project board u Communication Plan – Document communication methods of various level – Review with project board, various stakeholders u Risk Strategy u Project Plan u Execute HL Plan LL Plan

36. Projmgmt-36/35 In Class Exercise u Break Into Groups – Start the process of project definition u Work on a Charter u Write a specific goal statement u Define the scope of the project u Out of class deliverable – Create a project Charter, SOW, Responsibility Matrix and Communication Plan