ZeePedia buy college essays online

Software Project Management

<<< Previous PLANNING: Elements of SDP Next >>>
Software Project Management (CS615)
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
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
Software Project Management (CS615)
Description of how new system is to be developed
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
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
Software Project Management (CS615)
·  Resources such as licenses, servers, or other software/hardware related items
·  Personnel ­ how many people of what type and for how long
(Remember these are initial estimates in preliminary project plan)
g) Evaluation Methods
What methods to be used to validate performance
Testing for adherence to spec
Monitoring usage
Web trends
Database Logs
Transaction logs
Setup schedule for reviews
h) Overview of Project Management
Define where possible problems can occur
­  New technologies
­  Business risks
­  Resources
Define Contingency Plans
­  Development methods
­  If the worst happens, what to do
Table of Contents:
  1. Introduction & Fundamentals
  2. Goals of Project management
  3. Project Dimensions, Software Development Lifecycle
  4. Cost Management, Project vs. Program Management, Project Success
  5. Project Management’s nine Knowledge Areas
  6. Team leader, Project Organization, Organizational structure
  7. Project Execution Fundamentals Tracking
  8. Organizational Issues and Project Management
  9. Managing Processes: Project Plan, Managing Quality, Project Execution, Project Initiation
  10. Project Execution: Product Implementation, Project Closedown
  11. Problems in Software Projects, Process- related Problems
  12. Product-related Problems, Technology-related problems
  13. Requirements Management, Requirements analysis
  14. Requirements Elicitation for Software
  15. The Software Requirements Specification
  16. Attributes of Software Design, Key Features of Design
  17. Software Configuration Management Vs Software Maintenance
  18. Quality Assurance Management, Quality Factors
  19. Software Quality Assurance Activities
  20. Software Process, PM Process Groups, Links, PM Phase interactions
  21. Initiating Process: Inputs, Outputs, Tools and Techniques
  22. Planning Process Tasks, Executing Process Tasks, Controlling Process Tasks
  23. Project Planning Objectives, Primary Planning Steps
  24. Tools and Techniques for SDP, Outputs from SDP, SDP Execution
  25. PLANNING: Elements of SDP
  26. Life cycle Models: Spiral Model, Statement of Requirement, Data Item Descriptions
  27. Organizational Systems
  28. ORGANIZATIONAL PLANNING, Organizational Management Tools
  29. Estimation - Concepts
  30. Decomposition Techniques, Estimation – Tools
  31. Estimation – Tools
  32. Work Breakdown Structure
  33. WBS- A Mandatory Management Tool
  34. Characteristics of a High-Quality WBS
  35. Work Breakdown Structure (WBS)
  36. WBS- Major Steps, WBS Implementation, high level WBS tasks
  37. Schedule: Scheduling Fundamentals
  38. Scheduling Tools: GANTT CHARTS, PERT, CPM
  39. Risk and Change Management: Risk Management Concepts
  40. Risk & Change Management Concepts
  41. Risk Management Process
  42. Quality Concept, Producing quality software, Quality Control
  43. Managing Tasks in Microsoft Project 2000
  44. Commissioning & Migration