AGILE SCRUM

Question 1 – write Agile Manifesto

Scrum Project Name: Scrum Foods (Foods Delivery Applications)
Scrum Project Description:
Scrum Foods provides fast, reliable online food delivery application targeting
customers of all age group offering 24/7 service along with tracking of the
delivery real time

Product Vision – Meeting – Discussion – Document –

AGILE SCRUM
 AGILE SCRUM

Product Vision – Description – Notes

Customer:

Registration, Login, Search and View restaurants, View restaurant's menu,

Order food, Payment, Tracking, Cancel order, Feedback & Rating and Logout.

Delivery Boy: Registration, Login, View orders, Select and accept orders,
Order pickup and delivery, Status updates, Payment (COD), View Feedback,
Raise Issues, View Deliveries report and revenue generated, Logout.
 AGILE SCRUM
Restaurants:

Registration, Login, View Orders, Delivery Boy Verification, Payment, View

Feedback, Raise Issues, View revenue generated through Scrum Food app,
Logout

Regional Admin:

Admin Login, Tracking/status, Customer feedback, Managing Regional

delivery boys and restaurant , View regional revenue, Issues, Refunds, View
payment made to regional restaurant and Logout.

Admin: Login, Managing Regional Admin, Issues, Customer Feedback,

Approval/Rejections privileges on restaurants, Delivery boy, Restaurants and
Regional Admin requests, Resolve Issues and Logout

Business Owner:

Login, Issues, Reports, Update payments for restaurants and delivery boys
and Logout

End of Product Vision

User Story Workshop

How to write a user story:

Take a Sticky Note and take a contract colour Sketch Pen and write the user
story in CAPITAL letters only.

Make sure the user story is short, clear and unambiguous and one Scrum
Developer can develop in one agreed sprint.

If you come across complex, big User stories… these are called epics.

We can divide the epics into Themes and then into User Stories

Finalized User Stories Count:

AGILE SCRUM
AGILE SCRUM
AGILE SCRUM
AGILE SCRUM
 AGILE SCRUM

Adding BV and CP to User stories

BV – Business Value This is not the cost of Development or the complexity of

the feature. Business Value is how important is this feature (user Story) to the
Business. This is estimated by Scrum Currency Notes. We provide Rs 1000. Rs
 AGILE SCRUM
500, Rs 100, Rs 50, Rs 20 and Rs 10 Denominations. These estimations are
done by the Stakeholders (Clients). If different values are selected by the
stakeholders, then discussions will happen, and they agree to one BV value to
that user story.

CP – Complexity Points

CP is also known as Story Points (SP). CP is the effort required by the Scrum
Developers to develop this feature (user story) using technology. Efforts
include time taken to solve the complexity and write the code. CP is estimated
by the Scrum Developers by using Poker cards. We provide pokers with values
“?”, 1, 2, 3, 5, 8, 13, 20, 40, 100 and BIG. If the entire Project development takes
200 points, then this user story coding effort will be… how many points? …
Thinking in this way, Scrum Developers will give CP to the User story). If
different values are selected by the Scrum Developers, then discussions will
happen, and they agree to one CP value to that user story.

ANS: AGILE

Agile Manifesto is discovering new ways to better deliver our products.

It has Four Main Values

1.Individual and Interactions / Over processes and tools.

2.Working Products / Over Comprehensive documents

3.Customer Collaborations / Over Contract Negotiation.

4.Responding to Feedback / Over Following a Plan.

Agile has 12 principles:

1. Our highest priority is to satisfy the customer through early and continuous
delivery

2. welcome changing requirements, even late in development

3. Deliver Working Product frequently

4.Business-people and cross-discipline teams must work together daily

 AGILE SCRUM
5. Build projects around motivated individuals and trust them to get the job done.
6.The most effective and efficient method of conveying information is face-to-face
conversation

7. Working product is primary measure of progress

8. Maintain a sustainable pace indefinitely

9.Give continuous attention to technical excellence

10. Simplicity- the art of maximizing the amount of work done is essential

11.Teams self-organize

12. Teams regularly reflect and adjust to become more effective

Question 2 – User Stories- Acceptance Criteria-BV-CP

Write minimum 40 User stories and their Acceptance Criteria along with their
BV and CP

User story:1 Task: Priority:

2 highest
AS A DELIVERY BOY
I WANT TO REGISTER IN SCRUM FOODSSO THAT I
CAN DELIVER ORDER
BV:500 CP:02
Acceptance criteria
Registration Screen Text Boxes for User Name,
Password, Nation ID
Mobile No, Email, Address, Phone Number
Click on Register Button Send Successful Notification to
the user

User story:2 Task:2 Priority:

 AGILE SCRUM
highest
AS A RESTAURANT OWNERI WANT TO VIEW ORDERS
SO THAT I CAN VIEW THE LIST OF ORDERS
BV:500 CP:02
ACCEPTANCECRITERIA
View Order, Display List of orders in the tabular Form

User story:3 Task: Priority: highest

As a customer
I want to add the
Address
So that I can get the order to the address

BV:500 CP:02
ACCEPTANCE CRITERIA
Text Box to enter. Business Rules:
Withintheradiusof5km

User story:4 Task:0 Priority:

2 highest
As a customer
I want to select the payment mode
So that can make payment of my choice
BV:500 CP:03
Acceptance criteria
Display payment modes, radio buttons to select
payment modes, payments button.
Business Rule. Can select only one payment mode

User story:5 Task:1 Priority: highest

As an admin
 AGILE SCRUM
I want to view the restaurants
So that I can approve their registration
BV 200 CP 2
Acceptance criteria
Register in the platform with the details

User story:6 Task:1 Priority: low

As a customer
I want view the price
So that I can order the food
BV:50 CP:1
Acceptance criteria
Display price in the list of menu items

User story:7 Task :2 Priority: low

As a customer
I want the contact number
of delivery boy
So that I can contact
delivery boy for the status
BV: 50 CP:1
Acceptance criteria
1.Display delivery boy
mobile number
2.Display delivery boy
name in tracking field
3.Display Delivery boy
picture

User story:8 Task:2 Priority: medium

As a restaurant owner
I want to provide time slots
So that customers able to see opening and
closing hours
BV:100 CP:2
ACCEPTANCECRITERIA
1.Click on restaurant dashboard
2.Add from time to time
3.Clickonsubmit
4.Display updated successfully
 AGILE SCRUM
User story:9 Task :2 Priority: high
AS A Business OWNER
IWANTTOVIEWRESTAURANTREVENUEREPORT
SOTHATICANVIEWTHERESTAURANT’S
REVENUE
BV:200 CP:3
ACCEPTANCECRITERIA
Select Reports
Select Revenue Reports
Select to and from date
Select Region (can select all)
Generate Report
Download Report in EXCEL

