<commit_before>\section{Planning \& Group-Work Approach}

\subsection{Development of a Plan}

During the first couple of weeks of the project the group formed into a team,
and after receiving a detailed brief from the customer via video-call, quickly
went about setting up ground rules and how the project should be executed. It
was decided that weekly meetings with the project supervisor would be
appropriate, with one to two more group meetings during each week, as required.
It was decided that meetings should be informal in general, with loose notes
taken if required, to try and cut down on any unnecessary overhead.

%TODO: link to appendix using latex foo
The group established an understanding of the task, and duly created a project
brief in response to the first customer meeting. This contained a rough overview
of the group's understanding of the task, and can be found attached in appendix
A. The Gantt chart in the project brief is an elaboration on a project lifecycle
shown in the diagram shown below, chosen to fit in with the two customer
presentations over the course of the project so that a presentable work package
could be shown to the customer at each milestone. This approach also gives some
room for agile methods in the underlying development approach (discussed in
more detail later in the section). Further discussion of the time management
methods used by the group, with a more detailed evaluation of the Gantt charts
produced over the course of the project can be found in the evaluation section
of this report.

AWESOME L1 PLAN DIAGRAM.

Once the group had established a naive breakdown of the tasks involved with the
project, a skills audit was held to discuss which team members were best
qualified for the various roles required by the project. The table below shows
a summary of the audit, including the roles derived during the audit.

AWESOME SKILLS AUDIT TABLE

%maybe more stuff about streams of work?
After some background research had been performed, the group decided to split
the development tasks into discrete components allowing members of the group to
work in the areas of most experience, researching and developing independently
with progress and code produced periodically reviewed by other members of the
group.

\subsection{Group-work Approach}<commit_msg>Added table for skills audit<commit_after>\section{Planning \& Group-Work Approach}

\subsection{Development of a Plan}

During the first couple of weeks of the project the group formed into a team,
and after receiving a detailed brief from the customer via video-call, quickly
went about setting up ground rules and how the project should be executed. It
was decided that weekly meetings with the project supervisor would be
appropriate, with one to two more group meetings during each week, as required.
It was decided that meetings should be informal in general, with loose notes
taken if required, to try and cut down on any unnecessary overhead.

%TODO: link to appendix using latex foo
The group established an understanding of the task, and duly created a project
brief in response to the first customer meeting. This contained a rough overview
of the group's understanding of the task, and can be found attached in appendix
A. The Gantt chart in the project brief is an elaboration on a project lifecycle
shown in the diagram shown below, chosen to fit in with the two customer
presentations over the course of the project so that a presentable work package
could be shown to the customer at each milestone. This approach also gives some
room for agile methods in the underlying development approach (discussed in
more detail later in the section). Further discussion of the time management
methods used by the group, with a more detailed evaluation of the Gantt charts
produced over the course of the project can be found in the evaluation section
of this report.

AWESOME L1 PLAN DIAGRAM.

Once the group had established a naive breakdown of the tasks involved with the
project, a skills audit was held to discuss which team members were best
qualified for the various roles required by the project. The table below shows
a summary of the audit, including the roles derived during the audit.

\begin{center}
%\begin{table}
\begin{tabularx}{\linewidth}{|XXX|}
\hline
Group Member & Skill & Level of Expertise (1-5) \\ \hline
<NAME> & Python & bees \\ 
& Python Frameworks & bees \\ 
& Web Frameworks & bees \\ 
& Reading Documentation & bees \\ 
<NAME> & Python & bees \\ 
& AI & bees \\ 
<NAME> & Python & bees \\ 
& Project Management & bees \\ 
& Systems Integration & bees \\ 
& C & bees \\ 
<NAME> & AI & bees \\ 
& Python & bees \\
\hline
\end{tabularx}
%\end{table}
\end{center}

%maybe more stuff about streams of work?
After some background research had been performed, the group decided to split
the development tasks into discrete components allowing members of the group to
work in the areas of most experience, researching and developing independently
with progress and code produced periodically reviewed by other members of the
group.

\subsection{Group-work Approach}
{'fraction_non_alphanumeric': 0.037813479623824454, 'fraction_numerical': 0.0007836990595611285, 'mean_word_length': 4.471596998928189, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1854981', 'n_tokens_mistral': 1228, 'n_tokens_neox': 1160, 'n_words': 790}