Professional Documents
Culture Documents
Chapter No 1
Chapter No 1
Chapter No 1
By
Prof. Supriya Ghodekar.
Chapter No-1
Linear Project Management Framework
What is Project –
A project is a group of tasks that need to complete to reach a clear result. A
project also defines as a set of inputs and outputs which are required to achieve a
goal. Projects can vary from simple to difficult and can be operated by one
person or a hundred.
1.Time
2.Cost
3.Quality
Reporting –
Reporting in two ways has an impact on the project. Project directors can monitor
progress in two ways: first, it provides information to partners during introductions that
helps them stay on the right track. Reports on undertakings may differ in terms of task
advancement, cost, and variation.
Phase-5: Project Closure :
The customer or partner is notified of the ultimate expectations during the
fifth step, which is project completion. Once everything has been
verified, it is delivered, the paperwork is finished, and everything is
approved. The team and project manager can now take the lead in an
overview assessment of the project's activities and learn from it.
Depending on the project, transferring control to a different team—such
as the tasks supervisory team—may also occur at this point.In this
instance, it is the attempt supervisor's duty to make sure that the transition
goes well.
1)Move Deliverables –
2)Affirm Completion –
3)Audit Documentation –
4)Delivery Resources –
• Project Manager
A project manager is a character who has the overall responsibility for
the planning, design, execution, monitoring, controlling and closure of
a project. A project manager represents an essential role in the
achievement of the projects.
3)Every decision the project manager makes must directly profit their
project.
Role of a Project Manager:
1. Leader:
A project manager must lead his team and should provide them direction to make
them understand what is expected from all of them.
2. Medium:
The Project manager is a medium between his clients and his team. He must
coordinate and transfer all the appropriate information from the clients to his team
and report to the senior management.
3. Mentor:
He should be there to guide his team at each step and make sure that the team has an
attachment. He provides a recommendation to his team and points them in the right
direction.
Responsibilities of a Project Manager:
1.Managing risks and issues.
2.Create the project team and assigns tasks to several team members.
3.Activity planning and sequencing.
4.Monitoring and reporting progress.
5.Modifies the project plan to deal with the situation.
Activities
Software Project Management consists of many activities, that includes
planning of the project, deciding the scope of product, estimation of cost in
different terms, scheduling of tasks, etc.
The list of activities are as follows:
1. Project planning and Tracking
2. Project Resource Management
3. Scope Management
4. Estimation Management
5. Project Risk Management
6. Scheduling Management
7. Project Communication Management
8. Configuration Management
Now we will discuss all these activities -
1. Project Planning: It is a set of multiple processes, or we can say that it a task that
performed before the construction of the product starts.
2. Scope Management: It describes the scope of the project. Scope management is
important because it clearly defines what would do and what would not. Scope
Management create the project to contain restricted and quantitative tasks, which may
merely be documented and successively avoids price and time overrun.
3. Estimation management: This is not only about cost estimation because whenever
we start to develop software, but we also figure out their size(line of code), efforts, time
as well as cost.
Size of software
Quality
Hardware
Communication
Training
Additional Software and tools
Skilled manpower
4. Scheduling Management: Scheduling Management in software refers to all
the activities to complete in the specified order and within time slotted to each
activity. Project managers define multiple tasks and arrange them keeping
various factors in mind.
For scheduling, it is compulsory -
o Find out multiple tasks and correlate them.
o Divide time into units.
o Assign the respective number of work-units for every job.
o Calculate the total time from start to finish.
o Break down the project into modules.
5. Project Resource Management: In software Development, all the elements
are referred to as resources for the project. It can be a human resource,
productive tools, and libraries.
Resource management includes:
o Create a project team and assign responsibilities to every team member
o Developing a resource plan is derived from the project plan.
o Adjustment of resources.
6. Project Risk Management: Risk management consists of all the activities like
identification, analyzing and preparing the plan for predictable and unpredictable risk
in the project.
Several points show the risks in the project:
o The Experienced team leaves the project, and the new team joins it.
o Changes in requirement.
o Change in technologies and the environment.
o Market competition.
7.Project Communication Management: Communication is an essential factor in the
success of the project. It is a bridge between client, organization, team members and as
well as other stakeholders of the project such as hardware suppliers.
From the planning to closure, communication plays a vital role. In all the phases,
communication must be clear and understood.
Miscommunication can create a big blunder in the project.
8. Project Configuration Management: Configuration management is
about to control the changes in software like requirements, design, and
development of the product.
Quality metrics measure the value and performance of your business's products,
services, and processes.
Quality metrics can help assess customer satisfaction levels, identify areas for
improvement within your company, and track the overall quality of your
products or services
1. Code Quality – Code quality metrics measure the quality of code used for software
project development. Maintaining the software code quality by writing Bug-free and
semantically correct code is very important for good software project development. In
code quality, both Quantitative metrics like the number of lines, complexity, functions,
rate of bugs generation, etc, and Qualitative metrics like readability, code clarity,
efficiency, and maintainability, etc are measured.
2. Reliability – Reliability metrics express the reliability of software in different
conditions. The software is able to provide exact service at the right time or not checked.
Reliability can be checked using Mean Time Between Failure (MTBF) and Mean Time
To Repair (MTTR).
3. Performance – Performance metrics are used to measure the performance of the
software. Each software has been developed for some specific purposes. Performance
metrics measure the performance of the software by determining whether the software is
fulfilling the user requirements or not, by analyzing how much time and resource it is
utilizing for providing the service.
4. Usability – Usability metrics check whether the program is user-friendly or not. Each
software is used by the end-user. So it is important to measure that the end-user is happy
or not by using this software.
5. Correctness – Correctness is one of the important software quality metrics as this
checks whether the system or software is working correctly without any error by
satisfying the user. Correctness gives the degree of service each function provides as
per developed.
6. Maintainability – Each software product requires maintenance and up-gradation.
Maintenance is an expensive and time-consuming process. So if the software product
provides easy maintainability then we can say software quality is up to mark.
Maintainability metrics include the time required to adapt to new
features/functionality, Mean Time to Change (MTTC), performance in changing
environments, etc.
7. Integrity – Software integrity is important in terms of how much it is easy to
integrate with other required software which increases software functionality and
what is the control on integration from unauthorized software’s which increases the
chances of cyberattacks.
8. Security – Security metrics measure how secure the software is. In the age of cyber
terrorism, security is the most essential part of every software. Security assures that
there are no unauthorized changes, no fear of cyber attacks, etc when the software
product is in use by the end-user.
What is Risk?
"Tomorrow problems are today's risk." Hence, a clear definition of a "risk" is a problem
that could cause some loss or threaten the progress of the project, but which has not
happened yet.
These potential issues might harm cost, schedule or technical success of the project and
the quality of our software device, or project team morale.
“Risk Management is the system of identifying addressing and eliminating these
problems before they can damage the project.”
Risk Management
A software project can be concerned with a large variety of risks. In order to
be adept to systematically identify the significant risks which might affect a
software project, it is essential to classify risks into different classes. The
project manager can then check which risks from each class are relevant to
the project.
There are three main classifications of risks which can affect a software
project:
1.Project risks
2.Technical risks
3.Business risks
1.Project risks: Risks are threats affect the project schedule or resources. It is related
to loss of personnel or funds allocated to the project. An example of a project risk is the
loss of an experienced and talented staff. Finding an equivalent staff with appropriate
skills and experience may take a long time and, consequently, the software design will
take longer to complete.
2. Product risks: Risks that affect the quality or performance of the software. An
example of a product risk is the failure of a purchased component to perform as
expected. This may affect the overall performance of the system so that it is slower
than expected.
3. Business risks: Risks that threaten the viability of the software and affect the
organisation developing. For example, a competitor introducing a new product is a
business risk. The introduction of a competitive product will affect the sales of existing
software products..
Other risk categories
1.1. Known risks: Risks that become visible following a through evaluation
of the project schedule, the commercial and technological context in which
the plan is being created, and more reliable data sources (such as an
impossible delivery date)
1.2. Predictable risks: Risks that are assumed from previous project
experience (e.g., turnover in the past)
1.3. Unpredictable risks: Those risks that can and do occur, but are
extremely tough to identify in advance.
Principle of Risk Management
2. Risk analysis: You should assess the likelihood and consequences of these risks.
3. Risk planning: You should make plans to address the risk, either by avoiding it or
minimizing its effects on the project.
4. Risk monitoring: You should regularly assess the risk and your plans for risk mitigation
and revise these when you learn more about the risk.
The risk management process is an iterative process that continues throughout the project.
Once you have drawn up an initial risk management plan, you monitor the situation to
detect emerging risks. As more information about the risks becomes available, you have to
reanalyze the risks and decide if the risk priority has changed. You may then have to change
your plans for risk avoidance and contingency management.
1)Identification of Risk :
Risk identification is the first stage of the risk management process.
Risk identification may be a team process where a team get together
to brainstorm possible risks.
Alternatively, the project manager may simply use his or her
experience to identify the most probable or critical risks.
• It is concerned with o Identifying the risks
• What Type of risk it is
• To which it is associated
• From where it is derived.
• Possible threats of risk
• There are several other tools and techniques also for identifying
risks Five common information gathering techniques for risk
identification include brainstorming, Delphi
technique,interviewing,root cause analysis, and SWOT analysis.
Sr. Risk Type Associated /Derived From Possible Threats database used in
No.
1. Technology Derive from the software or The the system cannot process as many
risks hardware technologies that are transactions per second as expected.
used to develop the system Reusable software components contain
defects that mean they cannot be reused
as planned.
2. People risks Associated with the people in the It is impossible to recruit staff with the
development team. skills required Key staff are ill and
unavailable at critical times. Required
training for staff is not available.
5. Requirements Risks that derive from changes Changes to requirements that require
risks to the customer requirements major design rework are proposed.
and the process of managing the Customers fail to understand the
requirements change. impact of requirements changes.
6. Estimation Risks that derive from the The time required to develop the
risks management estimates of the software is under-estimated. The rate
resources required to build the of defect repair is underestimated. The
system. size of the software is underestimated.
Risk Analysis
During the risk analysis process, you have to consider each identified risk and make a
judgment about the probability and seriousness of that risk. To do this you have to rely
on your own judgment and experience of previous projects and the problems that arose
in them. It is not possible to make precise, numeric assessment of the probability and
seriousness of each risk. Rather, you should assign the risk to one of a number of bands:
1. The probability of the risk might be assessed as:
• Very Low (<10%)
• Low (10-25%)
• Moderate (25-50%),
• High (50-75%),Or
• Very High(> 75%),
Probability Effects
Sr. No. Type of Risk Risk Probability Effects
The risk planning process considers each of the key risks that have been
identified, and develops strategies to manage these risks. For each of the
risks, you have to think about the actions which will minimize the
interference to the project if the problem identified in the risk occurs. You
should have strategies in place to cope with the risk if it arises. Strategy
should be so effective that reduce the overall impact of a risk on the project
or product.
Sr. Risk Strategy document for senior
No.
1. Organizational financial a briefing is management Prepare showing how the project
problems making of a important contribution to the goals to the the
business very and presenting reasons why cuts project
budget would not be cost-effective.
3. Staff illness Reorganize team so that there is more overlap of work and
people therefore understand each other's jobs
Risk monitoring and control is an ongoing process for the life of the project.
The risks change as the project matures, new risks develop, or anticipated risks
disappear.
Sr.no Risk Type Potential Indicators
Resource Types
•Work resources − People and equipment to complete the tasks.
•Cost resources − Financial cost associated with a task. Travel expenses,
food expenses, etc.
•Material resources − Consumables used as project proceeds.
•For example, paint being used while painting a wall.
Sheduling
Project-task scheduling is an important project planning activity. It involves
deciding which tasks would be taken up when. In order to schedule the project
activities, a software project manager needs to do the following:
1. Identify all the tasks needed to complete the project.
2. Break down large tasks into small activities.
3. Determine the dependency among different activities.
4. Establish the most likely estimates for the time durations necessary to complete
the activities.
5. Allocate resources to activities.
6. Plan the starting and ending dates for various activities.
7. Determine the critical path. A critical path is the chain of activities that
determines the duration of the project.
Gantt chart
• Gantt charts are mainly used to allocate resources to activities.
• The resources allocated to activities include staff, hardware, and software.
• Gantt charts (named after its developer Henry Gantt) are useful for resource
planning.
• A Gantt chart is a special type of bar chart where each bar represents an activity.
The bars are drawn along a time line.
• The length of each bar is proportional to the duration of time planned for the
corresponding activity.
• Gantt charts are used in software project management are actually an enhanced
version of the standard Gantt charts.
• In the Gantt charts used for software project management, each bar consists of a
white part and a shaded part.
• The shaded part of the bar shows the length of time each task is estimated to
take. The white part shows the slack time, that is, the latest time by which a task
must be finished.
Gantt Chart Example
Advantages & Disadvantages of Gantt Chart
• The ability to grasp the overall status of a project and its tasks at once is the
key advantage in using a Gantt chart tool. Therefore, upper management or
the sponsors of the project can make informed decisions just by looking at the
Gantt chart tool.
• The software-based Gantt charts are able to show the task dependencies in a
project schedule. This helps to identify and maintain the critical path of a
project schedule.
• Gantt chart tools can be used as the single entity for managing small projects.
For small projects, no other documentation may be required; but for large
projects, the Gantt chart tool should be supported by other means of
documentation.
• For large projects, the information displayed in Gantt charts
may not be sufficient for decision making.
• Although Gantt charts accurately represent the cost, time and
scope aspects of a project, it does not elaborate on the project
size or size of the work elements. Therefore, the magnitude
of constraints and issues can be easily misunderstood.