Project Management

Requirement for the Project

The requirements refer to system input and output tools, data, documentations and systems needed before, during and after the project completion. The requirements will be divided into three categories namely: General, input and outpoint requirements.

The general requirements include:

The first requirement for the project is the budget. The budget for the project will about $30 million. The funds will be needed for the software development; payments will cover payment to the different suppliers of different inputs needed for the software development (Al-Rubaiei et al., 2018). The budget will cover needs such as human resources acquisition, organization structure reorganization and tests processes for the system.

The second requirement will be the testing requirements such as hardware to test the software compatibility with the various systems. The hardware will also include the data servers to test for needs such as the data backup. The backup requirements will need for hardware drivers and also cloud services.

Complementary software: the new system will work in conjunction with other with other softwares hence the organization will have to lias with other software developers to complete the final software development process. The complementary software will include security software, java scripts and operating systems.

The human resources: There are various human resources needed for this software. The human resources include the staff to run the system. The staff will include IT team, businesses analysts, softwares and system auditors. The human resources will also include suppliers who provide various software input (Al-Rubaiei et al., 2018). The corporate customers who will be part of the human resources since they will help during the prototype testing stages.

Input requirements include:

According to Gobov & Huchenko (2021), These requirements are ideal for system testing and approval. The inputs will include:

· The final requirement documentation for the project.

· System development processes and drafts

· Design, development and implementation plan.

· Quality and assurance checklist and requirements,

· Populated requirement tradability matrix

· Policy letters, regulations and legal mandates requirements.

· Feasibility study to show the system compatibility and benefits

Output Requirements include:

These are the outputs required from the system development process:

· Training and manual documents

· User requirements expressed in natural language and documentation.

· Design description layout and format.

· Compatible systems and softwares.

· System security and safety requirements

· Disasters and backup recovery plan.

· User interface requirements.

· System metrics, measures and diagnostic repots.

· System approval reports.

Roles and Responsibilities

Scope Definition

The system development project is ideal for the development of the organization’s new system to improve the customer services, process delivery, productivity, revenue and organization profitability.

The key project deliverables include:

· User training: The project should provide a clear documentation on how to use the system efficiently, diagnose for errors and how to fix them.

· User interface: The system should allow the computers and all the organization systems and hardware to work compatibly, efficiently without any glitches. It should work compatibly with all the computers to deliver the desired results.

· Data migration: the new system should have all the data in the old system transferred to the new storage system and have capacity to contain more data.

· Backup systems and development: This is a back up system to store the same organization to ensure the organization has some data to work on in case of any glitches and disruptions.

· System prototype: The first model of the system to be made to facilitate trials, testing and system improvement suggestions.

· Risk monitoring and control tools: These are the tools mostly softwares needed to protect the new system from issues such as cyber-attack, sabotage or fires.

· System design and layout framework: This is the outlook of how the system will look and operate after completion to ensure ease of diagnosis.

· Test results: The project should provide a complete documentation of the project results, anticipated performance and any test issues.

Project constraints: the project should cover various constraints encountered during the development of the new system. The constraints that may be covered include time, resources, system and process or development constrains.

Work Breakdown Structure

Initial WBS

Before the development of the actual system, this will be the WBS. This structure consists of processes that must be concluded before the initial system design and development begins. The WBS aims at gaining and discovering the system requirements, organization, customer and supplier needs which the system will play a significant role in correcting and resolving (Jainendrakumar, 2015). The WBS will be conducted by business analyst and organization employees. It will also be conducted by other organization stakeholders to discuss the need for a new system to deal with organization challenges.

System development WBS

After the development of the first WBS there will be a system development structure that will integrate the requirements, problems and specification into the new system. This WBS introduces the system development process, the necessary requirements at the different stages and the person in charge of the roles (Gobov & Huchenko, 2021). The system WBS will include analysis which involves analyzing the organization needs, the impacts on the organization and determining whether the system can resolve the unique needs.

The requirement specification stage will determine the resources, tools needed to complete the system development. It will also cover the auxiliary resources needed for the system operate efficiently and compatibility with all the subsystems (Gobov & Huchenko, 2021). It will determine the internal and external requirements necessary for the system development.

The next process is design which involves designing the system based on the identified organization needs, problems and requirements. It will also be ideal for indicating how the new system will fix the organization problems.

The implementation stage will involve the actual system development process. The implementation stage will also involve the various teams involved in the teams in the company. It will also involve the integration of the system with other systems such as security features, payment systems and many more (Nath & Momin, 2017). Finally, it will involve the determination of the needed hardware and running the new system alongside them. This stage will end with the creation of the system prototype.

The final two processes will involve testing the new systems and ensuring they compatible work with organization systems and they meet the required standards and solutions. The process completion will also include the development of system reports such as training manuals and other documentations.

Scope Verification

The project verification will be conducted in various ways. The verification process will be based on the project meeting certain requirements and approval by the necessary authorities. The first verification criterion is the meeting of all the organization needs, addressing all the organization challenges as identified by the requirement analysis (Moustafaev, 2014). The analysis will list out a solutions and needs checklist that the new system must meet.

The second verification criteria will be based on the system requirement standards. These requirements include the security standards, user standards and other standards. The system must have the necessary security features all implemented to protect the system. It must also meet the system features such as usability, compatibility, user friendliness and effectiveness. The system must meet all the hardware requirements and work with all of the hardware.

Finally, the last verification step will involve having the necessary system outputs. These outputs include the system manuals, diagnosis and error correction report. Other reports needed include the training manuals and many more. The last verification process will be conducted by the various personnel in charge of the system verification and approval (Moustafaev, 2014). This verification will be conducted by the sponsor, monitoring committee, program manager and system engineer.

Scope Control

This section deals with issues such as project and system changes, modifications and other needs. In case of any changes, the changes must be reexamined by the system development engineer who will approve if the change is worth or system modification is necessary. If the changes are suggested by the lower level employees in the development process, the supervisor must approve it then pass it to the project leader (Abdilahi et al., 2020). The project leader must work with the system and business analyst to determine the implications of the problem.

The changes will then be submitted to the project monitoring committee who will evaluate whether it is worth making the changes. They will then sign the changes and then pass it to the project sponsor who will have to sign on the project before any modifications.

Approval Acceptance

Approved by the:

System development engineer ………………………………………. Date………………………… Signature………………….

Project Sponsor……………………………………………………………… Date………………………… Signature…………………

Project Manager…………………………………………………………… Date………………………… Signature………………...

References

Abdilahi, S. M., Fakunle, F. F., & Fashina, A. A. (2020). Exploring the extent to which project scope management processes influence the implementation of telecommunication projects. PM World Journal, IX, 1-17.

Al-Rubaiei, Q. H. S., Nifa, F. A. A., & Musa, S. (2018, September). Project scope management through multiple perspectives: A critical review of concepts. In AIP Conference Proceedings (Vol. 2016, No. 1, p. 020025). AIP Publishing LLC.

Gobov, D., & Huchenko, I. (2021). Software Requirements Elicitation Techniques Selection Method for the Project Scope Management. In ITPM (pp. 1-10).

Jainendrakumar, T. D. (2015). Project Scope Management in PMBOK made easy. PM World Journal, 4(4), 1-10.

Moustafaev, J. (2014). Project scope management. CRC Press.

Nath, A., & Momin, M. M. (2017). Project scope management: A pivotal tool for project's success. International Journal of Management, IT and Engineering, 4(8), 279-288.