Professional Documents
Culture Documents
SPM - CH - 2lecture 2
SPM - CH - 2lecture 2
An
approach to planning software
projects
1
‘Step Wise’ - an overview
0.Select
1. Identify project 2. Identify project
project objectives infrastructure
3. Analyse
project
characteristics
Review
4. Identify products
and activities
5. Estimate effort
Lower for activity
level For each
detail activity
6. Identify activity
risks
10. Lower level
7. Allocate
planning
resources
8. Review/ publicize
9. Execute plan plan
2
Step 0:Select Project
• It is called 0 step
– It is outside main project planning process
• Here we do feasibility study
• Priority of projects
• Merits of project
3
Step:1-Project scope and objectives
4
Step:1-Cont…
• 1.4 Modify objectives in the light of stakeholder
analysis
– ‘do we need to do things to win over stakeholders?’
– Add new features for stakeholder’s benefit
• Drawback is size(work and finance) may increase
5
Step:1-Cont…
• Project Scope
• Identify the objectives
• Defining goals
6
Step:2- Establish project infrastructure
7
Tentative Priority steps
• The selection process—must select
• Proposals screening
• The priority Team
• Selection criteria
• Assessing results
8
Step:2-Cont…
• 2.2 Identify installation standards and
procedures
– What are the development procedures?
– ‘What standards do we have to follow?’
– Change control and management
• Changes to requirements are implemented in safe and
orderly manner.
– Quality standards
• Establish quality checks at each phase of SDLC.
9
Change control
• Change control is a systematic approach
to managing all changes made to a product or
system. The purpose is to ensure that no
unnecessary changes are made, that
all changes are documented, that services are
not unnecessarily disrupted and that resources
are used efficiently
10
Step:2-Cont…
12
Step:3-Cont…
15
STEP:4-IDENTIFY PROJECT PRODUCTS AND
ACTIVITIES
17
Products
• The following are NOT normally products:
– activities
• training
– events
• interviews completed
– resources and actors
• software developer
18
Product description (PD)
• Product identity • Relevant standards
• Description • Quality criteria
• Derivation
• Composition
• Format
19
4.2 Document Generic product
flows
Test Plan
Analysis report
Change
requests 20
Step 4.3 Recognize product instances
21
4.4. Produce ideal activity network
• Identify the activities needed to create each
product in the PFD
• More than one activity might be needed to
create a single product
22
Step 5:Estimate effort for each activity
23
Step 5:Estimate effort for each activity
24
Step 6: Identify activity risks
• 6.1.Identify and quantify risks for activities
– damage if risk occurs (measure in time lost or
money)
– likelihood if risk occurring
25
• 6.3 Adjust overall plans and estimates to
take account of risks
– Adjust the plans according to the risk involved
with it.
– e.g. add new activities which reduce risks
associated with other activities e.g. training,
pilot trials, information gathering
26
Step 7: Allocate resources
• 7.1 Identify and allocate resources to activities
– Type of staff needed
– Numbers
– Staff availability
• 7.2 Revise plans and estimates to take into account
resource constraints
– Some staff may be needed for more than one task at same
time so priority should be given to the critical activity
– e.g. staff not being available until a later date
– Non-project activities
– O/P of this step is Gantt chart
27
Week Gantt charts
APRIL
commencing MARCH
5 12 19 26 2 9 16
Plan testing
Select subjects
Design
questionnaire
Design Quality
Parameters
Conduct tests
Analyze results
Draft changes
28
Step 8: Review/publicise plan
30