IME-671

SOFTWARE PROJECT MANAGEMENT

Assignment-2 Newspaper Delivery System

Guided By Presented by
DR. S.C Mishra GROUP 7
PhD (Carleton), PDF (Harvard)
Professor, IME Department, IIT Kanpur Akash Singhal
Advisor, Indo Canada Education Council Neelanjan Ghosh
NSERC Fellow 2008, Harvard University, USA Swarn Kumar
Former Visiting Scientist, Harvard University, USA Upneet Gandhi
Vaibhav Goyal
Outline
Objective

01 Project Scope

Project Planning

03 Project Organization

04 Project Estimations

Software Process Model

05
Risk and It’s Management
 Objectives
• To develop a system which assist newspapers vendors and customers to better
deliver and receive the newspaper stem in a localized geography
• Cater to needs of newspaper vendors and customers, well tailored for each ones
need
• Automated (with least manual intervention) repetitive and monotonous tasks such
as billing
Software Project Management

• Is a sub-discipline of project management in which software projects are

planned, implemented, monitored and controlled

• SPM aims to deliver quality product, keeping the cost within client’s budget
constrain and deliver the project as per schedule
 Project Scope
Build a functional Build a Minimal UI Automated Billing, Functional of ge-
system which is for less tech flexible subscrip- ographical map-
very much adap- savvy users tion (holidays) ping of delivery
tive for each day and elastic location
and subscription (preferably non-
and delivery relational) data-
base
 Project Planning

Feasibility Study Requirement Anal- Design and Soft- Implementation Testing Plan Staff Training
ysis ware Project Plan
Project Organization:

Project Man-
ager

Technical Business An-

Lead alyst

Require-
Software Requirements
ments Engi-
Tester Engineer
neer
Project Estimation

A project estimate is your prediction of how much time and money is needed to complete a
project.

There are various methods that can be used to for estimations, such as top-bottom, Bot-
tom-Up, 3 point etc.

Here we have used the Bottom-up Approach as the tasks are obvious and usual.

We have also tried to take a higher upper bound for the estimate for being sufficiently able
to complete the project completely.
 Cost Estimation
HOSTING APP DESIGN
INR 20,000 for installation INR 30,000

Cost Estima-
tion
DATABASE HUMAN RESOURSE
Attached to pi cluster INR 40,000 – 1,00,000
INR 10,000
 Ghantt Chart:
17-Feb 19-Feb 21-Feb 23-Feb 25-Feb 27-Feb 1-Mar 3-Mar 5-Mar 7-Mar

Requirement Gathering

Database Design

Geographical Information Sys-

tem

User Interface Design

Testing And Implimentation

Testing And Implimentation User Interface Design Geographical Information System Database Design Requirement Gathering
STARTING DATE 04-Mar 2021 27-Feb 2021 27-Feb 2021 20-Feb 2021 17-Feb 2021
DAYS TO COMPLETE 2 3 4 7 3
SOFTWARE PROCESS:

• We used Spiral Model for processing of the data (changed as per our requirements)
• Risk management at regular stages – in development cycle
• Spiral model – spirals down to a number of iterations
• Fourth quadrant represents following activities :-
 Formulates plan to
 Identify software targets
 Selected to implement the program
 Clarify the project development restrictions
 Risk Analysis – Analytical assessment of selected programs & how to identify and eliminate risk
 Implementation of Project – Implementation of software development & verification
 Customer Evaluation
 Evaluation to development work
 Proposal of amendments
 Plans to formulate the next step
Software Process
Spiral Model
 Project Risk
• Two prong process

1. Risk Assessment (what risks are? & what to focus on?)

a. Preparing list of potential dangers affecting project

b. Assessing probability of occurrence & potential loss of each item listed

c. Ranking items (from most to least dangerous)

2. Risk Control

a. Come up with techniques & strategies to mitigate highest ordered risks

b. Implementing strategies to resolve the highest order risk factors

c. Monitoring effectiveness of strategies & changing levels of risk throughout the project
 Risk Assessment
RISK CATEGORIES

Schedule Budget Operational Technical Programmatic

When Project tasks & • Wrong budget • Improper process • Continuous changing • Incomplete un-
schedule not estimation implementation, requirements derstanding of
addressed. • Cost Overruns failed system or ex- • No advanced tech- requirements
Possibilities: • Project Scope ternal event risk nology available • Loss of data due
• Wrong time estim- Expansion • Causes: • Product is complex to Corruption
ation  Failure to address to implement • Building simple
• Resources not priority conflicts • Difficult project mod- and user friendly
tracked properly  Failure to resolve re- ulus integration software
• Failure to identify sponsibilities
complex function-  Insufficient resources
alities  No resource plan-
• Unexpected project ning
scope expansion  No communication in
 PROJECT RISK : PROBABILITY &
CATEGORY RISKS
IMPACT PROBABILITY IMPACT4 IS(1LEAST
MOST SERIOU &
SERIOUS)

SCHEDULE RISK PROJECT RUNNING OUT OF SCHEDULE & 35% 1

NOT MEETING DELIVERY DATES
BUDGET RISK COST OVERRUN 20% 1
OPERATIONAL RISK RISK OF LOSS DUE TO IMPROPER PROCESS 15% 2
IMPLEMENTATION, FAILED SYSTEM OR
SOME EXTERNAL EVENTS RISKS
TECHNICAL RISK FAILURE OF FUNCTIONAL- 10% 2
ITY &
PERFORMANCE
PROGRAMMATIC RISK INCOMPLETE UNDERSTANDING OF 10% 3
REQUIREMENT, LOSS OF DATA –
CORRUPTION ETC
TECHNOLOGY RISK OBSOLETE TECHNOLOGY 5% 2
BUSINESS IMPACT PRODUCTION MAY HARM BUSINESS 5% 3
 Scheduling Principles: Avoid Delays
Compartmentalization Time Allocation
Interdependency
• Divides projects in • Assign work units
• Task Interrelationship
several tasks • Estimated start date
• Interdependency of
• Makes Projects man- and end date on a full
one or more activities
ageable time or part time basis
or tasks on each other
• Becomes easier to
prepare project
schedule according
to tasks
 Scheduling Principles: Avoid Delays
Effort Validation Defined Responsi- Defined Outcomes
bilities
• Made sure resources
are available • People assigned with • Each task to have an
• Project management duties to perform output
teams have defined • According to skills and • Achieved after comple-
member of team abilities – perform tion of tasks
members tasks • Outcomes in form of
• Allocation must be product and these
according to effort products are combined
and time required to in deliverables
complete task
Thank you