02-03-2011, 11:07 AM
presented by:
Mohd Zeeshan Ali
[attachment=9331]
Abstract
Under the topic SOFTWARE PROJECT MANAGEMENT ,we discuss how the project and product processes fit together to define a unique project instance. The basic things meant for a project management are why, what , how, do it, and did it .which in turn relates to initiating, planning, executing, controlling and closing , regardless of the nature of the project.
There are mainly four main things to be kept in mind about software project management, they are four p’s people, product, process and project.
Key concepts to be observed here are Agile teams, co-ordination, critical practices, software scope, software team, stake holders, team leaders.
The following are the questions raised while preparing a software project management
How can software metrics be use to manage projects ?
How do we estimate effort, cost and project duration ?
Techniques to be used to formally assess the risks ?
How does a software project manager select tasks ?
How is a project schedule created ?
What is quality management
Why are formal technical reviews so important ?
How changes are to be made to the software after delivery to the customer ?
Now we shall see in brief the answers to above questions and the requirements to define the goal and scope of a unique software project management.
INTRODUCTION
SOFTWARE PROJECT MANAGEMENT
Is concerned with activities
software is delivered on time and on schedule
Meets the requirements of the organisations that develop and procure the software.
KEY ELEMENTS
Project Management
Estimation
Project Scheduling
Risk Management
Quality Management
Change Management
PROJECT MANAGEMENT
The People
people must be organized into effective teams such as PM-CMM.
The Product
Product objectives and scope are defined here.
The Process
Process provides the framework from which a comprehensive plan is designed.
The Project
Project is used to manage complexity.
ESTIMATION
The software project planner must estimate these basic things before a project begins,
Scope of the project and feasibility.
Analyze risks.
Define required resources.
Estimate cost and effort.
Develop a project schedule.
PROJECT SCHEDULING
Software project scheduling is an activity that shows the total effort of individual activities done inside a planned project. Basic principles for Product scheduling
Compartmentalization
Breaking the project into manageable actions, activities and tasks.
Interdependency
Interdependency of each compartmentalized activity , action , or task must be determined.
Time allocation
Each task must be allocated some number of work units.
Effort Validation
The number of people on the software team for a project must be defined.
Defined Responsibilities
Every task that is scheduled should be assigned to a specific team member.
Defined Outcomes
Every task that is scheduled should have a defined outcome.
Defined Milestones
Every task or a group of tasks should be associated with a project milestone
RISK MANAGEMENT
The Risk Management is to assist a project team in defining risks, assessing their impact and probability, and tracking risks through a software project.
Risk Identification
It is a systematic attempt to specify threats to the project plan
Risk Estimation
Establish a scale that reflects the perceived likelihood of a Risk.
Delineate the consequences of the Risk.
Estimate the impact of the risk on the project and the product.
Note the overall accuracy of the risk projection.
Risk Mitigation, Monitoring, And Management
Risk avoidance.
Risk monitoring.
Risk management and contingency planning.
QUALITY MANAGEMENT (SQA)
Software quality management is an umbrella activity that is applied at each step in the software process.
Consists the following steps:
SQA process
Specific quality assurance and quality control tasks
Effective software engineering practice
Control of all software work products
CHANGE MANAGEMENT(SCM)
The main objective here is to manage changes in effective way of software project.
SCM Activities
Identify and Control Change.
Audits and Reports modifications.
conclusion
Finally a project management activity encompasses the below things.
Measurement and metrics
Estimation and scheduling
Risk analysis, tracking and control
All these comprises to form a software project management
Mohd Zeeshan Ali
[attachment=9331]
Abstract
Under the topic SOFTWARE PROJECT MANAGEMENT ,we discuss how the project and product processes fit together to define a unique project instance. The basic things meant for a project management are why, what , how, do it, and did it .which in turn relates to initiating, planning, executing, controlling and closing , regardless of the nature of the project.
There are mainly four main things to be kept in mind about software project management, they are four p’s people, product, process and project.
Key concepts to be observed here are Agile teams, co-ordination, critical practices, software scope, software team, stake holders, team leaders.
The following are the questions raised while preparing a software project management
How can software metrics be use to manage projects ?
How do we estimate effort, cost and project duration ?
Techniques to be used to formally assess the risks ?
How does a software project manager select tasks ?
How is a project schedule created ?
What is quality management
Why are formal technical reviews so important ?
How changes are to be made to the software after delivery to the customer ?
Now we shall see in brief the answers to above questions and the requirements to define the goal and scope of a unique software project management.
INTRODUCTION
SOFTWARE PROJECT MANAGEMENT
Is concerned with activities
software is delivered on time and on schedule
Meets the requirements of the organisations that develop and procure the software.
KEY ELEMENTS
Project Management
Estimation
Project Scheduling
Risk Management
Quality Management
Change Management
PROJECT MANAGEMENT
The People
people must be organized into effective teams such as PM-CMM.
The Product
Product objectives and scope are defined here.
The Process
Process provides the framework from which a comprehensive plan is designed.
The Project
Project is used to manage complexity.
ESTIMATION
The software project planner must estimate these basic things before a project begins,
Scope of the project and feasibility.
Analyze risks.
Define required resources.
Estimate cost and effort.
Develop a project schedule.
PROJECT SCHEDULING
Software project scheduling is an activity that shows the total effort of individual activities done inside a planned project. Basic principles for Product scheduling
Compartmentalization
Breaking the project into manageable actions, activities and tasks.
Interdependency
Interdependency of each compartmentalized activity , action , or task must be determined.
Time allocation
Each task must be allocated some number of work units.
Effort Validation
The number of people on the software team for a project must be defined.
Defined Responsibilities
Every task that is scheduled should be assigned to a specific team member.
Defined Outcomes
Every task that is scheduled should have a defined outcome.
Defined Milestones
Every task or a group of tasks should be associated with a project milestone
RISK MANAGEMENT
The Risk Management is to assist a project team in defining risks, assessing their impact and probability, and tracking risks through a software project.
Risk Identification
It is a systematic attempt to specify threats to the project plan
Risk Estimation
Establish a scale that reflects the perceived likelihood of a Risk.
Delineate the consequences of the Risk.
Estimate the impact of the risk on the project and the product.
Note the overall accuracy of the risk projection.
Risk Mitigation, Monitoring, And Management
Risk avoidance.
Risk monitoring.
Risk management and contingency planning.
QUALITY MANAGEMENT (SQA)
Software quality management is an umbrella activity that is applied at each step in the software process.
Consists the following steps:
SQA process
Specific quality assurance and quality control tasks
Effective software engineering practice
Control of all software work products
CHANGE MANAGEMENT(SCM)
The main objective here is to manage changes in effective way of software project.
SCM Activities
Identify and Control Change.
Audits and Reports modifications.
conclusion
Finally a project management activity encompasses the below things.
Measurement and metrics
Estimation and scheduling
Risk analysis, tracking and control
All these comprises to form a software project management
