Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
by
INTRODUCTION
CHAPTER 2
45
CHAPTER 3
67
CHAPTER 4
89
CHAPTER 5
10 11
Introduction
INTRODUCTION TO PROJECT MANAGEMENT
Project Management body of knowledge is a Guide to Globally recognized standards to establish a good contact between Professionals and knowledge.
PROJECT:
Its a temporary nature task or bunch of tasks meant to provide an outcome w.r.t the requirements given. It may produce some service or a product as an outcome on its success. Temporary nature means it has some limits (start and end point). Apart from duration, end means Goals are achieved or the stakeholders requirements changed or the outcomes doesnt meets the requirements so its end of the project. Every project has some unique characteristics, which describes its structure (physical or logical), which results the definite, different design, circumstances and stakeholders as well. A project may have single Stakeholder may have multiple stakeholder or may involve multiple organizations; all depends upon the nature of the project.
PROJECT MANAGEMENT:
Project Management is the process of achieving certain kind of goals using appropriate knowledge, skills, tools and techniques. It comprises of 5(not limited to) major process groups like (1) Initiating (2) Planning (3) Executing (4) Monitoring and Control (5) Closing. These 5 major processes can be further elaborated according to the requirements and needs of stakeholders. The specific Project constraints that could be influences, project management team need to focus on are the circumstances and characteristics of Project. But we have to balance key factors of Project like Scope, Quality, Schedule, Budget, Recourse and Risks. If any of them is unbalanced it can affect one of the other or may be more than one.
PROGRAM MANAGEMENT:
Program Management is a Group Activity of sub-program and projects related to that program to obtain such outcomes that are not possible to achieve by doing them individually. A program is a sub-set of Portfolio but a project under a portfolio may or may not be a part of a program. On the other hand program must have some project(s).
PORTFOLIO MANAGEMNT:
Portfolio Management is a Group activity of an Organization comprises of Projects, Programs, Sub-Programs and Sub-Portfolios, to achieve an Organizations strategic Objectives where programs and projects are not necessarily be interdependent or directly related.
PORTFOLIO is a bigger picture of an Organizations Strategic plans, meant to achieve strategic objectives with the help of appropriate Programs and projects. PROGRAM is a set of sub-programs and projects established to support Portfolio while PROJECTS are the short term goals of an organization strategic plans under portfolio usually they are based on market demand, social needs or Environmental considerations etc.
PORTFOLIO Management:
Is directly associated with Organizations strategies with the support of Programs, projects and sub-portfolios. On the other hand Program Management is to take benefit using its appropriate programs and projects while Project Management is the process of developing and execution of plans to achieve Organizations Programs and Strategies under certain portfolio.
From planning to end user satisfaction its all the Governing body that manages all activities to give successful deliverable, and its success is measured in terms of completing a Project in time within scope and cost and should meet the end user requirement using planned resources. Success of a project can never be a one persons credit; its the whole PROJECT TEAM who worked beneath Management in short every single entity having some contribution to Project is beyond that success.
The main focus is to measure the performance of ongoing activity and it help to reduce the risk. It also helps to figure out the areas needed more attention and report back the issues.
PROJECT INFORMATION:
After completion of Project lots of data and related information is collected, which further transformed into various formats for future use or reports establishments or stakeholders guidelines, but its difficult for most of the people to distinguish between DATA & INFORMATION, so to establish a distinct names this data and information is classified into following known terminologies. Work Performance Data: it includes the raw observation and measurements collected during project activities. Work Performance Information: Includes the Performance data collected during controlling processes, analyzed in context and integrated from relationship across different process areas. Work Performance Reports: The Physical or Electronic Representation of work flow complied in project document to establish decisions.
BUSINESS CASE: A formal document used to describe the projects worth w.r.t business point of view and cost benefit analysis to define project scope and boundaries by analysis through stakeholders input. AGREEMENTS: Formal Contract documents between the sponsor and Project Manager, usually done when its External Project. Environment ENTERPRISE ENVIRONMENT: where the Project is going to be done, consideration of stakeholders ORGNAIZATIONAL PROCESS ASSETS: Organizations Assets influence TOOLS AND TECHNIQUES: Experts Judgments; used to access Inputs to Project charter. Facilitation Techniques; to develop conflict resolution guide for project charter. OUTPUT: Project Charter.
Its the process of leading and performing work a ctivity and makes changes described in Project Management Plan to achieve Objectives. Same is the case like Project charter and Management Plan, give some input, apply some tools and techniques and generate output. INPUT: Project Management Plan, Approved Changes Requests; Requests scheduled by project team, reviewed and approved by CCB (change control board) for implementation. They may impact the project or project management plan and also may require Corrective Action; that realign the performance with management plan or Preventive Action; that ensures future performance of project will be according to management plan, or Defect Repair & Update Enterprise Environment Factors, Organizational Process Assets. TOOLS & TECHNIQUES; Expert Judgments, Project Management Information System; A Part of Organizations Environmental Factor, Meetings; to ensure the work done is appropriate and no stakeholder is influencing or influenced by project. OUTPUT: Deliverables; outcomes of the Process, Work Performance Data; raw data collected through observations and measurements, Change Requests, Project Management Plan Updates, Project Documents Update.
CLOSE PROJECT/PHASE:
The final stage of the Project Management Process Groups, which finalize all activities, it gives lessons and formal release of all organizational assets. All deliverables are accepted according to Project Management Plan under some final meeting of sponsors and team or management with the help of some experts who ensures the deliverables are according to standard and meet requirements. Finalize the documents; maintain the Historic milestones files for future use and handover the PRODUCT.
COLLECT REQUIREMENTS:
To gather information and requirements to meet project objectives according to the needs of stakeholders, this helps to map project and product scope. INPUT: Scope Management Plan, Requirement Management Plan, Stakeholder Management Plan, Project Charter, Stakeholder Register; it keeps all the necessary stakeholders who are beneficiaries and acquire some benefits for project, also keeps stakeholders requirements and expectations. TOOLS & TECHNIQUES: Interviews; most formal way to gather information from stakeholders using prepared questioning or random asking and record their response, Focus Groups; using dialog between qualified stakeholders and experts groups, Facilitated Workshops; focused session of invited stakeholders to demonstrate the work structure and by their concern determine the requirements, Group Activity Techniques; several groups activity are conducted to a single task and gather information from their results, Groups Decision Making Techniques; using a groups to access a single task and the expected outcomes becomes the requirements, Questionnaires & Surveys; Develop a questionnaire to number of respondents to gather their views , Observations; observe the experts related to a project, their work, Prototypes; product model is used to get feedback from end users, Benchmark; comparing project ideas with actual product , Context Diagram; inputs to business system and gather information from system as output, Document Analysis; using past information relevant to new project like business management plan. OUTPUT: Requirements Documentation; complete the collected information into a set of unambiguous, traceable and acceptable form, Requirements Traceability Matrix; the alignment of requirements with business and project objectives.
10
DEFINE SCOPE:
The process of mapping detailed description of project and product along with final requirement document. INPUT: Scope Management Organizational Process Assets. Plan, Project Charter, Requirements Documentation,
TOOLS& TECHNIAUES: Expert Judgment, Product Analysis; general accepted method of translating project deliverables as product, Alternatives Generation; finding alternative ways of doing the same work, Facilitated Workshops. OUTPUTS: Project Scope Statement; defines the way of work has to be done under certain boundaries along with major deliverables, Project Documents Update.
CREATE WBS:
Defines the way of doing work in a systematic way of creating elaborated chunks and takle them individually to provide broader vision of deliverables. INPUTS: Scope Management Plan, Project Scope Statement, Requirements Documentation Enterprise Environmental Factors, Organizational Process Assets. TOOLS & TECHNIQUES: Decomposition; dividing the work into small meaningful segments, manage them according to cost and time duration and shift the control according to area of expertise, Expert Judgment. OUTPUTS: Scope Baseline; Approved version of scope statement including WBS and WBS dictionary, Project Document Update.
VALIDATE SCOPE:
Process of finalizing deliverables from approving authority to ensure that objectives have been achieved or not. INPUTS: Project Management Plan, Requirements Documentation, Requirements Traceability Matrix, Verified Deliverables; Approved Deliverables by Control Quality and should meet Objectives, Work Performance data. TOOLS& TECHNIQUES: Inspection; reviews of work done by different experts, Group Decision making techniques. OUTPUTS: Accepted Deliverables; final approvals of deliverables by sponsor and signing-off the Project, Change Requests; by reviews if found some defects may need some changes, Work Performance Information, Project Documents Updates; approval of final product document by customer.
CONTROL SCOPE:
11
The process of monitoring scope w.r.t objectives to control the change risks and change requests have processed accordingly
12