IT Project Management Report: Teamwork, User Stories, Stakeholders

This report is an analysis of an IT project management assignment, focusing on the development of the "Care Love" application. The report delves into teamwork dynamics, evaluating the strengths and weaknesses of the team's approach, including communication and task allocation. It examines the use of agile project management techniques, and user stories, discussing their advantages and disadvantages within the context of the project. The report also provides a stakeholder analysis, outlining their roles, responsibilities, and communication strategies. The assignment includes a discussion of the communication plan and the challenges faced during the project's development. The report covers how the project was managed, including methods such as PRINCE2 and agile methodologies, user stories, and stakeholder management. It identifies the strengths and weaknesses of each area, and the project team's approach to teamwork.

Running head: IT PROJECT MANAGEMENT
IT Project Management
Name of the Student:
Name of the University:

1
IT PROJECT MANAGEMENT
Table of Contents
1. Team work...................................................................................................................................2
2. User stories..................................................................................................................................4
3. Stakeholders.................................................................................................................................7
References......................................................................................................................................10

2
IT PROJECT MANAGEMENT
1. Team work
Strengths of team’s approach to team work:
In the project, there are total of 5 members and the project work is divided among them.
The strengths of the team work are to identify the stakeholder’s groups those are relevant for
development of application project. The team members are committed to the work ethics by
doing work efficiently by not wasting the time. The team members perform their work based on
the tasks which are allocated to them by the project manager (Costa, Passos and Bakker 2015).
They have technical skills as well as knowledge to perform their job so that they can demonstrate
accountability by taking responsibilities of the actions. The team work is positive as they are
showing positive attitudes towards their project work. Positive people keep setbacks into the
project perspectives which lean to achieve more in addition to append to the workplace
dynamics. The team members are required little supervision so that they are self-motivated to
meet with the project deadlines. All the members followed a strict deadline as per the scheduled
plan so that there is no possibility of any kind of delay in the plan. The team members are
focused to understand their assigned work and responsible to meet with project goals and
objectives (Mäkikangas et al. 2016). Effective communicational skills are encompassed with
both written as well as verbal abilities. The team members have good listening skills so that they
can understand their responsibilities for meeting project objectives and goals.
Weaknesses of team’s approach to team work:
Some of the team members are not communicating with the project manager on the team;
therefore they are not getting information as well as resources required to do the job efficiently.

3
IT PROJECT MANAGEMENT
The fellow members have lack of trust among each other to get the things performed properly.
This relationship has potential to make conflicts among the project team members. It adds
anxiety to the project team which provide effect on morale as well as productivity of the business
organization. Creating of the team member leads to a time consuming meetings in which the
team members are disagreed about the course of project actions (Salas et al. 2017). The team
deliberates on the project issues for extended period of time; therefore they are not able to make
decisions rather than making contributions. Therefore, weakness is that there is lack of making
decisions regarding development of application for Care Love.
Discussion of approaches and techniques used in the project plan:
While working with the project work, the project management approaches and techniques
are used to manage and serve for managing the project activities. The agile project management
method is used which allows the project to process in project phases and cycles. In this method,
it is found that the project manager works in environment which treats the project milestones as
the sprints to make changes in the project (Uhl and Gollenia 2016). Agile is best suited for this
project plan as it is a software related project which demands for technical solutions throughout
collaborative efforts and solutions.
PRINCE2 is used as method which defines the business justifications of the project to the
project team members. This technique is described by the products which are delivering on time
furthermore in price estimation. The roles are determined ahead of there is kick off the scheme
work and each member of the plan is conscious of the project tasks for doing well in completion
of the project work (Heagney 2016). In order to prepare the communication plan for conducting
weekly basis meetings, there is discussion of the features of application required to be

