Planning, Elements Of SDP-Software Project Management-Lecture Notes, Study notes of Software Project Management

Project Management is the art of maximizing the probability that a project delivers its goals on Time, to Budget and at the required Quality. This lecture handout was provided by Sir Debashis Koppale. It includes: Planning, Element, Scope, Output, Incorporate, Scope, Mutiple, Project, Decomposition, Level, Objectives

Typology: Study notes

2011/2012

Uploaded on 08/07/2012

angana
angana 🇮🇳

4.4

(52)

158 documents

1 / 3

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Software Project Management (CS615)
157
LECTURE # 25
4. PLANNING
4.7.4 Elements of SDP
Project Plan is iteratively defined through Concept & Requirements Phase. Initial
estimates are refined as scope and requirements become clearer. There are two
phases of project plan:
1. Preliminary
2. Final
Following are some elements of Software Project Plan:
a) Scope Planning
Scope planning is the process of progressively elaborating and documenting
the project work (project scope) that produces the product of the project.
Project Scope Planning starts with the initial inputs of product description, the
project charter, and the initial definition of constraints and assumptions.
Note that the product description incorporates product requirements that
reflect agreed-upon customer needs and the product design that meets the
product requirements.
The outputs of scope planning are the scope statement and scope management
plan, with the supporting detail.
The scope statement forms the basis for an agreement between the project and
the project customer by identifying both the project objectives and the project
deliverables.
Project teams develop multiple scope statements that are appropriate for the
level of project work decomposition.
b) Objectives – Business Requirements
Could be “Mission Statement”
Defines Business objectives for project
Includes Business Case (NPV Model) & Detailed Description of assumptions.
c) Technical Approach
docsity.com
pf3

Partial preview of the text

Download Planning, Elements Of SDP-Software Project Management-Lecture Notes and more Study notes Software Project Management in PDF only on Docsity!

LECTURE # 25

4. PLANNING

4.7.4 Elements of SDP

Project Plan is iteratively defined through Concept & Requirements Phase. Initial estimates are refined as scope and requirements become clearer. There are two phases of project plan:

  1. Preliminary
  2. Final Following are some elements of Software Project Plan:

a) Scope Planning

  • Scope planning is the process of progressively elaborating and documenting the project work (project scope) that produces the product of the project.
  • Project Scope Planning starts with the initial inputs of product description, the project charter, and the initial definition of constraints and assumptions.
  • Note that the product description incorporates product requirements that reflect agreed-upon customer needs and the product design that meets the product requirements.
  • The outputs of scope planning are the scope statement and scope management plan, with the supporting detail.
  • The scope statement forms the basis for an agreement between the project and the project customer by identifying both the project objectives and the project deliverables.
  • Project teams develop multiple scope statements that are appropriate for the level of project work decomposition.

b) Objectives – Business Requirements

  • Could be “Mission Statement”
  • Defines Business objectives for project
  • Includes Business Case (NPV Model) & Detailed Description of assumptions.

c) Technical Approach

docsity.com

  • Description of how new system is to be developed
    • Technologies
    • In House vs. Consultants
    • Derivatives of existing (i.e. use existing object model)
    • Architectural Layout – Layers

d) Contractual Aspects

  • Specifies general needs from outside sources
    • Consultants
    • Software Suppliers
    • Hardware Suppliers
    • Network/Infrastructure Suppliers
  • There are two types of contracts 1. Cost -Plus 2. Fixed Price

Most other relationships are some kind of combination of these two

1. Cost-plus (also called Time and material)

Cost-plus is a contractual relationship where the developer is paid for the cost of the service provided and in addition is allowed an agreed profit margin.

This is rather like renting a car the customer pays for the time that the car is used (by the hour, day, week etc.), and for any other expenses such as insurance and gasoline.

2. Fixed price

A fixed price contract is a commitment by the developer to provide an agreed product or service for an agreed fee, within an agreed schedule.

This is similar to purchasing a bus ticket, when the bus company agrees to take the customer to a specific destination within a published timetable, and for an agreed fee.

e) Schedules

  • Defines specific dates for milestones components
  • Work Breakdown Structure
  • Use Scheduling Engines like MS project etc.

f) Resource Allocation

docsity.com