Unit 1.2 Stepwise Project Planning.pdf

software project planning steps

1. Software Project Management
(Step-Wise Project Planning)

2. Contents
❑OverviewofProjectPlanning
❑DifferentStepsofProjectPlanning

3. Overview Of Project Planning
Introduction
•Project Planning is an aspect of project management, which comprises of
various processes.
•The aim of these processes is to ensure thevarious project tasks are well
coordinated and they meet the various project objectives including timely
completion of the project.

4. Stepwise Project Planning
Steps in ProjectPlanning
Step 0:Select project
Step 1: Identify project scope and objectives
Step 2: Identify projectinfrastructure
Step 3: Analyze projectcharacteristics
Step 4: Identify project products and activities
Step5:Estimate effort for eachactivity
Step 6: Identify activity risks
Step 7: Allocateresources
Step8:Review/Publicizeplan
Step9&10:Executeplan/lowerlevelofplanning

5. Source:-Bob Hughes & Mike Cotterell[1]

6. Step 0 : SelectProject

7. Step 1: Identify Project Scope and Objectives
Step 1.1 Identifyobjectivesand measureof
effectiveness
•Get the objectives of aproject
•Measuring effectiveness can be in terms of softwarequality
Performancemeasurement
Mean time of failure
Predictivemeasurement
Error in code

8. Cont..
Step 1.2 Establish a projectauthority
•‘Who is theboss?’
•Identify the authority of theproject
Step1.3Stakeholders Analysis
•Identify all stakeholders in theproject
•The stockholders who are all having interest in project

9. Cont..
Step1.4Change objectivesbased on stakeholder analysis
•The stakeholder suggestion is satisfied means change the
objective
•If it’s not satisfied means , don’t changethe original
objective of theproject
Step 1.5 Establish method of communication with all parties
•We should satisfy the customerrequirements
•How do we keep in contact withcustomer

10. Step 2: Establish project infrastructure
Step 2.1: Identifyrelationshipbetween projectand strategic
planning
•What are the standard methods going tocompletetheproject
Step 2.2: Identify installation standards andprocedures
•What are thefrontend and Backend
•Software are going to use in thisproject
Step 2.3: Identify project teamorganization
•Order of organizing to theproject

11. Step 3:Analyze projectcharacteristics
Step 3.1 :Distinguishprojectas objective drivenor productdriven
Product -Itwillbe given by the user & designby external person
Objective -Problem isgiven
Step 3.2: Analyze other projectcharacteristics
Including quality –basedones
What are the problems going tosolve

12. Cont..
Step 3.3:Identify high level of projectrisks
•Identify the level ofrisk
Step3.4:Take user requirementconcerningimplementation
•Confirm with the userrequirement
Step 3.5:Select development methodology and life cycleapproach
•Step by step process ,what are the methods going to follow in the
project.
Step 3.6:Review overall resourceestimation
•After risk identification, re-estimate effort & resources of project

13. Step 4 : Identify Project Productsand Activities
Step 4.1: Identify and describes project products
Deliverable: Product handover touser
•Inthisstep identify each and everyphase
•Identify the project going todeliver
•Each and every stage consider as aproduct
•Product hierarchy
•ProjectSpecification
Modulespecification
Systemproduct
Managementproduct

14. Cont..
ProjectSpecification
Design
OverallIntegrationTesting
Progress report
Module System Management
specification procedure products
Code

15. Cont..
Step 4.2 : Document generic productflows
•Product flowdiagram
•One stage output isgivento input of otherstage
•Eg:Requirements Design, Coding, Testing
Step 4.3 : Record productinstances
•For each and every product what are the steps going to follow
•Identifying product instance

16. Cont..
Step 4.4: Produce ideal activitynetwork
•Each and every module having severalactivity
•After complete individual module combine all the modules
Step 4.5: Modify ideal to take stages and checkpoints
•Project divided into number of product check each and every
stage we do correctly or not
•Check point to check the progress of the project

17. Step 5:Estimate effort for each activity
Step 5.1: Carry out bottom-up estimation
•Estimate staff effort
How much work in need to complete the project
Product elapse time
How much time taken to complete the project
Non-staffresources
Designing tools
Software need

18. Cont..
Step 5.2: Revise plan to create controllableactivities
•Every phase we need tocontrol
•Need to break a task into a series ofmanageable sub-
tasks
•Break up very long activities into a series of smaller
ones as we can’t judge the status in longactivities

19. Step 6 : Identify activity risks
Step 6.1 : Identify and quantify activity basedrisks
•Identify risk for eachactivity
•During the design phase identify therisk
•Identify damage andlikelihood
•Identify possibilities ofmistakes

20. Cont..
Step 6.2: Plan risk reduction and contingencymeasures
whereappropriate
Review plan and do some steps for reducerisk
Have the alternativeplan
Alternativemeasurement
Otherwise specify a contingencyplan
Forexample:
Contract temporary developer ifteam member becomes
unavailable through illness

21. Cont..
Step 6.3 : Adjust overall plans and estimates to take
account of therisks
Includingaddnew activities -such as training and
practice -ifneeded
Add new activities which reducerisk
associated with otheractivities
E.g.Training
Pilot trials
Informationgathering

22. Step 7 : Allocate resources
Step 7.1 : Identify and allocateresources
Type of staff needed for eachactivity
Staff availability areidentified
Staff are provisionally allocated totask
Step 7.2 : Revise plans and estimates to take into
account resourceconstraints
Staffingconstraints
Staffingissues

23. Step 8: Review / Publicize Plan
Step 8.1 : Review quality aspects of the projectplan
•To ensure each activity is completed with a quality
product
•Each activity should have “exit requirements”
•This ensures the quality of product on each activity
•Check quality of phase before going to next stage

24. Cont..
Step 8.2 : Document plans and obtainagreements
All parties understand and agree to the
commitments in theplan
Make sure everyone understands andagree
Specify this task in a communication planif needed
Develop thedocumentation

25. Step 9 & 10 :Execute plan / lower levelof
planning
•During the project draw up plans for activities in greater detail
as they becomedue
•Detail has to wait as more informationbecomes available
•Especially if you are using an iterative
developmentapproach
•Maintain provisional plans for more important latertasks
•Planning in great detail too soon could be awaste of time

26. References
1.Bob Hughes, Mike Cotterell and Rajib Mall: Software
Project Management –Fifth Edition, McGraw Hill.
2.https://www.youtube.com/watch?v=B8VbuVIym7k&t=136s

27. Thank
You