Unit 9: IT Project Management - Assignment 3 (P8, P9, M4, D4)

Evaluation & Closure of the Project
Table of Contents
Table of Contents
Table of Contents........................................................................................................................................1
Strengths in the Project...............................................................................................................................1
Reviewing the Methodology....................................................................................................................1
Reviewing the Management Processes...................................................................................................1
Reviewing the Job Roles..........................................................................................................................2
Reviewing Time Management Skills.........................................................................................................2
Reviewing Communication and Literacy Skills.........................................................................................3
Reviewing Problem Solving Skills.............................................................................................................3
Reviewing my Behavior & Responsibility.................................................................................................4
Recommending Improvements...................................................................................................................4
Improvements on my Skills & Behavior...................................................................................................4


Strengths in the Project
Reviewing the Methodology
I chose RAD for my project because I think it was the most suitable choice for the project. This is because
RAD supports software developers and provides many flexible and efficient processes to complete a
project related to software development. RAD approach's main advantage is fast project turnaround,
which makes it an ideal choice for developers who work in a fast-rapid environment like software
development. The focus of RAD on reducing the planning stage and emphasising more on prototype
development. I was able to confidently communicate with my client about the project to make him up
to date with the project due to RAD. I think I was able to finish the project well before the deadline
because of good planning as well as using RAD as I was using multiple sprints to improve the designs and
game.

Even though Rapid App Development is used for software development, Agile can be a better choice for
some reasons as it provides more flexibility and productivity for the project. However, I choose RAD
because my project and team was not big but if I had a bigger team then I would have chosen Agile
Methodology.

Reviewing the Management Processes
I think I have used the RAD methodology very well in the project. This is because I followed every step
and phrase to finish the project. At first, I created the user requirements document which contains the
requirements of the game and its other details such as how to make the levels. I added this in my work

, log as it is an important factor of RAD methodology. After this I planned my project including the factors
such as time plan, resource plan and other constraints that might come up during the development and
designing phrase. Following RAD, I used sprints to improve my design and game by making a
questionnaire and asking my peers to review it so I will know what went well and what went wrong in
the design and development. After receiving the feedback, I contacted my client to review it and
confirming improvements. After improving my design, I developed the game and contacted my client to
let him know where I am. This is a part of RAD methodology as you must use sprints to improve your
design and game. Then I tested the game using the test plan I created in planning phrase and fixed any
errors that came up. I sent the results of test plan to my client to keep him up to date with the project.
Lastly, I created technical documentation which contains information about the game that would be
useful for any other developer to develop the game.

Reviewing the Job Roles
Talking about the job roles, I think I have done pretty well in doing all the job roles that I was supposed
to do. Because I was the only person involved in this project, I had to do everything to complete the
project. For example, I was the project manager of my project as I managed everything of the project
throughout. I planned and solved the problem myself by doing different feasibility studies. I was the
designer as I created designs of the game and then improved it by asking for feedback. Then I did the
role of developer as I created the game my self. Furthermore, I tested the game to see if it meets the
requirements or not or if there are any errors to fixed, which is a role of a tester and quality assurer. I
also acted as a user for the game however, as I asked my other peers to review the designs and game
then they are also included as a user in this project. Throughout the project, I updated my time plan to
make a record log of everything that I have done and how much time did it took.

Reviewing Time Management Skills
I think that I have managed my time well in this project because I have hit every deadline that has been
set for me and had enough amount of work done for the deadlines set. I worked on the assignment both
in class as well as outside in order to get the level of detailed needed for it which will help me to get
highest marks possible and be successful. Overall deadlines were not a problem for me at all because I
have submitted everything on time which indicates that my time management skills are pretty good.




My Time
Plan