...
documentation
Technical Content
User Manuals
Design Decisions
Administration Content
Onboarding Procedures
knowledge base information
relevant information to our subteams
research processes
meeting minutes
all of our meeting minutes must go in confluence: https://uwarg-docs.atlassian.net/wiki/spaces/Meetings
timelining
in a limited capacity confluence can be used for timelines
would like to shift this to Asana over time
task delegation
in a limited capacity confluence can be used for task delegation
would like to shift this to Asana over time
...
If you have any question on WARG it’s recommended you start by searching Confluence to help you, if that doesn’t work be that squeaky wheel and ask for help!
Consequences of failing to handle data and documentation correctly
Not to roast other SDC teams but as of F23 WARG is up there for our documentation standards. This is a deliberate effort pushed to ensure the team can keep expanding and growing. As a student team the absolute max tenure any individual has on the team is four years and realistically the maximum we see is closer to two years because of FYDP and co-op (see Time Commitment ). This means that if we do not document we will lose knowledge and we will not progress forward. Team leads from other SDC teams have reported extreme difficulty in onboarding new members and integrating existing systems due to a lack of proper data handling and documentation. Please avoid these pitfalls 