Purpose
Milestone reports serve to inform me of what work you have
completed over the past implementation period, how the project
as a whole is progressing, and aid me in assessing your
understanding of how the system is implemented both at a micro
and macro scale.
My recommendation to how you go about authoring this report is
to first try and gather together all the points that need to go into
it, perhaps using the questions below for guidance. Then take all
of that content and work it into a concise and cohesive
narrative using a clear structure such as the outline below.
Outline
Below is a suggested (though not required) outline for the
milestone report. If you choose to stray from this format,
ensure that all the information in this outline is present in your
version.
The only thing that must be clearly presented at the top is
the milestone the report covers, your name and the project
components you worked on. For example, for the first milestone
report, your header should look substantially similar to the one below.
Header
CMSI 698 SS:NVE
Bobby R. McProgrammer
Milestone I Report
Drone I, 2DVisualizer I
The Outline
- Summary/Introduction
(the team; what is to be implemented; what worked; what didn't)
- Milestone Objectives
(what, your responsibilities)
- Implementation Strategy
(design; NVE concepts; tools, tactics and techniques employed; intended implementation)
- Outcomes
(results achieved; successes; failures; why what worked worked; why what didn't work didn't)
- Reflection
(your views on what worked and didn't; changes you would make if you were to do it again)
Questions
From a goal perspective, as the audience, I should be able to
answer the following questions after reading your report. This
list might prove useful in your forming the body of your report.
However, do not forget you must edit and organize your report!
Do not simply turn in a long list of answers to these questions
loosely strung together into paragraph form. Find answers to
these questions and then use that to compose a clear, flowing report.
- Who was in the implementation group?
- What parts of the component did you have direct responsibilty for?
- What was the original plan for implementing the component(s)?
- What languages were used by the team?
- What tools were used by the team?
- What problems did you/the team encounter?
- How did the problems affect the final outcome?
- If you were to re-implement the component, in what major ways would it differ?
- What parts of the component were too complicated/difficult to implement?
- Was the complication or difficulty exo- or endogenous to the component itself?
- What changes to the overall project should I consider?
- What formal NVE concepts did your component embody?
- How well does your current team structure function?
- What problems exist in the team structures that I can assist with?
- What parts of the project do you particularly enjoy?
- What specific aspects of NVEs have you gained understanding about?
- How much of the component was implemented?
- What parts of the component function according to the specifications?
- What parts of the component does not function according to the specifications?
- If complete, what choices or situations contributed to the success?
- If incompolete, what choices or situations contributed to the shortfall?
- What do you think you/your team did right, regardless of the outcome?
- What do you think you/your team could have done better, regardless of the outcome?
- What do you think you/your team did wrong, regardless of the outcome?
Version: 1.2