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 analysing 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.
Note: This is an online retail grocery web application project. I already did project charter and I will share the document.
Project Name: Online Retail Grocery Store website’s software development
Project Sponsor: Blake Andrews
Project Manager: Naga Srinivas Guntupalli
Date | Version | Description | Preparer |
01/23/2020 | 0.1 | Initial Draft | Naga |
01/25/2020 | 0.2 | All the sections filled with content information | Naga |
01/28/2020 | 0.3 | Project charter final review | Naga |
Table of Contents
3.1 Out-of-Scope:
Project Description and Justification:
The main reason to start project is to make sure that issues faced by the individuals who cannot travel far to the grocery stores physically and buy the products which they actually need. This project is software website development project which is built in order to bring the grocery items to the customer door so that customers need not travel to the grocery or individuals who don’t have car to travel where customer have to book the cab to reach the store physically.
The project is undertaken because after analysis customers faced issues in purchasing the products where there is necessity to show up physically at stores in order to purchase the products that they need. It would be very tough job for few to handle a greater number of products at time and if this project is successful the orders can be made online and customer need not struggle for carrying grocery or retail products.
The project is prestigious to the organisation where it is considering the issues of customers who are in need of grocery or retail products where the customer’s homes are far from the retail grocery store, individual who have transportation issues and individual who don’t have time or cannot give time to visit the grocery stores physically.
By considering all the issues, the organisation has got a chance to take an advantage of this opportunity through building a new software website application so that the customers can purchase the products through online ordering which are needed and the organisation can make profits once the project is successfully completed.
The organisation will provide employment opportunity for giving further technical assistance to the customers.
The business value where this project can bring to sponsors and stakeholder would be profits in terms of return on investment once the website application goes live or launched the customers as online users will dramatically increase a lot which good for organisation.
Stakeholders will be benefited by adding value in terms of delivery of products with no travel and also good value to the individuals in terms of employment. Stakeholders include customers, banks and e-commerce who can benefit from this project.
The organisation would hold responsible for site management where organisation contribution will be there for generating revenue. Banks can get benefit from the online purchases made through cash back offers and transactions made.
Project Objectives
Project Scope
Out-of-Scope:
Summary Milestone Schedule:
It is estimated that the project is going to complete in five phases of the project in total, which includes initiation, planning, execution, monitoring and closing.
Summary Milestone Schedule | January- March | April -June | July – September | ||||||
8th January | 2nd Feb | 3rd March | 6th April | 10th May | 5th June | 7th July | 8th August | 12th September | |
Project initiation | |||||||||
Finding the best e-commerce website builder | |||||||||
Determining the resources required for the project. | |||||||||
Determining how the resources will be acquired. | |||||||||
Project planning | |||||||||
Choosing the best plan | |||||||||
Get a domain for the store name | |||||||||
Project execution | |||||||||
Pick the e-commerce template | |||||||||
Customising the e-commerce template | |||||||||
Adding products | |||||||||
Setting up payment methods | |||||||||
Sorting out the shipping settings | |||||||||
Project monitoring | |||||||||
Using google analytics to measure metrics such as total visits and visit duration. | |||||||||
Project closure | |||||||||
Making the necessary adjustments based on the results of google analytics. | |||||||||
Launching the project. |
Assumptions, Constraints and Risks:
Assumptions:
Constraints:
Risks:
Risk Tolerance level
Category | High Tolerance | Medium Tolerance | Low Tolerance | Comments |
Schedule | X | The budget issues may cause delay for application going live. | ||
Budgeting issues | X | Budget may not sufficient when resource billing rate is high . | ||
Deployment | X | When deployment is not done correctly users may face errors and be unsatisfied | ||
Navigation | X | The navigation should be in correct way otherwise customer may raise and negative feedback on the application. |
Key Performance Indicators Measurement
KPI | Rating |
Project success | 1 |
Stakeholders Expectations | 2 |
Quality | 3 |
Navigation | 4 |
Average value of transactions | 5 |
Total number of users | 6 |
External Stakeholders
Internal Stakeholders
Name | Role | Power | Interest | Influence | Responsibility | Expectation |
Naga Srinivas | Project Manager | High | High | High | Responsible for reporting the updates on the project | Runs the projects successfully, schedules meeting and communicates effectively. |
Blake Andrews | Project Sponsor | High | High | High | Make sure the budget allotment is done correctly | Monitors the project continuously right from the start till end |
James Archer | Business Analyst | Medium | High | Medium | Makes sure the requirements are gathered correctly and identify the stakeholders through RACI matrix | The requirements are gathered should be correct way |
Michael Stones | Lead Developer | Medium | Low | Medium | Develops the entire application correctly makes decision on deployment in all the environments | Deployment is done correctly as per the FRD and BRD. |
Ravindra Kumar | Developer | Low | Medium | Medium | Develops the few features, makes bug fixes and reports to the project manager | Codes the application correctly |
Jessica Stevens | Quality Assurance Analyst | Low | Low | Medium | Makes sure the application is bug free | Does all types of testing and creates bugs wherever the issues are been found. |
Project Charter Approval
Signature Authority | |
Role | Member |
Project Manager | Naga Srinivas Guntupalli |
Project Sponsor | Blake Andrews |