Software Engineering Project Report: Team Dynamics & Outcomes

This report details a software engineering team's experience working on an application development project. The team, composed of members with no prior collaboration, faced challenges including communication breakdowns, lack of leadership, and unequal workload distribution. The report discusses the project's implementation using Apache Tomcat servers, highlighting issues such as the faster pace of front-end development compared to back-end work. Requirements like Java development, Google Docs for sharing, and database management are outlined. Risk analysis identifies the need for a dedicated team leader and more in-depth discussions before project commencement. The conclusion emphasizes the importance of risk analysis, leadership, and communication in ensuring project success. Desklib provides access to similar solved assignments for students.

Running head: SOFTWARE ENGINEERING
Software Engineering
Name of the Student
Name of the University
Author note

1SOFTWARE ENGINEERING
Table of Contents
Introduction....................................................................................................................3
The work........................................................................................................................3
Project implementation and Workload:.........................................................................3
Requirements..................................................................................................................4
Risk:...............................................................................................................................4
Conclusion......................................................................................................................5
References......................................................................................................................6

2SOFTWARE ENGINEERING
Introduction
This report is about a group whose task was to make application which would help
the customers and the clients in the day to day works (McNeil, Frey & Embrechts, 2015). The
team had no prior experience of working together, as the persons in the group never met each
other before the project. The report focuses on the working experience, the work load, the
risks and the project work schedule deduction and the things that were done though out the
project.
The work
As the team meet eventually, they decided for exchanging their personal details and
contact information’s as the team was meeting for the first time. The group also decided to
start the work using the Google docs, as that would help the team to easily share the progress
report. One of the major problem was that they were too much engaged in the discussing part
and usually meet up for 2 to 3 times a week. The first problem started from here as the
members were taking too much time to start the project (D’Innocenzo, Mathieu &
Kukenberger, 2016). One of the major problem that the team faced from the beginning was
the lack of communication between the team members. One of the major reason for this was
that the solely relied for the Facebook group, and it was not possible for everyone to connect
to Facebook every time. The lacked a proper leader from the beginning, making it one of the
major drawback one of the major drawback was that in the team not everyone worked in an
equal manner, someone was doing the task and someone was not and hence making it
difficult for everyone to collaborate.
Project implementation and Workload:
The project team used the apache tom cat servers for the work and the application ran
very well at the beginning and all the team members were able to view the proper update of

3SOFTWARE ENGINEERING
the work. One of the major fault at this time was that the front end developers were working
in a very faster speed than the back end developer, and none of the members noticed this until
the work was done yet the database work was not properly done (Liu, Lin & Chen, 2016).
This became a major drawback for the team as the project deadline came near but the yet the
work was not done. The major reason for this was the fact that there was no one to supervise
the team and follow up the progress report (Antonakis & Day, 2017). Near the end of the
prototype deadline it was clear for the team that the group had to do more depth of the task
and more discussion must have been done in order to make the task a feasible one.
Requirements:
Some of the major software requirements for the project is nessecery for the project to
be completed is the Java developing for the front end and the backend developing, Google
docs for the sharing task. Also there is the need of the browsers for the running the
application, apart from this the Ajax and the database are required for the data storing and
working purpose.
Risk:
The risk analysis that must have done, initially must have chosen a member who
would help the team to main a proper aspect of every task. The second thing that must have
been done is a proper depth discussion before the working on the project. After the deadline
expired the team also realised the fact that only one of the developer of the java programs are
not enough for the task development process (Cagliano, Grimaldi & Rafele, 2015). Also it
was very difficult for everyone to commence the project because not all the members knew
about the web applications and that was also from self-learning and hence the project
members should also have done the same for the development of the project (Fairhurst &
Connaughton, 2014). One of the other major risk in this that the entire project may fail due to

4SOFTWARE ENGINEERING
the lack of the proper knowledge and mishandling of the data available. The other major
problem was the browser compatibility of the application as different browsers have different
settings and none of the members knew the proper thing to be done and hence became tough
for the members to concentrate.
Conclusion:
Thus, concluding the topic it can be said that before starting the project the must have
properly analysed the risks. The team must have also selected a team leader who would have
been always keep up with the task and provide proper report to each and every member. Also,
initially the every member must have took contact details, which would have helped the
members contacted whenever the needed help from the others. Miscommunication and the
lack of the proper leadership is the major reason for the team projects problems.

5SOFTWARE ENGINEERING
References
Antonakis, J., & Day, D. V. (Eds.). (2017). The nature of leadership. Sage publications.
Cagliano, A. C., Grimaldi, S., & Rafele, C. (2015). Choosing project risk management
techniques. A theoretical framework. Journal of Risk Research, 18(2), 232-248.
D’Innocenzo, L., Mathieu, J. E., & Kukenberger, M. R. (2016). A meta-analysis of different
forms of shared leadership–team performance relations. Journal of Management, 42(7),
1964-1991.
Fairhurst, G. T., & Connaughton, S. L. (2014). Leadership: A communicative
perspective. Leadership, 10(1), 7-35.
Liu, B., Lin, Y., & Chen, Y. (2016, April). Quantitative workload analysis and prediction
using Google cluster traces. In Computer Communications Workshops (INFOCOM
WKSHPS), 2016 IEEE Conference on (pp. 935-940). IEEE.
McNeil, A. J., Frey, R., & Embrechts, P. (2015). Quantitative risk management: Concepts,
techniques and tools. Princeton university press.