The document summarizes a recipe database project created by Jeremy, Chris, and Sam. The project involves crawling websites to store thousands of recipes in a database and displaying them through a GUI interface that also checks if ingredients are in stock at Harmon's stores. The project had clear objectives, roles and responsibilities, and followed an agile Scrum development model over 10 weeks. Risks were assessed and mitigation plans put in place to address issues that could arise during the project.

1. Recipe Database By Jeremy, Chris, and Sam

2. Our Project Is a web app that has stored thousands of recipes through web crawling and displays them in a GUI and allowing the user to click to see if Harmon’s has those items in stock.

3. Objectives Back end crawls web on a regular basis GUI is clean and appropriate for users Database for store stock is updated daily On time

4. Have we achieved success? Crisp clean web app the users want to access Matches visual expectations from Harmon’s Easy to use Does it properly display recipes and shows if the ingredients are in stock?

5. Roles & Responsibilities Project Manager Developers with appropriate skill sets In company testers Public Testers/Actual Users

6. Communications Weekly meetings Daily planning with project manager

7. Work Approach Overview Will take approx 10 weeks starting 8/10/2010 Development model is a Scrum model.

8. Work Approach Phase 1 - Program Architecture Data Sources – Nutritional Facts, Recipes System & Hardware – Kiosks, Servers Software – Crawlers (Nutritional Facts, Recipe)

9. Work Approach Phase 2 - Web Crawling Recipe, Nutritional Facts Phase 3 – Web UI (Web and Service) Web Fronted, Crawler settings Phase 4 - Raid Sessions Testing – Functional, User, Performance Phase 5 - Implementation

10. Risk Assessment Risk Mitigation Plan Other projects taking SME Availability Signed acceptance from other competing managers giving this project top priority. Compatibility Issues with databases Write interface for each database, and cache the data. Changes to project scope Obtain acceptance from stakeholders on change management, and then adhere to the change procedure.

11. Schedule 10 week approach Deliverables daily

12. Change Management Changes will need to follow Change Procedure Project guidelines and expectations will be clear

13. Cost Summary

14. Acceptance Project manager goes through right steps to get project signed off Timeline of no signature or message project is complete

15. Conclusion Well managed 5 weeks Recipe database for cheap Harmon’s advertising