Sie sind auf Seite 1von 19

9/4/2010

Software Project Planning


Information Technology Project
Management
Eddy Gunawan, S.T.P, M.T.I

 Introduction to project phase


 Requirement gathering
 Vision & scope document
 Create project plan
 Statement of works
 Resource list
 Risk plan

 Project planning problems

9/4/2010

Phases of the Traditional Project Life


Cycle

33

PROJECT PHASE

ACTIVITIES

Definition
Requirements
Go/no Go decision
Proposal

Analysis
Functional
specification
Development
Proposal
Re-estimate

Design
System Design
ATP
Re-estimate

Module Design
Coding

John J. Rakos
System Test

Acceptance

Integration
Testing

Acceptance Test

Project Management

Operation
Cutover
Warranty
Sell next project
Post Project Rev.
Maintenance

Reviews
Status Reports
(*)

DOCUMENTS AND
(MILESTONES)

Programming

Requirement
Document (*)
(userS.O.)
Analysis Proposal
(User buys)
Preliminary
project plan
(resource provider
S.O)

Documentation

Functional
Spesification
(user S.O)
Estimates and
Project plan
(re-done)
Top level design

Design specifica.
(walked thru.)
Acceptance test
Plan (user s.o)
Revised estimates
(done)

Module Design
(walked thru)
System test Plan
(Done)
User DocumenTation
(started)
Programs
(tested)
Project leader
(S.O)

User Training
Working/
Debugged
System
(Proj.Mgr S.O.)

Test Result
(user S.O.)

New system
Operational
(user satis.)

User Supported
Proposal for
Next project
(user buy)

Relative Effort
(PM)

(Total Staff)

(*) The requirements Document may or may not be part of the project

9/4/2010

Engineering Workflows

Building House Analogy - Definition


 User : I am living in a tent on an empty lot in the north

eastern part of the country.


 What is the problem?
 It is wintertime and it is cold in my tent; in the summer it

is too hot. I need temperature control.


 It is too bright inside in the day time, and too dark at

night. I need lighting control.


 When I need to perform my necessities, I have to go out
and shovel a hole in the snow. If I need to wash, I must
heat the water on an open fie. I needplumbing.
 My spouse and two children are living with me in this
tent. We need privacy and sound isolation.
 Write them down to produce requirement definition
6

9/4/2010

Building House Analogy - Analysis




Promises to user :
 Mr./Ms. User, we will build a house for you. This house will have rooms with

opaque andsoundproof walls, to provide you withprivacy and sound isolation.

 We will put a 'gizmo' on the wall called a thermostat, (include a diagram of a

thermostat),which will provide you with temperature control. If you turn the
thermostat to the right, the house will get warmer. If you turn it to the left, the house
will become colder.
 In each room there will be a 'gizmo' called a light switch (provide a diagram) to
provide you withl ight control. If you push the switch upward, the room will be
bright, if downward, the room will be dark.
 Plumbing will be provided in a room called the 'bathroom' with utilities to do the
necessities and for washing. There will be a lever on one utility, which, when
pushed
 downward, will flush (provide a diagram?). There will be utilities with 'taps'. When
you turn the left tap clockwise hot water will come out. When you turn the right tap
clockwise cold water will come out (provide a diagram).


Functional Specification list the promises (deliverables) to solve user problem

Building House Analogy - Design


 The goal of design is to divide the system into

functional components, and then interconnect the


components efficiently (blueprint)
 Divided the house into living area, eating area,

sleeping area.
 Placement of each room, as well as the doors and
halls for the most efficient interconnection between
the rooms
 Furnace to control temperature
 Wiring location
 Placement plumbing
8

9/4/2010

Building House Analogy Programming


 The work of contractor, carpenters, plumbers,

electricians, etc
 They all work according to blueprint or design
specification.

Building House Analogy System


Test
 Putting the pieces together and ensuring that

everything works together (Integration)


 The basement, the first floor, second floor, etc is
correctly connected.
 Test each component : all the lights, thermostats,
plumbing, etc

10

9/4/2010

Building House Analogy Operation


 The user family is move in and live in the house
 The periode of warranty must be provided

because problems may still be found that need to


be fixed.

11

Building House Analogy


