Project 2: Requirements Gathering and Planning

Project/Presentation Groups

• Group 1 (Cinemark): Scott, Vincent C., Michael
• Group 2 (Texas Roadhouse): Jaret, Vincent E., Dylan
• Group 3 (Pittsburgh International Race Complex): Ryan, Chelsea
• Group 4 (Steelite): Ray, Noah, Aaron

Objectives

1. Identify the "Pain Points" from the Project Presentations. Rank them in descending priority order, from most adverse or increasing ROI most signicantly to least significant.
2. Propose the system(s) in concrete terms that need to be put in place to address these business problems. This can be one complex system that touches on multiple core activities, or several loosely-coupled systems that can address facets of the identified items of concern. Keep in mind that data collection/warehousing can also add value via process improvemnts from the insights gained using Data Mining/Business Analytics - e.g., Customer preferences and patterns can inform upselling opportunities or have predictive value (such as Meta's audience cloning).
3. For each of these systems, identify the core business activities - which business areas are impacted, whether they are directly or indirectly cascading into other areas - e.g., Sales impacts Inventory, Inventory impacts Supply Chain, lack of Inventory can negatively impact Customer Experience, etc. - be as specific as you can.
4. Identify the business's existing processes and systems that would need to be integrated with the new systems that you will put into place. Do any of these existing business processes need to change to accommodate the proposed solution?
5. Identify the components of proposed systems - e.g., hardware, software, Project staff (managers, developers, systems architects/administrators, data entry, QA, trainers, etc.), training, documentation, long-term support, etc.
6. Identify, prioritize, and itemize estimates of the types and quantities of resources (time, money etc.) that would be required to implement those components - e.g., labor costs, hardware costs if purchasing new hardware is warranted (also don't forget testing/QA if deploying mobile apps), software licensing fees (annualize these costs), any long-term internal staffing changes in the company (e.g., hiring systems administrators), training time for the client's existing staff to use the new systems. This will show the bottom line for the client budget. This should be expressed as a range: from completion of the minimum viable product, all the way up to the inclusion of optional features that would add value/revenue/ROI to the project. Assume standard 40-hour work weeks, where at least 20% of the time is spent for non-task activities, e.g., communication, reporting, team/client meetings, or similar accounting.

Submit this documentation as a PDF and construct slides from this information. On Monday Oct. 21st, we will have each team give a short slide presentation of no more than 10 minutes for the instructor and the rest of the class, who will pose as the propective clients, with a discussion and Q&A to follow each presentation. In Project 3, we will use the artifacts of this project to inform further analysis, as well as a timeline of dependent activities, project milestones, and construct a Gantt chart.