This Assignment Consists Of Two (2) Sections: A Business Req ✓ Solved

This assignment consists of two (2) sections: a business requirements

This assignment consists of two (2) sections: a business requirements document and a Gantt chart or project plan. You must submit both sections as separate files for the completion of this assignment. Label each file name according to the section of the assignment for which it is written. Additionally, you may create and/or assume all necessary assumptions needed for the completion of this assignment. Procuring quality business requirements is an important step toward the design of quality information systems.

Completion of a quality requirements document allows user needs and expectations to be captured so that infrastructure and information systems can be designed properly. Using the requirements document provided in the course shell, you are to speculate on the needs of the company. You must consider current and future requirements; however, assumptions should be realistic and carefully considered.

Section 1: Business Requirements Document

1. Write an eight to ten (8-10) page original business requirements document for the project plan using the template provided.

a. Describe the project including the following:

  • i. Describe the scope and analyze how to control the scope.
  • ii. Identify possible risks, constraints, and assumptions.
  • iii. Describe the integration with other systems and infrastructure.
  • iv. Define relevant terms that will be used throughout the project.

b. Use at least two (2) quality resources in this assignment.

Your assignment must follow these formatting requirements: This course requires the use of Strayer Writing Standards (SWS).

The format is different than other Strayer University courses. Please take a moment to review the SWS documentation for details. Include a cover page containing the title of the assignment, the student’s name, the professor’s name, the course title, and the date. The cover page and the reference page are not included in the required assignment page length.

Section 2: Revised Gantt Chart / Project Plan

Use Microsoft Project or an open source alternative, such as Open Project, to:

  • 2. Update the Gantt chart or project plan (summary and detail) template, from Project Deliverable 1: Project Plan Inception, with all the project tasks.

Paper For Above Instructions

The successful development of a business requirements document (BRD) is crucial for aligning the design of information systems with user expectations and organizational goals. This paper outlines a business requirements document for implementing an information system in a hypothetical organization, focusing on effectively capturing user needs, addressing risks, and ensuring alignment with current technologies. The insights here will assist in defining how to control project scope, identify risks, and establish a cohesive integration with existing systems.

Project Description

This project involves the implementation of an information system for XYZ Corporation, a mid-sized manufacturing company seeking to enhance operational efficiency through technology. The scope of the project includes evaluating existing processes, identifying user requirements, and integrating new software systems that facilitate data management and improve communication across departments.

The primary goals are to streamline operations, reduce errors, and provide real-time data insights. The project will follow a structured methodology that includes requirement gathering, system design, development, testing, and deployment phases. The anticipated project timeline is twelve months, culminating in a full-scale operational rollout.

Scope and Scope Control

The project scope encompasses the development and deployment of the new information system, including software selection, system customization, user training, and support. To control scope, the team will utilize a Change Control Board (CCB) to evaluate scope changes and their implications on the project timeline and budget. Additionally, routine stakeholder meetings will ensure alignment between project deliverables and business expectations.

Risks, Constraints, and Assumptions

Several potential risks could impact the project. These include:

  • Technological Risks: Integration incompatibilities with existing systems may arise, necessitating extra resources for customization.
  • Human Resource Risks: Employee resistance to change could delay user adoption; thus, effective change management strategies must be in place.
  • Financial Risks: Unforeseen expenses related to software acquisition or additional training requirements could lead to budget overruns.

Constraints for the project involve limited budget allocation and the need to minimize disruption of ongoing operations during system implementation.

Assumptions made for this project include a stable economic environment, timely decision-making by stakeholders, and the availability of required technologies within the proposed timeline.

Integration with Other Systems

Integration of the new information system with existing systems will require careful planning. Current systems include an ERP platform and customer relationship management (CRM). Ensuring these systems can communicate efficiently will enhance data flow and improve overall functionality.

Collaboration with IT specialists is crucial for assessing current infrastructure, identifying integration points, and creating an interoperability plan. Consideration of security protocols is paramount, particularly concerning data access and storage, which must comply with industry regulations.

Relevant Terms

Throughout the project, several important terms will be utilized, including:

  • Business Requirements Document (BRD): A formal agreement that outlines the necessary requirements for a project to be successful.
  • Change Control Board (CCB): A group responsible for evaluating and approving changes to the project scope.
  • Information System: A coordinated set of components that collect, process, store, and disseminate information.

Resources

Two quality resources used in this project are:

  • Schwalbe, K. (2015). Information Technology Project Management. Cengage Learning.
  • Wysocki, R. K. (2014). Effective Project Management: Traditional, Agile, Extreme. Cengage Learning.

Conclusion

In conclusion, the development of a robust business requirements document is paramount for the successful implementation of an information system. By clearly defining the project scope, identifying risks, and ensuring integration with existing technologies, XYZ Corporation can align its operational needs with technological advancements. The strategies outlined will facilitate effective project management and enhance the likelihood of achieving project objectives.

References

  • Schwalbe, K. (2015). Information Technology Project Management. Cengage Learning.
  • Wysocki, R. K. (2014). Effective Project Management: Traditional, Agile, Extreme. Cengage Learning.
  • Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Controlling. Wiley.
  • PMI (2017). A Guide to the Project Management Body of Knowledge (PMBOK Guide). Project Management Institute.
  • Meredith, J. R., & Mantel, S. J. (2017). Project Management: A Managerial Approach. Wiley.
  • Kloppenborg, T. J., & Opfer, W. A. (2002). The Project Management Process. In Project Management: A Managerial Approach. Wiley.
  • MindTools (2021). Gantt Chart: A How-to Guide. Mind Tools Limited.
  • Burke, R. (2013). Project Management: Planning and Control Techniques. Wiley.
  • Harvard Business Review (2020). The Right Way to Manage Project Risk. Harvard Business Publishing.
  • Open Project (2021). OpenProject - A Project Management Tool. OpenProject.org.