1. Eugene Marathon 5 Guys

2. What was planned to this point Main milestones ◦ Write first pass of documentation ◦ Create WebPages ◦ Get server running and create database for information queries ◦ Link between WebPages and server

3. Group Coordination 2-3 meetings a week ◦ Discuss current progress ◦ Go over what needs to be done ◦ Assign tasks for next meeting Kept meetings and milestones short and reasonable Communication through Facebook, email, phone, and in class Itinerary was more of a guideline of things needed to get done

4. Project Planning Effectiveness Planning and Idea generation occurred mostly during meetings Planning while together allowed us to go over pros and cons of milestones Posting schedule and notes allowed for efficient activity synchronization

5. Schedule Delays Unspecific requirements/information from client at first Overambitious documentation goals

6. Success of Risk Management Common risks like time constraints and client’s approval addressed. Management of such risks has been successful, providing better vision of how to proceed Kept procedure pitfalls in collective sight and methods for moving forwards

7. Risk Identification Several common risks successfully identified Defining the terms of such risks gave better insight towards the situation the risk occurs in Defining the terms of such risks gave better understanding of how to mitigate such issues

8. Risk Mitigation Defining mitigation gave better foresight to how project should proceed Ex: Mitigation for time constraint risks gave rise to use of iterative development model Ex: Mitigation for un-testable components inspired a build order so testing can keep pace with development

9. Three main parts: - Website theme and design (HTML, CSS, Photoshop) - Volunteers database (MySQL, PHP) - Hosting Server (Web, Database) Assigned roles: Khalil: User Interface Aaron: Programmer Even though Aaron is the main programmer, Khalil has some experience with web and database programming. Initially: Website: Khalil Database: Aaron Software Decomposition

10. -Aaron was working on the database design. -Khalil started designing the website. -Khalil implemented the database design using MySQL, and he was modifying the design as needed. -Aaron and Khalil are working interchangeably but not dependently. Distributed Work

11. Results The components work at integration time: -Correctly -On time Why? -Interfaces well defined for the developers. - Practically, one person is developing all the distributed components.

12. Walkthrough Display Jobs http://ix.cs.uoregon.edu/~kishehab/display_jobs.php Create Jobs (Admin Side) http://ix.cs.uoregon.edu/~kishehab/jobs.html Register Volunteers http://ix.cs.uoregon.edu/~kishehab/ Display Registered Volunteers http://ix.cs.uoregon.edu/~kishehab/display.php Admin Workspace http://ix.cs.uoregon.edu/~kishehab/admin.html http://ix.cs.uoregon.edu/~kishehab/display_jobs.php http://ix.cs.uoregon.edu/~kishehab/jobs.html http://ix.cs.uoregon.edu/~kishehab/ http://ix.cs.uoregon.edu/~kishehab/display.php http://ix.cs.uoregon.edu/~kishehab/admin.html

13. What do we want to change Moving to a weekly milestone ◦ Instead of meeting to meeting assignments Delegation of document subsections As we move away from documentation and more into development we need to divide work into individual sized components