User story: 10 Task:3 Priority: high

AS A REG ADMIN
IWANT TO MANAGE REGIONAL RESTAURANTS
SO THAT, ICAN TRACK THE PERFORMANCE OF
REGIONAL RESTAURANTS.
BV:200 CP:3
ACCEPTANCE CRITERIA
CLICK ON PERFORMANCE OF
RESTAURANTS
SELECT FROM DATE TO DATE
CLICK ON GENERATE REPORT WHICH
INCLUDES
RESTAURANTS ID, NAME, REVENUE
CLICKONDOWNLOADREPORTSHOULDBEIN
EXCEL

User story:11 Task:2 Priority: medium

AS An ADMIN
I WANT TO SEE THE
REGIONAL REVENUE
REPORTS,
SOTHATICAN VIEW THE
REGIONAL
PERFORMANCE
BV:1OO CP:3
ACCEPTANCE
CRITERIA
Select regional dropdown
View performance of each
rest of that region in
tabular form which
includes rest name,
revenue, generated
DownloadinexcelorPD
 AGILE SCRUM
User story:12 Task :2 Priority: high
AS A CUSTOMER
I WANT TO CHAT WITH
REG ADMIN
SO THAT I CAN REQUEST
FOR REFUND
BV:200 CP:2
Acceptance criteria
1)Br-all mandatory
2)text box fields
3)display order id
4)text box ,for description
5)submit button
6)generate issue id
7)display successful

User story:13 Task:2 Priority: high

ASAHUNGRYUSER
IWANTTOBROWSENEARBYRESTAURANTS
SOTHATICANORDERTHEFOOD
BV:200 CP:2
ACCEPTANCE CRITERIA
1)Each restaurant entry displays its name,
cuisine type, and rating
2)This list can be sorted by distance or rating

User story:14 Task:2 Priority: high

AS A CUSTOMER
I WANT TO BROWSE
DIFFERENT
RESTAURANTS AND
MENUS
SO THAT I CAN FIND A
PLACE TO ORDER
FOOD
BV:200 CP:2
ACCEPTANCE
CRITERIA
1)The menu includes
dishes, prices and
descriptions
2)Show the restaurant is
open or closed

User story:15 Task:1 Priority: high

AS ACUSTOMER
I WANT
TOBROWSEFORSPECIFICDISHES
 AGILE SCRUM
AND CUISINES SOTHATI
CANFINDAPLACETOORDERFOOD
BV:200 CP:2
ACCEPTANCE CRITERIA
1)App displays relevant restaurant
and dishes matching the query

User story:16 Task:1 Priority: high

AS ACUSTOMER I WANT
TOFILTER RESTAURANTS
SOTHATI
CANFINDAPLACETOORDERFOOD
BV:200 CP:2
ACCEPTANCE CRITERIA
1)Filter restaurants by cuisine type
and dietary options (vegan, veg,
nonveg, egg)

User story:17 Task:2 Priority: high

AS ACUSTOMER
I WANT
TOTRACKMYORDER SO
THAT
I KNOW THE TIME OF
DELIVERY
BV:200 CP:2
ACCEPTANCE
CRITERIA
1)App shows real time
update on the order
status
2)Display estimated
delivery time

User story:18 Task 2 Priority: high

AS AUSER I WANT
TORATEANDREVIEWRESTAURANT
S SOTHATI
CANRATEANDREVIEWTHE
RESTAURANTS I HAVE VISITED
BV:200 CP:2
ACCEPTANCE CRITERIA
1)Can see reviews from other users to
help me make dining decisions

User story 19 Task 1 Priority: high

AS AUSER I WANT
 AGILE SCRUM
TOSAVEFAVOURITE
RESTAURANTS AND DISHES
SOTHATI
CANORDERFROMMYFAVOURITES
BV:200 CP:2
ACCEPTANCE CRITERIA
1)Access my list of favourites easily
for future orders

User story 20 Task 3 Priority: high

AS AUSER I WANT
TOVIEWPASTORDERHISTOR
Y SOTHATI CANORDERAGAIN
BV:200 CP:2
ACCEPTANCE CRITERIA
1)Can see the details such as
order items, total cost and order
date

User story 21 Task 2 Priority: medium

AS AUSER I WANT
TORECEIVE
NOTIFICATIONS
SOTHATI CANRECEIVE
UPDATES
BV:200 CP:2
ACCEPTANCE
CRITERIA 1)Notifications
for order confirmation
2)Notification for dispatch
3)Notification for delivery

User story 22 Task 2 Priority: high

AS ACUSTOMER I WANT
TOCONTACTCUSTOMERSUPPOR
T SOTHATI CANSUBMIT QUERIES
ORISSUES
BV:200 CP:2
ACCEPTANCE CRITERIA
1)Customer support section with
contact information

User story 23 Task 2 Priority: high

ASARESTAURANTOWNER
IWANTTORECEIVEANDMANAGEORDERS
SOTHATICANUPDATEORDERSTATUS
BV:200 CP: 2
 AGILE SCRUM
ACCEPTANCE CRITERIA
1)Manage order status
2)Notify restaurants about incoming orders

User story 24 Task 1 Priority:

medium
‘ASARESTAURANTOWNER
IWANTTOACCESSTOCUSTOMERREVIEWS
SOTHATICANVIEWANDRESPONDTOCUSTOMER
REVIEWS
BV:100 CP:4
ACCEPTANCE CRITERIA
1)Owners can address feedback
2)Owners can improve their services

User story 25 Task 1 Priority:

medium
ASACUSTOMER
IWANTTOAPPLYPROMOCODESANDDISCOUNTS
SOTHATICANORDERATLOWERPRICE
BV:100 CP:4
ACCEPTANCE CRITERIA
1)Active Promo codes

User story 26 Task 7 Priority: high

ASACUSTOMER
IWANTTOAPPLYPROMOCODESANDDISCOUNTS
SOTHATICANORDERATLOWERPRICE
BV:200 CP: 4
ACCEPTANCE CRITERIA
1)Active Promo codes

User story 27 Task 5 Priority: high

ASADELIVERYBOY
IWANTTOVIEWTHEORDERS
SOTHATIACCEPTTHEORDER
BV: 200 CP: 4
ACCEPTANCE CRITERIA
1)Order visibility
2)Real-time updates
3)Order details
4)Order filtering and sorting
5)Order map view
6)Order navigation
7)Order completion and
confirmation
 AGILE SCRUM
User story 28 Task 5 Priority: high
ASADELIVERYBOY
IWANTTOLOGIN
SOTHATICANACCEPTTHEORDER
BV:200 CP: 4
ACCEPTANCECRITERIA
1)User Authentication
2)Error Handling
3)Password security
4)Multi-factor Authentication
5)Compatibility and Usability

