Software Project Planning

1
Software Project Planning

• Should Know the project Justification or
  Goals?
• Improve Productivity
• Increase Market Share
• Reduce Expense
• Improve Competitiveness
• .
• .
• keep up with the Jones (surprisingly number
  of CEOs)
• for you (this class) the course
  project goal may be
• Ace the course - - - pass the
  course
• Test out some techniques ----
  learn some ideas

2
Project Planning

• Planning - - needs to understand cover 4 1
  major areas
• project deliverables
• deliverable characteristics
• schedules and checkpoints
• cost people resources, tools, processes,
  methods, etc.
• risks

What does this mean ? Does it tie back to
justification goal?
3
Quick Plan

• Needs to Include
• What is the Project?
• Main goals or target
• Brief Project/Product Description (with a list
  of no more than 5-10 major components ---- so one
  must elevate to high level descriptions)
• How much does it cost?
• Rough Cost Estimate people, tools, training,
  etc.
• Rough size and productivity estimate is needed
  for Cost Estimate
• When will it be done?
• High Level Schedule (Use size/productivity and
  estimated resources)
• Major Risks? (sometimes optional depends on the
  risks)

Note that details of project/product
characteristic is not always included
4
More Comprehensive Plan

• What is the project?
• Project Goals/Objectives
• Product/Project List/Description of Deliverables
• Product/Project Attributes and Measurements
• How do you plan to do this?
• Process Methodology (both technical and
  managerial)
• Organizational structure
• When will it be done by Whom?
• Detailed Schedule
• task sequencing
• resource allocation (people staffing and tools)
• How much will it cost?
• resources by type of and levels of skill
• tools, equipment, consultants
• recruiting, travel, training, awards, etc.
• What problems may we encounter?
• Risks and mitigations

5
Software Project Plan Will Change

• Some Reasons
• Functional Non-Functional Requirement Content
  Modified
• Number of Requirements Increased/Decreased
• Technology Change
• Methodology and Process Changes and Improvements
• Deeper Awareness/Understanding of certain
  characteristics
• security
• reliability
• performance
• reuse
• defects quality
• Corrections to Earlier Misunderstandings (e.g.
  after reviews)
• Schedule, Financial, Resource, Tool, etc. changes
  
• As we gain more accurate knowledge about the
  project, that knowledge may often drive further
  changes

6
Software Project Management Plan IEEE Format

• List of content
• Introduction to briefly describe the project and
  the deliverables
• Project organization to describe the process ,
  organizational responsibility structure
• Managerial process to describe the management
  objectives, assumptions, risks, control
  mechanisms, staffing and resource plan
• Technical process to describe the methodology,
  tools, supports and techniques to be used
• Work Packages, Schedule, and Budget

Try the following URL for a copy of the IEEE
1058-1988 Software Project Management plan ---
URL not guaranteed
http//ieeexplore.ieee.org/stamp/stamp.jsp?tparn
umber741937userTypeinst