1. PROJECT PLANNING AND SCHEDULING BY: AMINATH SHAAYAN SHAHID

2. LEARNING OBJECTIVES 1.Understand how to Define and manage Project Scope 2.Understand the importance of project planning 3.Understand how to develop a project plan 4.Understand how to develop and maintain project schedules 2

3. UNIT STRUCTURE SessionContent Session 1Defining the Project Scope Session 2Establishing Project Priorities Session 3Work Breakdown Structures Session 4Process Breakdown Structures Session 5Understanding Project Plans Session 6Developing the Project Network Session 7Constructing a Project Network Session 8Activity-On-Node (AON) Fundamentals Session 9Network Forward and Backward Pass Information Session 10Resource Scheduling Session 11Resource Allocation Methods Session 12Revision 3

4. ASSESSMENT SCHEDULE ComponentsWeighting Group Assignment30% Final Exam70% 4

5. Defining the Project Scope SESSION 1

6. WHAT IS A PROJECT? A project is temporary It has a definite start and end date Thereby having a defined scope and resources A project is also unique It is not a routine everyday operational work with repetitive outcome It is a specific set of activities designed to accomplish a well- defined unique objective 6

7. FAMOUS PROJECTS 7

8. 8

9. 9

10. EXAMPLE Putting together a team of research analysts to come up with a design and prototype of a water proof phone within 6 months Project Manufacturing thousands of those water proof phones using the design blueprint Operation 10

11. Did your project ask for this? 11

12. ….And end up building this instead? 12

13. Why does it happen? 13

14. MEANING OF SCOPE? Scope refers to all the work involved in creating the products of the project and the processes used to create them. It defines what is or is not to be done Project scope is a definition of the end result or mission of your project—a product or service for your client/customer. Scope describes what you expect to deliver to your customer when the project is complete. For planning and measuring project success. 14

15. Definition: Project Scope Statement The narrative description of the project scope, including major deliverables, project objectives, project assumptions, project constraints, and a statement of work, that provides a documented basis for making future project decisions and for confirming or developing a common understanding of project scope among the stakeholders. 15

16. Purpose of Scope Statement To clearly define the deliverable(s) for the end user. To focus the project on successful completion of its goals. To be used by the project owner and participants as a planning tool and for measuring success. Should be developed under the direction of the project manager and customer The complete understanding of and management of exactly what is and is not to be delivered within the project 16

17. Scope Management Definition? Scope Management involves… Initiation, Planning, Definition and Verification of the features and functionality required for completion of the project. 17

18. Project Scope checklist 1. Project Goal and objective 2. Deliverables 3. Milestones 4. Technical requirements 5. Limits and exclusions 6. Reviews with customer or client 18

19. Project Scope Checklist 1. Project objective: to define the over-all objective to meet your customer’s need(s) Objectives should be SMART –Specific, Measurable, Attainable, Realistic, Time-limited – what, when, and how much Example: to develop a program that automatically translates verbal sentences in English to Dhivehi. The project should be completed within three years at a cost not to exceed $1.5 million. 19

20. Project Scope Checklist 2. Deliverables : the expected out-puts over the life of the project. Any measurable, tangible, verifiable outcome, result or item that must be produced to complete a project or part of a project. For example, deliverables in the early design phase of a project might be a list of specifications. In the second phase deliverables could be software coding and a technical manual. The next phase could be to test prototypes. The final phase could be final tests and approved software. 20

21. Project Scope Checklist 3. Milestones : significant event in a project that occurs at a point in time. A rough-cut estimates of time, cost, and resources for the project for example: testing complete and finished by July 1 of the same year. 21

22. Project Scope Checklist 4. Technical requirements: to ensure proper performance. Examples from information systems projects include speed and capacity of database systems and connectivity with alternative systems. 5. Limits and exclusions: The things that will not be included in the project. Examples: house will be built, but no landscaping or security devices added; software will be installed, but no training given. 22

23. Project Scope Checklist 6. Reviews with customer: Clear communication in all these issues is imperative to avoid claims or misunderstanding. 23

24. Scope Statements or Project Charter Scope Statements Also called statement of work (SOW) Project Charter Can contain an expanded version of scope statement a document that authorizes the project manager to initiate and lead the project 24

25. Scope Creep scope creep means added costs and possible project delays. Changes in requirements, specifications, and priorities frequently result in cost overruns and delays. Scope Creep is one of the reasons why you must:  spend the necessary time in the definition of the project’s scope  verify the scope with the stakeholders. 25

26. Scope Creep Projects are steered by the business needs of an organization… …and influenced by the Triple Constraint:  Scope  Time  Cost 26

27. PROJECT CONSTRAINTS 27 Note that these constraints are interrelated, so a strain on one of the core constraints will affect one or more of the other constraints This is also called Iron Triangle of Project Management

28. ANY QUESTIONS? 28

29. THANK YOU 29