User story 29 Task 5 Priority: high

ASADELIVERYBOY IWANTTOVIEWFEEDBACK
SOTHATICANKNOWTHECUSTOMERSFEEDBACK
BV:200 CP: 4
ACCEPTANCECRITERIA
1)Access to feedback system
2)Feedback Visibility
3)Feedback sorting and filtering
4)Response Mechanism
5)User Support

User story 30 Task 5 Priority: high

ASAADMIN IWANTTOVIEWFEEDBACK
SOTHATICANKNOWTHECUSTOMERSFEEDBACK
BV:200 CP:4
ACCEPTANCECRITERIA
1)Access to feedback system
2)Feedback Visibility
3)Feedback sorting and filtering
4)Response Mechanism
5)User Support

User story 31 Task 3 Priority: high

ASARESTAURANTOWNER
IWANTTOVIEWFEEDBACK
SOTHATICANKNOWTHECUSTOMERSFEEDBACK
BV:100 CP:3
ACCEPTANCECRITERIA
1)Access to feedback system
2)Feedback Visibility
3)Feedback sorting and filtering
4)Response Mechanism
5)User Support

User story 32 Task 3 Priority: high

 AGILE SCRUM
AS AADMIN I WANT
TOKNOWTHEISSUES
SOTHATI
CANRESOLVETHEM
BV:200 CP:4
ACCEPTANCE
CRITERIA 1)Display
issue section 2)Sorting
and filtering of issues list
3)Editing and modifying
the issues

User story 33 Task 6 Priority: high

AS AREGIONAL ADMIN I
WANT
TOKNOWTHEISSUES
SOTHATI
CANRESOLVETHEM
BV:200 CP:4
ACCEPTANCE
CRITERIA 1)Display
issue section 2)Sorting
and filtering of issues list
3)Editing and modifying
the issues

User story 34 Task 2 Priority: high

ASARESTAURANTOWNER
IWANTTOVIEWREVENUEGENERATED
SOTHATIVIEWRESTAURANTSREVENUE
BV:200 CP:4
ACCEPTANCECRITERIA
Select Reports
Select Revenue Reports
Select to and from date
Select Region (can select all)
Generate Report
Download Report in EXCEL

User story 35 Task Priority:

2 low
ASARESTAURANTOWNER IWANTTOKNOWDELIVERYBOY
SOTHATIVERIFYTHEDELIVERYBOY
BV:50 CP:1
ACCEPTANCECRITERIA
ID proof
Punctuality and reliability
 AGILE SCRUM

User story 36 Task 2 Priority:

medium
ASACUSTOMER
IWANTTOVIEWTHECONTACTNUMBEROF
DELIVERYBOY
SOTHATICANCONTACTDELIVERYBOYFORTHE
STATUS
BV:100 CP: 2
ACCEPTANCECRITERIA
1.Display delivery boy mobile number
2.Display delivery boy name in tracking field
3.Display delivery boy picture

User story 37 Task 3 Priority: high

ASARESTAURANTOWNER
IWANTTOPROVIDETIMESLOTS
SOTHATCUSTOMERCANCHECKOPENINGAN
D CLOSINGHOURS
BV:200 CP: 2
ACCEPTANCECRITERIA
1.Click on restaurant dashboard
2.Add from time to time
3.Click on submit
4.Display updated successfully

User story 38 Task 1 Priority: medium

AS AUSER I WANT
TORECEIVE
NOTIFICATIONS
SOTHATI CANRECEIVE
UPDATES
BV: 200 CP: 2
ACCEPTANCE
CRITERIA
1)Notifications for order
confirmation
2)Notification for dispatch
3)Notification for delivery

User story39 Task 4 Priority: high

AS ACUSTOMER I WANT
TOCONTACTCUSTOMERSUPPOR
T SOTHATI CANSUBMIT QUERIES
ORISSUES
 AGILE SCRUM
BV:200 CP: 3
ACCEPTANCE CRITERIA
1) Customer support section with
contact information

User story 40 Task 4 Priority: medium

ASACUSTOMER
IWANTTOVIEWTHEORDER
SOTHATICANCANCELIT
BV: 200 CP: 3
ACCEPTANCECRITERIA
Order status
Method of cancellation
Refund policy Timeframe

user story:40 task: 4 Priority high

ASAREGIONALADMIN
IWANTTOTRACKTHEDELIVERY
SOTHATICANVIEWTHESTATUSOFTHEDELIVERY
BV 200 CV 3
ACCEPTANCECRITERIA
Real time tracking
Security and data privacy
User friendly Interface

Question 3– What is epic? Write 2 epics

Business Value and Complexity Points
ANS:
EPIC:
Epic is a large user story or a collection of related user stories that represents a
significant feature or functionality
Epics are high level, often spanning multiples prints or iterations, and they provide a
way to organize and prioritize work in a product backlog
2 Epics
1.Ratings and reviews:
As a user, I want to view ratings and reviews for restaurants on scrum foods, so that
I can make informed decisions about where to order food from.
As a user, I want to provide ratings and reviews for restaurants on scrum foods, so
that I
can share my experiences with other users and contribute to the community.
 AGILE SCRUM
Acceptance Criteria
● Users can view average ratings and reviews for each restaurant on the
restaurants details page
● Users can read detailed reviews and comments left by the other customers
● Users can sort and filter reviews based on criteria such as rating and relevance
● Users can rate the restaurants and leave a review after placing the order
● Users can edit or delete their own reviews within a specified timeframe
● Reviews are displayed in a way that provides helpful insights to other users
● The rating and review system maintains the integrity and authenticity of user
feedback
2.Epic: Real-Time Order Tracking for Food Delivery App
Description:
The real-time order tracking epic aims to provide users with a seamless and
transparent
experience by allowing them to track the status and location of their food orders in
real-time. This feature enhances customer satisfaction, reduces support inquiries,
and
improves overall user engagement.
User Stories:
As a customer, I want to see the live status of my order.
● Display the current status of the order, such as "order confirmed,"
"preparing" "out for delivery," and "delivered."
● Provide real-time updates as the order progresses through various stages.
As a customer, I want to track the location of my delivery.
● Integrate GPS or location services to show the delivery partner's real-time
location on a map.
● Allow customers to view the estimated time of arrival (ETA) based on the
delivery partner's location.
As a customer, I want to receive notifications for order updates.
● Send push notifications or SMS updates to inform customers about order
confirmation, preparation, and delivery status changes.
 AGILE SCRUM
