IT Project Management Report: Hunger Bowl Application Analysis

This report provides a comprehensive analysis of an IT project, specifically focusing on the development of the "Hunger Bowl" application. The report begins by evaluating the strengths and weaknesses of the team's approach, highlighting the division of tasks, effective communication, and the use of agile techniques. It then delves into the advantages and disadvantages of employing agile techniques for writing user stories, emphasizing the benefits of high-value delivery, increased user collaboration, and improved transparency, while also acknowledging potential drawbacks such as systemic task complications and functional fragmentation. Finally, the report assesses the strengths and weaknesses of the team's stakeholder list and communication plan, noting the organized stakeholder categorization and the structured communication plan, while also pointing out the non-versatile nature of the stakeholder list and the limited focus on certain stakeholder groups. The report concludes by providing references to support its findings.

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

1IT PROJECT MANAGEMENT
Table of Contents
Strength and Weaknesses of Team’s Approach:........................................................................2
Strengths Regarding Team’s Approach:................................................................................2
Weaknesses Regarding Team’s Approach:............................................................................3
Advantages and Disadvantages of the Agile Technique of writing user stories:.......................4
Advantages of the Agile Technique of writing user stories:..................................................4
Disadvantages of the Agile Technique of writing user stories:.............................................5
Strengths and Weaknesses of team’s Stakeholder list and Communication Plan:.....................6
Strengths of team’s Stakeholder list and Communication Plan:............................................6
Weaknesses of team’s Stakeholder list and Communication Plan:.......................................7
References:.................................................................................................................................8

2IT PROJECT MANAGEMENT
Strength and Weaknesses of Team’s Approach:
The current approach of the team for developing the hunger bowl application is by
using the agile technique of software development method. Currently in the team there is
total 7 team members who are working on this project. In this project seven members are
performing some different kind of tasks related to the project. In this project six members out
of the seven are working on the sign up page and on the login page of the application. This
login page will be used for registering to the hunger bowl application for finding the food for
the charity people. The one team member who is not related with the development of login
page and register page is solely working on the development of the donation screen. This
donation screen will help to list the donations that has been done. The other six team
members are also working on the other requirement of the project. The group leader of the
project is Gayathri Bommu and this member of the project is currently working on the
identification of the stakeholder list, scheduling meetings for the project, meeting agenda
preparation and for preparing report regarding the project. Team member Sravani Reddy
Ravulapati is having the responsibility of deciding the app name, currently which has been
chosen as “Hunger Bowl.” This team member is also having the responsibility of developing
description of the application and developing the communication plan of stakeholders.
Another team member Sindhura Gogireddy has taken the responsibility of prioritising the
user story and estimation. The other team members are working on the development of the
sign up and login page.
Strengths Regarding Team’s Approach:
The main strength in this case regarding the approach of the team is that the all the
task are divided among the team members of the project on an equal force. This has helped
the project to run many of its operations simultaneously. Thus the execution speed of the

3IT PROJECT MANAGEMENT
project has increased a lot (Malakooti 2013). Here another advantage in this project is that the
communication plan developed by the team members are excellent. This communication plan
has been developed considering all the aspects of the project and it is outlined perfectly when
the stakeholders need to communicate with each other and the medium of the communication
is also defined by the team members. Another strength regarding the approach of the team is
development of the user story and prioritising them. In this case with prioritising the user
story estimation for completing the user story is also determined (Lucassen et al. 2016). As
per the developed timeline it has been determined that to complete the whole project
approximately 70 days will be required. By determining the project timeline, the project can
be managed easily which provides another strength to the project. Another considerable
strength in this case was the clarification of the roles. The roles of the team members was
clearly defined in this case which was reflecting a big strength regarding the approach of the
team.
Weaknesses Regarding Team’s Approach:
An approach that could have been implemented in this project was rewarding the
team members on excellent teamwork. This approach was omitted in this case but it can be
very much useful for influencing the team members more towards their work. Thus it can
increase the efficiency of the project (Serrador and Turner 2014). Another weakness
regarding the approach of the team is that no feedback is collected from the project team
members. In such scenarios feedback can be collected from the project team members about
their work experience and their thoughts on the project progress. By collecting this data, if
this is any error in the project can be determined. Also, assessing the feedbacks from the
project team members can help to improve the overall project conditions as they can come up
with some ideas on how the project can be improved.

4IT PROJECT MANAGEMENT
Advantages and Disadvantages of the Agile Technique of writing user
stories:
In this project approach, agile techniques of writing user stories has been
implemented which has many advantages and disadvantages in the project. The advantages
and the disadvantages of agile technique of writing user stories are discussed in the following
section.
Advantages of the Agile Technique of writing user stories:
One of the main advantage of agile technique of writing user stories is the highest
value delivery. In this case the user story focuses on the immediate and small needs of the
customer which delivers the highest value in the project (Hamouda 2014). This agile
technique breaks the needs of the users in smaller features that can be delivered within a
shorter amount of time and these user stories can be prioritised according the user value,
business value and risk which significantly increases the delivered value by the project team.
The next advantage that is provided by the agile technique of writing user stories is
bringing the user closer. These user stories is capable of delivering a high amount of
customer value. This agile team is also capable of collaborate with the end user on a regular
basis and it encourages the project team members to communicate with each other (Lin et al.
2014). The main advantage of this to the project is that by better collaboration perspective of
the users can be understood easily thus it becomes very much easy to execute the project
considering requirements of the clients.
Another advantage of this type of this type of agile technique of writing user stories is
that the transparency can be increased among the team members for a project. The user
stories is capable of increasing the transparency within the project team members and the
stakeholders of the project. In such scenarios the index card remains visible to everyone

