Skip to content
Snippets Groups Projects
Commit 349a40f9 authored by Mikhail Andrenkov's avatar Mikhail Andrenkov
Browse files

Added Gantt Chart Hyperlink

parent 9ef3aba2
No related branches found
No related tags found
No related merge requests found
No preview for this file type
......@@ -111,25 +111,7 @@ Google's C++ Style Guide calls for inline comments describing classes, functions
\label{schedule_label}
\indent
Over the course of a one-hour meeting, the Rogue++ team decided on an overarching timeline for the development of the project. The timeline consists of several components, tasks, and deadlines that occasionally overlap. This timeline exists as a way of benchmarking the project's completeness; a guideline, not a rulebook. It will be wise to refer back to this schedule at least once a week (most likely during the weekly meetings), update the project status accordingly, and assess any complications that could arise. The schedule will be created in the form of a Gantt chart (soon to be made available). Listed below are the deadlines that were established in the previous team meeting:
\bigskip
\begin{table}[h!]
\centering
\caption{\textbf{Project Deadlines}}
\bigskip
\begin{tabular}{lll}
Requirements Document & Sept 26 & Oct 7\\
Milestone 1 (Rev -1) & Oct 10 & Oct 14 (Break)\\
Technology Exploration & Oct 17 & Oct 21\\
Test Plan + Boost Integration & Oct 24 & Oct 28\\
Design Document & Oct 31 & Nov 11\\
Revision 0 (Milestone 2) & Oct 21 & Nov 19\\
Revision 1 Fixes (Milestone 3) & Nov 18 & Nov 30\\
Final Design Document & Nov 26 & Dec 7
\end{tabular}
\end{table}
The project schedule can be found at \href{run:../../ProjectSchedule/Rogue.gan}{this location}.
\section{Project Review}
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment