ENGG3800 Team Project II - Final Report
ENGG3800 Team Project II - Final Report
ENGG3800 Team Project II - Final Report
Version: 17/10/2022
The report must be submitted via the Turnitin submission link on Blackboard. This report
is individual – all parts must be completed individually. Please be aware that there are
grade hurdles associated with this task; see the course profile for more details.
Report Sections
The final report should have the following sections. Start each section on a new page.
Title page: Identify your team number, your name and student number and the names of
your other team members.
Team Design Overview (1 page maximum): Detail the overall methodology of the team
and where you fit within the team. Identify which aspects of the project were undertaken
by which team members.
● What did you expect from the course and how was your experience different from
your expectations?
● Describe what you’ve learned from a technical/design point of view.
● Choose three competencies from Engineers Australia’s 16 stage one competencies
(including at least one from section 2 and at least one from section 3) and reflect on
how your experiences in the course have helped your development of that
competency. (Make sure you nominate each specific competency you are
addressing.)
● Discuss what you have learned about how to work in a group by documenting what
worked well within your group, what did not work well, and why.
● How might you organise teamwork differently to improve performance?
● If your group had conflicts or problems in working as a team, describe them and
describe how such problems were resolved, or could be avoided in the future.
2
● How useful was your team code of conduct/code of ethics. (e.g. Was your team code
used? Should it have been? Was anything missing? How could it have been
improved?)
● How do you think you could have learned better in this course with respect to your
own behaviour? What changes could you make to your own behaviour or learning
strategies to improve things?
● What changes would you suggest (both to the course and your approach to learning
overall)? Note that some students have a tendency to use this dot point as the
majority of their reflection - you should not do this, and instead refer to the
previous points above and make sure you are addressing them all in a reasonably
equitable fashion.
Further Information
You may include figures/diagrams as appropriate. Figures must add value to the text,
must be numbered and captioned, and must be explicitly referred to in the text. (Page
counts above include figures, except for the individual contribution section.)
This report must conform to engineering report standards, including referencing and be
written in clear and concise English. You are not required to produce a contents page or an
executive summary for this report.
The course reflection may be in first-person but other parts should be in third person.
However, you should avoid repeatedly referring to people or using pronouns, and instead
just state the contributions. Just initially state who you are describing the contributions
for (in third person, eg “Bob was responsible for the PCB” or “Alice was responsible for
the GUI software”), and then state the contributions or works, ie “The PCB was
soldered…”, “The GUI was installed…”, “It was decided that…”. You can also use “The
team decided that…”.
Page format must be A4, single line spacing, all margins a minimum of 1.5 cm, and
suitable font and size (e.g. Times New Roman, 12pt font).
3
Marking Criteria (15 marks total)
Pages exceeding the page counts specified will not be marked. Fractional marks can be awarded if
the standard of the work falls below that expected for the satisfactory standard or is between the
two standards below.
Team Design Team’s allocation of work Team’s methodology and allocation of work is
Overview between members is mostly clear and coherent, with no doubts as to the
(2 marks) clearly described and there are approach taken and the roles of all team
no or limited inconsistencies members. The described roles cover the
with the descriptions by other complete scope of the project and there is no
team members. inconsistency with the descriptions by other
team members.