2023-01-23 Competition Report Debrief
- Dhruv Upadhyay
Things that went well
It was formatted well
Work was initially started early
Operational Limits and Capabilities section was done well
Pictures and renders were very nice and effective
Things that could be improved
A lot of the Operational Limits section was a bit of nonsense
Aircraft requirements should be more tightly defined
Aircraft should be tested to those limits
GANTT Chart should be more high level and less detailed
Nice if the report was a little closer to the theme:
Unified branding related to WARG (color palette, unified headings, etc.)
Starting with Latex wasn’t ideal since it blocked off contribution from other team leads, and not see changes live
Start with Google Docs, transfer to LaTex later
Content was being written the DAY OF - not acceptable
Everything should be complete re content 2-3 weeks before deadline
Having a more effective conclusion would help close off the document better
Content being written should be accessible to the rest of the team
E.g. Google Docs should be accessible to the rest of the team
Key Takeaways
Identify operational requirements during system architecture stage
Create a more unified brand for WARG related reports
Consistent colour palette with headings, images, diagrams, etc. (have WARG logo in corner of images)
Use color scheme on CAD, etc. that is consistent with team brand
Create report templates for easy editing
Consider report requirements when designing the system architecture so we have clear answers to many of the questions being asked
Use Google Docs or some other form of shareable format that can be seen and edited live by team members, that is shared with all of the other members
Communicate the report’s source of truth clearly, rather than moving around platforms arbitrarily which causes further issues
Assign section owners to the report clearly with due dates early on in the report writing process
Â