-
Notifications
You must be signed in to change notification settings - Fork 0
Weekly report
Pedro Felix edited this page Feb 24, 2018
·
4 revisions
-
The students should maintain a weekly projectreport as a table sorted in reverse chronological order, with the following columns:
- Main outcomes.
- Risks and decisions to make.
- Next tasks to focus on.
-
This report should not take more than 10 minutes to make and be completed until the end of Saturday.
-
In the main outcomes, include links to the produced artefacts (e.g. commits, pull requests, documentation pages).
-
This report has two main goals
- Create a space for the students to reflect on what they have accomplished and what needs to be done next.
- Provide better visibility to the project supervisor, namely to prepare the agenda for the following week regular meeting.
-
Example
Week | Main outcomes | Risks and decisions to make | Next tasks |
---|---|---|---|
3 | |||
2 | |||
1 | Project summary delivered. Regular meetings scheduled. | None | Start the progress report. Define the project's calendar |