SlideShare a Scribd company logo
Project Management
Planning
in
software Projects
JAYAKUMAR.PP
Post Graduate Diploma in eGovernance
IIITM-K,Technopark,Trivandrum
9847435193
SUBJECT MATTER
Introduction to Project
Management.
Planning in Project Management.
Planning in Software Projects.
Activities involved in Planning a
Software Project.
Journal 1 ( IEEE) - Successful
software projects need
requirements planning
Journal 2( IEEE) - Software
project initiation and planning - an
What is Project Management ?
Project management is the discipline of planning,
organizing, securing, managing, leading, and controlling
resources to achieve specific goals. A project is a
temporary endeavor with a defined beginning and end
,undertaken to meet unique goals and objectives. It is a
systematic approach to planning and guiding project
processes from start to finish
Five Stages: Initiation, Planning, Executing,
Controlling, and Closing.
Planning in Project
Management
Project planning is a discipline for stating how to
complete a project within a certain timeframe, usually
with defined stages, and with designated resources. One
view of project planning divides the activity into:
Setting objectives (these should be measurable)
Identifying deliverables
Planning the schedule
Making supporting plans
Supporting plans may include those related to human
Planning in Software
Projects
Software project management begins with a set of
activities that are collectively called project planning. Before
the project can begin, the Project Manager and the
software team must estimate and look into.
 The work to be done
 The resources that will be required
And the time that will elapse from start to finish.
The future and accept some degree of uncertainty as
matter of course.
Lack of Planning leads to …
It is often said that early planning is impossible
because precise information concerning the project goals,
customer needs and system constraints is not available at
the beginning of a software project. But a major purpose of
the planning phase is to clarify goals and needs required
to plan a software project. Lack of good planning leads to
Schedule slippage
Cost overruns
Poor quality
High maintenance cost.
Software Project PlanningActivities
1.Define the Problem,
2.Develop Solution Strategy,
3.Planning the Development Process.
I. Define the Problem Involves :-
Understanding the problem
Justifying the need of a Software
Identifying the functions of a major subsystem
Identify the goals and requirements
Establishing high- level acceptance criteria for the
system.
II. Developing Solution Strategy involves:-
Outlining several solution strategies
Conducting feasibility study for each strategy
Recommending a solution strategy, indicating why
other strategies were rejected.
Developing a list of priorities for product
characteristics.
III. Planning the Development Process involves:-
Defining a life Cycle model and an organizational
structure of the project.
Planning the configuration management, quality
assurance and validation activities.
Determining phase development tools, techniques
and notation to be used.
III. Estimation in Planning Phase include:-
Preliminary cost estimation for system development
•Expert judgment
•Work breakdown structure
•Algorithmic cost model.
Preliminary staffing estimates
Computing resources required to operate and maintain the
system.
Identifying the sources of information and refer to them throughout
the project plan.
Software measures for quality and product
•Metrics used – Size oriented and function oriented
•
Journal 1 ( IEEE) - Successful software projects need
requirements planning
by Annie I Anton, Professor, College of Eng.
North Carolina State University
This paper mainly focus on importance of
understanding the requirements.
According to this author top three project challenged
factors are:
1. Lack of user involvement
2.Incomplete requirement and specification
3.Changing requirements and specifications
Standish Group surveyed that bad requirement
causes 40 – 60% software failures
Key Principles can help eliminate defects during requirement planning.
1.Understanding the problem before expressing the requirement.
2. Involve the stake holders early on and sustain their involvement to validate
requirements. We must give customers repeated opportunities to validate
requirement.
Prototypes – give users a tangible product – it helps to interact
Journal I ( IEEE) - Successful software projects need
requirements planning
by Annie I Anton, Professor, College of Eng.
North Carolina State UniversityKey Principles can help eliminate defects during requirement planning.
3. Ensure that Critical Requirements are considered.
Scenario Analysis – Obstacle analysis – What if questions
4.Give non-functional and quality requirements as much attention as functional
requirements.-users emphasis on functional requirements.
Non functional requirements express a software system’s properties,
including security, reliability, portability, and robustness.
Good requirement planning mean software can be cheaper to produce,
easier to build and less prone to unexpected failures.
Journal 2( IEEE) - Software project initiation and
planning - an empirical study
by D.Greer-UK & R.Conradi- NorwayThis paper describes the study on 14 established Norwegian software
companies - How they initiate and pre-plan software development projects.
The aim was to obtain an indication of the range of planning activities
carried out be these 14 software firm.
The Instrument of study was structured interviews. (Questions are left completely
open ended )- Sampling convenience sampling of 31 companies.
CMM level integration (Capability Maturity Model ) approach emphasis the role of
through planning in the software projects for improving the predictability and to ensure
the process improvement.
Question included from the topics :
 Software process Choice
 Feasibility Study
 Early Planning Documents
 Release Planning
 Risk Management
