This is Assignment 3 for Unit 9 IT Project Management. IT meets all the distinction Criteria allowing for an overall Distinction Grade. IT Project Management has 3 Assignments in total and this is one of them. Please check out my page for Assignment 1 and 2 which will be sold separately.
Criteri...
Unit 9 - Assignment 3
IT project management
________________________________________
Introduction
For this assignment we have been asked to create a report in which we analyse The
project we have just completed looking at the project management skills and
behaviours we applied and how effective they were. Additionally, I've been requested
to offer suggestions for improving my project management abilities and behaviours
going forward.
My approach to managing my project
Before my project had begun I had created a space for me to communicate with not
only the programming expert but other necessary team members.
This space was created on google chat as it was convenient for all of us as we all
used the service regularly and were familiar with it. I also incorporated Trello, a
collaborative project management application, to the google chat so that I could
make boards and lists to display to the stakeholders during the meetings. Google
meet allows for convenient meetings as stakeholders and developers could join the
call from their workspaces meaning no time and money had to be spent on travelling
and renting a local for us to meet. As well as this as the meeting took place at the
workplace more topics were brought up allowing more collaboration between the
stakeholders and the project team which was a key factor of RAD as during the user
design phase it is important that the clients and developers work hand in hand to
ensure all needs are met at every step of the design process. Google meet also
helped with the iterative process included in RAD as developers could teak the
design models and show this live to the stakeholders until they found a satisfactory
design that worked for the clients.
, As we were using RAD as our methodology, communication with team members
was extremely important as we could discuss the project and notify each other of
problems or milestones. This was essential for us as RAD is a methodology that
does not focus too heavily on planning but emphasises prototype iterations. What
this means is that through collaboration between the clients and the project team
current and potential issues can be determined and addressed early on. Also
through getting approval from the key stakeholders and developers the teams
involved with the project can avoid miscommunications and costly change down the
road. This then means that there will be less interference and delays from either
parties as an agreement has already been made which would then further ensure
that we stay on track with the project and avoid risking falling behind on an already
tight schedule. As falling behind would have a negative impact on the outcome for
the client and for the project team, mainly me the project manager as this failure will
be recorded and be stuck with my record as a project manager. During the meetings
on google chat I broke down the sections of the project into more manageable
sections which made it easier for team members and stakeholders to know what our
plans were and how long the project would take. The reason for this was to further
simplify the tasks for the stakeholders but was also an advantage for the multiple
teams involved in the project and here's why. The tasks were broken into short
sprints which allowed for smaller goals and milestones in a several month project.
This not only benefited the teams progress but the employees themselves as it gave
them more peace of mind as they were congratulated for the small goals they
achieved showing them they had been making progress throughout the project's life
cycle rather than them being drained throughout the project and being given
recognition/praise at the end of project. This allowed for the employees to remain
keen on the project and dedicated to successfully completing the project. The short
sprints also allowed for an easier assessment of monitoring progress throughout the
project.
One way we showed this was using a gantt chart.
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller adilhass. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for £9.49. You're not tied to anything after your purchase.
