Camp Izza

Development Process

• We met with our sponsor every Wednesday to present completed work and plan tasks for the upcoming week.

• We kept track of our work through a Trello Board.

• Since our group was working with a pre-existing system, we attempted to identify and resolve critical system bugs within the first few sprints.

Design Decisions

Our design decisions were based on the previous group's style guidelines and additional functionality outlined by our sponsor.

• Our initial focus was on resolving the bugs within the previous system.

• However, we recognize that it would be productive to spend our entire focus and energy on resolving these bugs.

• As such, we collaborated with our sponsor to identify additional pages to design including but not limited to:

1. Counselor and Camper Attendance

2. Counselor and Camper Information

3. Manage Campers

Implementation Decisions

Towards the end of the quarter, we made the difficult decision of transitioning to a new system.

• This stemmed from our unfamiliarity with the pre-existing system's frameworks along with difficulty resolving identified bugs.

• Fortunately, we were able to transfer over a lot of the front-end files to the new backend, so we did not waste all of our efforts done these two quarters.

Documentation Process

We started off this project by reading the Developer Handoff Resource Guide from the previous group. This contained information on:

1. The existing system's structure

2. Current Style Guidelines

3. Access to GitHub Repository and Figma

These are the steps we took to accommodate for our issues with the pre-existing system:

• We began developing new documentation for use by future groups to assist with implementation and design.

• For implementation documentation, our group has created comments on each file to indicate its purpose.

• We also created a UML Diagram and Entity Relationship Diagram for future groups to better understand the structure of the system we created.

Meanwhile, these are the steps that we took for design documentation:

• We included a Figma page dedicated to the current style guidelines.

• We separated our designs from the previous group's designs to showcase the evolution of the design over time.

• This documentation will make the style guidelines more accessible and will also clarify how it was used within previous designs.

Additionally, this is how we kept track of our progress and followed agile development:

• We wrote seven total sprint reports, each one covering progress over two weeks, which includes a burndown chart, backlog, review summary, retrospective summary, success criteria, and mockups.

• We compiled all of our work from the two quarters into a requirements and design document, which includes user personas, functional/non-functional requirements, high fidelity mockups, diagrams, deliverables plan, and revision history.

Evaluation

Our group continuously received feedback from our sponsor through correspondence on Discord and our weekly sponsor meetings.

Design Feedback

As a result, we received suggestions on how to make the overall navigation and user experience smoother for our potential users.

Development Testing & Feedback

• Our group provided a live link of the registration for our sponsor and his team to test and provide feedback.

• We also communicated with our sponsor through a document listing identified bugs and desired website style changes.

Final Product

The final product of our design work is a functioning website and registration system for parents to register their children in summer camp. Some key functionality that we would like to highlight is: