Algorithm project "Code"

<Sample> CS-411 Project-1 Zeta – Standup Status Report <Sample>

Standup Status: CS-411 Project-1 Zeta <Sample from Zeta project> Team: ABX = Alice Allison, Bob Robertson, Eve Evans Alice: 1. Completed: #4 (Initialize Zeta Array), #12-Verified 2. Plan to complete: #7 (Move Glider Object) 3. Obstacles: None Bob: 1. Completed: None, still working #6 (Check for Fixed Collision) 2. Plan to complete: #6 (Check for Fixed Collision) 3. Obstacles: Trouble sub-tasking #6 <Sub-tasking so as to have a demoable result takes practice.> Eve: 1. Completed: #12 (Paint Background), #13 (Draw Walls) 2. Plan to complete: #14 (Draw Dragon Lair) 3. Obstacles: Waiting on format for Fixed Object Structure

Progress Board <Sample from Cella project> <NB, Dotted task numbers to show dependencies can get in the way of Rule #0(Fast).> <NB, Not all tasks have been "fleshed out", yet.>

Ready: #2 Setup Initial Layout (nested on #2.*, dep on #1) #2.2 Setup Project Info #3 Run Cella #3.1 Generate next row (nested on #3.*)

Working: #4 Draw XY cell color (Wk by Alice, 11/3) <Where's Bob and Eve? Are they working on something?> Done: #11 Get XY cell next state (Wk by Bob, 11/2-11/2) <”Wk” = “Working/Worked”> #12 Get color from state (was #6, Wk by Alice, 10/30-10/30) <Always write a task title before you start working on something. Change the title later, if needed.>

Verified: #1 Setup Infrastructure Demo (QA by Alice, Wk by Bob 10/30-10/31) #2.1 Setup Cella Grid (QA by Eve, Wk by Alice 10/30-11/1)

Issues: <Tech Debt, Fix-later Defects, Issues that may need to be Resolved> o- Do we need an FSM object to “hold” the Cella rules? o- Grid gen code is very ugly

OBE: <To connect with earlier status-reported task names. Renaming is flexible.> #6 Get XY cell next color ==> replaced by #11 (...next state) and #12 (...next color) #2 Setup Cell Board ==> renamed Setup Initial Layout

C. Siska February 4, 2019 Page 1 of 1