● Provide delivery partner details, including name, contact information, and
a profile picture.
As a customer, I want to contact the delivery partner directly.
● Enable in-app chat or call functionality to allow customers to communicate
with the assigned delivery partner.
● Ensure privacy by using masked phone numbers or secure messaging
channels.
As a customer, I want to view the delivery route.
● Display the delivery route on the map, showing the path the delivery
partner will take to reach the destination.
● Allow customers to track the progress of the delivery in real-time along the
route.
As a customer, I want to provide feedback on the delivery experience.
● Allow customers to rate the delivery partner and overall delivery
experience after the order is delivered.
● Implement a feedback system with written comments to gather valuable
insights.
As a customer, I want to see estimated delivery time adjustments.
● Account for real-time traffic conditions and other factors that may affect the
delivery time.
● Update the estimated delivery time accordingly and inform the customer
promptly.
As a customer, I want to have a seamless tracking experience across platforms.
● Ensure the real-time order tracking feature is available and consistent on
all supported platforms (e.g., mobile app, web).
As an admin, I want to monitor order tracking performance.
● Provide analytics and reporting on order tracking metrics, such as average
delivery time and customer satisfaction ratings.
● Use data to identify areas for improvement and optimize the delivery
process.
 AGILE SCRUM
Acceptance Criteria:
Real-Time Order Updates:
● The app should provide real-time updates on the status of the user's order,
such as "Order received," "Preparing," "Out for delivery," and "Delivered."
Order Location Tracking:
● The app should display the live location of the delivery driver while en
route to the user's address.
● The map should update at regular intervals to reflect the driver's
movement accurately.
Estimated Delivery Time:
● The app should provide an accurate estimated time of delivery (ETA)
based on the driver's current location, distance to the delivery address,
and traffic conditions.
Delivery Notifications:
● Users should receive push notifications or in-app alerts for significant
order updates, such as when the order is dispatched for delivery or when
it is near the delivery address.
Map Zoom and Interaction:
● Users should be able to zoom in and out on the map to view the delivery
driver's route more closely.
● The map should support standard interactions, such as panning and
rotating, to improve the user experience.
Delivery Status History:
● Users should have access to the delivery status history, allowing them to
see the timeline of their order from placement to delivery completion.
Accuracy and Reliability:
● The real-time tracking information should be accurate and reliable,
providing users with the most up-to-date data available.
● The system should handle location updates efficiently, minimizing delays
or inaccuracies.
 AGILE SCRUM
Privacy and Security:
● The real-time tracking feature should adhere to data privacy regulations
and ensure that user location data is handled securely and used only for
order tracking purposes.
Compatibility:
● The real-time order tracking should work smoothly across various
platforms, including iOS and Android devices, as well as web browsers.
Opt-Out Option:
● Users should have the option to disable real-time order tracking if they prefer not
to share their location information.
User Education:
● Provide clear instructions or tooltips to educate users on how to use the real-time
order tracking feature effectively.
Support for Multiple Orders:
● If a user places multiple orders, the app should allow them to track each order
individually with its own status and location updates.
By meeting these acceptance criteria, the food delivery app can successfully
implement
real-time order tracking, providing users with a transparent and convenient way to
monitor their orders from the moment they are placed until they are delivered to their
doorstep.
Question 4 –What is the difference between BV and CP
Product Backlog
Your user stories will go into Product Back log
ANS: Difference between BV and CP
● Business Value (BV):
● Business Value refers to the perceived or quantifiable worth or benefit that
a specific task, feature, or requirement brings to the business or project.
● It is typically determined based on factors such as revenue generation,
cost savings, customer satisfaction, market competitiveness, strategic
alignment, and other business-related criteria.
 AGILE SCRUM
● Business Value helps prioritize tasks or features based on their importance to the
overall project goals and objectives.
● Examples of Business Value considerations: Increased revenue, improved
user experience, compliance with industry regulations, competitive
advantage.
Techniques used: Moscow, Currency notes technique
MOSCOW:
The MOSCOW technique is a prioritization and requirements management
technique used in project management and software development. It helps
stakeholders and project teams prioritize and categorize requirements or tasks
based on their importance and urgency. The acronym "MOSCOW" stands for the
four categories into which requirements or tasks are typically classified:
● Must Have: These are critical requirements or tasks that are essential for the
project's success. Without these, the project would likely fail to meet its objectives.
● Should Have: These are important requirements or tasks that are not absolutely
critical but significantly contribute to the project's value. They are high-priority
items that should be included if possible.
● Could Have: These are desirable requirements or tasks that would enhance the
project but are not essential. They are often considered nice-to-have features that
can be addressed if time and resources allow.
● Won't Have (this time): These are requirements or tasks that are deliberately
deprioritized and will not be included in the current phase of the project. They
may be considered for future iterations or versions.
● Complexity Points (CP):
● Complexity Points, also known as story points or function points, are a
measure of the relative complexity or effort required to complete a task,
feature, or requirement.
● They are used to estimate the effort, time, and resources needed to
implement a specific item.
● Complexity Points are often assigned based on factors such as technical
difficulty, development effort, integration challenges, and other technical or
 AGILE SCRUM
development-related criteria.
● Complexity Points help in assessing the workload and resource allocation
needed for different tasks or features.
● Examples of Complexity Points considerations: Integration with legacy
systems, technical dependencies, data migration, algorithmic complexity.
Techniques used: Planning poker
Planning poker:
Planning Poker is a consensus-based technique commonly used in Agile and Scrum
methodologies for estimating the effort or complexity of user stories or tasks. It helps
teams collaborate and arrive at a shared understanding of the work involved in a
particular item. The term "CP" in your question likely stands for "Complexity Points,"
which are used in Planning Poker to represent the relative effort or complexity of a
task.
Here's how the Planning Poker technique works:
Preparation:
● The team gathers to estimate the effort or complexity of user stories or
tasks that need to be completed in a sprint or iteration.
Estimation Cards:
● Estimation cards are used, each containing a number representing a
predefined range of Complexity Points (e.g., 0, 1, 2, 3, 5, 8, 13, 20, 40,
100).
● The cards are often designed such that the numbers increase non-linearly,
reflecting that as tasks become more complex, the uncertainty in estimates also
increases.
Facilitator:
●A facilitator (often the Scrum Master or Agile Coach) leads the session and
explains the process to the team.
Estimation Process:
● Foreach user story or task, the team discusses the requirements, assumptions,
and any relevant information.
 AGILE SCRUM
