What are the actions (reflected in the WBS) that will be taken to ensure risk is managed and quality expectations are met?
*All required Material will be uploaded in file section with Project charter all the information. *Please read all instructions carefully along with project charter.Part A. Create the Requirements Traceability Matrix for your selected project:The requirements traceability matrix is an extremely important tool for the project. Requirements define customer expectations and the traceability matrix allows the team to follow each requirement through the Project Mgmt. Life Cycle (PMLC). The team elicits requirements from the customer and then moves the requirement through design, development, testing and implementation. This tool helps the team to audit the project as well during the PMLC, and take a litmus test, “Are we delivering what the customer has requested?”, thereby avoiding costly rework and unwanted change requests. Additionally, the traceability matrix assists the team in analyzing the impact of changes to requirements during the project.You want to provide the appropriate level of detail while maintaining a reasonable number of requirements since you will base your planning and scheduling on these requirements. While there is no minimum or maximum number of requirements, the expectation is that most students will have somewhere between 3-7 high level requirements which will then be used as the basis for the Work Breakdown Structure (WBS). At a minimum, you should identify several high level requirements, functions, and features. You can approach requirements in one of two ways: 1.Using a Simple Sentence format that outlines the high-level parent requirements and then breaks these down into multiple user requirements, which then flow into system requirements. 2.Creating User Stories. In this format, you will have high-level requirements known as Epics and in each Epic you will have multiple User Stories that follow the formatted language:
