Project Planning

This project is a single large student-managed team-based computer programming project to create a phone or tablet app.

Form a Team

It is up to you to create your team to work with. Teams should be 2-3 people (no more, no less). Team members must be from the same class. Once you have your team, tell your teacher who is working with who (this could be filling out a Google Form, or other method depending on your teacher).

Topic Brainstorming

It is the job of your team to create an app that completes one of the following:

• Helps solve a specific portion of a social justice issue, or, an oppression or marginalization issue (i.e. anti-Black racism, Islamophobia, classism, colonization, sexism, etc.), or
• A visual simulation of a natural phenomenon (i.e. physics, chemical, wind, water, sound, etc.), or
• A 2D video game that must include a menu, multiple levels, a high score system, and possibly other criteria (ask the teacher for more information).

Other criteria/notes

• All projects must be approved by the teacher before beginning.
• There must be a programming component to the project.
  • There is no set programming language for this portion of the course, so choose the language appropriate to the project.
• If you chose #1:
  • The scope of the project must be larger than simply bringing awareness to a topic (e.g. users should be able to take action)
• If you chose #2:
  • The scope of the project must be from a ground-up build-it-yourself style of simulation, and
  • Must not use any libraries to help you with the simulation portion.
• If you chose #3:
  • There might be other requirements per your teacher

Create a Plan

Once you have received approval to move forward, you are required to complete the following:

• Complete a Software Scope and Plan document. There is a template provided for you here. The link is to a Google Document that should offer you to copy it. If not, copy the information and create your own.
• Complete the Work Breakdown Structure (WBS). There is a template available for this here. Remember that the WBS has a very high-level understanding at the top (level 1) and breaks down tasks into smaller chunks as it gets lower (level 2, 3, 4, ...).
• Create a calendar or use another long-term organization tool to plan out a variety of work and when it will be completed. This is best done after completing the above documentation, as there will be dates you can use from there to inform the information you place in the calendar.

Important note: You are going to want to break up the work so that everyone has something distinct to work on. Each student is assessed individually on all the success criteria. If it cannot be easily identified on who did what, then no one will receive a mark for that portion of the project. Plan accordingly.

Due Dates and Submission Details

Each team will submit the following:

• One Software Scope and Plan Document, and
• One Work Breakdown Structure, and
• A link to (or screenshot of) your planning board/calendar/etc.

Overarching Learning Goal(s) and Success Criteria

The Overarching Learning Goal(s) for this include 📘 Project Management.

Success Criteria	Look Fors	Reevaluation Opportunity
📘 I can create a software project plan by producing a software scope document and determining tasks, quality standards, deliverables, and schedule.	To be co-created.	None.
📘 I can use an appropriate project management tool to manage project components (i.e. charts, calendar, etc.)	To be co-created.	None.
📘 I can contribute, as a team member, to the planning, development, production, and close out of a large software project.	To be co-created.	None.
📘 I can meet project goals and deadlines by managing individual time during a group project.	To be co-created.	None.