0% found this document useful (0 votes)
250 views8 pages

STANDARD Project Management Chapter 1

A project is a temporary endeavor undertaken to create a unique product, service, or result. Level of Effort (LOE) is a support-type project activity that must be done to support other work activities or the entire project effort. A project's end is reached when the project's objectives have been achieved or when the project is terminated.

Uploaded by

Manoj
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
250 views8 pages

STANDARD Project Management Chapter 1

A project is a temporary endeavor undertaken to create a unique product, service, or result. Level of Effort (LOE) is a support-type project activity that must be done to support other work activities or the entire project effort. A project's end is reached when the project's objectives have been achieved or when the project is terminated.

Uploaded by

Manoj
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

STANDARD PROJECT MANAGEMENT

1.1. Project - PMBOK

Types of e-Gov project Approach paper

Specific - (Reference 1)- Software extensions ( page 4)

1.2. Level of Effort


- ( Wikipedia /SE)
1.3. Project Management PMBoK
1.4. Program management- PMBoK
1.5. Project life cycle (Software Ext, Govt Extension)

Project phases
O&M
Project Boundaries

1.6. Project Stakeholders - PMBOK


1.7. Project Constraints
1.8. Project Governance/Composition of project team section 2.3.1, SE
page 24
1.9. Importance of Project Management Framework in in e-Governance
Project Life Cycle ( PMBoK pg 2- generic, e-Gov)
1.10. Knowledge Areas PMBOK
1.11. Process Groups PMBOK
1.12. Applicability of Framework to different types of e-Gov projects
1.13. Description

1.1 Project (PMBOK)


A project is a temporary endeavor undertaken to create a unique product, service, or result. The
temporary nature of projects indicates that a project has a definite beginning and end.
The end is reached when the projects objectives have been achieved or when the project is
terminated because its objective will not or cannot be met, or when the need for the project no
longer exists.
A project can create:

A product that can be either a component or another item, an enhancement of an item,


or an end item in itself;

A service or a capability to perform a service (e.g., a business function that supports


production or distribution);

An improvement in the existing product or service lines (e.g., A Six Sigma project
undertaken to reduce defects); or

A result, such as an outcome or document (e.g., a research project that develops


knowledge that can be used to determine whether a trend exists or a new process will
benefit society).

Types of e-Gov project Approach paper


To be completed through other sources

1.2 Level of Effort (Wikipedia)


In project management, level of effort (LOE) is a support-type project activity that must be
done to support other work activities or the entire project effort. It usually consists of short
amounts of work that must be repeated periodically. Examples of such an activity may be
project budget accounting, customer liaison, or oiling machinery during manufacturing.
LOE is used to define the amount of work performance within a time and is measured in staff
days or staff hours per day/week/month.
LOE estimation is one of the primary tasks of a project manager.
(Below reference is from Software extension to the PMBOK-page no.5)

Software projects may also be undertaken to satisfy service requests, maintenance needs, or to
provide operations support. These activities may occur as level-of-effort (LOE) activities; they

are considered projects when they are specified as temporary endeavors to provide deliverables
and outcomes.
1.3 Project Management [1] (PMBOK)
Project is the application of knowledge, skills, tools, and techniques to project activities to meet
the project requirements. Project management is accomplished through the appropriate
application and integration of processes, which are categorized in the five process groups.
These five process groups are:

Initiating

Planning

Executing

Monitoring and Controlling, and

Closing

1.4 Program Management [2] (PMBOK)


A program is defined as a group of related projects, subprograms, and program activities
managed in a coordinated way to obtain benefits not available from managing them individually.
A project may or may not be part of a program but a program will always have projects.
Program management is the application of knowledge, skills, tools, and techniques to a program
in order to meet the program requirements and to obtain benefits and control not available by
managing projects individually.
Program management focuses on the project interdependencies and helps to determine the
optimal approach for managing them.
1.5 Project life cycle (PMBOK & Wikipedia)
A project life cycle is the series of phases that a project passes through from its initiation to its
closure. The phases are generally sequential, and their names and numbers are determined by
the management and control needs of the organization or organizations involved in the project,
the nature of the project itself, and its area of application.
Projects vary in size and complexity. All projects can be mapped to the following generic life
cycle structure:

Starting the project,


Organizing and preparing,
Carrying out the project work, and

Closing the project.

Project phases

A project may be divided into any number of phases. A project phase is a collection of logically
related project activities that culminates in the completion of one or more deliverables.

O&M
Project Boundaries

1.6 Project Stakeholders (PMBOK & Wikipedia)

Project Stakeholder Management includes the processes required to identify the people,
groups, or organizations that could impact or be impacted by the project, to analyze stakeholder
expectations and their impact on the project, and to develop appropriate management strategies
for effectively engaging stakeholders in project decisions and execution.
Stakeholder management also focuses on continuous communication with stakeholders to
understand their needs and expectations, addressing issues as they occur, managing conflicting
interests and fostering appropriate stakeholder engagement in project decisions and activities.
Stakeholder satisfaction should be managed as a key project objective.
The stakeholder management comprises four steps, which are below:

Identify, recognize and acknowledge stakeholder;


Determine their influence and interest;
Establish communication management plan
Influencing and engaging stakeholder

1.7 Project Constraints

