The Requirements for Verizon FIOS Fiber Optic Cable Management Plan

Key outputs in this phase are the Projects Requirements definition, the capability and capacity assessment, project delivery strategy and the Project Management plan. The role of the construction/ project manager in this phase is, once project authorized, it is the project manager’s responsibility to implement the project. In terms of the Project Requirements Definition the, the project manager refines and details the project authorization and details what the project is required to accomplish in terms of the products/services the project will deliver and the scope of work that needs to be done. The project manager must provide project team members, corporate sponsors, and other stakeholders with a common understanding of what the project is all about, and is the authoritative reference document that defines the project.

Business requirements document (BRD) that provides additional details regarding the expectations (such as user, system, and functional) that must be met for achieving project goals

The purpose of this section is to identify the documentation that will be used for ensuring quality.

They will need to provide objectives for issues that surround the project and an outline of how to ultimately reach the goal of building this system for an operational organization that is attributed by many stages such as:

Full implementation should be completed in six months. The boundaries are the human resource system. Crossing over into design or inclusion of other departments such as accounting or sales would be out of scope. The business requirements are that the system is to be a single system instead of the multiple tools they are using now. The other business requirement is more vague, only stating that they would like to take advantage of more sophisticated, state-of-the-art technology. Project feasibility is determining if the technical, economical, and operational factors of the project can be accomplished under the schedule given. Technical looks at what hardware and software are available compared to what the requirements of the project are. Economic compares the cost of the overall project to what is budgeted and what can be justified by potential financial returns. Operational factors examine if the system will receive support from the people that use it and make it work (“System Development Life Cycle”, 1998).

| (TCO B) You are a project manager for a new Hardware Software Project. You just received the project charter and established your scope statement. Within the scope statement you defined some of the key components to meet the overall project objective. Establishing requirements will be critical to define and get approved. The hardware will be new for your company, so you will need to ensure the vendor is selected and the hardware is appropriately installed into your environment. The supporting software will need to be designed and coded. It will also need to be installed and tested on the system. To ensure the users know how to use the new software, training will be needed for managers and the associates. You have assembled your team of experts, and they are anxious to get started.

The FSA system project manager should acknowledge the requirements, take part in discussions related to the requirements, evaluate and agree requirements. Frequently, assess the status of the requirements and solve the problems if raised in the requirements. Always make sure if there is a need for changing the requirements. Lead the meetings regularly by informing the team about meeting times prior to start. "Create and maintain all requirements

| Manage the project and contribute to the project requirements. Authorize any changes to the project. Oversee all project work as it relates to the project plan, budget, and schedule. Manage communications between all parties involved.

Ensure that you note any requirements that are out of scope to achieve absolute clarity about what is and is not covered by this project, and to avoid the potential for problems later on.

Requirement Traceability: Provide inputs to User stories, proposing the enhancements, review user stories written by business analysts and discuss with Business users to ensure all requirements are captured and provide

Note: This documentation must outline the revisions made to the previous deliverables required in Section 1: Written Project Plan.

This will help me and the team to understand how the system works. The documents will serve as the reference point on the basic requirements. For cohesiveness, I will have the team to discuss my findings during meetings (Trotter & Uhlman, 2011).

According to Glass, resources are acceptable if 15-30 of the project effort was spent on the requirements definition. In regards to correctly obtaining valid sources of knowledge without saturating requirements, it was found that involving customers, consulting all resources and involving highly skilled people was the most successful approach. Furthermore, processes that involved the concentration of prioritization, traceability and validation of requirements was also recommended.

Project Manager is responsible for performance measurement which includes finding variances between planned and actual work, cost and schedule. The project manager assigns the tasks to the team members and they follow the required course of action. The project manager provides the status reports to all the vital stakeholders in order to provide visibility. The Stakeholders review the metrics and variance and initiate necessary steps for the variances determined in order to complete the project within budget and time.

This report will consist of the recommended sections a project plan should possess. These sections include a framework, necessary