(When we figure out a system for the Notion, this page will be reorganized to a better location…)
During the FINCH mission, the UTAT-SS Notion was organized by Mission Phases as Epics, with Stories and Chapters documenting the team’s progress in each Phase (mostly Phase C). However, while the next mission is starting in Phase A, the team is repurposing legacy hardware/FINCH projects which are in later design phases. The team also aims to design in a reusable way, with early design concepts being applicable to future missions as well as the current one.
In addition, there are many databases on Notion (Builds, System Architecture, Test Plans, etc.) that vary in use between subsystems.
The team is aiming to optimize each of these databases and set up the project management/documentation framework in a way that is sustainable and productive for all mission phases and design efforts, for the current mission and future ones.
Chapters document the work assigned to Space Systems members, and they are composed of a series of tasks - when the tasks are completed, the chapter is considered completed. The Chapter template on Notion includes space for writing down notes relevant to the tasks being completed.
Stories document larger projects composed of multiple chapters - when each chapter is completed and the system-level artifacts are completed, the story is considered completed.
System-Level Artifacts
<aside>
Epics are composed of multiple stories.
Mission Phases are a subset of Epics in line with the NASA systems engineering framework for space missions. A mission phase is considered complete when the Exit/Completion Criteria for that mission have been met, relevant design reviews have been conducted, and the team as a whole has decided to advance to the next phase.
See Builds
While Chapters and Stories track the tasks needed to complete a project during the design process [project management], Builds are written after project completion and describe the project itself, as well as lessons learned from the design process [documentation]. When a Story is completed, the relevant Build pertaining to that story is updated with the results of the work conducted in the Story.