Write me a project paper like this The aim of the project is to practice software development life cycle with applying the scrum framework of Agile project management. Students are going to create scrum teams and going to apply scrum framework to their imaginary software project. They are going to demonstrate a sprint in detail. Project topic can be a feature of any popular software application. Software development is not expected. Students are only responsible from documenting and presenting each phase/practice of scrum framework (scrum team roles, scrum events, etc.). Each group must provide a project documentation and in class presentation. Project Sections:1. Creating Scrum Teams (3-9 persons)2. Distribution of Scrum Roles (Product Owner, Scrum Master, Development Team)3. Determining Values of Scrum team4. Determination of Requirements5. Task Breakdown6. Estimation7. Planning8. Kick-Off9. Regular meetings10. Retrospective Each step is 10 points (10x10 = 100% they are expect us to write scrum team project topic and agile project management team workbreakdown structure something i will send you the example project make me a project like this everything should be the same you can choose the topic make a scrum team make a wbs Do it by looking at the sample project example I sent you. SAMPLE PROJECT(EXAMPLE PROJECT do the same but different topic names are just example):STUDENTS

Uur Bilgin - 1730858

Samet Artan - 1804335

Fatma Nur Yoku - 2001173

Ahmet Tuncel - 1802272

Edanur Budak - 1804749

Muhammet Talha Happani - 1804499 TABLE OF CONTENTS

1. Scrum Team

2. Values of Scrum team

3. Requirements

4. Work Breakdown Structure

5. Time Estimation and Sprint Planing

6. Kick Off

7. Regular meetings

8. Retrospective SCRUM TEAM

Uur Bilgin: Scrum master

Uur has expertise or certification in the Scrum framework. He uses this expertise to lead other team members on different processes. He serves much like the foreman of a given project, keeping team members on track and mentoring them on Scrum concepts along the way. The duties of Uur include:

Fostering an effective, collaborative work environment for team members

Understanding Scrum framework and Agile principles

Mentoring team members on following Agile principles

Strategically motivating team members

Maintaining productive relationships with stakeholders and team members

Preventing any distractions that may interrupt productivity

Samet: Product owner

Samet takes responsibility for developing high-value products. He specializes in the oversight of development teams and meticulously analyzes project decisions to ensure they align with team goals. He possesses a deep understanding of business processes and customer-oriented values. The duties of Samet includes:

Establishing a product vision and creating a marketing strategy

Monitoring potential customer engagement and requirements

Working proactively for creating solutions for the development team

Optimizing the development team's workflow to increase product value

Ordering and managing project backlog

Fatma Nur Yoku: Scrum Developer

Fatma has a lot of experience on backend and frontend development. She is an expert on programming languages like Python, C++, Javascript. She also has knowledge about HTML and CSS.

Ahmet Tuncel: System Analyst

Ahmet is a skilled professional that works to enhance user experience with software programs.

Edanur Budak: Scrum Developer

Edanur is responsible for managing data of our platform. She is an expert on Database.

Talha: Scrum Developer Talha has expertise on UI/UX. He evaluates better UX for the end users. He knows a lot about design tools.

VALUES OF SCRUM TEAM Courage

The Scrum team members have courage to do the right thing and work on tough problems. The Scrum Guide

Scrum teams must have the courage to be honest, open, and transparent both with themselves and with stakeholders about the projects progress and any roadblocks theyre experiencing.

Focus

Everyone focuses on the work of the Sprint and the goals of the Scrum team. The Scrum Guide

In order to get the most out of each sprint, each team member must remain focused on the task at hand as well as how it impacts the sprint goal.

Commitment

People personally commit to achieving the goals of the Scrum team. The Scrum Guide In order to successfully navigate these life and death situations, each team member must be 100% committed not only to the mission at hand but to their fellow team members, too.

Respect

Scrum team members respect each other to be capable, independent people. The Scrum Guide

Just as it does in any team endeavor, respect in a Scrum team means recognizing that no single individual or their contribution is more valuable than another. Respect also means trusting your fellow team members to fulfill their tasks, listening to and considering their ideas, and recognizing their accomplishments.

Openness

The Scrum team and its stakeholders agree to be open about all the work and the challenges with performing the work. The Scrum Guide

In order for the Scrum team to make the most progress in the shortest time possible, each team member must be brutally honest and open about their own progress.

REQUIREMENTS

This application we have developed has diverse functional and nonfunctional requirements for food-ordering.

Initially, we would like to determine the application's functional requirements. The main functional requirements can be listed as follows:

The user's addresses should be stored in the database and the user should be able to enter new addresses.

In the order sections on the main page, the names of the restaurants that are near the user, the photos of their meals and the comment page of that restaurant should be included.

The user should be able to get live support whenever he/she needs it through the "live support" button on the main page.

The user should be able to add the dishes he/she wants to add to the cart.

The user should be able to see the previous orders on the "my previous orders" page.

When any of the restaurants is clicked, a special screen should be opened for the restaurant where discounts and all other products belonging to that restaurant are displayed.

By writing a note in the text field, the user should be able to send his/her comment on how he/she wants the product to the restaurant. The user should be able to receive a return message/comment from the restaurant where he/she asked a question or commented.

When the user clicks on the name or photo of the restaurant, he/she should be directed to the page with the menus and products of that restaurant.

Restaurants should be able to be evaluated and interpreted by the people who order from them.

The user should be able to safely pay the amount of the order to be placed, and save the card information in the application and use it in future orders.

For each restaurant, the user should be able to see the estimated delivery time of that restaurant's product to the user, with an interval of +-10 minutes.

The user should be able to see the instant location of the motorcycle courier who brought his/her order until the order is delivered.

And these are non functional requirements of this application:

User login shall be no longer than 30 seconds.

The food-ordering app system shall restrict the access to the login page after five unsuccessful login attempts.

Each page must load within 3 seconds.

Users should easily understand the interface of the product during the first interaction

This feature of the application should be compatible on both Android and IOS operating systems

The application does not grant access until the user creates a strong password.

WORK BREAKDOWN STRUCTURE

Work breakdown structure is a project management tool that takes a step by step approach to complete large projects with several moving pieces.

Workbreakdown structure is also the visualization of the work in the form of a hierarchy by dividing it into parts according to departments.

After works divide, they tabularize. By categorazing functional and nonfunctional requirements, we built a hierarchy. By this way, process monitoring is became easier.

It helps to determine which part of the project have problems while development and it helps to solve them in the fastest way.

It is logical to works countinue with this schedule for things go forward step by step and for these things do not collapse.

Dividing works make us to see better that how much project improves.

TIME ESTIMATION AND SPRINT PLANNING

The task had been divided into "user stories" by System Analyst. We could have followed a number of strategies, such as planning poker or t-shirt sizes, to determine the amount of time needed to complete each user story. We decided to choose Planning Poker and started to deal with the cards and distributed the points. The reason weve gone with Planning Poker is that we can easily monitor our speed of labor and optimize it accordingly.

Since We have followed the Scrum Poker, As a Scrum Master Ive distributed the tasks in accordance with our velocity. For the first sprint, We dealt with 23 points of task and there was no rollover thus we increased the velocity. Contrary to general convention weve raised the velocity of the project time.

Frontend / UI

1.1.1.1 Showing Photos of the Foods From Nearby Restaurants 13 +

1.1.1.2 Showing Previous Orders 5+ 1.1.1.3 Displaying Promotions on Restaurants' page 5 +

1.1.1.4 Displaying Restaurant Comments 3+

1.1.1.5 ETA Indicator 8 +

1.1.1.6 Status of the order 8 +

total: 42

Frontend / UX

1.1.2.1 Adding Live Support 8 +

1.1.2.2 Adding Note to Order 3 +

1.1.2.3 Write Restaurant Reviews 3 +

1.1.2.4 Avoiding long service times 5 +

total: 19

Backend / Integrity

1.2.1.1 Integrating with IOS & Android 13

total: 13

Backend / Legal

1.2.2.1 Providing Industry Standart Encryption 13 +

total: 13

Backend / Database

1.2.3.1 Create Tables 5 +

1.2.3.2 Read Tables 5 +

1.2.3.3 Update Tables 5+

1.2.3.4 Delete Tables 5+

total:20

overall total: 107

Sprint 1

Goal of the Sprint 1: Users can list the restaurants and choose what they'll order

1.1.1.1 Showing Photos of the Foods From Nearby Restaurants 13

1.1.1.3 Displaying Promotions on Restaurants' page 5

1.2.3.1 Create Tables 5

0.0.0.0 Installation and operation of necessary environments 3

velocity: 23

Sprint 2

Goal of the Sprint 2: Users can order and restaurants receive the order as well

1.2.3.2 Read Tables 5

1.2.3.3 Update Tables 5

1.2.3.4 Delete Tables 5

1.1.1.2 Showing Previous Orders 5

1.1.1.4 Displaying Restaurant Comments 3

velocity: 23

Sprint 3 Goal of the Sprint 3: Users can spectate the status of their order and also user data encrypt so that users data security is assured 1.2.2.1 Providing Industry Standart Encryption 13

1.1.1.5 ETA Indicator 8

1.1.1.6 Status of the order 8

velocity: 29

Sprint 4

Goal of the Sprint 4: User can take a few more action to specified their order, can consult customer relations department about their

1.1.2.2 Adding Note to Order 3

1.1.2.1 Adding Live Support 8

1.1.2.3 Write Restaurant Reviews 3

1.1.2.4 Avoiding long service times 5

1.2.1.1 Integrating with IOS & Android 13

velocity: 32

KICK-OFF

The kickoff meeting is a chance to introduce our project to the team, discuss how to collaborate, and set up common project controls and goals. It seeks to cover concerns including how to communicate, how frequently we will meet, what the schedule is, what can cause the project to go longer than expected, and how to handle this circumstance. During the meeting, our team will be dealing with these highlights:

Project goals: The objectives, goals and requirements of the project will be reviewed and discussed with the team.

Schedule: The team will clarify checkpoints, prioritize them and create an approximate timeline.

Roles and responsibilities: Each team member's role in the project and what they will be responsible for, will be determined.

Budget and resources: The budget determined for the project and the resources provided will be discussed. Limitations, exceptions and constraints for the budget will be set.

Risks and risk handling: The team will talk about the risks that could arise during the project and how to solve the problem with the least amount of damage.

Stakeholders: The team will discuss about the individuals, organizations, communities, and enterprises that must be involved and may be impacted by the project's actions.