4
IT PROJECT MANAGEMENT
implemented. Project management framework discovers of new applications for the traditional
linear approaches which is suitable for specifying the project requirements.
The success and failure of this project work is based on the technique to find out right
team members those are suitable for the development of application project. The project
management technique defines needs of the project and team member’s expectations related to
the project work (Eskerod and Jepsen 2016). The organizational goals are outlined and kept in
mind with the project features. The roles and responsibilities of all project team members are
properly mentioned using the project management technique. The processes aim to assist the
project manager with project guidelines through the plan and steps are required to complete the
project tasks.
2. User stories
Advantages of agile techniques for writing user stories:
The user stories are division of the agile approach which assists the shift to be focused
from scripting about the project needs. The agile user stories are included series of the
conservations about desired functions. The agile techniques for writing the user stories helps to
estimate the factors while estimating the user stories. It shows the functions of doctor, patient
and user (Jones, Wicks and Freeman 2017). One of the advantages of agile user stories are that it
writes about varying levels of the project details. Following are the advantages of agile user story
from the application project are:
The doctor can offer services such as home visit to the patients those are not able to come
to travel them. In this user story, the agile team completes in single iteration. It splits into various

5
IT PROJECT MANAGEMENT
smaller user stories before it works on. The above statement is split in following three epics such
as:
 As a doctor I can able to show the hours of home visit publicly.
 As a doctor I can able to access location of patient.
 As a doctor I have the contact details of the patients.
Similarly, the user stories are being written through the agile project. The story writing is
next to the starting of the agile project. Each of the project team members are participating with a
objective to create product backlog which can describe functionality of the project course work.
The user story for the patient is “As a patient I can book doctors home visit just via one app”,
and it is sprint which is developed as:
 As a patient I can able to review doctor’s availability for visiting the home.
 As a patient I am not able to explain address to my doctor.
 As a patient I can get contact details of the doctor.
The agile user stories are decomposed in smaller stories which can fit into single
iteration. The new stories are to be printed as well as added to product backlog at anytime and
any person (Mok, Shen and Yang 2015). The user stories using agile technique is used into
project planning.
Disadvantages of agile techniques for writing user stories:
The disadvantage of the agile techniques for writing the user stories are that they are
leaving lot of details out relies on the conversational methods and there is time development for
the users (Eskerod, Huemann and Savage 2015). The developer is slower to implement the

6
IT PROJECT MANAGEMENT
feature as they cannot understand the technologies needed to develop the user story. There is a
single user story for the user such as: As a user I can book ambulance for patient. Therefore,
details of the user story of project user are missing in this stage. The story is being implemented
into single iteration on the agile project; therefore it is common that there is splitting of user
cases into various iterations (Tantalo and Priem 2016). The iterations are also longer as
compared to application development project. The most common errors in the user stories by
using agile techniques are as follows:
 It distracts the project team as well as creates a risk of missing key significant part of the
conversion.
 It creates issues with extraction functions into provided iterations.
 It distracts from the user plus lessons readability of the project descriptions.
 It lists the technical tasks of user history which contribute to provide effect on the
prioritization of project tasks.
 The user stories becomes a risk to maintain correct directions of the project plan and
skips functions which are required for the user to write the user stories.
For the software deliverables, the developers are not measure the extent of the need towards
project efforts. It is starting of development of the project lifecycle on the larger products. Less
predictability leads to drive frustrations of the team members, poor practices as well as poor
decisions (Sunder 2016). The agile method makes it a difficult to quantify the team effort, time
plus cost of delivering the initial products. There is lack of documentation of the user stories;
therefore it is difficult to learn about details of the features which are required to perform.

7
IT PROJECT MANAGEMENT
3. Stakeholders
Strengths of stakeholder list:
The stakeholder list provides with responsibilities of them those are involved for the
application development project. They estimate the user stories and list a higher level user stories
for the project plan. The stakeholders provide short description of application which is helpful
for the service provider organization. The stakeholder list describes decision making and strategy
used to provide responsibilities of all the project team members (Harrison, Freeman and Abreu
2015). The stakeholders can understand the areas where the misunderstanding occurs in the
project plan so that they can take proper steps for making changes. The stakeholder performs the
meetings with each other so that they can know the points that require adding in the task and
mistakes which are done in the past projects.
Weaknesses of stakeholder list:
The stakeholders are not interested into the business work and there is lack of support
from them. Communicational plus technological advances affect relationships among the project
team members and project manager. The management is conflicted on key issues which are
raised due to lack of trust among the members. The weaknesses of stakeholder list are lack of
effective communication among the project parties as the stakeholders only performed face-to-
face meetings for discussing the problems (Mok, Shen and Yang 2015). Other possible ways to
interact are presentation, emails and conferences. Five of the team member’s tasks are provided
but in-depth details of their responsibilities are not provided so it is difficult to understand for
others.

