Weekly Report 31 4/29/19 - 5/5/19
Upon reaching the beta stage of the Final Product’s development, it was clear to me that while there was enough time to get everything into the game which was needed, there were also tiny details which I thought to include after the fact but could not in light of what “beta” means. This demonstrates that the schedule change for the alpha portion was a much needed thing, but also that working under the guidelines of the schedule labels of “alpha” and “beta” help keep the schedule outside the realm of continuously creeping things in.
Instead, the project will come creeping to a close this week. When beta ends, mentor visits end, and the project will be turned in. Overall, the experience for the project has been very enlightening and important in ways which will be described more in the Setup and Summary document. In the coming days, the plan will be to complete the last few lingering tasks necessary to call the whole project complete and fully reflect on its effects. For this there have been months of git commit logs and documentation on the burndown chart to help this overview come into place.
In the meantime, other important things have kept the schedule busy. For example, over the weekend I assisted Masaraat Asif, a peer, with her Final Product, which was helpful for both of us because on her end, it helped her figure out how to advance, and on my end, it demonstrated an important connection building investment which for the entire year has been extended in the opposite direction by other professionals. Therefore, as AP exams begin this week, it will not be planned for that to stop progress in any huge ways - it will take a sustained effort to pull through the week in a way that allows the complete and final shift of attention from the Product to the Presentation Night.
LEVEL CLEAR.