Download presentation
Presentation is loading. Please wait.
Published bySteven Clark Modified over 9 years ago
1
Topic 2- 1ICT 327 Management of IT Projects Semester 1, 2005 Topic 2 Project Planning & Initiation Schwalbe: Chapter 3 Compiled by Diana Adorno and contributions by Yvonne Parle, Senior Consultant. Peritia Project Management, www.peritiapm.comwww.peritiapm.com
2
Topic 2- 2ICT 327 Management of IT Projects Semester 1, 2005 Reading Essential Schwalbe Chapter 3 CHAOS reports Recommended PMBOK Chapter 3 See also List of references and website at end of topic.
3
Topic 2- 3ICT 327 Management of IT Projects Semester 1, 2005 Learning Objectives At the end of this topic, you should be able to: Identify what activities comprise the project initiation and planning. Give examples of the key risks at this stage of the project. List the key factors of success as listed by the CHAOS reports and what can be done about them at the initiation and planning stage
4
Topic 2- 4ICT 327 Management of IT Projects Semester 1, 2005 Learning Objectives At the end of this topic, you should be able to: Review a case study of an organization and identify the project management activities in the initiative and planning phases in any project. Explain the contribution that effective project initiation, project planning, makes to project success
5
Topic 2- 5ICT 327 Management of IT Projects Semester 1, 2005 Time and projects time Phase Project startProject end
6
Topic 2- 6ICT 327 Management of IT Projects Semester 1, 2005 Overlap of Process Groups in a Phase (PMBOK® Guide, 2000, p. 31)
7
Topic 2- 7ICT 327 Management of IT Projects Semester 1, 2005 Project Definition (Buttrick 2000) If you don’t know why you are doing the project, consider terminating it If you don’t know what you are delivering, regard your costs and timescales as unstable and your risk high If you don’t know when it will be done, carry out more investigations until you do If you don’t know how you will approach the project, regard risk as high and investigate further
8
Topic 2- 8ICT 327 Management of IT Projects Semester 1, 2005 9 Knowledge Areas
9
Topic 2- 9ICT 327 Management of IT Projects Semester 1, 2005 Relationships Among Process Groups & Knowledge Areas (PMBOK® Guide 2000, p. 38)
10
Topic 2- 10ICT 327 Management of IT Projects Semester 1, 2005 Project Initiation Initiating a project includes recognizing and starting a new project or project phase Some organizations use a pre-initiation phase, while others include items like developing a business case as part of initiation Main goal is to formally select and start off projects Key outputs include: Assigning the project manager Identifying key stakeholders Completing a business case (see text pp74-76) Completing a project charter & getting signatures on it (see text pp77-78)
11
Topic 2- 11ICT 327 Management of IT Projects Semester 1, 2005 Question What is a stakeholder? What is it important to identify all of the stakeholders?
12
Topic 2- 12ICT 327 Management of IT Projects Semester 1, 2005 Example stakeholders
13
Topic 2- 13ICT 327 Management of IT Projects Semester 1, 2005 Stakeholders List stakeholders Consider external groups, internal groups, other projects, people groups, partners Identify their stake (or interest) StakeholderInterest
14
Topic 2- 14ICT 327 Management of IT Projects Semester 1, 2005 Stakeholder analysis map Degree to which they are critical to the success of project Impact on stakeholder High Low High Buy-in Address concerns Ownership Address concerns & active involvement Buy-in Some involvement required Awareness Keep informed
15
Topic 2- 15ICT 327 Management of IT Projects Semester 1, 2005 Exercise List all of the stakeholders for the Nanny website Against each person or group, write down what their stake is. That is, what is their interest in the project. Place them on the map
16
Topic 2- 16ICT 327 Management of IT Projects Semester 1, 2005 Project Initiation Documents Every organization has its own variations of what documents are required for project initiation. It’s important to identify the need for projects, who the stakeholders are, and what the main goals are for the project
17
Topic 2- 17ICT 327 Management of IT Projects Semester 1, 2005 Project Planning & Initiation “If you plan for nothing – you will surely get there” Define the job in detail Get the right people in the right roles Estimate the time and costs Break the job down into smaller tasks Develop project standards Establish a change procedure Agree on Acceptance criteria
18
Topic 2- 18ICT 327 Management of IT Projects Semester 1, 2005 Activities in the planning phase Integration Project plan development Scope Scope planning, scope definition Time Activity definition, activity sequencing, activity duration, estimating, schedule development Cost Resource planning, cost estimating, cost budgeting
19
Topic 2- 19ICT 327 Management of IT Projects Semester 1, 2005 Activities in the planning phase Quality Quality planning Human Resource Organisational planning, staff acquisition Communications Communications planning Risk Risk management planning, risk identification, qualitative risk analysis, risk response planning Procurement Procurement planning, Solicitation planning
20
Topic 2- 20ICT 327 Management of IT Projects Semester 1, 2005 Detailed planning approach 90% planning, 10% execution Why do I need to write it up? CTRs (Cost, Time, Resource sheets) XX Hour Rule – no task should be more than 30 hours. CTRs are used as Checklist for completeness Clear communication document Input to Kick off Meeting Progress reporting
21
Topic 2- 21ICT 327 Management of IT Projects Semester 1, 2005 Project Planning 90% planning, 10% execution The main purpose of project planning is to guide execution Every knowledge area includes planning information (see Table 3-5 on pages 79-80) Key outputs include: A team contract A scope statement A work breakdown structure (WBS)* A project schedule, in the form of a Gantt chart with all dependencies and resources entered* A list of prioritized risks* See sample documents on pages 83-90 (text) * Project Plan
22
Topic 2- 22ICT 327 Management of IT Projects Semester 1, 2005 Question Why is a scope statement critical? If you were organising a party, what is in scope and what is out of scope.
23
Topic 2- 23ICT 327 Management of IT Projects Semester 1, 2005 Work Breakdown approaches Using guidelines Analogy Top down Bottom up Mind-mapping More on this in Schwalbe, Chapter 5 pp157-167
24
Topic 2- 24ICT 327 Management of IT Projects Semester 1, 2005 Example Project Gantt Chart
25
Topic 2- 25ICT 327 Management of IT Projects Semester 1, 2005 Question For a party: Use mind-mapping method to produce a WBS. Use the top-down approach Use the bottom-up approach
26
Topic 2- 26ICT 327 Management of IT Projects Semester 1, 2005 Example List of Prioritized Risks
27
Topic 2- 27ICT 327 Management of IT Projects Semester 1, 2005 Activity List all of your risks for completing this unit. Identify the top 5
28
Topic 2- 28ICT 327 Management of IT Projects Semester 1, 2005 Project Checklist Has a project definition been written, reviewed by the stakeholders and approved by the project sponsor Have the benefits been fully assessed and quantified wherever possible Do the benefits match the needs? Have all the risks been identified and categorized? Has a comprehensive and satisfactory work breakdown been developed? Does the work breakdown reflect the deliverables to be produced? Are all key logical relationships between projects and activities clear? Has the plan been developed to minimize or offset the risks?
29
Topic 2- 29ICT 327 Management of IT Projects Semester 1, 2005 For each deliverable, check Are the project deliverables relevant and are they feasible both to produce and implement? Have quality criteria been established? Is it clear who is accountable for preparing each deliverable? Is it clear who will review the deliverable prior to signing off acceptance of each deliverable? Is it clear who will sign off each deliverable? Has sufficient time been allowed for reviewing/amending each deliverable?
30
Topic 2- 30ICT 327 Management of IT Projects Semester 1, 2005 References Text A guide to the Project Management Body of Knowledge (PMBOK Guide) 2000, PMI Project Management – Best practices for IT Professionals, 2 nd edition, Murch, Richard, 2001, Prentice Hall The Interactive Project Workout, Buttrick, Robert, 2000,Prentice Hall
31
Topic 2- 31ICT 327 Management of IT Projects Semester 1, 2005 References Websites Project Management Institute www.pmi.comwww.pmi.com Gantthead www.gantthead.comwww.gantthead.com Thomsett www.thomsett.com.auwww.thomsett.com.au ProjectNet www.projectnet.co.ukwww.projectnet.co.uk The International Project Management Help Desk www.geocities.com/Athens/Delphi/8390www.geocities.com/Athens/Delphi/8390
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.