Pmo, project objectives and project life cycles

Project Objectives &

Project Life Cycles

Roman Kolodchak, for SoftServe PMO

Project Objective What is Project Objective Project Objective Types Task 1

Project Life-Cycle PLC definition PLC vs SDLC

SDLC SDLC Types SDLC Samples

Agenda

Project Objective: Goal vs Objective

Goals - are high-level statements that provide the overall context for what the project is trying to accomplish

Objectives - are concrete statements describing what the project is trying to achieve.

Project Objective: Goal vs Objective

Goal Objective

High-Level Specific

Generally non-measurable Measurable

Not always achievable achievable and realistic

time-bound

Goal statements are designed to be vague. Objectives should not be vague.

Objectives must be SMART

Project Objective: Types

Main objectives (the reasons for doing the project)

Additional objectives (the benefits achieved almost as side-effects, not the reasons for doing the project)

Non-objectives (the benefits that are not to be expected as a result of the project).

Project Objective: Task 1

“Improve Maintainability Index for application for >90” - Goal or Objective ?

“Reduce TCO (Total cost of ownership) of the system by 20% before Christmas Eve” – Goal or Objective?

“Project (deadline 31 Dec) should implement method x() of class Y that should return Boolean value” – is this project objective ?

Project Lifecycle: Definition

Project Lifecycle models how a project is planned, controlled, and monitored from its inception to its completion.

Project Lifecycle: PLC vs SDLC

The project life cycle represents the processes use to manage the work while the SDLC actually represents the work of creating the software system.

SDLC: Types

Predictive life cycle models - "favor optimization over adaptability“

Waterfall Prototyping Rapid application development (RAD) Spiral

Adaptive/Agile life cycle models - "accept and embrace change during the development process and resist detailed planning “

Adaptive software development (ASD) Extreme programming (XP) Scrum

SDLC: Waterfall (Traditional)

Linear ordering of the phases, which can be strictly sequential or overlapping to some extent. No phase is normally repeated.

SDLC: Prototyping

Functional requirements and physical design specifications are generated simultaneously.

SDLC: Rapid Application Development

80/20 rule

The focus is on delivering projects in small pieces.

Deliverables, including the final solution, are created using a repeating process of analysis, design, construction, and testing.

RAD emphasizes reuse.

SDLC: Spiral

Advantage High amount of risk analysis Good for large and mission-

critical projects Software is produced early in the

software life cycle

Disadvantage Can be a costly model to use Risk analysis requires highly

specific expertise. Project's success is highly

dependent on the risk analysis phase

NO clear END date

SDLC: Adaptive Software Development

Adaptive cycle planning

Concurrent component engineering

Quality review Final QA and release

SDLC: Extreme programming

Teams of developers, managers, and users;

Programming done in pairs; Iterative process Collective code ownership.

SDLC: SCRUM

Questions ?

Thank You