SOFTWARE ENGINEERING ALM-1

TOPIC : ROLE PLAY ON SCRUM PROCESS

BATCH-7

Team Members:
24EU04310- Jennish – Team Lead / Scrum Master
24EU04312- Rachitha – Manager
24EU04307- Ritwik – Client / Product Owner
24EU04311- Saryu – Developer
24EU04313- Chaitanya Verma-Developer
24EU04308- Chaitanya Sri-Tester
24EU04309- Geethika – Designer

PICTURE OF THE ROLEPLAY

 SOFTWARE ENGINEERING ALM-1

Introduction to Scrum Software Development

Scrum is part of agile software development and teams practice agile. The name comes from
the sport of rugby, where scrum is a formation where everyone plays a specific role, but
everyone is working towards a quick adoption of strategies.
It enables teams to deliver high-value work iteratively and incrementally, ensuring quick
feedback and high adaptability.

Core Philosophy of Scrum

Scrum is based on three pillars:
• Transparency- All aspects of the process must be visible to those responsible for the
outcome.
Everyone (developers, product owner, stakeholders) should see the same truth.
Common tools for transparency:Visible task boards,Burndown charts,Clear Definition
of Done (DoD)
• Inspection- Scrum teams frequently inspect the product and the process to detect
unwanted variances.
Inspections are done at various points:
• During Daily Scrum (checking progress)
• At Sprint Review (validating deliverables)
• At Retrospective (improving processes)
• Adaptation-If a deviation is found during inspection, the process or material must be
adjusted immediately.
Scrum provides multiple points for adaptation:
• Sprint Planning: adjust goals based on capacity.
• Daily Scrum: adapt daily work.
• Retrospective: adapt processes and collaboration.
Scrum, known for its empirical process framework, revolves around three core
pillars: transparency, inspection, and adaptation. At the heart of Scrum lies transparency, an
overarching principle that centers on open and unobstructed communication.

Scrum Team Structure

The Scrum Team is small, cross-functional, and self-managing, comprising three distinct
roles:
1. Product Owner (PO):
▪ Represents the voice of the customer.
▪ Manages the Product Backlog.
▪ Ensures that the team works on the most valuable features first.
▪ Has the authority to accept or reject work.
2. Scrum Master (SM):
▪ A servant leader and coach for the team.
▪ Ensures Scrum is understood and enacted correctly.
▪ Removes impediments that hinder team progress.
▪ Facilitates Scrum events.
▪ Shields the team from external distractions.
3. Development Team:
▪ Cross-functional members such as developers, designers, testers, etc.
▪ Responsible for delivering potentially shippable product increment.
▪ Self-organizing with no hierarchy.
 SOFTWARE ENGINEERING ALM-1

Scrum Master provides key information for transparency and progress tracking.
❖ Product Backlog
▪ A dynamic list of all required features, enhancements, bug fixes, and technical
tasks.
▪ Managed solely by the Product Owner.
▪ Continuously refined and reprioritized.
❖ Sprint Backlog
▪ A subset of Product Backlog selected during Sprint Planning.
▪ Contains the Sprint Goal, the selected User Stories, and the plan to deliver
them.
▪ Owned by the Development Team.
❖ Increment
▪ The sum of all completed work at the end of a Sprint.
▪ Must be in a usable condition, even if not released.
▪ Must meet the Definition of Done (DoD).
Scrum Events
Scrum prescribes five formal events, each designed to enable key aspects of empirical
process control.
1. The Sprint
• A time-boxed event (1 to 4 weeks).
• The heartbeat of Scrum — all development happens here.
• A new Sprint starts immediately after the previous one ends.
• No changes are allowed that jeopardize the Sprint Goal.
2. Sprint Planning
• Time-boxed to 8 hours (for 1-month Sprint).
• Held at the beginning of each Sprint.
• The Scrum Team decides:
• What can be delivered in the Increment.
• How the work will be achieved.
Inputs:
Product Backlog
Past performance
Team capacity
3. Daily Scrum
• A 15-minute daily meeting for the Development Team.
• Same time, same place, every day.
• Helps synchronize activities and plan for the next 24 hours.

Each member answers:

1. What did I do yesterday?
2. What will I do today?
3. Are there any impediments?
4. Sprint Review
• Time-boxed to 4 hours (for 1-month Sprint).
• Held at the end of the Sprint.
• The team presents the Increment to stakeholders.
• Feedback is collected for the next Sprint.
 SOFTWARE ENGINEERING ALM-1

