MAD-501 Project Requirements Summary

Phase 1: Project Pitch Deck

Phase 1: Project Pitch Deck
You need to pitch your simulated company to the client and why you’re best a for developing this application.
Phase 1 Requirements:
1. An inoffensive Company Name
2. An inoffensive Company Logo
3. A brief simulated history of your company
4. Simulated Past Successful Projects
5. In Power Point (pptx format)
6. Visually appealing slides with some kind of unique colour theme
7. Minimum of 10 slides
Check-in date: October 18th, 2021
MAD-501 – Version_1.0.0 Page 3
Phase 2: Functional Requirements Document
You will then need to take the user stories (see appendix A) and write a
Functional Requirements Document. This is a simple document that is nontechnical
and is written in the context of a User. It clearly explains the problem
which is to be solved and each of the user workflows.
Phase 2 Requirements:
1. Company Name in the footer
2. Company Logo in the footer
3. Page number in the footer
4. Document version number
5. Well-formatted, following the visual style of your Pitch Deck
6. All user stories in Appendix A covered
7. All additional workflows which come out of discovery while crafting this
document
8. Must be in PDF format
Phase 3: Bid for tender
Now you take all the information from the FRD and use it to fill out the MAD501 – Final Project Estimator spreadsheet. Remember that the client has a budget of only $50, 000 which isn’t a lot. You must balance the budget so you don’t lose money on this project or go over budget.
Phase 3 Requirements:
1. Fill in the Output Tab with all the correct information
2. Slippage Percentage must be >= 8%
3. QA Overhead must be >= 33%
4. Project Manager Overhead must be >= 23%
5. Employee Overhead must be >= 60%
6. All tasks outlined in the FRD must be in the INPUT tab
7. Must make a profit of >= $1 on the OVERVIEW tab
8. Must use all employees as equally as possible in the COSTING tab
9. Must have an external sell cost of <= $50, 000 on the OVERVIEW tab
10. Must use T-Shirt sizes for initial estimate duration in the INPUT tab
for each task
11. Estimates must be realistic and not all the smallest possible
a. Use an equal distribution of T-Shirt sizes (xs, sm, medium, lg, xlg)
12. Make sure to add a margin for responsive web app of at least >= 5%in the MARGINS tab
13. Submit the completed Excel file
Check-in date: November 1st, 2021
MAD-501 – Version_1.0.0 Page 5
Phase 4: Wireframes
Now that the budget for the project is set and approved by the client, we need to make rough wireframes for the application. The purpose of the wireframe isn’t to display colour schemes for the project or art assets, it’s to give the client a mock-up of what the overall look and feel of the website will be.
Phase 4 Requirements:
1. Wireframes must be in greyscale with no art assets
2. Simple layout elements
3. Clickable, you can progress through the app by clicking on the associated buttons
4. No animations
5. Always a way to return to home in the application with some element on page
6. Must output to a file type that I can use offline, no online only application
Check-in date: November 8th, 2021
MAD-501 – Version_1.0.0 Page 6
Phase 5: Sprint layout
We have our approved budget and wireframes it’s time to get to simulated work. We now need to plan out the 2-week sprint iterations on how we are getting this project done. These are the rough first draft iterations and don’t account for any project issues. Remember as a PM you’ve been doing “discovPhase 1: Project Pitch Deck You need to pitch your simulated company to the client and why you’re best afor developing this application. Phase 1 Requirements: 1. An inoffensive Company Name 2. An inoffensive Company Logo 3. A brief simulated history of your company 4. Simulated Past Successful Projects 5. In Power Point (pptx format) 6. Visually appealing slides with some kind of unique colour theme 7. Minimum of 10 slides Check-in date: October 18th, 2021 MAD-501 – Version_1.0.0 Page 3 Phase 2: Functional Requirements Document You will then need to take the user stories (see appendix A) and write a Functional Requirements Document. This is a simple document that is nontechnical and is written in the context of a User. It clearly explains the problem which is to be solved and each of the user workflows. Phase 2 Requirements: 1. Company Name in the footer 2. Company Logo in the footer 3. Page number in the footer 4. Document version number 5. Well-formatted, following the visual style of your Pitch Deck 6. All user stories in Appendix A covered 7. All additional workflows which come out of discovery while crafting this document 8. Must be in PDF format Check-in date: October 25th, 2021 MAD-501 – Version_1.0.0 Page 4 Phase 3: Bid for tender Now you take all the information from the FRD and use it to fill out the MAD501 – Final Project Estimator spreadsheet. Remember that the client has a budget of only $50, 000 which isn’t a lot. You must balance the budget so you don’t lose money on this project or go over budget. Phase 3 Requirements: 1. Fill in the Output Tab with all the correct information 2. Slippage Percentage must be >= 8% 3. QA Overhead must be >= 33% 4. Project Manager Overhead must be >= 23% 5. Employee Overhead must be >= 60% 6. All tasks outlined in the FRD must be in the INPUT tab 7. Must make a profit of >= $1 on the OVERVIEW tab 8. Must use all employees as equally as possible in the COSTING tab 9. Must have an external sell cost of <= $50, 000 on the OVERVIEW tab 10. Must use T-Shirt sizes for initial estimate duration in the INPUT tab for each task 11. Estimates must be realistic and not all the smallest possible a. Use an equal distribution of T-Shirt sizes (xs, sm, medium, lg, xlg) 12. Make sure to add a margin for responsive web app of at least >= 5% in the MARGINS tab 13. Submit the completed Excel file Check-in date: November 1st, 2021 MAD-501 – Version_1.0.0 Page 5 Phase 4: Wireframes Now that the budget for the project is set and approved by the client, we need to make rough wireframes for the application. The purpose of the wireframe isn’t to display colour schemes for the project or art assets, it’s to give the client a mock-up of what the overall look and feel of the website will be. Phase 4 Requirements: 1. Wireframes must be in greyscale with no art assets

