Project management

Midterm exam Revision

● 1/ Project management definition :

- Project management is the application of knowledge, techniques, skills

and tools to project activities to meet the project requirements.

- Steps : initiating, planning, executing, controlling, and closing the work

of a team

- Project manager he needs to have knowledge +personal +performance.

- project manager is responsible of leading the team to achieve objectives.
-why we need project management :

- Expertise with experienced and qualified project teams

- Delivering the project on time and budget successfully

- Improved control

- Improved project support opportunities

- Improved performance

● 2/ Project definition :

- Project is an activity with a fixed start and end point, managed with
finite resources, involving change and often achieved by the collective
effort of the team of people

- Features :

- start and end point

-unique activity with visible output

-May involve uncertainty and risk

 Project management

-Involve team , budget , non-repetitive tasks , use of resources , clearly

defined team roles , single point of ultimate responsibility , clear aims
objectives and goals.

- Temporary :(could be for long period ) project has definite beginning

and definite end , end is reached when objectives are achieved or
impossible to be achieved or the project terminated

- Unique : involve doing something that has not been done before ( shih
fama hajet tetaawed ema baz fama heja tbadlet )

-Progressive elaboration: unique+temporary

● 3/ Project statement of work SOW and Project charter :

1- SOW

- Narrative description
of products or
services to be
supplied under
contract
- Detailed and
structured statement
of what we have to
do , product elli bech
na3mlouh deadlines
, milestones ,
processess .. ( yji
feha zeda ay heja
client they agree on m3a charika , acceptance criterion , quality
measures , constraints , payment…)
- Contractual document ( appendix l el main contract )
 Project management

- It’s usually collaboratively written : client/servie provider and the

company ( usually drafted first by project managers and different
parts of it it’s assigned to different departments )
- Goal : reduce risk by setting clarity , setting clearing expectations for
both parties
- It’s written by both parties , they go over the project details

After developing a sow we need to develop a project charter then we

develop project scope

2/ Project charter :

- High level project initiation document, no projects start without

the approval of project charter
- Definittion : formal documented statement feha outline of the
project , scope , objective , goals n roles , shareholders and
project management authority .
- written by project initiator /sponsor
- objective : sets directions for the project
- Documents :project title , purpose , objectives ,
stakeholders,risks , budget,project manager , solution for
upcoming problems
- Elements ; Business case , project scope ( a component of
project implementation that helps determine goals,
constraints, workflow management strategies, tasks, and
deliverables. : The project aims to kadhe and kadhe ) , target
and goals , success criteria , timeline, team , communication
plan .

trends that impact the environment in which projects are managed today:

Corporate globalization
Massive mergers and reorganizations
Flatter organizations
Short-term results driven
Team environment
Contract PM and outsourcing
Primacy of interpersonal skills
Multinational projects
Importance of cultural differences
Dependence on technology
 Project management

4/Organisational structure :

- we have 3 types :
- Functional structure :authority with functional manager ,
hierarchical structure , koll department wahdou chef fih
functional manager with expertise , suitable for on going
operations kima manufacturing and production ( el heja el
khayba feha elli project maanagers have weak authority o el
multiple projects y competiew 3la limited resources )
- Projecteorized structure :authority with project manager ,
opposite of functional organisation , loyalty to project and
not to the functional manager , 3aref howa chief excutive
officer , tahtou project managers o tahtou team , teams are
always allocated to projects
- Matrix structure : fih strong , balanced and weak. heya seaa
ma bn functional o el projectorized . 3ana functional
manager tahtou project managers o tahtou team
- It improves el project management control over resources ,
more support from functional ares + highly visible objectives

- Strong :authority with project manager ,

- Balanced : authority shared by functional and project

manager ( project manager lena has a full time role

-Weak : authority with functional manager , project manager

weak authority and part time role ( as if howa commincator
mabin el functional manager o el team )

Matrix heya ahssen type surtout strong

 Project management

5/ Projects and operations

6/ Factors affecting project success :

- Efficient Planning
- Methodical Approach
- Unclear objectives
- Lack of senior management support
- Lack of effective project integration
- Inadequate funding
- Change in business priorities
- Original assumptions invalid
- Ineffective team
- Lack of effective communication processes

6/ Portfolio ,Program and projects :

- Programme : have a range of strategies working toward a defined

outcome, could have many projects, variety of methods , expl : new
satellite system will include the project of design and construction of
satellite
 Project management

- Portfolio: collection of projects , programs and subsidiary portfolios

and operations managed as group to achieve strategic goals
- Portfolio management aligns with organizational strategies by
selecting the right programs or projects, prioritizing the work, and
providing the needed resources
- Program management harmonizes its projects and program
components and controls interdependencies in order to realize
specified benefits

- integration management is the process of analyzing your situation and deciding where you can
make efficient changes by combining time , quality ,and cost.
 Project management

7/Project lifecycle

- Project phase: “A collection of logically related project activities

usually culminating in the completion of a major deliverable.”

- Project life cycle: “Collectively the project phases are known as the
project life cycle.”

Concept and Proposal , Development , ,Implementation ,

Termination Verification

- Product life cycle: The natural grouping of ideas, decisions, and

actions into product phases, from product conception to operations
to product phase-out.
check slide 71/73

Process is a step-by-step structure, with milestones and stages (

outcome based ,

Methodology is a way of interacting with the team or customers to

move them from stage to stage. Process as the “what” and
Methodology as the “how.” ( standards based )

- A third category of “skills and activities” is separate from the

methodology

more process , less methodology ( traditional product development

process + agile )
 Project management

8/Methodologies

● waterfall : Linear model

- Fih requirement analysis , design , implementation , testing
and maintenance .
- Ya3ti l el client output blata wahda , less interaction m3a client
- Used by banks , gvt , insurance companies , large teams
- Output : product that match the client requirements
- Heja khayba feha heya elli upfront document
● Agile : Technology-enabled network of teams with a
people-centered culture that operates in rapid-learning and
fast-decision cycles
- Follows principles called agile manifesto
- Akther communication m3a client par rapport l el waterfall
,dima fama retour men 3and client and product development
updates
- Tossal7 l startups and small teams , saas
- Heja khayba feha eli heya sa3at u don’t meet timeline due to
changes made
- Heja behya feha elli heya ta3tina continiously working product
● Spiral: 7alazouna
- Incremental risk oriented lifecycle model , ya3tina feedback fi
kol iteration
- 4 phases : determine objectives , identify and resolve risks ,
development and test , plan next iteration .
- Why ? minimize risk
- Heja khayba yest7a9 barsha expertise process koll based 3la
risk analysis ( ghalta ta7chelek ) , model complex and costly .
● Scrum : process is break down into smaller pieces : several
incremental releases called sprints fehom :
- Plan build test and review , ta93ed taaweded lin product is
complete
 Project management

- Bech tenjah el 3ameleya yelzmek 3 ppl roles , product owner ,

scrum master and team .