Use Case
Confluence is used by WARG for all of our:
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
What should be documented?
Of course everything that’s documentation should go into confluence but what needs to be documented? In short nothing needs to be documented until we have a problem or foresee an imminent problem if said documentation does not exist. More specifically nothing needs to be documented until:
We are unsure of a decision and would like scrutiny from others
We want to share and collaborate on our engineering process
We want people in the future to reference the material
When you arrive at a justification for any design decision please add into the confluence doc for future reference so that if anyone questions a design decision you have the answer ready to go
We don’t want to repeat ourselves over and over again saying the same information
Why did someone link a confluence doc to me?
Often times we send links in response to questions or when we see conversations. This is done because we want the people to read said document as we believe it either answers the question asked or contains relevant information that will assist in the conversation. Most of our confluence docs are extremely short, if someone links you one, please please please at least give it a skim to see if it helps you out!
If I have a question where should I start?
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 