●Each team member selects an estimation card representing their individual view of
the Complexity Points required to complete the task. The card is kept face down.
Reveal and Discussion:
● After everyone has selected a card, all team members reveal their chosen
cards simultaneously.
● If there's a wide variation in estimates, team members have a discussion
to share their reasoning and insights. This helps clarify assumptions and leads to a
shared understanding.
Re-Estimation and Consensus:
● After the discussion, team members may revise their estimates by selecting a
different card based on the insights gained.
●The process of discussion and re-estimation continues until a consensus
is reached. The goal is to align the team's estimates.
Repeat for Each Task:
● The process is repeated for each user story or task in the backlog.
Final Estimate:
●The final estimate for each user story or task is often determined by the
mode or median of the estimates chosen by the team members.
Planning Poker helps mitigate individual biases and provides a collaborative and
transparent way to estimate work. It encourages discussions, helps identify potential
challenges, and allows the team to make informed decisions about how much work
can be taken on in a sprint or iteration in summary, Business Value focuses on the
business impact and significance of tasks or features, while Complexity Points focus
on the technical effort and complexity involved in implementing those tasks or
features. Both concepts are valuable in project management and software
development, as they help prioritize and plan work based on both business goals
and technical constraints.
Question 5 –Explain about Sprint
Sprint Understanding
What is sprint Duration: 2 Weeks - Your sprint Value
Scrum is a subunit of Sprint.
What is scrum Duration: 1 day – Your scrum Value?
 AGILE SCRUM
PBI: Product Backlog Item
Task: Unit of Work done by 1 Developer in 1 Scrum
WIP: Work in Progress
Sprint Backlog

ANS:
SPRINT:
In the context of software development and project management, a sprint is a time-
boxed, iterative development period during which a specific set of tasks and goals
are worked on by a development team. Sprint is a core concept in Agile
methodologies, such as Scrum, which emphasizes flexibility, collaboration, and
delivering value to the customer in shorter cycles.
Here are the key characteristics and components of a sprint:
●Time Frame: A sprint typically has a fixed duration, often ranging from 1 to 4
weeks. The duration is consistent across all sprints to provide a predictable cadence
for development and planning.
● Goals and Objectives: At the beginning of each sprint, the development team,
along with stakeholders, selects a set of user stories, features, or tasks to work
on during that sprint. These items are collectively referred to as the sprint
backlog.
● Planning: During sprint planning, the development team breaks down the
selected items from the product backlog into smaller tasks and estimates the
effort required for each task. The team commits to completing these tasks within
the sprint duration.
● Daily Stand-ups: Throughout the sprint, the team holds daily stand-up meetings
(also known as daily scrums) to discuss progress, obstacles, and plans. Each
team member shares what they've accomplished, what they're working on, and
any challenges they're facing. These meetings foster communication and
 AGILE SCRUM
collaboration.
● Development: The development team works on the tasks identified in the sprint
backlog. They collaborate closely, often using techniques like pair programming
and frequent code reviews to ensure high-quality work.
● Continuous Integration: Developers integrate their code changes into the main
codebase regularly, ensuring that the software remains functional and stable
throughout the sprint.
● Testing: Testing is an integral part of a sprint. Automated tests are run to validate
code changes, and manual testing may be conducted to ensure the quality of the
software.
● Review and Demo: At the end of the sprint, the development team conducts a
sprint review and demo. They showcase the completed work to stakeholders,
gathering feedback and validation. This helps ensure that the delivered features
align with expectations.
● Retrospective: Following the review and demo, the team holds a sprint
retrospective. They reflect on what went well during the sprint, what could be
improved, and actions to take in the next sprint. The retrospective encourages
continuous improvement.
● Incremental Development: Each sprint results in a potentially shippable product
increment, meaning that at the end of each sprint, a new version of the software
is available with additional features or improvements.
● Adaptability: Agile methodologies emphasize adaptability and the ability to
respond to changing requirements. If new priorities or insights emerge,
adjustments can be made in subsequent sprints.
Sprints allow development teams to iteratively deliver value to customers and
stakeholders in a controlled and predictable manner. By breaking down the work into
manageable chunks and continuously seeking feedback, Agile teams can enhance
collaboration, reduce risk, and improve the overall quality of the software being
developed.
Question 6 – Explain Product backlog and sprint back log
 AGILE SCRUM
Sprint Planning Meeting: All 8 Scrum Developers will gather before the sprint
starts and understand how many user stories, they can develop in 1 sprint (2
weeks), and move them from the product Backlog to the sprint Backlog. They
take inputs from Sprint Retrospective meeting.
Scrum Meeting – Daily Stand-up Meeting End of every Scrum, Scrum
Developers will participate in Scrum meeting. Here they must answer 3
Questions.
a. What task did you work in this scrum?
b. What task will you work on next scrum?
c. Any Challenges/impediments? When you will complete the user story?
ANS:
Product Backlog and Sprint backlog:
The Product Backlog is a dynamic, prioritized list of all the features, user stories,
enhancements, bug fixes, and other work items that need to be addressed over the
course of a project. It represents the entire scope of the product's development and
is managed by the Product Owner. The Product Backlog is continually refined and
updated based on feedback, changing requirements, and new insights. The Sprint
Backlog is a subset of the Product Backlog that represents the work that the
development team commits to completing during a specific time period called a
"Sprint."
A Sprint is a fixed-duration iteration, usually lasting two to four weeks, in which the
team Works on a set of items from the Product Backlog. The Sprint Back log is
created during the Sprint Planning meeting, where the development team selects a
set of items to work on based on their capacity and the priorities set by the Product
Owner

S.no Product backlog Sprint backlog

1 Anything that needed to Accomplish the Anything that needed to
project vision fulfil the sprint goal
2 Product owner owns Development team owns
3 Contains requirements, tasks, defects A subset of product
backlog items defined as
a priority by the product
owner
4 Every one contributes to the product Sprint planning meeting is
catalogue to refine the sprint
backlog items
5 Product back log evolves and changes will be NO changes are all owed
done by the PO to the sprint backlog items
 AGILE SCRUM
through the product lifecycle once the sprint has
started
6 Product backlog refinement meeting is to Sprint planning meeting is
refine the product backlog to refine the sprint
backlog items
7 Release burndown metric is used Sprint burn down metric is
used
8 Estimation is done at a user Estimation is done at
Story level activity or task level
9 Daily standup meeting does not discuss Daily standup meeting
product backlog items discusses the sprint
backlog in accordance
with sprint goal

Question 7 – What is impediments log? write 2 impediments

Impediments Log:
All challenges faced by the team will be logged in this impediments log
Once the Sprint is completed
1. From the Done state of the sprint Backlog, we will product Increment and we
can deliver it to
the client
2. Sprint Retrospective meeting: Only the Scrum Developers will participate
and will discuss about
Challenges faced and come up with lessons learnt. We can use these lessons
learnt in Sprint
planning meeting to select user stories for the next sprint.
3. Sprint Review meeting: All Stakeholders like Scrum Developers, Product
owner, Scrum master,
Client, 3rd party reviewers will participate. What they discuss is
• Velocity – How many CP is covered in this sprint
• Sprint Burn Down Chart
 AGILE SCRUM

Sprint 1
 AGILE SCRUM

