Scribd
Upload
49 views16 pages

Software Project Management Lecture Three

The document discusses software project management, including defining a project plan with tasks, milestones, and deliverables broken down using a work breakdown structure (WBS). It explains that a project plan is a formal document used to manage and control a project, and a WBS breaks down project goals and activities into smaller, more manageable tasks. An exercise at the end involves revising team structures, breaking goals into tasks, assigning tasks to teams, and scheduling tasks.

Uploaded by

Milkiyas Jc
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
49 views16 pages

Software Project Management Lecture Three

The document discusses software project management, including defining a project plan with tasks, milestones, and deliverables broken down using a work breakdown structure (WBS). It explains that a project plan is a formal document used to manage and control a project, and a WBS breaks down project goals and activities into smaller, more manageable tasks. An exercise at the end involves revising team structures, breaking goals into tasks, assigning tasks to teams, and scheduling tasks.

Uploaded by

Milkiyas Jc
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/ 16

Software Project Management

Lecture Three
Contents
• Project Plan, WBS
• Milestones and Deliverables
• Exercise
Project Plan, WBS
• Project Plan
– A project plan is a formal, approved document
that is used to manage and control a project.
– The project plan forms the basis for all
management efforts associated with the project.
– It is a document that is also expected to change
over time.
– The project plan represents the basic tool for
successfully executing a project.
• The project plan documents the project planning
process and consists of the following basic tasks:
– Defining the sequence of tasks to be performed.
– Identifying all deliverables associated with the project.
– Defining the dependency relationship between tasks.
– Estimating the resources required performing each task.
– Scheduling all tasks to be performed.
– Defining the budget for performing the tasks.
– Defining the organization executing the project.
– Identifying the known project risks.
– Defining the process ensuring quality of the project product.
– Defining the process for configuration management.
– Defining the process specifying and controlling requirements
Work Breakdown Structure
• How do we know how long each task will take?
• How do we devise a complete list of tasks in the first place?
• For this we have to identify the Task.
• Most project control techniques are based on breaking down the
goal of the project into several intermediate goals.
• Each intermediate goal can in turn be broken down further.
• The process can be repeated until each goal is small enough to
be well understood.
• We can then plan for each goal individually its resources
requirements, assignments of responsibility, scheduling, etc.
• A semiformal way of breaking down the goal is called the work
breakdown structure (WBS).
• In this technique, one builds a tree whose root is labeled by the
major activity of the project such as build a compiler.
• The goal of a work breakdown structure is to identify all
the activities that a project must undertake.
• Once these manageable pieces have been identified, they
can be used as units of work assignment.
• The work structure can be refined and extended easily by
labeling the nodes with appropriate information, such as
the planned length of the activity, the name of the person
responsible for the activity, and the starting and ending
date of the activity.
• In this way, the structure can summarize the project plans.
• The work breakdown structure can also be an input into
the scheduling process
MILESTONES AND DELIVERABLES
• Define Milestones
– Milestones are the end-point of a process activity
• EXAMPLES:
– Delivery of requirements spec;
– Delivery of alpha tested code.
• The completion of key actions is important in all
projects.
• These events have no duration. For example,
deliverables often are represented as milestones,
while the effort to produce the deliverable is referred
to as a task.
• While milestones are unique to each project, some example project
milestones are shown below:
– Requirements Approval
– Phase Review Approval
– Prototype Approval
– Design Reviews Complete
– Code Reviews Complete
– Unit Test Complete
– Integration Test Complete
– Acceptance Test Complete
– System Acceptance by User
– Customer Shipment
– Documentation Delivery
• Milestones can occur at the end of each work package in the WBS and
serve as a measurable item upon which to base success of a task.
• Major project milestones should be summarized and included in the
summary project plan.
Defining Deliverables

• Deliverables are project results delivered to customers


• Examples:
– A report (e.g., requirements spec);
– Code (e.g., alpha tested product).
• Deliverables are indicators (but only indicators) of
progress.
• Deliverables associated with each task are shown in the
WBS and are reflected in the Deliverables portion of the
Project Plan.
• While the deliverables list is a compilation of information
identified in the WBS and the project schedule, it is
useful to maintain a separate list since deliverable
completion can be a key metric of project progress.
Exercise
• Revise your team structure and finalize it
• Breaking down the goal of your project into
several intermediate goals
• The process can be repeated until each goal is
small enough to be well understood
• Set time required to complete each mall tasks
• Assign each small tasks to the selected Teams
• Schedule each small tasks
Cash Flow Management
• Cash in
• Cash Out
• Requirement
• How many banks and list of Bank branches
• Source of In come
– List of Customers
• Source of Out come
– List of suppliers
– List of Service providers
– Employees
– Others (House Rent, car rent, fuels)
• Design
• Database
– Required tables
– Bank
– Customer
– Supplier
– Service Provider
– Others
• Interface Design
– Interface for inFlow –Team 1 -1 day
– Interface for outFlow –Team 2- 1 Day
– Interface for Weekly Summary
– Interface for Monlthly Summary
– Interface for time based summary
• Database Development
– Table Implementation
• Back end Code for InFlow -Team 1-1 day
• Back end Code for OutFlow
• Weekly inFlow Summary
• Weekly outFlow Summary
• Monthly inFlow Summary
• Monthly outFlow Summary
• Time Based inFlow Summary
• Time Based outFlow Summary

You might also like