A Case Study on Zomato - How Agile Can Help to Generate Early Feedback While Building New Features

  • Rate and Review
  • Filters
  • Online Ordering ( Payment )
  • Users are not involved in the design and implementation stages so users are often not aware of what they want at the end. They start raising change requests and new features later in the process when they’re harder to accommodate.
  • Deadline creeps — when one phase in the process is delayed, all the other phases are delayed.
  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change by following a plan
  • Kanban
  • Scrum
  • XP ( Extreme Programming )
  • Crystal
  • DSDM ( Dynamic Systems Development Method )
  • FDD ( Feature Driven Development )
  • Lean
  • Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. This is based upon 3 scrum pillars ( Transparency, Inspection, Adaptation )
  • Lean Thinking reduces waste and focuses on the essentials.
  • The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules.
  • Scrum Master
  • Product Owner
  • Developers
  • Product Backlog
  • Sprint Backlog
  • Increment
  • Sprint
  • Sprint Planning
  • Daily Scrum
  • Sprint Review
  • Sprint Retrospective
  • Analyze requirements and break them down on the basis of features and sub-features level.
  • The feature is known as Epic
  • All sub-features related to common features will lie under the same Epic
  • Sub features are known as user stories.
  • Break the total work of Epics into multiple releasable chunks (also known as a user story)
  • Start analysis for User Story — 1
  • Design of Feature1
  • Implementation of User Story — 1
  • Testing of Feature1
  • Release User Story — 1 as a working increment and move to User Story — 2
  • Based upon team velocity, the team can work on multiple user stories of the same feature or a couple of stories of different features at the same time too.
  • Rate and Review
  • Filters
  • Online Ordering ( Payment )
  • Daily Scrum is to inspect progress toward the Sprint Goal
  • Adapt the Sprint Backlog as necessary, adjusting the upcoming planned work
  • During Sprint review developers will showcase the increment of the current sprint and gather feedback.
  • The purpose of the Review is to inspect the outcome of the Sprint and determine future adaptations. This is never a PowerPoint presentation but it is a working session.
  • The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness
  • Inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done.
  • Ideate
  • Design
  • Implement
  • Test
  • Deploy
  • Embrace Uncertainty
  • Welcome Changes
  • Celebrate Failures
  • Always Learning
  • People First
  • Full Collaboration
  • Value Obsession

--

--

--

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

GraalVM + AWS Lambda or solving Java cold start problem

Building a model of a Doom level

Pathway to learn DID for engineers (reliable source and references)

Good observability is simply more important than good testing

Git — Cheat Sheet

var deathMethod

Bezop / Bezex Community Report!

🏆I ❤️ Pika Finance🏆

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Snehil Mishra

Snehil Mishra

More from Medium

I discovered the Discovery document or how to form an idea using Discovery in the Software…

6/28 #ProductDiaries: Project Brainstorm

The Pen Problem: The PO and Quality

Agile Interview Talks#8