Prepare Tasks from PBI

How many Scrums, we will have in this sprint?
Allocate Tasks to Developers
Scrum 1
Start Time:
End Time:
10
Duration:
Participant and Task Selected
Scrum Meeting
End of every Scrum, Scrum Developers will participate in Scrum meeting. Here
they must answer 3
Questions.
a. What task did you work in this scrum?
b. What task will you work on next scrum?
c. Any Challenges/impediments? When you will complete the user story?
Scrum 2
Scrum 3
Scrum 4
 AGILE SCRUM
Repeat the same activities for all scrums
Sprint 1 – Closing Activities
From the Done state of the sprint Backlog, we will product Increment and we
can deliver it to the client
What is the Product Increment we made now?

Sprint Retrospective meeting: Only the Scrum Developers will participate and
will discuss about Challenges faced and come up with lessons learnt. We can
use these lessons learnt in Sprint Planning
Meeting to select user stories for the next sprint.

Write here

Sprint Review meeting: All Stakeholders like Scrum Developers, Product

owner, Scrum master, Client, 3rd party reviewers will participate. What they
discuss is

We as team,
Write here

ANS:
Impediments Log:
An impediment log, also known as an issue log or obstacle log, is a document or tool
used in Agile software development to track and manage obstacles, bottlenecks, or
any
factors that impede the progress of a project or team.
2 Impediments:
● Delivery partner shortage in a specific region
● Technical issue causing intermittent order processing failure
Delivery partner shortage in a specific region:

Login ID 1
Description Delivery partner storage in specific
region
Impact Delays in order deliveries and increases
 AGILE SCRUM
customer dissatisfaction
Priority High (due to its impact on customer
experience)
Assigned to Operations team and HR team
Status Open
Action taken The operations team is actively
recruiting new delivery partners
Resolution Delivery partner recruitment efforts are
ongoing and the HR
team is streamlining the onboarding
process to expedite new
hires. Regular updates are being
provided in team meetings.

Technical issue causing intermittent order processing failure

Login ID 2
Description Technical issue causing intermittent
order processing failures
Impact Delays in order processing and potential
revenue loss
Priority High(due to its impact on revenue and
customer experience )
Assigned to Tech team and QA team
Status In progress
Action taken The tech team has identified the root
cause and is working on a fix.
The QA team is conducting extensive
testing to ensure the issue is resolved
Resolution The tech team has implemented a fix
and conducted through testing. The
issue has been resolved, and orders are
now processing smoothly.

Question 8 – Explain Velocity of the Team

Velocity – How many CP is covered in this sprint
ANS:
VELOCIT YOF THE TEAM:
Velocity refers to the measure of the amount of work a development team can
complete during a sprint.
 AGILE SCRUM
The calculation of velocity is performed by the development team itself, as they are
Responsible for estimating the effort required to complete each user story or
backlog item.
Story point estimation:
Story point estimation is a technique used in agile software development to estimate
the effort required for a specific task or user story. It's a relative measure of
complexity rather than a fixed time unit. Team members assign story points based on
their understanding of the work involved, considering factors like complexity, effort,
and uncertainty.
The actual time a story point represents can vary from team to team. For some, it
might equate to hours, while for others, it might represent days. It's important to
establish a consistent baseline with in the team so that story point estimates can be
used effectively for planning and prioritization.
Tracking completed work:
Tracking completed work in Agile development typically involves calculating the total
story points completed by the team over a specific time frame, usually a sprint or
iteration. Here's how you can calculate completed work:
● Identify Completed Stories: At the end of the sprint or iteration, review the user
stories or tasks that were completed and accepted as done.
● Sum Story Points: Add up the story points assigned to all the completed user
stories. Exclude any story points that were not fully finished or accepted during
the sprint.
● Calculate Total Completed Work: The sum of story points completed
represents the total completed work for that sprint.
This completed work can be used to calculate the team's velocity for that specific
sprint, as mentioned in the previous response. It provides insights into the team's
capacity and helps with future sprint planning and estimation.
Summing story points:
Summing story points involves adding up the numerical values assigned to
individual user stories or tasks during the estimation process in Agile development.
Story points are used to represent the effort, complexity, and size of a piece of work
relative to other items on the backlog. Here's how you can sum story points:
● List Completed User Stories: Gather a list of user stories or tasks that have
been completed during a specific sprint or iteration.
 AGILE SCRUM
● Identify Story Point Values: Each user story or task should have a story point
value assigned to it during the estimation process. These values are usually
relative, such as 1, 2, 3, 5, 8, 13, etc., representing increasing levels of
complexity or effort.
● Add Up Story Point Values: Sum up the story point values for all the completed
user stories or tasks. For example, if you completed user stories with story point
values of 3, 5, and 8, the sum would be 16.
The sum of story points provides a quantitative measure of the work completed by
the
team during a sprint. This sum is often used to calculate the team's velocity, which
helps
in future sprint planning and estimation.
Average velocity:
Average velocity in Agile development refers to the average amount of work,
measured
in story points, that a team completes during a series of sprints or iterations. It's a
key
metric used for planning and estimating future work. Here's how to calculate
average
velocity:
● Select a Time Frame: Choose a specific number of past sprints or iterations for
which you want to calculate the average velocity. For example, you might choose
the last 5 sprints.
● Sum Completed Story Points: Add up the total story points completed by the
team in each of the selected sprints. This will give you the total completed work
for the chosen time frame.
● Calculate Average: Divide the total completed story points by the number of
sprints or iterations you selected. This will give you the average velocity for that
period.
Formula: Average Velocity = Total Completed Story Points / Number of Sprints
Use for Planning: The average velocity can serve as a guideline for future sprint
 AGILE SCRUM
planning. It helps the team estimate how much work they can commit to in
upcoming
iterations based on their historical performance.
Keep in mind that average velocity is a rough estimate and can fluctuate based on
various factors. It's important to consider the team's capacity, any changes in team
composition, and improvements in estimation accuracy over time.
Question 9 – Draw Sprint Burn Charts and Product Burn Down Chart
Sprint Burn down Chart

Product Burn down Chart

ANS:
SPRINT BURNDOWNCHART

sprint burn down chart

12

10

0
1/26/2024 1/27/2024 1/28/2024 1/29/2024 1/30/2024 1/31/2024 2/1/2024

planed actual

Product burn down chart

 AGILE SCRUM

product burn down chart

12
10
8
6
4
2
0
1/26/2024 1/27/2024 1/28/2024 1/29/2024 1/30/2024 1/31/2024 2/1/2024

planed actual per=centage

Question 10 – Explain about Product Grooming

Product insights for improvement

Used for product grooming

ANS: PRODUCT GROOMING

