Chapter 3

Fundamentals of Project Management

Contents of Chapter
• Overview of project Management
• Project management life cycle-IEEE Life Cycle
• Project Management Process
• Role of Project Manager
• Quality Metrics
• Risk Management Process (Case Study Based)
Risk Identification
Risk Analysis
Risk Mitigation
RMMM
1.1 Overview of project Management
• Project management is the practice of applying knowledge, skills, tools, and
techniques to complete a project according to specific requirements.
• It comes down to identifying the problem, creating a plan to solve the problem,
and then executing on that plan until the problem has been solved.
• Software project management is an art of planning and leading software
projects. It is a sub-discipline of project management in which software
projects are planned, implemented, monitored and controlled.
• The Project Management Institute defines a “project” as “a temporary work
accepted to create a unique product, service or result.”
• The word “temporary” means projects must have a defined beginning and end.
This means every project must include a timeline, scope and resources.
• The purpose of a project must be “to create a unique product, service, or
result.” This means a project will be started in order to accomplish a specific
goal that is typically different from day-to-day business operation.
Every project must have the following components:-
• Goal: What are you trying to achieve?
• Timeline: When are you trying to achieve it by?
• Budget: How much will it cost to achieve?
• Stakeholders: Who are the major players who have an interest in this project?
• Project manager: Who is going to make sure everything that needs to be
completed gets completed?
1.2 Project management life cycle-IEEE Life Cycle
The 5 basic phases in the project management process are:-

1.Project Initiation
2.Project Planning
3.Project Execution
4.Project Monitoring and Controlling
5.Project Closing
The initiation phase
• The project initiation phase is the first stage of turning an abstract idea into a
meaningful goal.
• The goal of this phase is to define the project, develop a business case for it,
and get it approved. During this time, the project manager may do any of the
following:
• Perform a feasibility study –
• Create a project charter-short document
• Identify key stakeholders- people involves in Project
• Select project management tools-
• By the end of this phase, the project manager should have a high-level
understanding of the project's purpose, goals, requirements, and risks.
The planning phase
• The planning phase is critical to creating a project roadmap the entire team
can follow. This is where all of the details and goals are outlines in order to
meet the requirements.
During this phase, project managers will typically:
• Create a project plan
• Develop a resource plan
• Define goals and performance measures
• Communicate roles and responsibilities to team members
• Build out workflows
• Expected risks and create possibility plans
The execution phase
• The project execution stage is where team does the actual work. As a project manager,
your job is to establish efficient workflows and carefully monitor the progress of your
team.
• Another responsibility of the project manager during this phase is to consistently
maintain effective collaboration between project stakeholders. This ensures that
everyone stays on the same page and the project runs smoothly without any issues.
• phase (execution) typically begins with a project kickoff meeting where the project manager
outlines the project objectives to all. It involves the following-
• Establish goals and deliverables
• Identify your team members and assign tasks and roles
• Define which metrics will be used to measure project success
• Identify and prepare for potential barriers comes in project
• Establish schedules for team communication
• Choose your preferred project management methodology
• Ensure your team has access and knowledge of the relevant tools
• Schedule the meeting
The controlling and monitoring phase
• This phase happens in cycle with the execution phase. As the project moves forward,
the project manager must make sure all are faultlessly headed in the right direction.
• If adjustments to the project plan need to be made due to unexpected situations or a
change in direction, they may happen here.
• During the controlling and monitoring phase, project managers may have to do any of
the following:
• Manage resources
• Monitor project performance
• Risk management
• Perform status meetings and reports
• Update project schedule
• Modify project plans
At the end of this phase, all the agreed project deliverables should be completed and
accepted by the customer.
The Project closure
• The closing phase is a critical step in the project management life cycle. It
signals the official end of the project and provides a period for reflection,
wrap-up, of Project.
Project managers can:
• Take inventory of all deliverables
• Tie up any loose ends
• Hand the project off to the client or the team that will be managing the
project’s day-to-day operations
• Perform a post-mortem to discuss and document any learnings from the
project
• Organize all project documents in a centralized location
• Communicate the success of the project to stakeholders and executives
• Celebrate project completion and acknowledge team members
1.3 Project Management Process
1.4 Role skills and Responsibilities of Project Manager
Who is Project Manager? :- Project managers is a person who play the lead
role in planning, executing, monitoring, controlling and closing projects.
They are accountable for the entire project scope, project team, resources,
and the success or failure of the project. The role also requires a number
of non-technical skills like leadership, motivation, communication,
organization, prioritization, problem-solving, and adaptability.
Role and Responsibilities:-
1. Planning the activities
2. Organizing a project team to perform work
3. Delegating the teams
4. Controlling time management
5. Managing deliverables
6. Monitor progress
7. Establish Regular Meetings
8. Communicate a vision with the team
9. Managing reports and necessary documentation
1.5 Quality Metrics:- Software Quality Metrics
• Software quality metrics are a subset of software metrics that focus on the
quality aspects of the project.
• Quality metrics are a key component of an effective quality management plan and are the
measurements used in ensuring customers receive acceptable products or deliverables.
7 metrics to ensure software quality:-
• The following principles or factors are things that can be measured.
• Number of lines, files, etc. :- How do your file sizes affect your software? What is the function of the code lines? Are
your numbers maintainable?
• Field bugs.:- What are the problems in the already running software? How many bugs did you find in production? Is
your software reliable? How many times did it fail over a set period of time?
• Code churn.(a metric that measures how often code is changed during the development cycle) :- Why is one part
of the code churning more than others? Why is it error-prone? Is anything in the completion rate standing out? Is the
code usable once it has churned?
• Static analysis findings. :- What is consistent about the software? How long does it take to fix code? Is the software
secure in its current standing vs. what has changed?
• Bug arrival rate. :- How are you finding bugs? When did a bug show up? Why did you think the software was ready?
What are the rates at which bugs are coming in? How many software releases happened during a period?
• Performance.:- Does the software code last during updates? Is it performing as it should? Why isn’t it performing in
load, stress, or response testing? Do users enjoy it?
• Test failures.:- Automated and manually, what tests are failing? Was a test working and now it is failing? What is your
failure balance? How can testability be improved with technologies?
1.6 Risk Management Process
Includes-
1.6.1 Risk Identification
1.6.2 Risk Analysis
1.6.3 Risk Mitigation
1.6.4 RMMM:-
(Risk Mitigation
Monitoring and Management)
What is Risk?
Very simply, a risk is a potential problem. It’s an activity or event that may
compromise the success of a software development project. Risk is the
possibility of suffering loss, and total risk exposure to a specific project
will account for both the probability and the size of the potential loss.
Step 1: Risk identification:-
• To start this process, list out any and all events that would have a negative
impact on your Project. Be sure to ask leaders in other departments to
identify risks, too.

