Running head: Quality and Risk Management Plan Name
Quality and Risk Management Plan 1 Quality and Risk Management Plan
1. Abstract/Executive summary
**Please provide ABSTRACT/EXECUTIVE SUMMARY** 2 Quality and Risk Management Plan
2. Work Breakdown Structure 3 Quality and Risk Management Plan 4 3. Activity/Network Diagram
a. Critical Path
This is an activity and network diagram for a software project. The activity and network diagram is a series of step by step of how the software diagram will start progress until it is
finished. The Network starts with gathering the project requirements. The project requirements
are all the necessary resources that will be needed to start the software project run it until it is
complete in the end. After gathering the requirements, a database for the software will be
designed. The database is a part of the system where the data to be collected by the system will
be stored. As the database is being designed a graphical user interface designing will progress. A
graphical user interface is the front design of the software; it is a part of the system where a user
can login into the system, add data, edit information and carry out other system functions.
A programmer will be in charge of designing of programming both the database and the
graphical user interface at the same time a writer manual of the system will be designed; this
manual is a guide on how to use the system. Once designing the database and the graphical user
interface the programmer will code the graphical user interface and the database. Coding
involves making the logical system into an executable system which can carry out the normal
functions. After the system has been coded the programmer will test whether the designed
functions are working as they are expected if they are working the programmer will take the
system to the IT department who will also test the system and assess whether it is working as
expected and whether it has all the expected functions. Once it has been confirmed the system
has all the expected features the software design process will be complete, and the project will be
**Could you please fie the below process** Quality and Risk Management Plan Day 5 5 Day 11 Design Database Day 0 Day 5 Day 11 Project Requirements Day
25 Design GUI Day
35 Code Database Day
40 Code GUI Day
44 Integrate and Test Day
44 Finish Project Day
30 Write User Manual a.
The software project will be created in 46 days. The software development will start with the
gathering of requirements, after the graphical user interface and the database will be designed.
The programmer will take time developing both after the programmer will code both the
graphical user interface and the database. The coding part is the most critical part of software
development project; after the software has been coded it is followed by testing whether what
has been coded is working as it is supposed ensuring it has all the functions that are required.
Once the programmer, the IT department has provided that there expected features are in the
system and working the project properly is described as being over. While the project is being
marked as complete.
b. Lead/lag Day
46 Quality and Risk Management Plan 6 Lead is software project software that is used to determine when a project will be
started at an early date and how long it will take to complete it. On the other hand, the lag
of a software project is used to determine how slow the project may run. Lag shows if a
project is started late and when it might be completed[Pau15]. For this project the Lead
used is indicating the software project may take 46 days to while the lag used to
determine the slow take on the project shows that it may take the up to 60 days to
The early start for a project is an old time when a project is supposed to start. The
project can be started on day 0. The first day the project requirements are gathered which
will be followed by creating both a database and a graphical user interface. Once the
database and graphical user interface have been designed, the database and the graphical
user interface will be coded later tested and if they are running as expected the software is
tested and the project is finished. The Early finish of this project is expected to be 46
days. If there will be a late start for the project, it will be started late with ten days if the
gathering of the software requirements takes a long time. There are other processes of the
project such like software coding which might take a lot of time if a programmer is not
found. Coding of the software is supposed to take ten days for both the graphical user
interface and the database, but it may take 20 days to complete the software project. The
late finish of the project will be an additional 20 days totaling up to 66 days.
4. Project Schedule Quality and Risk Management Plan 7 Quality and Risk Management Plan 5. Project Budget
**CAN YOU FIX THE BUDGET** 8 Quality and Risk Management Plan 9 6. Change Management Plan
This is a software project which means that it the organization will be using new software
in work processes and organization management. The software will change all the organization
working processes. The previous working processes of the organization include producing work
in hard copy printed papers, file the work done and later submitting the work to the department
head who would go through the work and submit it to the top management. The working culture
of the organization is a step by step process of which the working ladder is to be followed
strictly. Now that the software is being developed all work will now be computerized. Employees
will work by login in the system working there and submitting the work output in the system.
Once they upload the work in the system, the department heads will be able to check on the work
The software will make the working process easier because once the employee is through with
work, he/she can send it to the department managers for assessment. If the top management is Quality and Risk Management Plan 10 not present in the office the top management of the company can be able to access the work
without the department heads being there. The top management can also be able to check the
work being done in progress, a change in the work culture is good for the organization because
the work flow is easy and it will save time as some of the irrelevant work procedures will be
avoided. A software also avoids a lot of paper work which takes the organization a lot of time
since the employees have to work produce the work in reports so that they can be able to forward
the work to the top management[Hel11].
**ADD CHANGE FORMS** LIKE THE ONES IN THE ATTACHED FILES** 7. Communication Management Plan
**CAN YOU PLEASE PROVIDE A COMMUNICATIONS MANAGEMENT PLAN AND
A COMMUNICATIONS FLOW CHART LIKE IN THE ATTACHED FILES**
8. Risk Management Plan
**CAN YOU PLEASE PROVIDE A RISK MANAGEMENT PLAN LIKE IN THE
ATTACHED FILES TO INCLUDE numbering convention, risk identification, impact,
probability, and response in the plan. **
Every project must have a risk management plan. Project managers most of the time avoids it
thinking that the project will run smooth automatically which is not the case. The first step of
using a risk management plan in a project is identifying how to use the risk management plan. In Quality and Risk Management Plan 11 a project plan, the manager must know every step of the project has a risk or risks. After
identifying the risks of every project step, it is followed by working out the probability of the
risks occurring. In the event of calculating the probability of the risk occurring the project
manager must also identify what is the impact of the risk occurring. If the risk is to occur what
are contingency plans to be taken in all risks. After the project manager has identified all of
them, he has to reduce the probability of the risk occurring. After coming up with a risk
reduction plan, the project manager has to reduce the risk exposure to the project.
Numbering convention in the risk management is listing the risks according to how they will
occur. The step will be according to step by step in according to the project schedule. The fast
step is gathering the project requirements. There are risks that the project time might not identify
all the risk the project manager will have to carefully analyze all the risks and check if there is a
missing risk. Once the project requirements are gathered the next step is designing the graphical
user interface and the database, the risks in this step are that the programmer might miss some
making some design structures of the software the project team must, therefore, help the
programmer all the steps in the designing step to make sure all software structures have been
designed. After the software designs are complete the programmer is supposed to code the
logical software steps into an executable structure there is a chance that some of the lines of code
might be difficult to code the programmer must seek help to ensure all the software processes are
coded, and no single step is skipped.
Risk identification Quality and Risk Management Plan 12 This process in risk management involves identifying all the risks that are likely to occur in all
the project steps. The project team must identify all the project risks. In the first step involves
identifying the project requirements, in the first step there is a risk that all the software
requirements might not be gathered therefore the team must analyze all the possible
requirements. After identifying the requirements the database and graphical user interface must
be designed. There is possible risk that the programmer might forget some designing some
processes of the database of the interface, the project team must help the programmer. When
coding the programmer will seek help if there are lines of code which might be hard to come up
with. After the system has been coded testing of the software is next the programmer will test the
software first followed by the project team to check all the steps according to the requirements
are there. During project finishing the project team might forget to develop a user guide for the
system. The project team must ensure the user guide for the system is developed.
The project team will be in charge of identifying the project risk. The team will also carry out
the impact of either of the risks occurring. The risk of not gathering all the software requirements
is that the organization might not get standard software for the system to use that will efficiently
serve the organization. When designing the software structure, the project team will ensure all
the software requirements are converted into a structure. After designing the software structure,
the programmer must ensure all the software events are coded into a system if they are not coded
it means the system will not be complete.
Probability Quality and Risk Management Plan 13 In the risk management plan, all the risks are likely to occur. The project team must, therefore,
assess all the risks as they are likely to occur. All the risks are likely to occur there is a chance all
the risks in all the project stages might occur.
Response in the plan
All the risks that have been analyzed must occur the project team must have plans to all the
risks that will be taken if the risk occurs. From gathering the requirements, all the requirements
must be gathered to ensure the software is fully designed, and no step is missed. When designing
the software structure, the project team must ensure all the structures are designed. Once the
software design is complete, the project team must ensure the programmer codes all the software
events. If all the events are coded the software must be tested to ensure all the software events
9. Quality Management Plan
**PLEASE ADD MORE TO THE SECTION**
A quality management plan is to ensure the entire project plans runs smoothly. The quality
management plan is a plan to assess the whole project as it is taking place to ensure the project is
not only finished but it is delivered in quality.
10. Procurement Management Plan
**CAN YOU ADD MORE TO THIS SECTION** Quality and Risk Management Plan 14 A procurement management plan is a plan to ensure the company acquires the affordable
services. There are many requirements when the company will be acquiring the system it will
have to hire and purchase some requirements.
Source selection criteria
The selection criteria will be for the quality services with the most affordable prices. Other
selection criteria will be the reputation of the company offering the service. The company
offering the service must have a good reputation in the service industry.
Make or buy decisions
The top management of the company will be responsible for making decisions on which
services to be selected from the various companies.
11. Stakeholder Management Plan
a. Stakeholder register
b. Stakeholder engagement assessment matrix Quality and Risk Management Plan 12. References
**PLEASE ADD MORE REFERENCES** REFERENCES
Cooke, H., & Tate, K. (2011). Porject management . New York: McGraw-Hill.
Maylor, H. (2010). Project management. New York: Financial Times Prentice Hall.
Tinnirello, P. C. (2015 ). Project managment . London : Amsterdam publishers . 15