Product grooming, also known as backlog grooming or refinement, is a crucial
activity in Agile development that involves preparing and refining items in the product
backlog to ensure they are well-understood, prioritized, and ready for development.
Let's break down the process step by step:

● Setting the Context: At the beginning of the backlog grooming process, the team
and relevant stakeholders come together to understand the overall goals and
objectives of the project. This helps set the context for the work to be done and
aligns everyone's understanding.

● Backlog Review: The product owner and the development team review the items
in the product backlog.

This involves assessing the user stories, tasks, and other items to ensure they are
accurate, up-to-date, and still relevant to the project's goals.
 AGILE SCRUM
● Prioritization: During backlog grooming, the team collaboratively prioritizes the
backlog items based on their value to the product and the needs of the users or
customers. This helps ensure that the most important and valuable work is
addressed first.

● Refinement and Estimation: In this step, the backlog items are refined to provide
clear and detailed descriptions. The team breaks down user stories into smaller
tasks and discusses the technical requirements. Estimation involves assigning story
points or other sizing metrics to each item, indicating the relative effort needed for
implementation.

● Dependency Analysis: The team examines potential dependencies between

backlog items. Identifying and understanding dependencies helps in planning the
order of implementation and managing potential bottlenecks.

● Acceptance Criteria: Well-defined acceptance criteria are established for each

backlog item. These criteria outline the conditions that must be met for the item to be
considered complete and ready for delivery. Clear acceptance criteria help prevent
misunderstandings and ensure a shared understanding of what is expected.

● Backlog Grooming Meetings: These are recurring meetings where the product
owner and the development team come together to perform the activities mentioned
above. These meetings often occur before sprint planning sessions to ensure that
the upcoming sprint backlog is well-prepared.

Backlog grooming is an iterative process that helps maintain a healthy and well-
organized product backlog. It ensures that the development team always has a
prioritized list of well-defined, estimated, and ready-to-develop items. This, in turn,
supports the efficient planning and execution of sprints and helps the team deliver
value to customers in a more predictable and effective manner.

Criteria Product owner Scrum master

Nature of work Collaborates with all the Acts as a team coach and
stakeholders and brings is responsible for
the vision of a product maintaining the quality of
into the product backlog the product
Responsibility Responsible for Ensures the scrum
 AGILE SCRUM
completing the project on frameworks followed and
time. Acts as an helps the development
intermediary between team create a quality
development team and product
the customers
Accountability Responsibleforproject Accountable for the
backlog and the timely quality of the entire
completion of the product project and for giving
and for providing updates updates to the
to the clients and management about the
stakeholders completion of the product
Reporting Reports to top Reports to top
management and clients management about the
efficiency of the team and
the quality of the product
Qualities Communication and the Thorough knowledge of
Leadership skills, scrum theory and
creativity, practices. Being able to
critical thinking and a lead the team but without
sharp the sense of authority
mind are key assets for
any product owner

Question 12 – Explain all Meetings Conducted in Scrum Project

ANS:

All the meetings in scrum project

Sprint Planning:

This meeting kicks off each sprint, which is a time-boxed iteration of work, usually
spanning 2-4 weeks. During this meeting, the Scrum team, including the Product
Owner, Scrum Master, and Development Team, collaborates to determine which
backlog items (user stories, features, etc.) will be worked on in the upcoming sprint.
The team also breaks down these items into tasks and estimates the effort required.
 AGILE SCRUM
Daily Stand-up (Daily Scrum):

Held daily during the sprint, this short meeting aims to facilitate quick and focused
communication among team members. Each team member answers three key
questions: What did I accomplish since the last stand-up? What will I work on until
the next stand-up? Are there any obstacles or impediments in my way? This meeting
helps keep everyone aligned and informed about the progress and challenges.

Sprint Review:

At the end of each sprint, the team holds a review meeting to showcase the work
completed during the sprint to stakeholders, customers, and the Product Owner. The
team demonstrates the potentially shippable product increment and gathers
feedback. Based on this feedback, the Product Owner can update the backlog.

Sprint Retrospective:

Also held at the end of each sprint, the retrospective is a dedicated time for the team
to reflect on their processes and practices. The team discusses what went well, what
could be improved, and any potential change they'd like to make in the next sprint to
enhance their efficiency and effectiveness.

Backlog Refinement (Grooming):

While not officially part of the Scrum events, backlog refinement is an important
ongoing activity. During these sessions, the team and the Product Owner review and
refine backlog items, adding details, clarifications, and estimates to make them ready
for inclusion in future sprints.

Product Backlog Refinement:

This meeting focuses on refining the product backlog items. The team and the
Product Owner discuss and clarify requirements, priorities, and any changes needed
in the backlog items. This ensures that the backlog is well-prepared for upcoming
sprints.

Release planning:
 AGILE SCRUM
This meeting occurs at the start of the project or major release and involves the
product owner, development team, and stakeholders. It aims to discuss and plan the
high level scope, timeline, and goals for the project.

Ad hoc meetings:

These meetings may be schedules as needed to address specific topics or issues,

such as resolving impediments, discuss technical challenges, or conducting
additional planning or collaboration sessions

Question 13 – Explain Sprint Size and Scrum Size

Ans: sprint size and scrum size

Sprint Size:

In Scrum, a "sprint" is a time-boxed iteration during which the development team

works to deliver a potentially shippable product increment. The length of a sprint is
referred to as the "sprint duration" and is usually fixed throughout the project.
Common sprint durations are 1 to 4 weeks. The choice of sprint duration depends on
factors such as team velocity, project complexity, and business needs. A shorter
sprint encourages more frequent opportunities for feedback and adaptation, while a
longer sprint provides more time for development.

Scrum size

The Scrum team size refers to the number of individuals who collectively contribute
to the development of the product. A Scrum team consists of three key roles: the
Product Owner, the Scrum Master, and the Development Team. The Development
Team, in particular, is responsible for creating the product increment. Scrum
recommends that the Development Team size be kept small, typically between 3 to 9
members, to facilitate effective communication, collaboration, and decision-making.

Question 14 – Explain DOR and DOD

Ans: DOR and DOD

DOR (definition of ready):

 AGILE SCRUM
The Definition of Ready outlines the criteria that a product backlog item (user story,
feature, task, etc.) should meet before it is considered ready to be taken into a sprint
for development. The DOR ensures that the item is well-defined,

understood, and prepared for efficient development. The specific criteria in the

DOR can vary from team to team, but commonly include elements such as:

● Clear description and acceptance criteria: The item's requirements are

clearly stated, and the conditions for its successful completion are well-defined.

● Dependencies identified: Any dependencies on external factors, teams, or

resources are identified and addressed.

● Estimable: The team has enough information to provide a reasonable estimate of

the effort required.

● Testable: It's possible to determine whether the item has been