Project constraints are anything that restricts or dictates the actions of the project team. That
can cover a lot of territory. The triple constraintstime, resources, and quality - are the big
hitters, and every project has one or two, if not all three, of the triple constraints as a project
driver.
http://pmtips.net/Blog/defining-project-constraints
A constraint, in project management, is any restriction that defines a project's limitations;
the scope, for example, is the limit of what the project is expected to accomplish.

Project constraints are also considered to be somewhat mutually exclusive. In the project
management triangle, it is assumed that making a change to one constraint will affect one or
both of the others. For example, increasing the scope of the project is likely to require more time
and money.
http://whatis.techtarget.com/definition/constraint-project-constraint

1.8 Project Governance/Composition of project team (Wikipedia & SE to the PMBOK


page-24, 34)
Project governance is the management framework within which project decisions are made.
Project governance is a critical element of any project since while the accountabilities and
responsibilities associated with an organizations business as usual activities are laid down in
their organizational governance arrangements, seldom does an equivalent framework exist to
govern the development of its capital investments (projects). For instance, the organization
chart provides a good indication of who in the organization is responsible for any particular
operational activity the organization conducts. But unless an organization has specifically
developed a project governance policy, no such chart is likely to exist for project development
activity.
Therefore, the role of project governance is to provide a decision making framework that is
logical, robust and repeatable to govern an organizations capital investments. In this way, an
organization will have a structured approach to conducting both its business as usual activities
and its business change, or project, activities
The decision making framework is supported by three pillars:

Structure
People
Information

Project governance is an oversight function that is aligned with the organizations governance
model and that encompasses the project life cycle. Project governance framework provides the
project manager and team with structure, processes, decision-making models and tools for
managing the project, while supporting and controlling the project for successful delivery.
The composition of a software project team is often a balance between ideal consideration and
practical constraints. Ideal considerations for composing software development teams included:

Dedicated vs. non-dedicated team members


Collaborative team vs. functional division
Virtual vs. collocated
Specialists vs. generalists
Stable vs. interim.

1.9 Importance of Project Management Framework in e-Governance Project Life Cycle


A project management framework defines how projects of various sizes and complexity should be
managed within an organization so that all projects are managed in a consistent way. Not all projects
will require every part of the framework to the same degree, for instance small or non-complex
projects may not require such detailed processes but the processes they do use will be common to
all projects.
A project management framework is usually compatible with an organizations chosen project
management methodology and provides the practical tools to actually do the work required for the
project.
A Project Management Framework supports the implementation of project management within an
organization because:
1.
2.
3.
4.

It supports the development and replication of accepted practice.


Helps communication within the team because of a common language.
Streamlines the use of tools and techniques for key project management processes.
Establishes a consistent approach which aid customers understand the project management
processes.
5. Ensure that focus is maintained on the early stage of the project lifecycle.

Sources: http://blog.parallelprojecttraining.com/project-management-articles/what-is-a-project-managementframework/#ixzz439187h4W

A project management framework is a combination of processes, tasks, and tools used by


individuals working on a project to transition a project from start to finish. An overview of a generic
process used by this framework is:

Initiate is when the project starts


Plan is when all of the key decisions are made
Execute is when project work actually takes place
Control is when adjustments are made to the plan
Monitor is when project progress is checked
Terminate is when the project comes to an end

Each stage of this process involves the completion of many tasks by project team members using
various tools.
Sources: http://study.com/academy/lesson/what-is-a-project-management-framework-definition-examples.html

The main objectives of E-Governance Project Lifecycle are:

Need for change in current service delivery model and role of e-Governance.
National e-Governance Plan, MMPs, institutional structures and related policies.
E-Governance evolution model and approach for implementation of e-Governance.

Lifecycle and phases, scope, approach and deliverables in each phase in e-Governance
project development and implementation.
Approach for addressing project requirements during the lifecycle.
Role for private sector participation.
Capacities and resources required for e-Governance implementation.
Policy and legislative framework support for e-Governance.

Sources: http://202.138.105.5/cbpegov/pages/egplctraining.aspx

1.10 Knowledge Areas (PMBOK)


A knowledge area represents a complete set of concepts, terms, and activities that make up a
professional field, project management field, or area of specialization.
The Knowledge areas are:

Project Integration Management


Project Scope Management
Project Time Management
Project Cost Management
Project Quality Management
Project Human Resource Management
Project Communications Management
Project Risk Management
Project procurement Management
Project Stakeholder Management

These ten knowledge areas are used on most projects most of the time. Project teams should utilize
these ten knowledge areas and other knowledge areas, as appropriate, for the specific project.

1.11. Process Groups PMBOK


The project management processes are required on a project to cover its management aspect. The
project management processes are grouped together into five process groups. The five project
management process groups are as follows:

Initiating Process Group


Planning Process Group
Executing Process Group
Monitoring and Controlling Process Group
Closing Process Group

One of the common misconceptions among many people, including some PMP certified individual, is
to consider project management process groups as project phases. Project management process
groups are not project phases. In fact, the five project management process groups are repeated for
every single phase of a project.

1.12. Applicability of Framework to different types of e-Gov projects


To be completed through other sources

1.13. Description
To be completed through other sources

References:
2013 Project Management Institute. A guide to the Project Management Body of Knowledge (PMBOK Guide) Fifth
Edition
Software Extension to the PMBOK Guide Fifth Edition
Wikipedia

You might also like