2. Simple layout elements

3. Clickable, you can progress through the app by clicking on the associated buttons

4. No animations

5. Always a way to return to home in the application with some element on page

6. Must output to a file type that I can use offline, no online only application Check-in date: November 8th, 2021 MAD-501 – Version_1.0.0 Page 6 Phase 5: Sprint layout We have our approved budget and wireframes it’s time to get to simulated work. We now need to plan out the 2-week sprint iterations on how we are getting this project done. These are the rough first draft iterations and don’t account for any project issues. Remember as a PM you’ve been doing “discovery” for an estimated 2 weeks so make sure to have that in your start date calculations. Phase 5 Requirements:

Each sprint should be a separate Trello board with the title MAD501 – YOUR NAME – Sprint X with your name being your name and X being the sprint number starting at 1 2. Trello board should have the following 5 columns: a. To Do b. In Progressing c. Testing / QA
d. Review e. Done 3. Each sprint should have all the tasks for that week assigned to the correct developer along with the duration in the title
Each developer should have as much non-blocked working hours as possible up to a maximum of 40 hours per week
Developers cannot exceed 40 hours per week 6. Once each sprint is planned out you need to do the following: a. Record in a word document the start date and end date for that sprint b. A screenshot of the trello board c. An export of the trello board to JSON with the filename being the trello board name as written above Check-in date: November 15th, 2021 MAD-501 – Version_1.0.0 Page 7 Phase 6: Simulated Backlog Grooming / Sprint Planning Now that we have our sprints planned out let’s simulate how they will play out. This will involve simulating the actual durations and seeing how it effects all tasks in the sprint and thereafter. Phase 6 requirements: 1. For each task you need to randomly generate a number between 1-6 (use a 6-sided dice or https://g.co/kgs/qmCzjD ) 2. Based on the random number you nery” for an estimated 2 weeks so make sure to have that in your start
date calculations.
Phase 5 Requirements:
1. Each sprint should be a separate Trello board with the title MAD501 –
YOUR NAME – Sprint X with your name being your name and X being the
sprint number starting at 1
2. Trello board should have the following 5 columns:
a. To Do
b. In Progressing
c. Testing / QA
d. Review
e. Done
3. Each sprint should have all the tasks for that week assigned to the correct
developer along with the duration in the title
4. Each developer should have as much non-blocked working hours as
possible up to a maximum of 40 hours per week
5. Developers cannot exceed 40 hours per week
6. Once each sprint is planned out you need to do the following:
a. Record in a word document the start date and end date for that
sprint
b. A screenshot of the trello board
c. An export of the trello board to JSON with the filename being the trello board name as written above