successfully implemented through testing.

● Minimal ambiguity: The item's details are clear, and any uncertainties are

Resolved

Definition of Done (DOD):

The Definition of Done outlines the criteria that must be met for a product increment
or backlog item to be considered complete and potentially shippable. The DOD
ensures that the team maintains a consistent level of quality and completeness in
their work. The specific criteria in the DOD can vary based on the team's standards,
the nature of the project, and the industry, but commonly include elements such as:

● Code complete: All development work is finished, including coding,

testing, and integration.

● Peer-reviewed: Code has been reviewed by other team members for

quality and adherence to coding standards.

● Automated tests passed: Automated tests (unit tests, integration tests,

 AGILE SCRUM
etc.) have been successfully executed and passed.

● Functional requirements met: The item meets all specified acceptance

criteria and functional requirements.

● Documentation updated: Any necessary documentation, user guides, or

technical documentation has been updated.

Question 15 – Explain Prioritization Techniques and MVP

ANS:

Prioritization Techniques

Prioritization techniques are methods used to determine the order in which tasks,
features, or items should be addressed in a project. These techniques help teams
allocate resources effectively and focus on delivering the most valuable work first.
Some common prioritization techniques include:

MOSCOW:

This technique categorizes items into Must have, should have, could have, and won't
have categories. It helps clarify essential features from those that are optional or
lower priority.

Weighted Shortest Job First (WSJF):

WSJF assigns a priority score to each item based on factors like business value,
time sensitivity, and risk. Items with higher scores are considered more important to
work on.

Kano Model:

This model categorizes features into Basic Needs, Performance Needs, and
Delighters. It helps prioritize based on how features impact user satisfaction.

Value vs. Effort Matrix:

Items are plotted on a matrix based on their potential value and effort required. This
helps identify quick wins and high-value tasks.

Relative Prioritization:
 AGILE SCRUM
Teams compare items pairwise to determine which is more important. This helps
create a relative ranking of items.

Buy a Feature:

Stakeholders are given a budget to 'buy' features, which helps prioritize features
based on how much value they see in them Prioritization Techniques:

Minimum Viable Product (MVP):

An MVP is the smallest version of a product that includes just enough features to
provide value to early adopters and gather feedback. The MVP approach helps
validate assumptions, learn from users, and iteratively build upon a product's
foundation. It involves:

● Core Functionality:

An MVP focuses on delivering the core functionalities that address the primary
needs or pain points of the target users.

● Minimal Features:

The MVP omits non-essential features to avoid unnecessary complexity and

expedite development.

● Testing Hypotheses:

The MVP tests assumptions and hypotheses about user behaviour, market demand,
and product viability.

● Iterative Development:

Based on user feedback, the product is refined and

expanded in subsequent iterations, gradually adding more features.

● Early Value:

The MVP allows the product to be released faster, gaining valuable Insights and
attracting early adopters.

Aspect Business analyst Product owner

 AGILE SCRUM
Role focus Understanding business Define, prioritize and
needs process and convey requirements for
requirements the product
Requirement gathering Gathers and documented Creates user stories and
detailed business define product features
requirements
Problem solving Identifies problems, in Drives the product vision,
efficiencies and suggest strategy and value
improvements proposition
Communication Act as a liaison b/w stake Collaborates with
holders and development stakeholders, customers
team and development team
Documentation Creates documentation of Manage the product
Business rules, work backlog and maintains
flows, and requirements clear user stories
Scope definition Helps define scope of the Define the product
project based on business features and
needs enhancement
Vision and strategy Focus specific project or Has a holistic vision for
process improvement product and its strategic
direction
Backlog management Not typically responsible Mange and prioritize the
for managing a product product backlog items
backlog
Prioritization Does not have primary Prioritize features based
role in prioritizing features on business needs,
customer value and
market trends
Decision making Provide inputs but not Make final decision on
responsible for final product features,
product decisions enhancement and
priorities
Iterative development May or may not involved Actively participate in
in iterative development sprint planning, review
 AGILE SCRUM
life cycle and retrospectives
Collaboration Collaborate with stake Collaborates closely with
holders and development the stakeholders,
team customers and
development team
Acceptance Ensures business Ensures user stories met
requirements met the acceptance criteria
and align with product
vision
Leadership and strategy Focus on tactical Focus on strategic
solutions and leadership and product
improvements direction
Continuous Contributes to process Incorporates feedback for
improvement improvement and ongoing product
business efficiency enhancement

Question 17 – Prepare a sample Resume of 3yrs exp Product Owner

Ans: sample resume of 3 years exp product owner

Nikita Sharma

Product Owner

+919640382461| [email protected] | https://www.linkedin.com/in/nikita-

sharma/

SUMMARY

Experienced Product Owner with demonstrated history of working on transformative

initiatives and achieving results. Proven track record of leadership skills with an
ability to develop high-performing team and team members.

 Multi-sector product expertise, with experience working with users across

publishing, financial, technical, and consumer sectors.
 AGILE SCRUM
 Proficient at leveraging key data from stakeholders through guided workshops
on Miro.
 Dedicated to meeting and exceeding expectations for product launches and
sprint updates.
 Expertise in executing A/B testing and drafting Technical User Stories for
product development.

EMPLOYMENT HISTORY

Product Owner

Steam global service, Mumbai 2018 - 2021

 Facilitated project meetings to capture testing and project updates within

credit risk reporting processes.
 Created project plans/timelines in Microsoft Projects, resolved issues to
promote efficient and successful project releases across multiple teams.
 Led multiple tasks to implement best practices by documenting, tracking end-
to-end life cycle review and signoff processes.
 Collaborated closely with technology, business partners to develop business
requirement documents, and test scripts during multiple release phases.

Product Owner

Crowd strike, Pune 2015 - 2018

 Provided roadmap baseline, prioritized projects, implemented requirements

change control, and synchronized cross functional teams.
 Provided market analysis, design recommendations.
 Managed Quarterly releases of the product, supported strategic planning,
designing, and delivering new features within the product.
 Oversaw the product team and guided them on issues related to product
development.
 Served as liaison between customers and multiple teams to establish
business requirements and create functional specifications.

EDUCATION
 AGILE SCRUM
Bachelor of Engineering, Electronics and Communications | University Of Mumbai

SKILLS

 User-Centred Design Processes

 Design Quality Standards
 User Validation
 Product Roadmap
 Product Design Methodologies
 Agile and Scrum

COURSES

 Certified Scrum Product Owner at IIBA

 Certified Product Owner at AIPMM

LANGUAGES

Telugu | English | Hindi

EXTRACURRICULAR ACTIVITIES

Volunteering

Volunteer once a month as clothes intake assistant at Goodwill

Blood Donation

Donated blood at the blood donation camp organised by the lions club