Step 2: Risk assessment:-

• Now that you have a list of potential or existing threats and risks, it’s time
to assess the event happening and the level of impact. Doing this risk
analysis helps determine the priority levels of each risk.

Step 3: Risk mitigation:-

• Risk mitigation is where you will create and begin to implement the plan
for the best way to reduce the impact of each risk. You may not be able to
come up with a mitigation plan for each and every risk, but it’s important
to try to identify what changes in your current processes can be adjusted
to reduce risk.
Step 4: Risk monitoring
• Now that you have identified, assessed, and made a mitigation plan, you
need to monitor for both the effectiveness of your plan and the
occurrence of risk events. Monitoring the status of risks, monitoring the
effectiveness of mitigation plans implemented, and consulting with key
stakeholders are all parts of the risk monitoring step. Risk monitoring
should happen throughout the risk management process.
Step 5: Risk reporting:-
• You need to document, analyze, and share the progress of your risk
management plan. Reporting on risks serves two key purposes: It helps
you analyze and evaluate your risk management plan and helps keep
stakeholders engaged in mitigating risks by sharing the progress made.
RMMM Plan :- Risk Mitigation, Monitoring, and
Management
• A risk management technique is usually seen in the software Project plan. This can be divided
into Risk Mitigation, Monitoring, and Management Plan (RMMM). In this plan, all works are
done as part of risk analysis. As part of the overall project plan project manager generally
uses this RMMM plan.
• In some software teams, risk is documented with the help of a Risk Information Sheet (RIS).
This RIS is controlled by using a database system for easier management of information i.e
creation, priority ordering, searching, and other analysis. After documentation of RMMM and
start of a project, risk mitigation and monitoring steps will start.
Risk Mitigation (to minimize degree of any loss or harm): It is an activity used to avoid
problems (Risk Avoidance). Steps for mitigating the risks as follows.:-
1. Finding out the risk. 2. Removing causes that are the reason for risk creation.
3. Controlling the corresponding documents from time to time. 4. Conducting timely reviews
to speed up the work.
Risk Monitoring : It is an activity used for project tracking. It has the following
primary objectives as follows.
1. To check if predicted risks occur or not. 2. To ensure proper application of risk
aversion steps defined for risk.
3. To collect data for future risk analysis. 3. To allocate what problems are caused
by which risks throughout the project.
Risk Management and planning :- It assumes that the mitigation activity failed,
and the risk is a reality. This task is done by Project manager when risk becomes
reality and causes severe problems. If the project manager effectively uses project
mitigation to remove risks successfully then it is easier to manage the risks. The
main objective of the risk management plan is the risk register. This risk register
describes and focuses on the predicted threats to a software project.
Case Study On- Takeaway Subscription and Food Ordering
System.
Risk Identification and Mitigation
Case Study Assignment for you……
Write a risk management plan for online shopping system.
Consider any one system?
Any Questions…….?
Thank You……!