Technical Management Process Report

The technical management process report focuses on how we can manage everything. It is a
step-by-step procedure/guide which helps the project to be as efficient as possible. This
process report consists of the eight processes, each one having details related to the relevant
process. In this report, KEP project is discussed as well as all the processes of this project are
defined step-by-step according to the technical management process steps.

• Project Planning Process:

The project planning process of the KEP project is to create the whole software with the
front end and back end within three months with all the available resources. The project
proposal of the KEP project has the brief idea of the project, some domain specific
knowledge and details about the technology on which this project will be created with the
front end and back end specific description of the software. The KEP project plan also
covers the organizations best practices and procedures to be followed along with the
project development and the testing of the project. The rules and regulations play most
important part for completing the project on time while maintaining the quality of the
work.
Once the project proposal of the KEP project is prepared and the rules and regulations are
identified with respect to the organization, then the work break down structure of the KEP
project is created based on all the modules listed. The modules for the KEP project are the
requirements gathering, designing the project, development, and coding of the project,
testing and then the production stage of the project. These modules are listed in the work
breakdown structure and the timelines of the KEP project are defined along with the
resources which will be working with each other on that module. The input to this project
planning process is the life cycle model, source documents, strategy documents and the
project directions. The output for the project planning process are the systems engineering
management plan and the work break down structure with the timelines and resources
plan. The main purpose of the project planning process is very important part of the
technical project management process as it helps the team to be motivated and provides
them guidance on what to do next for the KEP project.

• Project Assessment & Control Process:

The purpose of the project assessment and control process step is to monitor how the
project is doing with respect to the project plan and timelines of the work break down
structure, which was developed in the project planning process step. This step checks
whether the schedule which is agreed in the above planning phase is going in the right
direction. This step also considers that the resources which are estimated for completing
the project, according to the timeline, are sufficient. These resources include the developers
and the testers, costs, materials, and the equipment etc. This step also recognizes the team
performance throughout the project with respect to the work that is assigned to them. If
the team performance does not meet the expectations, it is recorded for future planning
and new goals are assigned to the team, following the timelines of the project. The project
assessment and control process step also emphasize on the risk management of the KEP
project with respect to the interface management and change control of the project. It also
describes the feasibility of the project with respect to the timelines, developers and the
testers, costs, materials, and the equipment etc.
For the KEP project, the project assessment and control process step followed by the
scheduling assessment and the resource usage, was analyzed with respect to the timelines,
developers and the testers, costs, materials, and the equipment etc. Furthermore, the
performance of the KEP project was checked with different criteria defined in the proposal
stage of the project. The risk identification was also done based on the FMEA created
previously. The fault tree was developed to identify the major risks which are associated
with the KEP project. The KEP project costs is estimated to be $8,000 and around 41 people
would be needed to complete the project on time.

• Decision Management Process:

The Decision Management Process analyzes and determines the correct decisions and steps
to be taken for the project. For example, if the output of the module is not up to the desired
mark, then some of the requirements are changed to obtain the required output. The
performance of the project is also determined by the various stakeholders willing to
complete their work thoroughly and timely with respect to the project timeline. This step
also emphasizes on which tools to use for the risk management of the project to minimize
the risk as much as possible.
For the KEP project, the Decision Management Process step is followed by taking the
correct decisions with respect to getting the desired output. The performance of the KEP
project is highly dependent on various stakeholders’ performance; for example, following
the schedule of the project etc. The risk analyzing tools are created for minimizing the risk
of the project, which consist of the FMEA and the fault tree. The KEP project should be
ready for the testing after 2 months or the project timeline will be affected.
• Risk Management Process:
The Risk Management Process works on assessment, identification, and correction of the
risks in the project. All the risks are assigned with values and priority, which is called the
Risk Priority Number (RPN). These risks are identified with the priority associated to them.
The correction steps are also given to mitigate the effects of the error from the project. This
concept is tested early during the life cycle of the project. The test results can reveal
strengths, weaknesses, opportunities, and the threats to the project.
The main risk which is associated with the KEP project is the performance of the algorithm
of the kidney matching pair. For the KEP project FMEA was created with the RPN to mitigate
the risk as much as possible.

• Configuration Management Process:

The Configuration Management Process works on how the different configurations; for
example, different versions of the project and changes of the project, will be managed
throughout the life cycle of the project. Each configuration has all the change requests; for
example, how and when someone is changing the code and/or the testing procedures etc.
The Configuration Management Process for the KEP project also follows the change
management tools. These tools include the GIT tool and SVN tool for the changes which are
done by the stakeholders on all modules. All the request for changes and variances is
managed during this step.

• Information Management Process:

The Information Management Process works on how the information is passed and given to
the stakeholders and the collaborators of the project. This stage focus on how the
confidential information is processed within the team of the project. This process also
validates that the information provided is correct and measured.
The information related to the KEP project will be passed via proper documentation, to the
appropriate stakeholders only during the weekly meetings. These documents would be
password protected to ensure security of the information, and thus promote and enable
sharing the information only with the relevant team members and stakeholders.

• Measurement Process:
The Information Measurement Process monitors the project activities throughout the
project life cycle. This step considers the measurement history and measurement reports to
 monitor the project. This step also measures the performance of the system. After
completing the performance evaluation, the problem is identified correctly in early stages
of the life cycle. It also emphasizes on the value of the project so that the customer needs
are measured correctly.
The measurement of the performance and security of the KEP project will be assessed each
week on how the system is working in terms of performance and security. For the KEP, the
effectiveness of the project and its modules with respect to the customer requirements is
identified after every phase of the life cycle.

• Quality Assurance Process:

The Quality Assurance Process often builds from the measurement processes throughout
the life cycle of the project. This step adds the quality management to the performance of
the system. This is like the FMEA, but it also works on the failure modes of the system with
respect to the wastage of the resources and the loss of the functionality of the system with
respect to the performance criteria. This tool is like the fault trees, but this step focuses
mainly on the end nodes of the trees.
The quality of the KEP project will be measured using the test cases of each module by
identifying any loopholes in the system. Once the faults are identified, then the corrective
actions are listed, and the priority is given to each fault based on the risk priority number.
The quality assurance of the KEP focuses on the development and production stage, and its
active steps.

The design and development of the KEP project is implementing the rules and regulations of
the technical project management. These steps of the technical project management report
help the project to be on time according to the timeline. It also helps the project to be
developed according to the performance matrices defined, while not compromising the quality
of the development and design of the system.