• Key Activities:
✓ Demo of completed work
✓ Discuss backlog status
✓ Gather feedback
✓ Update Product Backlog
5. Sprint Retrospective
• Time-boxed to 3 hours (for 1-month Sprint).
• Held after Sprint Review, before the next Sprint.
• Aimed at continuous improvement.
6. Definition of Done (DoD)
• A formal checklist of criteria which the Increment must satisfy.
• Ensures quality and consistency.
7. Scrum Lifecycle
➢ Product Owner creates and prioritizes the Product Backlog.
➢ The team selects items during Sprint Planning and develops them in time-
boxed Sprints.
➢ After each Sprint, they conduct a Review and Retrospective to improve and
plan the next cycle

Advantages of Scrum
❖ Improved product quality
❖ Early and continuous delivery
❖ Quick feedback loop
❖ Reduced time to market
❖ Greater team collaboration and morale
❖ Increased transparency and control
Challenges in Scrum
❖ Requires high team discipline and maturity
❖ Misinterpretation of roles and responsibilities
❖ Stakeholder resistance to frequent changes
❖ Needs a supportive organizational culture
 SOFTWARE ENGINEERING ALM-1

SCRUM ROLE PLAY: Smart Health App

Project: Health App with Step Counter, Calorie Tracker, Heartbeat Monitor

Cast & Roles:

Jennish - Scrum Master
Rithwik - Product Owner
Rachitha - Manager
Chaitanya Varma - Developer 1
Saryu - Developer 2
Geethika - UI/UX Designer
Chaitanya Sri - Tester

➢ Scene 1: Sprint Planning Meeting

Sprint Planning Call
Jennish (Scrum Master):
“Alright team, welcome to our Sprint Planning session for the Smart Health App. We’ve got
a two-week sprint ahead. Mr. Rithwik, please walk us through the product priorities.”
Rithwik (Product Owner):
“Thanks, Jennish. Based on user research and current trends, the MVP features we need are:
1. Step Counter
2. Calorie Tracker
3. Heartbeat Monitor UI
4. Health Dashboard basics”
“These features will give us a good start. We’ll collect feedback from beta users later.”
Rachitha (Manager):
“Let’s also ensure our designs are user-friendly. We don’t just want functional features, we
want a delightful experience. Rithwik, any UX expectations from the start?”
Mr. Rithwik (PO):
“Yes — minimalist design, readable fonts, and friendly color schemes. Geethika, you’ll be
key here.”
Geethika (Designer):“Noted. I’ll share initial wireframes within 48 hours.”
Chaitanya Varma (Developer 1):
“I’ll begin integrating the step counter using Android’s native sensors.”
Saryu (Developer 2):“I’ll handle calorie calculations and support UI integration once
designs are ready.
Chaitanya Sri (Tester):
“I’ll prep test cases in parallel. If you all can send API and UI components early, I’ll get
started quicker.”

Rachitha (Manager):
“Let’s remember — keep documentation updated. I want our work to be trackable and re-
usable. Jennish, help ensure blockers don’t slow us down.”

Jennish (SM):
“Absolutely, Rachitha. We’ll keep communication tight. Final Sprint Goal:
‘Deliver a functional MVP with step count, calories, heartbeat UI, and dashboard layout
ready for feedback.’
Let’s crush this Sprint!”
 SOFTWARE ENGINEERING ALM-1

➢ Scene 2: Daily Scrum

Team Standup Call
Jennish (Scrum Master):“Time for our daily sync. Stick to three points:
1. What you did yesterday?
2. What’s next?
3. Any blockers?”
Chaitanya Varma (Dev 1):
Yesterday: Integrated basic step counter.
Today: Working on real-time updates.
Blocker: Device permission inconsistencies.
Saryu (Dev 2):
Yesterday: Created calorie logic formula.
Today: UI binding.
Blocker: Waiting for finalized designs.
Geethika (Designer):
Yesterday: Completed dashboard wireframe.
Today: Starting heartbeat UI.
Blocker: None.
Chaitanya Sri (Tester):
Yesterday: Reviewed step counter build.
Today: Preparing performance test cases.
Blocker: Still need calorie module.
Rithwik (PO):
“Designs look great so far. Geethika, let’s keep font accessibility in mind. Also, I’ve got early
feedback from potential users – they’d love personalized daily health tips.”
Rachitha (Manager):
“That’s great insight. Let’s add it to the backlog for Sprint 2. Also, keep communication
sharp — Jennish, please facilitate a mid-sprint check tomorrow.”
Jennish (SM):
“Got it. I’ll set up a brief sync. Let’s stay focused and flag any issues early!”

➢ Scene 3: Mid-Sprint Check-in

