Unit Four
Capstone

Wed March 23

 1 | Getting Started

    • Trello

      • Set up your trello board, share the link, and invite members

        1. Board must be public

      • Review expectations

        1. Lists (at least: Long Term, To Do, In Progress, Completed)

        2. Labels (at least: Code, Design, Media, Bugs)

        3. Members Assigned Cards

    • Contracts

      • Share your contract with me and begin work

      • Transfer ownership

    • Design Documents (Optional)

      • Write down as much as your team finds to be useful

      • You may share it with me, but it isn't graded

Trello + Contract Due Next Class

    • By the start of next class, your Trello and Contract are completed.

    • Earn up to 10 points based on Mr. M's evaluation of how complete, organized, and realistic these documents are.

Phase One

Fri March 25

 2 | Preliminary Conferences

    • Meet with Mr. M to review contract expectations

    • Make revisions and lock contract documents

End of Quarter 3

    • All missing + late work must be submitted by end of next class on Tuesday March 29th

Tues March 29

 3 | Code

    • Work Time

    • Last day to run extra Astraeus Trials

Thur March 31

 4 | Code

    • Work Time


Mon April 4

 5 | Code

    • Work Time

Wed April 6

6 | Prepare for Checkpoint

    • Work with your team to build submission package

      • Try to submit by 8:30. If you do so, Mr. M can confirm submission

      • Rubric

        1. 10 points for contract goals

        2. 10 points for process (+4 on time, +2 trello, +1 jar, +1 code, +1 description, +1 screenshots)

      • To make a jar, review instructions in Coder's Handbook - Jarsplice

      • Test your runnable jar before submitting it!

    • Begin next phase of coding!

Wed April 6 @ 11:59 pm

Submit Program for Checkpoint #1

    • Send a Schoology message to Mr. M including the following:

      • A paragraph description of your project. This will be posted on the website.

      • At least two screenshots of your game in its current state.

      • A zip file to Schoology containing program code and a Runnable Jar file.

SPRING BREAK

Phase Two

Fri April 8

 7 | Conferences

    • Review Last Submission and Revise Contract Goals

Wed April 20

 8 | Code

    • Work Time

Fri April 22

 9 | Code

    • Work Time

Tues April 26

 10 | Code

Thur April 28

 11 | Code

    • Work Time

Mon May 2

 12 | Code

    • Work Time

Professional Development Day (May 3)

Tues May 3 @ 11:59 pm

Submit Program for Checkpoint #2

    • Send a Schoology message to Mr. M with a zip file attached containing the following elements:

      1. Your program as a runnable jar file.

      2. Your program code

      3. At least two screenshots of your game

    • Process Grade (10 points) and Goals (10 points)

      1. On Time - 3 Points

      2. Jar - 2 Points

      3. Code - 2 points

      4. Trello - 2 Points

      5. Screenshots - 1 Point

Phase Three

Thur May 5

 13 | Conferences

    • Review Last Submission and Revise Contract Goals

Mon May 9

 14 | Code

    • Work Time

Wed May 11

 15 | Code

    • Work Time

Fri May 13

 16 | Code

Sun May 15 @ 11:59 pm

Submit Program for Checkpoint #3 (Release)

    • Send a Schoology message to Mr. M with an attached zip file including your program code, a runnable jar file, and at least two screenshots of your game.

Tues May 17

 17 | Launch Day!

    • Play Each Others Games

    • Farewell to Seniors

SENIORS LAST DAY

Phase Four

Thur May 19

 19 | Junior Expansions

    • Conferences

MEMORIAL DAY

GRADUATION DAY (Tues May 31)