0% found this document useful (0 votes)
19 views20 pages

Week 1

Project planning

Uploaded by

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

Week 1

Project planning

Uploaded by

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

Introduction

Week 1
OULTILNE
1.Introduction
2.Software Project Versus other types of Project
3.Activities covered by software project
management
4.setting objectives
CONTENTS

1 Introduction
What is PROJECT

“A Specific plan or design”


“A Planned undertaking”
Project can be defined as
Unique process consisting of a set of
coordinated and controlled activities with start and
Finnish dates, undertaken to achieve an objective
conforming to specific requirements, including
constraints of time, cost and resources.
Characteristics of project

A task is more ‘project-like’ if it is:


• Non-routine tasks are involved
• Planning is required
• Aiming at a specific target
• Work carried out for a customer
• Involving several specialisms
• Made up of several different phases
• Constrained by time and resources
• Large and/or complex
Software Project Vs Other Types of Project

Not Really but ...


Invisibility: Unlike building bridge, s/w
development is hard to tell how much work is done
until it’s finished.
Complexity: more complex than original things
built, requires skill of problem solving
Conformity: s.w is build for peoples and they can
change their minds often. so make s/w flexible
Flexibility:software often work with thing in real
world like machines, which can be easily changed.
Activities Covered by Software Project Management (SPM)

Usually there are three successive processes that


bring a new system into being.
Activities Covered by Software Project Management (SPM)

Feasibility Study: assess whether project is


worth staring, valid business case.
Development/operational cost is also estimated
Planning: after feasibility study appears viable
planning can start, create outline for whole project
Project Execution: now project can be executed
i.e designing and implementation
Activities Covered by Software Project Management (SPM)

Software development
life cycle ISO 12207
Activities Covered by Software Project Management (SPM)

Requirement Analysis: starts with requirement


elicitation or requirement gathering
it could be quality requirement or functional
requirement. it could resource requirements relate
to development costs.
Architecture Design: Identify components
(software, hardware, processes) that fulfill system
requirements. Consider existing components and
legacy systems.
Detailed Design: Design the smaller units within
each software component.
Activities Covered by Software Project Management (SPM)

Code and Test: Write and debug code for each


unit.
Integration: Combine and test components
together, including hardware and user interactions.
Qualification Testing: Ensure the entire system
meets all requirements.
Installation: Make the system operational, set up
data, install software, and train users.
Acceptance Support: Resolve issues, correct
errors, and implement improvements.
Maintenance is ongoing.
Some Ways to categorize Projects

Projects may differ because of different technical


products to be created. thus we need to identify
characteristics of project which are
-> Compulsory vs Voluntary Users
-> Information system vs embedded system
-> Objectives vs Products
Compulsory Versus Voluntary Users

Who Uses the Project?

Compulsory Users: Users have no choice but to


use the system, like sales staff recording sales.
Planning can focus on clear requirements and
efficiency. (Example: Payroll system)
Voluntary Users: Users choose to use the
system, like gamer. Planning needs to consider
user preferences and enjoyment, which can be
harder to predict. (Example: Mobile game)
Information system vs embedded system
What Kind of System is it?

Information System: Helps people do their jobs, like


managing inventory. (Example: Inventory management
software)
Embedded System: Controls machines, like air
conditioning. Planning needs to consider real-time
performance and reliability. (Example: Car engine control
unit)
Combination System: System has both elements, like
inventory software that also controls a warehouse robot.
Planning needs to consider both information flow and
machine control. (Example: Automated warehouse
system)
Objective Vs Products
What Kind of System is it?

Information System: Helps people do their jobs, like


managing inventory. (Example: Inventory management
software)
Embedded System: Controls machines, like air
conditioning. Planning needs to consider real-time
performance and reliability. (Example: Car engine control
unit)
Combination System: System has both elements, like
inventory software that also controls a warehouse robot.
Planning needs to consider both information flow and
machine control. (Example: Automated warehouse
system)
Stakeholders

There are two type of people having interest in


project
1. Internal to project team: under direct
managerial control of project leader e.g.
developers/designers
2. External to project team but within same
organization: project leader might need assistance
of users. but not directly controlled by leader. e.g.
testing.
3. External to both project team and
organization: e.g. Customers, contractors
What is management

Management involves following activities:


• Planning - Deciding what is to be done
• Organizing - Making arrangements
• Staffing - Selecting right people for job
• Directing - Giving instructions
• Monitoring - Checking on progress
• Controlling - Taking action to remedy holdups
• Innovating - Coming up with new solutions
• Representing - Liasing with clients, users,
developer, suppliers and other stakeholders.
Objectives

Informally, the objective of a project can be defined by


completing the statement:

The project will be regarded as a success


if………………………………..

Rather like post-conditions for the project

Focus on what will be put in place, rather than how activities


Objectives should be smart

S – specific, that is, concrete and well-defined e.g increase


website traffic by 20%," instead of "Improve online presence.
M – measurable, that is, satisfaction of the objective can be
objectively judged. e.g. reduce customer complaints by 30%
A– achievable, that is, it is within the power of the individual or
group concerned to meet the target .e.g Train 50 Employees
R– relevant, the objective must relevant to the true purpose of
the project e.g. develop mobile app to enhance customer service
instead of launch a social media campaign
T– time constrained: there is defined point in time by which
the objective should be achieved. Set a clear deadline to stay
THANK YOU
The Reader Group of Colleges

You might also like