Acceptance
 The user sees the complete house.
 Systematically test each light switch, thermostat

and so forth to ensure that they work according to


the promise made to her.

12

9/4/2010

Who needs software?


 Most software is built in organizations for

people with specific needs.

 A stakeholder is a anyone who has an interest (or

stake) in the software being completed

 A user is someone who will need to use the

software to perform tasks.

 Sometimes stakeholders will be users; but often the

stakeholder will not use the software.

 For example, a senior manager (like a CEO or CTO in a

company) will usually have a stake in the software that is


built (since it affects the bottom line), even if she wont ever
use it.

13

Who builds software?


 Software is typically built by a team of

software engineers, which includes:


 Business analysts or requirements analysts who

talk to users and stakeholders, plan the behavior of


software and write software requirements
 Designers and architects who plan the technical
solution
 Programmers who write the code
 Testers who verify that the software meets its
requirements and behaves as expected

14

9/4/2010

Project Management
 The project manager plans and guides the

software project
 The project manager is responsible for identifying

the users and stakeholders and determining their


needs
 The project manager coordinates the team,
ensuring that each task has an appropriate software
engineer assigned and that each engineer has
sufficient knowledge to perform it
 To do this well, the project manager must be familiar
with every aspect of software engineering

15

Identifying Needs
 The project manager drives the scope of the

project.
 The project manager should identify and talk to the

main stakeholder
 The effective way to show stakeholders that their
needs are understood and that those specific needs
will be addressed is with a vision and scope
document

16

9/4/2010

Relationship of several types of


requirement

17Software Requirements, Second Edition. Karl E. Wiegers , Microsoft Press

Vision and Scope Document




A typical vision and scope document follows an


outline like this one:
1. Problem Statement
a) Project background
b) Stakeholders
c) Users
d) Risks
e) Assumptions
2. Vision of the Solution
a) Vision statement
b) List of features
c) Scope of phased release (optional)
d) Features that will not be developed

18

9/4/2010

Vision Statement
 A general statement describing how those needs

will be filled
 Vision statement summarizes the long-term
purpose and intent of the new product.
 The vision statement should reflect a balaced
view that will satisfy the needs of diverse
stakeholders.
 It can be somewhat idealistic but should be
grounded in the realities of existing or anticipated
markets, enterprise architectures, corporate
strategic directions, and resource limitations
19Software Requirements, Second Edition. Karl E. Wiegers , Microsoft Press

Example of Vision Template


 For [target customer]
 Who [statement of the need or opportunity]
 The [product name]
 Is [a product category]
 That [key benefit, compelling reason to buy or

use]
 Unlike [primary competitive alternative, current
system, or current business process]
 Our product [statement of primary differentiation
and advantages of product]
20Software

Requirements, Second Edition. Karl E. Wiegers , Microsoft Press

10

9/4/2010

Example of vision statement


 For scientists who need to request containers of chemicals, the

Chemical Tracking System is an information system that will


provide a single point of access to the chemical stockroom and
to vendors. The system will store the location of every chemical
container within the company, the quantity of material remaining
in it, and the complete history of each container's locations and
usage. This system will save the company 25 percent on
chemical costs in the first year of use by allowing the company to
fully exploit chemicals that are already available within the
company, dispose of fewer partially used or expired containers,
and use a single standard chemical purchasing process. Unlike
the current manual ordering processes, our product will
generate all reports required to comply with federal and state
government regulations that require the reporting of chemical
usage, storage, and disposal.

21Software

Requirements, Second Edition. Karl E. Wiegers , Microsoft Press

Three Sphere Model for Systems


Management

22
Information Technology Project Management, Fifth Edition, Copyright 2007

11

9/4/2010

Media Snapshot: Where IT Matters


 In 2006, Baseline Magazine published Where I.T.

Matters: How 10 Technologies Transformed 10


Industries as a retort to Nicholas Carrs ideas
(author of IT Doesnt Matter)
 VoIP has transformed the telecommunications

industry and broadband Internet access


 Global Positioning Systems (GPS) has changed the
farming industry
 Digital supply chain has changed the entertainment
industrys distribution system

23

Criteria for Selecting Methodology

