SCRUM AGILE
SOFTWARE
DEVELOPMENT MODEL
Aahish Aayan(1), Hardik Kumar(23), Manavendra Sing(33), Oorja
Saxena(43)
INTRODUCTION TO SCRUM
• Scrum is an Agile framework designed for managing and completing complex projects. It
emphasizes iterative progress through regular feedback and adaptation.
• Key Principles:
• Iterative Development: Work is divided into small, manageable units called sprints,
typically lasting 2-4 weeks.
• Collaboration: Cross-functional teams work together, involving all stakeholders to ensure
the product meets the requirements.
• Flexibility: Scrum is adaptable to changes, allowing teams to respond quickly to new
requirements or challenges.
PRINCIPLES OF SCRUM
• Small working team used to maximize communication, minimize overhead and maximize
sharing of internal knowledge.
• Process must be adaptable to both technical and business challenges to ensure best product
produced.
• Process yields frequent increments that can be inspected, adjusted, tested, documented and
built on.
• Development work and people performing it are portioned into clean, low coupling
partitions.
• Testing and documentation is performed as the product is built.
• Provides the ability to declare the product done whenever required.
SCRUM FRAMEWORK
• Scrum principles are consistent with the agile manifesto and are used to guide
development activities within a process that incorporates the following framework
activities: requirements, analysis, design, evolution, and delivery.
• Within each framework activity, work tasks occur within a process pattern (discussed in
the following paragraph) called a sprint.
• The work conducted within a sprint (the number of sprints required for each framework
activity will vary depending on product complexity and size) is adapted to the problem at
hand and is defined and often modified in real time by the Scrum team.
• Scrum emphasizes the use of a set of software process patterns that have proven
effective for projects with tight timelines, changing requirements, and business criticality.
Each of these process patterns defines a set of development actions:
SCRUM DEVELOPMENT
ACTIVITIES
• Backlog—a prioritized list of project requirements or features that provide business value for
the customer. Items can be added to the backlog at any time (this is how changes are
introduced). The product manager assesses the backlog and updates priorities as required.
• Sprints—consist of work units that are required to achieve a requirement defined in the
backlog that must be fit into a predefined time-box (typically 30 days). Changes (e.g.,
backlog work items) are not introduced during the sprint. Hence, the sprint allows team
members to work in a short-term, but stable environment.
• Scrum meetings—are short (typically 15 minutes) meetings held daily by the Scrum team.
Three key questions are asked and answered by all team members [Noy02]:
• What did you do since the last team meeting?
• What obstacles are you encountering?
• What do you plan to accomplish by the next team meeting.
SCRUM
PROCES
S
FLOW
SCRUM FRAMEWORK OVERVIEW
• Roles:
• Product Owner: Prioritizes the product backlog and ensures the team delivers value to the
customer.
• Scrum Master: Facilitates the Scrum process, removes impediments, and supports the team.
• Development Team: Cross-functional members who work together to deliver the product
increment.
• A team leader, called a Scrum master, leads the meeting and assesses the responses from
each person. The Scrum meeting helps the team to uncover potential problems as early as
possible. Also, these daily meetings lead to “knowledge socialization” [Bee99] and thereby
promote a self-organizing team structure.
• Demos—deliver the software increment to the customer so that functionality that has been
implemented can be demonstrated and evaluated by the customer. It is important to note
that the demo may not contain all planned functionality, but rather those functions that can
be delivered within the time-box that was established.
SCRUM FRAMEWORK OVERVIEW
• Events:
• Sprint: A time-boxed iteration, usually 30 days, where work is completed and reviewed.
• Sprint Planning: Team plans the work for the upcoming sprint.
• Daily Scrum: 15-minute daily meeting where team members answer three questions:
• What did you do since the last Scrum meeting?
• Do you have any obstacles?
• What will you do before the next meeting?
• Sprint Review: Demonstrate and inspect the work done at the end of the sprint.
• Sprint Retrospective: Reflect on the sprint and plan for improvements.
• Artifacts:
• Product Backlog: A prioritized list of product features desired by the customer.
• Sprint Backlog: Specific features assigned to the sprint.
• Increment: New functionality demonstrated at the end of the sprint.
SCRUM VALUES & BENEFITS
• Scrum Values:
• Commitment: Team members commit to achieving the goals of the sprint.
• Focus: Everyone focuses on the work of the sprint and the goals of the Scrum team.
• Openness: Team members and stakeholders are transparent about the work and the
challenges.
• Respect: Everyone respects each other’s skills, experience, and efforts.
• Courage: Team members have the courage to do the right thing and tackle tough problems.
• Benefits:
• Increased Transparency: Regular meetings and updates keep everyone informed about the
project’s progress.
• Improved Product Quality: Continuous testing and reviews ensure high-quality outcomes.
• Higher Customer Satisfaction: Frequent delivery of increments allows for regular feedback
CASE STUDY : ZOMATO
CHALLENGES FACED BY ZOMATO
• Market Demands:
• Rapidly changing customer preferences in the competitive food tech industry
• Quick Feature Releases:
• Need for faster innovation and feature deployment to enhance user experience
• Global Team Coordination:
• Difficulty in coordinating and communicating effectively across distributed teams
• High Quality:
• Balancing speed with thorough testing to maintain product quality.
• Scalability:
• Ensuring systems can handle increasing loads and user demands as Zomato expands.
• User Feedback:
• Integrating customer insights into the development process for continuous improvement.
SCRUM IN ZOMATO
• Adoption of Scrum:
• Transitioned from traditional methods to Scrum for more agility and flexibility.
• Formed cross-functional teams to enhance collaboration and efficiency.
• Sprint Cycles:
• Introduced regular sprints for continuous delivery of features.
• Frequent reviews and retrospectives to ensure continuous improvement.
• Scrum Roles:
• Product Owner: Prioritizes the backlog based on business value and customer feedback.
• Scrum Master: Facilitates Scrum processes and removes impediments.
• Development Team: Delivers potentially shippable increments of the product at the end
of each sprint.
RESULTS & BENEFITS FOR
ZOMATO
• Improved Productivity:
• Faster delivery of new features and updates.
• Enhanced ability to respond to market changes and user feedback
• Enhanced Collaboration:
• Better communication and coordination across global teams.
• Use of Scrum events to align team efforts and resolve issues promptly
• Increased Customer Satisfaction:
• More frequent releases leading to timely updates and enhancements.
• Focus on customer needs through iterative development and regular feedback.
THANK YOU
