SE Exp2 Saivignesh, Adit, Shivam

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 5

Exp-2-Application of Agile Model

Name Class-Div Roll No


Saivignesh Adepu TE-3 42

Adit Chheda TE-3 47

Shivam Jadhav TE-3 53

Title
Video Meeting Android App using Scrum Model

Problem Statement
In a large, multinational organisation, borderless collaboration is key. It’s no longer just about
personal productivity – success rides on teams working together effectively, no matter where in
the world they are. As our business expands, we need the tools to bring our people closer. To
each other and to the processes and information they need to deliver. Video Meeting provides a
complete, cloud-based collaboration suite across voice, video, messaging and conferencing.
Enabling always-on, real-time collaboration, Video Meeting has the ability to break down siloed
ways of working and boost productivity. In an enterprise that demands continuous delivery across
multiple, cross-functional teams, full adoption of Video Meeting will provide the seamless
connectivity and agility we need to keep everyone engaged and working effectively together.
Agile Model
Agile SDLC model is a combination of iterative and incremental process models with focus on
process adaptability and customer satisfaction by rapid delivery of working software products.

Drawing
Scrum
Scrum is an agile development methodology used in the development of Software based on
iterative and incremental processes. Scrum is an adaptable, fast, flexible and effective agile
framework that is designed to deliver value to the customer throughout the development of the
project.

Drawing
Scrum Process
1) Product Backlog
a) Creating an Android App through which Video Meetings can be conducted.
b) Creating a Chat Box through which everyone can chat with each other.
c) Creating Call Feature through which Internet Calling can be possible.
d) Creating a Group Section in which People can be added in that group so that all the
group work can be done easily.
e) Creating a Calendar to keep track of individuals' work.

2) Sprint Planning

The Project Team Members will start from Creating App with Video Meeting feature and
proceed according to the Product Backlog all the way up to Creating a Calendar.

3) Sprint Backlog

The Sprint will be of 2 weeks which means that after every two weeks the team should have
a functioning piece of the product to show for their work.

a) In the first Sprint, focus will be on creating a Video Meeting feature in which option of
“Video Calling” will be implemented. It will have a Voice Button and Video Button
which can be turned on and off. Maximum 100 People will be allowed in one Video
Call. That video call can be recorded by anyone with Recording feature.
b) In the second Sprint, a Chat section will be created which will allow everyone to chat
with each other. It will have options such as sending text messages, images, videos,
gifs, stickers, files, emojis.
c) In the third Sprint, a Call feature will be introduced so that everyone can call each
other directly from this App with the help of the Internet.
d) In the fourth Sprint, the Group section will be introduced so that people can chat with
each other in a group, make Video Calls directly in that specific group by one click
instead of adding individuals to Video Call one by one.
e) In the fifth Sprint, Calendar will be created so that Statistics about Individual people
can be displayed in which everyone will get to know about how much time they
spend on video calls, chats, calls.

4) Daily Scrum

Daily Scrum will be usually 15 to 30 minutes long. In this time, Scrum team members interact
with each other during the Sprint to encounter progress as well as issues. This is mainly
supervised by the Scrum master to make sure that all of the scrum theories, rules, and
practices are truly followed by the team members.

5) Sprint Review

As when the sprint is ended, the product owner organizes a sprint review meeting. In this
meeting, the development team reveals whatever they have accomplished so far since the
last sprint. And then, the product owner informs about what is yet to be achieved on the
product backlog, followed by the estimated time in which the project has to be completed.

6) Sprint retrospective

The scrum team comes all together in a sprint retrospective meeting, where the team
discusses what went well, what did not, and how they could have done it in a better way.
This might be due to some technical issue or maybe a team member is burdened with tasks.
The decision-makers decide how to solve such issues and put up a plan to get rid of them in
the next sprint.

You might also like