Project management evaluation and reflection 3
Time planning and schedule 3
Evaluating Gantt chart 4
Budget 6
Adherence to the project methodology 10
RAD methodology 10
Waterfall methodology 12
Improvements that could be made to the project management skills and behaviours applied during
this project 14
Release Form 15
Document 15
Signed document 16
, Project management evaluation and
reflection
Time planning and schedule
Overall, this project can be considered a success in terms of time scheduling as it was ultimately
completed on schedule - that also includes this section of evaluating the project management of
the project. While it was not completed upon the planned time set out in the gantt chart, the
precautions taken that were laid out in the: ‘feasibility study’ > ‘Schedule - minimising risks’.
The final completion date was 06/06/23 meaning the project was complete 2 days before the due
date yet 2 days after the intended completion date, 04/06/23. The reason why the project was still
able to be completed on time was that during the planning for the time scheduling, a four day buffer
zone was allowed, this could then be utilised during the project and be used as a means, by the
project manager, to determine the likelihood of going over the official due date.
However, during the project, there was a point where the project was actually five days behind
schedule, meaning if all following tasks were completed within the duration they were given, the
project would not be completed by the due date. This was the biggest setback in the whole project
and was the only point in time throughout where the project seemed to have the possibility of
failing. In terms of time management and all other criteria that are to be covered in this evaluation
and reflection, this was the biggest weakness overall.
- This shows the estimated start and finish date of this stage of the project.
- This shows the actual finish date of the last task in this stage of the project(right, 23/05/23).
Due to this setback, it meant that another precaution that was emphasised in the project feasibility
study was utilised, this was ensuring that sufficient communication was being made between team
members and that efficiency was a key priority, more so than previous(although the importance
was always present throughout the project regardless). This was especially important in the Peer
review/feedback and optimization stages of the project. It was made apparent, to those who would
be given the feedback, of the previous setback, thus the importance of efficient work to be done by
them. This was also made clear to the animation developer.
Due to this, the Peer review/feedback and optimization stage was completed in significantly less
time than was initially planned - this now meant the trajectory of the time scheduling was before the
official due date(however, was still behind the schedule set out by the project manager).
- This shows the dates and duration that this stage was estimated take up(left-side dates)
and the actual dates that it took up(right-side dates)