5IT PROJECT MANAGEMENT
related with the project thus faster decision making and better collaboration can be achieved.
Improved transparency can build better trust within the project environment. Here the
transparency actually maintained about priorities of the user stories and the customer segment
that is usually addressed through a particular user story.
Reduced risk is considered as one of the most important advantage that is provided by
the agile technique of writing user stories. In many traditional type of project technique
proactive measures are not followed of reducing the risks (Costa et al. 2014). Here the user
stories can effectively reduce the risks regarding the project by improving the collaboration,
creating transparency, focusing on the customer needs and by creating shared understanding.
This can eliminates potential risk in the project such as technical risks, business risks,
financial risks and the communication risks.
Disadvantages of the Agile Technique of writing user stories:
With many advantages there are various disadvantages regarding agile technique of
writing user stories. For a systemic task this user stories can create very much problem within
the project. In this case complications can arise regarding the description of user story
including spikes and bugs.
Another disadvantage of the agile technique of writing user stories is that it creates
discrepancy in the functional approach of a provided story among the developer team and
client.
The next disadvantage in this case is that there can be lack of information regarding
the development method and design interface and this can vary between the developers (Flora
and Chande 2014). Thus new user story need to be developed in the event of changing the
development team.

6IT PROJECT MANAGEMENT
Also, focus on the business functionality can be missed due to the development of
user story. Technical definition is also not present in the user story which is also a
disadvantage in this case.
Functional fragmentation can also occur due to the agile technique of writing user
stories (Amir et al. 2013). Due to the user stories development control can be loosen over the
whole vision and due to that functionary fragmentation occurs.
Strengths and Weaknesses of team’s Stakeholder list and Communication
Plan:
There can be various strengths and weaknesses of the stakeholder list and the
communication plan in this project. The main strengths and the weaknesses are discussed in
the following section.
Strengths of team’s Stakeholder list and Communication Plan:
The main strength of the stakeholder list is that it is currently presenting all the
important stakeholder of the regarding the project. Here in this case the stakeholders are
divided into four major groups which are the primary, secondary, tertiary and facilitating.
This breakdown structure of the stakeholder list provides the idea about which stakeholders
need to be treated in which way (Eskerod and Jepsen 2016). Here the primary stakeholders
are such peoples who are going to use the system directly. Thus it is determined that primary
stakeholders of the project must be given highest priority.
The communication plan is also very much important in this case and it has been
determined that the main strengths of the developed communication plan for this project is
that it has provided the outline of when and how the stakeholders will communicate with the
development of “Hunger Bowl” application. Also, the four stakeholders group will
communicate with the other members of the project individually which simplifies the project

7IT PROJECT MANAGEMENT
execution more. In this communication plan also the method of communication is determined
and this provides another strength to the developed communication plan for the project.
Weaknesses of team’s Stakeholder list and Communication Plan:
The main weakness of the developed stakeholder is that the provided list of
stakeholder is not versatile. That means the stakeholder list need to be developed again in the
event of changes in the development thus (Cooper 2017). Thus this stakeholder list is
identified as non-versatile. This stakeholder list is also very much critical compared to the
traditional stakeholder list where only two types of stakeholders are listed which are external
and internal stakeholders.
The current developed commutation plan is mainly focused on the primary
stakeholder group. It might be a positive side but due to that the other three stakeholder group
is less communicated or neglected and this is a huge weakness of the developed
communication plan for the project.

8IT PROJECT MANAGEMENT
References:
Amir, M., Khan, K., Khan, A. and Khan, M.N.A., 2013. An appraisal of agile software
development process. International Journal of Advanced Science & Technology, 58(56),
p.20.
Cooper, S., 2017. Corporate social performance: A stakeholder approach. Routledge.
Costa, N., Santos, N., Ferreira, N. and Machado, R.J., 2014, June. Delivering user stories for
implementing logical software architectures by multiple scrum teams. In International
Conference on Computational Science and Its Applications(pp. 747-762). Springer, Cham.
Eskerod, P. and Jepsen, A.L., 2016. Project stakeholder management. Routledge.
Flora, H.K. and Chande, S.V., 2014. A systematic study on agile software development
methodologies and practices. International Journal of Computer Science and Information
Technologies, 5(3), pp.3626-3637.
Hamouda, A.E.D., 2014, July. Using agile story points as an estimation technique in CMMI
organizations. In 2014 agile conference (pp. 16-23). IEEE.
Lin, J., Yu, H., Shen, Z. and Miao, C., 2014, June. Using goal net to model user stories in
agile software development. In 15th IEEE/ACIS International Conference on Software
Engineering, Artificial Intelligence, Networking and Parallel/Distributed Computing
(SNPD) (pp. 1-6). IEEE.
Lucassen, G., Dalpiaz, F., van der Werf, J.M.E. and Brinkkemper, S., 2016. Improving agile
requirements: the quality user story framework and tool. Requirements Engineering, 21(3),
pp.383-403.

9IT PROJECT MANAGEMENT
Malakooti, B., 2013. Operations and production systems with multiple objectives. John Wiley
& Sons.
Serrador, P. and Turner, J.R., 2014. The relationship between project success and project
efficiency. Procedia-Social and Behavioral Sciences, 119, pp.75-84.