Manager-led check
Rachitha (Manager):
“Quick pulse check. Are we on track? Anything that might block timely delivery?”
Chaitanya Varma (Dev 1):
“Step counter is done and stable. I’ll start cleanup and minor bug fixes.”
Saryu (Dev 2):
“Calorie calculations are wired up. Just verifying edge cases.”
Geethika (Designer):
“Heartbeat UI is ready. Final files will be shared today.”
Chaitanya Sri (Tester):
“Got it. I’ll begin exploratory testing tonight.”
Rithwik (Product Owner):
“Looks promising. Don’t forget — we need a clean demo for the stakeholders in the Sprint
Review. Show visual progress.”
Jennish (Scrum Master):
“Let’s document known issues in Jira so we don’t miss them during the Retrospective.
Thanks, everyone!”
 SOFTWARE ENGINEERING ALM-1

➢ Sprint Review
Sprint Demo to Stakeholders
Rachitha (Manager):“Alright, let’s begin. What’s ready to show?”

Chaitanya Varma (Dev 1):

“Step counter is working and updates instantly with a smooth UI.”
Saryu (Dev 2):“Calorie tracker adjusts based on user age and step data.”

Geethika (Designer):
“Dashboard is responsive, clean, and aligned with color guidelines. Heartbeat UI is functional
and themed.”
Chaitanya Sri (Tester):
“Tested everything end-to-end. Minor UI bugs were fixed. Step accuracy is 96%.”
Rithwik (Product Owner):
“Fantastic job! This looks production-ready.I am genuinely impressed with this Sprint’s
outcome!
Everyone performed their role with dedication, and the collaboration between development,
testing, and design was seamless.
This version is not only functional, but it’s clean, user-ready, and better than I expected.
Huge kudos to the entire team — I’m extremely satisfied. Let’s get ready to amaze our users
in the next Sprint! ”

➢ Sprint Retrospective
Team Huddle – Reflecting on Sprint 1
Jennish (Scrum Master):
“Alright team, time for our Sprint Retrospective. Let’s follow our three-question format:
1. What went well?
2. What didn’t go well?
3. What can we improve next Sprint?”
Chaitanya Varma (Developer 1):
“Well: The team was cooperative and quick to solve issues.
Didn’t go well: Some delay in sensor integration.
Improve: Start device testing earlier.”
Saryu (Developer 2):
“Well: I enjoyed pairing with Geethika for UI integration.
Didn’t go well: Late access to final designs.
Improve: Try to sync up design and development sooner.”
Chaitanya Sri (Tester):
“Well: Testing was thorough this Sprint.
Didn’t go well: Had to wait for some components.
Improve: Get access to builds earlier.”
Geethika (Designer):
“Well: Feedback loop with Rithwik helped polish the design.
Didn’t go well: Too many small revisions late in Sprint.
Improve: Finalize designs earlier in planning.”
Rachitha (Manager):
“I appreciate how everyone stayed committed and transparent throughout.
Documentation was solid. Let’s just try to reduce last-minute rush next time.”
 SOFTWARE ENGINEERING ALM-1

Rithwik (Product Owner):

“I’m honestly beyond satisfied with this team’s performance.
You all took the vision seriously, communicated openly, and delivered beyond expectations.
I especially loved how feedback was implemented quickly, and everyone respected timelines
and quality.”
Jennish (Scrum Master):
“Well said, Rithwik. Let’s carry this energy into our next Sprint Planning. Great job, team!”

➢ Final Scene: Client Review & Project Closure

Project – Client Demo Day

Rachitha (Manager):
“Thank you all for joining us today. We’re proud to present the final version of the Smart
Health App. All planned features — step count, calorie tracker, heartbeat monitor, and the
user dashboard — have been implemented across multiple sprints.”

Rithwik (Product Owner):

“Fantastic job! As the client and product owner, I’m thrilled with the result — this app
reflects exactly what we set out to build. The team has exceeded expectations. Thank you
all!”

Final Team Closing Statements

Jennish (Scrum Master):
“This journey has been a great example of the power of Agile and teamwork. Every challenge
turned into an opportunity, and every sprint took us closer to excellence.”

Rithwik (Product Owner):

“Seeing the final product today, I can confidently say — this team exceeded expectations.
Thank you all for your commitment, creativity, and collaboration.”

Rachitha (Manager):
“This app wasn’t just built — it was crafted with care. A heartfelt congratulations to each one
of you for making it happen.”

Entire Team Together:

“Thank you! Together we build. Together we deliver.”

FROM
CSE-5
BATCH-7