Project Management Introduction To Project Management
Project Management Introduction To Project Management
Project Management Introduction To Project Management
Lecture 1
Learning Objectives
Understand the growing need for better project management, especially for information technology projects. Explain what a project is, provide examples of information technology projects, list various attributes of projects, and describe the triple constraint of projects.
2
Learning Objectives
Describe project management and discuss key elements of the project management framework, including project stakeholders, the project management knowledge areas, common tools and techniques, and project success factors.
Understand the role of the project manager by describing what project managers do, what skills they need, and what the career field is like for information technology project managers.
3
What Is a Project?
A project is a temporary endeavor undertaken to create a unique product, service, or result.*
Operations is work done to sustain the business. A project ends when its objectives have been reached, or the project has been terminated. Projects can be large or small and take a short or long time to complete.
*PMI, A Guide to the Project Management Body of Knowledge (PMBOK Guide) (2004), p. 5.
6
Project Attributes
A project:
Has a unique purpose. Is temporary. Is developed using progressive elaboration. Requires resources, often from various areas. Should have a primary customer or sponsor.
The project sponsor usually provides the direction and funding for the project.
Involves uncertainty.
7
Successful project management means meeting all three goals (scope, time, and cost) and satisfying the projects sponsor! Not easy!!!
10
*PMI, A Guide to the Project Management Body of Knowledge (PMBOK Guide) (2004), p. 8.
11
12
Project Stakeholders
Stakeholders are the people involved in or affected by project activities. Stakeholders include:
Project sponsor Project manager Project team Support staff Customers Users Suppliers Opponents to the project
13
7. Firm basic
requirements 8. Formal methodology 9. Reliable estimates 10. Other criteria, such as small milestones, proper planning, competent staff, and ownership
*Northwest Center for Emerging Technologies, Building a Foundation for Tomorrow: Skills Standards for Information Technology, Belleview, WA, 1999. 17
Soft skills include being able to work with various types of people.
19
20
21
UK Jobs Market
www.itjobswatch.co.uk as at 15/01/08
22
The WBS is shown on the left, and each tasks start and finish dates are shown on the right. First used in 1917, early Gantt charts were drawn by hand. (Use MicroSoft Project or similar tool) 23
Each box is a project task from the WBS. Arrows show dependencies between tasks. The bolded tasks are on the critical path. If any task on the critical path takes longer to complete than planned, the whole project will slip unless something is done. Network diagrams were first used in 1958 on the Navy Polaris project before project management software was available. 24
26
27
Table 3-1. Relationships Among Process Groups and Knowledge Areas (contd)
28
Project Initiation
Initiating a project includes recognising and starting a new project or project phase. Some organisations use a pre-initiation phase, while others include items such as developing a business case as part of the initiation. The main goal is to formally select and start off projects. Key outputs include:
Assigning the project manager. Identifying key stakeholders. Completing a business case. Project charter completion and getting signatures on it. 29
Project Planning
The main purpose of project planning is to guide execution. Every knowledge area includes planning information (see Table 3-5 on pages 87-89). Key outputs included in projects 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 prioritised risks (part of a risk register).
See sample documents on pages 90-98.
30
31
32
33
Project Closing
Involves gaining stakeholder and customer
acceptance of the final products and services. Even if projects are not completed, they should be formally closed in order to reflect on what can be learned to improve future projects. Outputs include project archives and lessons learned, which are part of organisational process assets. Most projects also include a final report and presentation to the sponsor or senior management. 35
Further Information
Refer to X-Stream Project Management module for further references & materials Recommended Reading:
Information Technology Project Management 4th ed by K Schwalbe Introduction to Project Management by K Schwalbe A hackers Guide to Project Management by A Johnston PRINCE 2 a practical handbook by Colin Bentley
36