An ObjectObject-Oriented Approach, Alan Dennis, Barbara Wixom, and David Tegarden. Second Edition

2424

12

9/4/2010

Project Plan
 The project plan defines the work that will be done on

the project and who will do it. It consists of:


 A statement of work (SOW) that describes all work products






that will be produced and a list of people who will perform that
work
A resource list that contains a list of all resources that will be
needed for the product and their availability
A work breakdown structure and a set of estimates
A project schedule
A risk plan that identifies any risks that might be encountered
and indicates how those risks would be handled should they
occur

25

Statement of Work
 The statement of work (SOW) is a detailed

description of all of the work products which


will be created over the course of the project.
It includes:
 A list of features that will be developed
 A description of each intermediate deliverable or

work product that will be built.


 The estimated effort involved for each work product
to be delivered

26

13

9/4/2010

Resource List
 The project plan should contain a list of all

resources that will be used on the project.


 A resource is a person, hardware, room or anything

else that is necessary for the project but limited in


its availability
 The resource list should give each resource a
name, a brief one-line description, and list the
availability and cost (if applicable) of the resource

27

Estimates and Project Schedule


 The project plan should also include estimates and a

project schedule:
 A work breakdown structure (WBS) is defined. This is a list of

tasks which, if performed, will generate all of the work


products needed to build the software.
 An estimate of the effort required for each task in the WBS is
generated.
 A project schedule is created by assigning resources and
determining the calendar time required for each task.

Estimates and project schedules will be discussed in


detail in later slides.

28

14

9/4/2010

Risk Plan
 A risk plan is a list of all risks that threaten the

project, along with a plan to mitigate some or


all of those risks.
 The project manager selects team members to

participate in a risk planning session:


 The team members brainstorm potential risks
 The probability and impact of each risk is estimated
 A risk plan is constructed

29

Risk Plan Example

30

15

9/4/2010

The Four Steps of Risk Management


 Anticipate the risk
 Eliminating the risk where possible
 Reducing the risk by contingency planning and

pricing
 Staying in control when things go wrong

31

Situation that expose your project to


risks
 General risk situations
 Improper working environment
 Third party supplied resources
 Crash projects
 Unspecified payment / budget

 Financial risk situations


 Technical risk situations
 The wrong solution
 Bad requirements / specification
 Not knowing the user
32

16

9/4/2010

Project Plan Inspection Checklist


 Statement of work
 Does the project plan include a SOW?
 Is the SOW complete does it contain all of the features

that will be developed?


 Are all work products represented?
 If estimates are known, have they been included?
 Resources

 Does the project plan include a resource list?


 Does the resource list contain all resource available to

the project?

 Are there any resources known to be assigned to other

project at the same time they are assigned to this one?

 Have dates that the resources are unavailable been

taken into account?

33

Project Plan Inspection Checklist


(cont)
 Project schedule
 Does the project plan include a schedule?
 Are there any task that are missing or incorrect?
 If a WBS was generated by a Delphi session, does the project








schedule reflect all of the task that were identified by the


team?
Does each task have a predecessor?
Is a resource allocated to each task?
If multiple resource have been assigned to a single task, has
the taskduration been update properly to reflect that?
If multiple resources have been assigned to a single task, has
the tasks duration been update properly to reflect that?
Is ther a more efficient way to allocate resources?
Does the project schedule contian perodic reviews?

34

17

9/4/2010

Project Plan Inspection Checklist


(cont)
 Risk plan
 Does the project plan include a risk plan?
 Are there any risk that are not in the plan?
 Are there any assumptions (from the vision and

scope document or a delphi session) that represent


risks that should be included in the plan?
 Is each risk prioritized correctly?
 Has the impact of each risk been estimated
correctly?
 Have the risks been sufficiently mitigated?

35

Project Planning Problems


 Lack of leadership
 The mid-course correction
 The detached engineering team

36

18

9/4/2010

Tugas 1
 Pilih proyek yang diketahui dari tempat magang,

kampus ataupun dari Internet


 Buat dokumen vision & scope
 Buat perencanaan proyek
 SOW (statement of work)
 List of feature
 Description of intermediate deliverable of work product
 Estimate effort
 Resource list
 Risk plan

37

19

Das könnte Ihnen auch gefallen