8
IT PROJECT MANAGEMENT

9
IT PROJECT MANAGEMENT
Strengths of communication plan:
The application development team communicates with the stakeholder group throughout
entire project work. The team members attended face-to-face meetings with the project manager
for deciding the name of application and overview of that application through using
communication plan. Each of people has various ideas for implementation of application which
lists the ideas to conclusion and decided how the application is going to run. The app project is
able to distinguish and attract the employees to perform team meetings (Salas et al. 2017). The
employees are feeling comfortable to identify and accept the changes in the growth of care
services. As the team members are communicating via meetings, and then there is no possibility
of misunderstanding among them. This project work follows a proper step to communicate with
each other such as development of the application requires an approval letter from the
government side and meetings are conducted to discuss features of application (Harrison,
Freeman and Abreu 2015). The project manager takes all the project approval requires to release
the application into the market.
Weaknesses of communication plan:
Poor communication plan provides an effect on relationships as well as productivity of
Care Love. The weaknesses of communication plan are resulted in failure to focus on messages
and its respective medium. Email is the best communication method which is not used in this app
development project as it provides details regarding the entire development plan to each of the
project team members individually. The email can highlight critical information as well as offer
the recipients with the documents and links that they are used to do enough research on the
development work (Uhl and Gollenia 2016). The communication plan can harm the workplace

10
IT PROJECT MANAGEMENT
when there is misinformation of project details which result in costly mistakes in the project
work. The workers are required to encourage taking time for verifying the information before
they used the communication method as verbally as well as written part. One of the
disadvantages of written communication is that there is susceptible to the misinterpretations.

11
IT PROJECT MANAGEMENT
References
Costa, P.L., Passos, A.M. and Bakker, A.B., 2015. Direct and contextual influence of team
conflict on team resources, team work engagement, and team performance. Negotiation and
Conflict Management Research, 8(4), pp.211-227.
Eskerod, P. and Jepsen, A.L., 2016. Project stakeholder management. Routledge.
Eskerod, P., Huemann, M. and Savage, G., 2015. Project stakeholder management—Past and
present. Project Management Journal, 46(6), pp.6-14.
Harrison, J.S., Freeman, R.E. and Abreu, M.C.S.D., 2015. Stakeholder theory as an ethical
approach to effective management: Applying the theory to multiple contexts. Revista brasileira
de gestão de negócios, 17(55), pp.858-869.
Heagney, J., 2016. Fundamentals of project management. Amacom.
Jones, T.M., Wicks, A.C. and Freeman, R.E., 2017. Stakeholder theory: The state of the art. The
Blackwell guide to business ethics, pp.17-37.
Mäkikangas, A., Aunola, K., Seppälä, P. and Hakanen, J., 2016. Work engagement–team
performance relationship: shared job crafting as a moderator. Journal of Occupational and
Organizational Psychology, 89(4), pp.772-790.
Mok, K.Y., Shen, G.Q. and Yang, J., 2015. Stakeholder management studies in mega
construction projects: A review and future directions. International Journal of Project
Management, 33(2), pp.446-457.

12
IT PROJECT MANAGEMENT
Salas, E., Prince, C., Baker, D.P. and Shrestha, L., 2017. Situation awareness in team
performance: Implications for measurement and training. In Situational Awareness (pp. 63-76).
Routledge.
Sunder M, V., 2016. Lean Six Sigma project management–a stakeholder management
perspective. The TQM Journal, 28(1), pp.132-150.
Tantalo, C. and Priem, R.L., 2016. Value creation through stakeholder synergy. Strategic
Management Journal, 37(2), pp.314-329.
Uhl, A. and Gollenia, L.A. eds., 2016. A handbook of business transformation management
methodology. Routledge.