Journal 2( IEEE) - Software project initiation and
planning - an empirical study
by D.Greer-UK & R.Conradi- NorwayFindings of the Study
1. Most of the firms using Agile method (IID), few of them using Water fall model
2.Study confirms the perceived importance of Feasibility Study , but firms mainly
focus on Economical feasibility ,although several did mention on technical
feasibility.
3.Most companies produce at least a partial requirements documents. Early cost,
schedule and budgets are often documented, but other data on decision taken are
not documented.
4.Waterfall process associated with a single release do often include provision for
future releases. For agile scrum projects , the number of releases planned is
always two or more.
5.Risk Identification and Risk Monitoring are common activities but other risk
management were not explicitly performed in most of the companies.
Conclusion …..
The early planning of software project is very vital
and the software project planner must estimate three
things before a project begins:
How long it will take
How much effort will be required
How many people will be involved
In addition , the project planner must predict the
resources ( Hardware and Software ) that will be
required and the risk associated with this project.
The Success of software project relay on
user involvement and their participation
nces
study book on SE
A Practitioners Approach- Roger.S.Pressman
e.co.in
Questions
??
Thanks ….
END
Question Time
No
Yes
Start

More Related Content

PPTX
Software project planning
PPT
Software quality assurance lecture 1
PPT
Software metrics
PPTX
Software metrics
PPTX
Software quality assurance
PPTX
Software quality assurance
PDF
Pragmatic Approaches to Project Costs Estimation
PPTX
Software project estimation
Software project planning
Software quality assurance lecture 1
Software metrics
Software metrics
Software quality assurance
Software quality assurance
Pragmatic Approaches to Project Costs Estimation
Software project estimation

What's hot (20)

PPT
Software Quality Management
PPT
SOFTWARE PROJECT MANAGEMENT TOOL PPT
PPT
Software Project Management( lecture 1)
PPT
Risk management in software engineering
PPT
Risk management(software engineering)
PPT
Software effort estimation
PPT
Software Estimation Techniques
PPTX
Software Measurement and Metrics.pptx
PPTX
Software Configuration Management
PPTX
Project scheduling and tracking
PPTX
Project Estimation
PPTX
Software Project Management
PDF
Software project management
PPTX
Software Project Management ppt
PPT
Software metrics
PPT
Software cost estimation
PPT
Software Quality Metrics
PPTX
Software Evolution
PPT
Unit 7
PPTX
Language and Processors for Requirements Specification
Software Quality Management
SOFTWARE PROJECT MANAGEMENT TOOL PPT
Software Project Management( lecture 1)
Risk management in software engineering
Risk management(software engineering)
Software effort estimation
Software Estimation Techniques
Software Measurement and Metrics.pptx
Software Configuration Management
Project scheduling and tracking
Project Estimation
Software Project Management
Software project management
Software Project Management ppt
Software metrics
Software cost estimation
Software Quality Metrics
Software Evolution
Unit 7
Language and Processors for Requirements Specification
Ad

Similar to Planning in Software Projects (20)

PDF
SOFTWARE PROJECT PLANNING on Software Engineering
DOCX
Software project planning and monitoring
PPT
1 2. project management
PDF
Software engineering by Dr. vishnu sharma
PPTX
Introduction-to-Software-Project-Management.pptx
PPTX
Unit 1 spm
PPTX
Unit 1 spm
PPTX
Project Management System Architecture for Today
PPT
PPT
Project planning
PPT
01- Lecture 01 - Introduction to SPM.ppt
PDF
Software Project Management | An Overview of the Software Project Management
PDF
nicolas emanuel liso fabbri_project management
PDF
Project Planning in Software Engineering
PPTX
Responsibilities of a Software Project Manager
PDF
Unit 1.2 Stepwise Project Planning.pdf
PPTX
Software Engineering and Project Management - Introduction to Project Management
PDF
Lect-1: Software Project Management - Project Dimensions, Players, SDLC and P...
PPTX
SPM-Lecture 2.pptx
PPTX
Software project management introduction
SOFTWARE PROJECT PLANNING on Software Engineering
Software project planning and monitoring
1 2. project management
Software engineering by Dr. vishnu sharma
Introduction-to-Software-Project-Management.pptx
Unit 1 spm
Unit 1 spm
Project Management System Architecture for Today
Project planning
01- Lecture 01 - Introduction to SPM.ppt
Software Project Management | An Overview of the Software Project Management
nicolas emanuel liso fabbri_project management
Project Planning in Software Engineering
Responsibilities of a Software Project Manager
Unit 1.2 Stepwise Project Planning.pdf
Software Engineering and Project Management - Introduction to Project Management
Lect-1: Software Project Management - Project Dimensions, Players, SDLC and P...
SPM-Lecture 2.pptx
Software project management introduction
Ad

