Math-Team-Scorekeeper App

Wrapping up our work with the Mckinley High School Math Team for the MathTeamScorekeeper app.  It was a blast working on a real life project with a local non-profit.  I learned a lot about software engineering and ruby on rails.  The web app is not fully complete according to the prototypes and features we worked out, but it's off to a nice start.  You may find links to the slides, app, git repo, and pivotal tracker at the end of this post.

Hope you enjoy our final presentation:

Presentation slides

rails app

git repo

pivotal tracker

LoFi Prototypes for Math Team Scorekeeper

Here are some Low Fidelity interface mockups that I worked out with my customers.

Homepage:
https://docs.google.com/drawings/d/1tg6LYJyUYLIssnsLfOdwutLYA4h6TzdILLpQzw6zZvg/edit?usp=sharing

School registration page:
https://docs.google.com/drawings/d/1Wb0rYBcflQnE3PWAfje9NLM4olF5RKpNMnLVyuLROf0/edit?usp=sharing

Score input page:
https://docs.google.com/drawings/d/1wHCn0-n6j7c_oWMY8cLRzrFBgtiTmOgG78sBD-MQOrM/edit?usp=sharing

Scoreboard:
https://docs.google.com/drawings/d/18niFj8ffIK7uX5HO6Tsx6CO9leSyZOw7_1f7SQLC6JU/edit?usp=sharing

Create event page:
https://docs.google.com/drawings/d/1kKvRze91lcwSR2WjGl-3rbw2ZbaVwCCpf5zaUFDghRI/edit?usp=sharing

Interview Plan: Mckinley Math Team

I'm pretty excited to be able to implement this idea and help out my Alma mater.  The math team coach with whom I would be meeting with was previously my calculus teacher.  I have visited him a few times recently so this interview will be somewhat casual, although we will be there to get work done and get this project started.  Here is a draft of our plan:

Setting

Objective of Interview

-Determine the main pet peeves (mainly data that needs to be calculated and recorded manually) in the math team and figure out whether we can develop some technology to help them

Date, Time, and Location

-To be determined

User Participants (names and titles/positions)

-Jon Furukawa, Math team head coach and instructor at Mckinley High School

Project Team Participants

-Kevin Goo

Interview/Discussion

1. During math meets how is the score keeping currently done?
2. What is the actual algorithm for computing someone's score?
3. Can we provide a system to make it easier?
4. Is there valuable information that should be saved?
5. What other tasks need to be done, perhaps not during the meet but at practices?
6. Can we provide functionalities to help train new students?

Follow-Up

Important decisions or answers to questions

- Refer to notes taken

Open items not resolved with assignments for solution

- Refer to notes taken

Date and time of next meeting or follow-up session

-To be determined

Reaching out: Mckinley Math Team

In preparation for contacting the math team coach about my project idea this is a quick draft email that I will be sending them:

Greetings Mckinley Math Team Coach,

We are with HPU's Software Engineering and Systems Analysis class and we would like to help you out by creating a system to manage scores and statistics for the math team.  This project will be a good opportunity for both of us as we are able to gain experience while helping out a local non-profit.

We have a strong background in programming and would like to work with you to develop a system to suit your needs.  We would love to provide something that will be useful to you and the students in the Mckinley math team.  If you are interested, we would like to meet with you and discuss further possibilities of this project.

Please let us know if we can help, we look forward to working with you.

Best regards,
Kevin Goo

Stakeholders: Math Team Scorekeeper

This idea in my previous post about a score keeping application for the local high school math team is one I would be excited to work on.  There are a few contacts I have that could be the stakeholders for this project.

Coaches (Internal/Operational/Executive):  The math team coaches, some of which were my high school math teachers, would be the main internal stakeholders.  They would be using this application and the information it provides.

Students (External/Operational): The students will be benefiting from this application externally.  They will not input the scores, but still be able to see the results and know what areas to study for the next meet.

Stakeholders:Housing Helper

In one of my previous posts, I talked about an idea of creating a helpful tool for those looking for a place to stay.  Now I will go over some potential stakeholders for this project.

Customers (External/Operational): The main users of this application would be the people wanting to sell or buy a house or apartment.  Mainly the people of Hawaii, unless this project gets larger and branches out to the mainland.

Realtors (Internal/Executive/Operational): For the internal stakeholders I do not have any sure contacts setup.  The internal stakeholders would definitely be realtors or a company involved with housing.  There is someone in one of my classes that I found out is a realtor so he could be a potential stakeholder.

Stakeholders: Programming Challenges Assistant

Following up on my previous post about a programming challenges assistant website.  It's now time to talk about the stakeholders for this project.

Professor (Internal/Executive/Operational):  Dr. Curt Powley, being the head coach of the programming team and professor teaching the programming challenges class, would definitely be the main internal, executive stakeholder for this project.  He would probably interact with the system internally and sort of use the information given by the system at an executive level.

HPU Students (External/Operational): The HPU students would be the main consumers for this application.  Their input about desired features would be the most important in the design of this system.  Senior students could also be internal operational stakeholders if they are allowed to interact with the backend and add new features.