More from Jayakumar PP (9)

PDF
Financial Crime and Investigation- Finacial Frauds
PDF
Blockchain technology and logistics management
PDF
Akshaya Banking Kiosk
PDF
Akshaya Project of Government of Kerala
DOCX
Akshaya down the years
PDF
Cyber Space Threats and Opportunities
PDF
IT to IOT Evolution
PPT
CCTNS
PPSX
Class on cyber crime
Financial Crime and Investigation- Finacial Frauds
Blockchain technology and logistics management
Akshaya Banking Kiosk
Akshaya Project of Government of Kerala
Akshaya down the years
Cyber Space Threats and Opportunities
IT to IOT Evolution
CCTNS
Class on cyber crime

Recently uploaded (20)

PDF
Unlocking AI with Model Context Protocol (MCP)
PPTX
Digital-Transformation-Roadmap-for-Companies.pptx
PPTX
MYSQL Presentation for SQL database connectivity
PDF
Electronic commerce courselecture one. Pdf
PDF
Diabetes mellitus diagnosis method based random forest with bat algorithm
PDF
Per capita expenditure prediction using model stacking based on satellite ima...
PDF
Build a system with the filesystem maintained by OSTree @ COSCUP 2025
PDF
CIFDAQ's Market Insight: SEC Turns Pro Crypto
PDF
Bridging biosciences and deep learning for revolutionary discoveries: a compr...
PDF
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
PDF
Approach and Philosophy of On baking technology
PDF
Shreyas Phanse Resume: Experienced Backend Engineer | Java • Spring Boot • Ka...
PDF
Encapsulation theory and applications.pdf
PPTX
VMware vSphere Foundation How to Sell Presentation-Ver1.4-2-14-2024.pptx
DOCX
The AUB Centre for AI in Media Proposal.docx
PDF
TokAI - TikTok AI Agent : The First AI Application That Analyzes 10,000+ Vira...
PPT
“AI and Expert System Decision Support & Business Intelligence Systems”
PDF
The Rise and Fall of 3GPP – Time for a Sabbatical?
PDF
Reach Out and Touch Someone: Haptics and Empathic Computing
PDF
KodekX | Application Modernization Development
Unlocking AI with Model Context Protocol (MCP)
Digital-Transformation-Roadmap-for-Companies.pptx
MYSQL Presentation for SQL database connectivity
Electronic commerce courselecture one. Pdf
Diabetes mellitus diagnosis method based random forest with bat algorithm
Per capita expenditure prediction using model stacking based on satellite ima...
Build a system with the filesystem maintained by OSTree @ COSCUP 2025
CIFDAQ's Market Insight: SEC Turns Pro Crypto
Bridging biosciences and deep learning for revolutionary discoveries: a compr...
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
Approach and Philosophy of On baking technology
Shreyas Phanse Resume: Experienced Backend Engineer | Java • Spring Boot • Ka...
Encapsulation theory and applications.pdf
VMware vSphere Foundation How to Sell Presentation-Ver1.4-2-14-2024.pptx
The AUB Centre for AI in Media Proposal.docx
TokAI - TikTok AI Agent : The First AI Application That Analyzes 10,000+ Vira...
“AI and Expert System Decision Support & Business Intelligence Systems”
The Rise and Fall of 3GPP – Time for a Sabbatical?
Reach Out and Touch Someone: Haptics and Empathic Computing
KodekX | Application Modernization Development

Planning in Software Projects

  • 1. Project Management Planning in software Projects JAYAKUMAR.PP Post Graduate Diploma in eGovernance IIITM-K,Technopark,Trivandrum 9847435193
  • 2. SUBJECT MATTER Introduction to Project Management. Planning in Project Management. Planning in Software Projects. Activities involved in Planning a Software Project. Journal 1 ( IEEE) - Successful software projects need requirements planning Journal 2( IEEE) - Software project initiation and planning - an
  • 3. What is Project Management ? Project management is the discipline of planning, organizing, securing, managing, leading, and controlling resources to achieve specific goals. A project is a temporary endeavor with a defined beginning and end ,undertaken to meet unique goals and objectives. It is a systematic approach to planning and guiding project processes from start to finish Five Stages: Initiation, Planning, Executing, Controlling, and Closing.
  • 4. Planning in Project Management Project planning is a discipline for stating how to complete a project within a certain timeframe, usually with defined stages, and with designated resources. One view of project planning divides the activity into: Setting objectives (these should be measurable) Identifying deliverables Planning the schedule Making supporting plans Supporting plans may include those related to human
  • 5. Planning in Software Projects Software project management begins with a set of activities that are collectively called project planning. Before the project can begin, the Project Manager and the software team must estimate and look into.  The work to be done  The resources that will be required And the time that will elapse from start to finish. The future and accept some degree of uncertainty as matter of course.
  • 6. Lack of Planning leads to … It is often said that early planning is impossible because precise information concerning the project goals, customer needs and system constraints is not available at the beginning of a software project. But a major purpose of the planning phase is to clarify goals and needs required to plan a software project. Lack of good planning leads to Schedule slippage Cost overruns Poor quality High maintenance cost.
  • 7. Software Project PlanningActivities 1.Define the Problem, 2.Develop Solution Strategy, 3.Planning the Development Process. I. Define the Problem Involves :- Understanding the problem Justifying the need of a Software Identifying the functions of a major subsystem Identify the goals and requirements Establishing high- level acceptance criteria for the system.
  • 8. II. Developing Solution Strategy involves:- Outlining several solution strategies Conducting feasibility study for each strategy Recommending a solution strategy, indicating why other strategies were rejected. Developing a list of priorities for product characteristics.
  • 9. III. Planning the Development Process involves:- Defining a life Cycle model and an organizational structure of the project. Planning the configuration management, quality assurance and validation activities. Determining phase development tools, techniques and notation to be used.
  • 10. III. Estimation in Planning Phase include:- Preliminary cost estimation for system development •Expert judgment •Work breakdown structure •Algorithmic cost model. Preliminary staffing estimates Computing resources required to operate and maintain the system. Identifying the sources of information and refer to them throughout the project plan. Software measures for quality and product •Metrics used – Size oriented and function oriented •
  • 11. Journal 1 ( IEEE) - Successful software projects need requirements planning by Annie I Anton, Professor, College of Eng. North Carolina State University This paper mainly focus on importance of understanding the requirements. According to this author top three project challenged factors are: 1. Lack of user involvement 2.Incomplete requirement and specification 3.Changing requirements and specifications Standish Group surveyed that bad requirement causes 40 – 60% software failures Key Principles can help eliminate defects during requirement planning. 1.Understanding the problem before expressing the requirement. 2. Involve the stake holders early on and sustain their involvement to validate requirements. We must give customers repeated opportunities to validate requirement. Prototypes – give users a tangible product – it helps to interact
  • 12. Journal I ( IEEE) - Successful software projects need requirements planning by Annie I Anton, Professor, College of Eng. North Carolina State UniversityKey Principles can help eliminate defects during requirement planning. 3. Ensure that Critical Requirements are considered. Scenario Analysis – Obstacle analysis – What if questions 4.Give non-functional and quality requirements as much attention as functional requirements.-users emphasis on functional requirements. Non functional requirements express a software system’s properties, including security, reliability, portability, and robustness. Good requirement planning mean software can be cheaper to produce, easier to build and less prone to unexpected failures.
  • 13. Journal 2( IEEE) - Software project initiation and planning - an empirical study by D.Greer-UK & R.Conradi- NorwayThis paper describes the study on 14 established Norwegian software companies - How they initiate and pre-plan software development projects. The aim was to obtain an indication of the range of planning activities carried out be these 14 software firm. The Instrument of study was structured interviews. (Questions are left completely open ended )- Sampling convenience sampling of 31 companies. CMM level integration (Capability Maturity Model ) approach emphasis the role of through planning in the software projects for improving the predictability and to ensure the process improvement. Question included from the topics :  Software process Choice  Feasibility Study  Early Planning Documents  Release Planning  Risk Management
  • 14. Journal 2( IEEE) - Software project initiation and planning - an empirical study by D.Greer-UK & R.Conradi- NorwayFindings of the Study 1. Most of the firms using Agile method (IID), few of them using Water fall model 2.Study confirms the perceived importance of Feasibility Study , but firms mainly focus on Economical feasibility ,although several did mention on technical feasibility. 3.Most companies produce at least a partial requirements documents. Early cost, schedule and budgets are often documented, but other data on decision taken are not documented. 4.Waterfall process associated with a single release do often include provision for future releases. For agile scrum projects , the number of releases planned is always two or more. 5.Risk Identification and Risk Monitoring are common activities but other risk management were not explicitly performed in most of the companies.
  • 15. Conclusion ….. The early planning of software project is very vital and the software project planner must estimate three things before a project begins: How long it will take How much effort will be required How many people will be involved In addition , the project planner must predict the resources ( Hardware and Software ) that will be required and the risk associated with this project. The Success of software project relay on user involvement and their participation nces study book on SE A Practitioners Approach- Roger.S.Pressman e.co.in