Question 1 – Write Agile

Manifesto – 8 Marks
Ans:

Agile

● Agile is light weight and can be implemented where faster delivery

is required.
● Agile no documentation is required
● Customer retention since no documentation
● Agile does not support scalability and extendibility

Four Main values of agile.

● Individuals and interactions over processed and tools
● Working software over comprehensive documentation
● Customer colaboration over contract negotiation
● Responding to change over following a plan.

Twelve principles of Agile

Software

1. Satisfy the customer through early and continous delivery of

valuable software.
2. Welcome changing requirements, even late in development.Agile
processes harness change for the customer’s competitive
advantage.
3. Deliver working software frequently, from a couple of weeks to a
couple o months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout
the project.
5. Build projects around the motivated individuals. Give them the
environment and support they need and trust them to get the job
done.
6. The most efficient and effective method of conveying information to
and within a development team is face to face conversation.
7. Working software is primary measure of progress.
8. Agile processes promote sustainable development. The
Sponsors, developers, and users should be able to maintain
constant pace indefinitely.
9. Continuous attention to technical excellence and good design
enhances agility.
10. Simplicity the art of maximizing the amount of work not done is
essential.
11. The best architectures, requirements and designs emerge from
self organizing teams.
12. At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behaviour accordingly.

Question 2 – User Stories-

Acceptance Criteria-BV-CP – 40
Marks

USER STORIES AND THEIR ACCEPTANCE CRITERIA

Story 1

 Issue Type: Story

 Summary: Delivery Boy Registration
 Description:
As a Delivery Boy
I want to register in Scrum Foods
So that I can deliver customer orders
 Acceptance Criteria:
o Registration screen with fields: Name, Password, Nation ID, Mobile No,
Email, Address, Phone Number
o Click on Register button
o Show success notification
 Business Value (BV): 500
 Complexity Points (CP): 2
 Priority: Highest
 Labels: registration, deliveryboy

Story 2

 Issue Type: Story

 Summary: Customer Login Functionality
 Description:
As a Customer
I want to log in to Scrum Foods
So that I can place food orders
 Acceptance Criteria:
o Login screen with username and password fields
o Forgot password link available
o Redirect to dashboard after login
 BV: 400
 CP: 2
 Priority: High
 Labels: login, customer

Story 3

 Issue Type: Story

 Summary: Add Restaurant Details
 Description:
As a Restaurant Admin
I want to add restaurant information
So that customers can view my menu
 Acceptance Criteria:
o Form includes Name, Address, Contact, Cuisine Type, Timings
o Upload menu file
o Show confirmation
 BV: 450
 CP: 3
 Priority: High
 Labels: restaurant, admin

Story 4

 Issue Type: Story

 Summary: Browse and Order Food
 Description:
As a Customer
I want to browse restaurants and food items
So that I can place orders online
 Acceptance Criteria:
o Restaurant list with filter options
o Menu items with "Add to Cart"
o Checkout and order confirmation
 BV: 600
 CP: 3
 Priority: Highest
 Labels: order, food

Story 5

 Issue Type: Story

 Summary: Make Online Payment
 Description:
As a Customer
I want to make a secure payment
So that I can confirm my food order
 Acceptance Criteria:
o Multiple payment methods (Card, UPI, Wallet)
o Secure payment gateway
o Show success/failure message
 BV: 550
 CP: 3
 Priority: High
 Labels: payment

Story 6

 Issue Type: Story

 Summary: Real-Time Order Tracking
 Description:
As a Customer
I want to track my food delivery
So that I know when it will arrive
 Acceptance Criteria:
o Real-time map view
o Delivery status updates
o Contact delivery boy button
 BV: 500
 CP: 3
 Priority: Medium
 Labels: tracking, delivery

Story 7

 Issue Type: Story

 Summary: Submit Customer Feedback
 Description:
As a Customer
I want to provide feedback
So that I can share my service experience
 Acceptance Criteria:
o 1–5 star rating and comment box
o Submit button
o Feedback stored in system
 BV: 300
 CP: 2
 Priority: Medium
 Labels: feedback

Story 8

 Issue Type: Story

 Summary: Admin View Orders Dashboard
 Description:
As an Admin
I want to view all orders
So that I can manage delivery flow
 Acceptance Criteria:
o Filter by date, status, customer
o Update order status
o Export data option
 BV: 400
 CP: 3
 Priority: High
 Labels: admin, dashboard

Story 9

 Issue Type: Story

 Summary: Delivery Boy View Assigned Orders
 Description:
As a Delivery Boy
I want to see my orders
So that I can deliver them on time
 Acceptance Criteria:
o Show active and past orders
o Map with delivery route
o Status update button
 BV: 450
 CP: 3
 Priority: High
 Labels: delivery, orders

User Story 1 – Delivery Boy Registration

Field Details

Summ
Delivery Boy Registration
ary

As a Delivery Boy

I want
Register in Scrum Foods
to

So
I can deliver customer orders
that

Accept
Registration screen with fields: Name, Password, Nation ID,
ance
Mobile No, Email, Address, Phone Number; Register button; Show
Criteri
success notification
a

BV 500

CP 2

Priorit
Highest
y

Labels registration, deliveryboy

User Story 2 – Customer Login Functionality

Field Details

Summary Customer Login Functionality

As a Customer

I want to Log in to Scrum Foods

So that I can place food orders

Acceptance Login screen with username & password; Forgot password link;
Criteria Redirect to dashboard

BV 400

CP 2

Priority High

Labels login, customer

User Story 3 – Add Restaurant Details

Field Details

Summary Add Restaurant Details

As a Restaurant Admin

I want to Add restaurant information

So that Customers can view my menu

Acceptance Form with Name, Address, Contact, Cuisine Type, Timings; Upload menu;
Criteria Confirmation shown

BV 450

CP 3

Priority High

Labels restaurant, admin

User Story 4 – Browse and Order Food

Field Details
Summary Browse and Order Food

As a Customer

I want to Browse restaurants and food items

So that I can place orders online

Acceptance Restaurant list with filters; Menu with "Add to Cart"; Checkout;
Criteria Order confirmation

BV 600

CP 3

Priority Highest

Labels order, food

User Story 5 – Make Online Payment

Field Details

Summary Make Online Payment

As a Customer

I want to Make a secure payment

So that I can confirm my food order

Acceptance Payment via Card/UPI/Wallet; Secure gateway; Show

Criteria success/failure message

BV 550

CP 3

Priority High

Labels payment


User Story 6 – Real-Time Order Tracking

Field Details

Summary Real-Time Order Tracking

As a Customer

I want to Track my food delivery

So that I know when it will arrive

Acceptance Real-time map; Delivery status updates; Contact

Criteria delivery boy button

BV 500

CP 3

Priority Medium

Labels tracking, delivery

User Story 7 – Submit Customer Feedback

Field Details

Summary Submit Customer Feedback

As a Customer

I want to Provide feedback

So that I can share my service experience

Acceptance 1–5 star rating; Comment box; Submit button;

Criteria Store feedback

BV 300

CP 2

Priority Medium
Labels feedback


User Story 8 – Admin View Orders Dashboard

Field Details

Summary Admin View Orders Dashboard

As a Admin

I want to View all orders

So that I can manage delivery flow

Acceptance Filter by date, status, customer; Update order status;

Criteria Export option

BV 400

CP 3

Priority High

admin, dashboard
Labels

User Story 9 – Delivery Boy View Assigned Orders

Field Details

Summary Delivery Boy View Assigned Orders

As a Delivery Boy

I want to See my orders

So that I can deliver them on time

Acceptance Show active/past orders; Map with route; Status

Criteria update button
BV 450

CP 3

Priority High

Labels delivery, orders

Question 3– What is epic? Write 2 epics – 5

Marks

Ans : An Epic in Agile is a large body of work that can be broken down into smaller
tasks called User Stories. Epics are high-level features or requirements that deliver
significant value to the user. They are typically too big to complete in a single sprint and
are usually split across multiple sprints.

 Epics help in managing large, complex functionalities.

 They provide a high-level overview before diving into granular-level stories.
 Epics are often mapped directly to features or modules in a product.

🧾 Epic 1: User Registration and Authentication

Epic Name: Account Creation and Secure Login

Epic Description:
As a new user of the Scrum Foods app, I want to register myself and securely log in, so
that I can personalize my experience and access all features of the food delivery
system.

Acceptance Criteria:
 Users must be able to register using mobile number, email, or social logins.
 Users must receive OTP/email confirmation for verification.
 Passwords must be securely encrypted.
 Users must be able to log in with valid credentials.
 Invalid login attempts should show error messages.
 A ‘Forgot Password’ option should be available.

Related User Stories:

 As a user, I want to register with my email/mobile and password.

 As a user, I want to receive a confirmation message after registering.
 As a user, I want to log in with my credentials.
 As a user, I want to reset my password via email or OTP.

🧾 Epic 2: Order Placement and Checkout

Epic Name: Place and Pay for Food Orders

Epic Description:
As a customer, I want to browse the menu, select items, place an order, and pay
online, so that I can quickly get my desired food delivered to my location.

Acceptance Criteria:

 Users should be able to browse restaurants and menus.

 Users must be able to add/remove items from the cart.
 The total price and taxes should be calculated correctly.
 Users must choose delivery address and time slot.
 Users should be able to pay via credit card, debit card, UPI, wallet, or cash on
delivery.
 Users should receive order confirmation and invoice.

Related User Stories:

 As a user, I want to search and filter restaurants by cuisine or rating.

 As a user, I want to add items to my cart with quantity adjustments.
 As a user, I want to choose my preferred payment option.
 As a user, I want to receive a confirmation after placing my order.s
Question 4 –What is the difference between
BV and CP – 2 Marks
1. BV - BV stands for business value which is given by the client according to the
importance of task.

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 500, Rs
100, Rs 50, Rs 20 and Rs 10 Denominations

2. CP - 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.

The main difference between the BV and CP is that the BV value is decided
or given the client according to the importance or the priority of task to be
performed. However the CP value is indentified or given by the
development team according to the efforts needed to perform the tasks.

Product Backlog Your User stories will go into Product Back log

Question 5 –Explain

about Sprint– 5 Marks

Ans :

Sprints are time boxed iterations of a continuous project development

cycle—short repeatable phases that last between one and four weeks.
Sprints lie at the core of Agile and Scrum methodologies, an approach that
takes large, complex product development projects and breaks them down
into smaller, more manageable pieces.
Sprint Backlog

 A Sprint is a time-boxed iteration in Agile, typically lasting 1–4 weeks.

 It allows teams to build and deliver small, usable parts of the product.
 Sprint includes Scrums (daily stand-ups) to check progress and blockers.
 Sprint Duration: 2 weeks
 Scrum Duration: 1 day
 Sprint Backlog Example:

PBI TASKS WIP DONE

Registration 3 2 1
Login 2 2 0
Add Restaurants 3 3 0
Order Food 3 3 0
Make Payment 3 3 0
Track Delivery 3 3 0
Customer
2 2 0
Feedback

✅ 1. Sprint and Scrum Duration and Value

Duratio
Term Description Your Value
n
Sprin 2 Your Sprint Value: 2
A time-boxed iteration
t Weeks Weeks
Scru Daily team meeting within a Your Scrum Value: 1
1 Day
m Sprint Day

Question 6 – Explain Product backlog and

sprint back log– 5 Marks

Product Backlog - The product backlog is a list that compiles all the tasks
and user stories that must be done to complete the whole project. But it’s
not just a simple task list. An effective product backlog breaks down each
of the backlog items into a series of steps that help the development
team.
The product backlog is very important for product management, the
implementation of agile and it’s also one of the seven scrum artifacts,
which shape the scrum methodology. But even if it’s been planned out,
the product backlog is not set in stone. Like most aspects of agile project
management, there are going to change. Flexibility is crucial.

The product backlog shows project tasks and user stories, as well as their
deadline, who’s assigned to complete them, their priority level and percent
complete. Managers can easily drag and drop these tasks to refine the
product backlog. In addition, Project Manager also allows team members to
interact in real time.

 Sprint backlog : A subset of the product backlog

selected for a particular sprint. It includes tasks that
can be completed within that sprint and remains
unchanged during the sprint.

Question 7 – What is impediments log? write 2 impediments – 5 Marks

Ans : Impediments :

In terms of Scrum, they are “blockers” that prevent the Scrum Team from
completing work, which in return impacts velocity. Anything that prohibits
the team from doing work is considered an impediment.

Impediments are hurdles or obstacles and these are recorded in

Impediment Logs. They are “blockers” preventing the Scrum Team from
completing work and should be included within impediment logs.

All challenges faced by the team will be logged in the impediments log.

Question 8 – Explain Velocity of the Team – 1

Marks
Ans : According to Scrum, Inc., team velocity is a “measure of the amount
of work a team can tackle during a single sprint and is the key metric in
Scrum”. When you complete a sprint, you'll total the points for all fully
completed user stories and over time find the average number of points
you complete per sprint.

Velocity – How many Complexity Points is covered in this sprint. Velocity of

team is 8

Question 9 – Draw Sprint Burn Charts n Product Burn Down Charts– 3

Marks

Here is the Sprint Burndown Chart. It shows how your team is progressing
toward completing the sprint goal over the 2-week period. The blue line
represents the actual work completed, and the green dashed line shows
the ideal progress rate
Question 10 – Explain about Product Grooming – 2 Marks

Ans : Product Grooming /

Product refinement
Product Grooming is the session in which the vision or
goal of the project or product is discussed and who will
be your target group in which market segment does the
product address. What are the needs and solution does
the product required. Also what benefits the client will
get.

Also to indentify the EPICs from the product backlog.

Product grooming is processes of planning the project
and understanding the needs.

Thus product grooming includes the refinement t

understand what does the stakeholder require and why
does it require and what is the value addition is to be done.
Question 11 – Explain the roles of Scrum Master and Product Owner – 3
Marks

Ans.
The Scrum Master is accountable for establishing Scrum as
defined in the Scrum Guide. They do this by helping
everyone understand Scrum theory and practice, both
within the Scrum Team and the organization. The Scrum
Master is accountable for the Scrum Team’s effectiveness.
They do this by enabling the Scrum Team to improve its
practices, within the Scrum framework.

The Product Owner is accountable for maximizing the value of

the product resulting from the work of the Scrum Team. The
Product Owner is one person, not a committee. The Product
Owner may represent the needs of many stakeholders in the
Product Backlog. Those wanting to change the Product
Backlog can do so by trying to convince the Product Owner.

Scrum Master - The day to day activity of a Scrum Master

involves servant leadership where they are involved in
performance planning, coaching, self- organization,
removing obstacles, resolving conflicts and serving the
team.

Product Owner - The first responsibility of the product owner is

customer satisfaction and this they carry out by ensuring that
customer requirements are given priority and there is
transparency between development team and stakeholders.
The product owner guarantees stakeholder satisfaction by
ensuring product success, and building a product which meets
business requirements.

The Scrum Master ensures project success, by assisting the

product owner and the team in using the right Scrum

processes for creating the end product and establishing the

Agile principles. The Product Owner interacts with the users

and customers, Stakeholders, the Development team and the

Scrum Master to deliver a successful product.

The Product Owner and the Scrum Master are both invaluable

members of a Scrum project team, as they build the perfect

relation with the development team and strive to deliver the

best results.

Question 12 – Explain all Meetings Conducted in Scrum Project – 8 Marks

Ans : There are five types of scrum meetings held during the scrum
process which are as follows.
1. Sprint Planning Meeting
2. Daily Scrum Meeting
3. Sprint Review Meeting
4. Sprint Retrospective Meeting
5. Backlog Refinement Meeting
● Sprint Planning Meeting :

This meeting begins with the Product Owner. In this

meeting the PO explains their vision and how the team
should go about completing this step of the project. During
this meeting, team members decide the amount of work
they can complete within the sprint. This is also when the
team moves work from the Product Backlog to the Sprint
Backlog. This step requires a lot of planning and can take
several hours for the group to decide on a finalized Sprint.

● Daily Scrum Meeting :

From the planning meeting, we move into the daily scrum

meetings. Every single day for 15 minutes, the team
gathers together to report any issues or progress on their
tasks. Though brief, this meeting is an essential part of
the scrum process. It is designed to keep all group
members on track in a cohesive manner. Normally the
Product Owner is present during all daily scrum meetings
to assist in any way

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?

● Sprint Review Meeting :

This meeting is used to showcase a live demonstration of
the work completed. During this meeting the Product
Owner, Scrum Master and stakeholders are present to
review the product and suggest changes or improvements.
They will see the Velocity – How
many CP is covered in this sprint
Sprint Burn Down Chart.

● Sprint Retrospective Meeting :

This meeting is held to facilitate a team’s reflection on
their progress. The team speaks openly about their
organizational concerns and teamwork. During this
meeting, dialogue should remain friendly, non- judgmental
and impartial. This review session is a key part of team
building and development and it’s also very important for
future scrum projects. In this meeting team 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.

● Backlog Refinement Meeting :

Last, is the backlog refinement meeting. In this meeting,

team members focus on the quality and skill of the work
involved during the sprints. This meeting is necessary for
the business owners to connect with the development
team and is used to assess the quality of the final product.
This meeting involves important reflection on the team
backlogs.

Question 13 – Explain Sprint

Size and Scrum Size– 2 Marks
Ans :
Sprint Size The whole concept of sprint is to identify User
stories that the scrum team would work on and complete
within a specific sprint duration. Typically known as the
sprint length. Sprints can be of 1, 2, 3 or 4 weeks long at
the max. Anything beyond 4 weeks is never agile scrum
project management.

Scrum Size : Scrum Team size can 8 to 10 people.

1. Product Owner
2. Scrum Master
3. Developers 8

Question 14 – Explain DOR and DOD – 2 Marks

Ans.

The definition of Ready DOR

The product owner could work together with the team to define an artifact
called “the Definition of Ready” (DOR) for ensuring that items at the top of
the backlog are ready to be moved into a sprint so that the development
team can confidently commit and complete them by the end of a sprint.

The term “Definition of Ready” isn’t described in the Scrum

Guide similar to the user stories and the Acceptance Criteria

embedded in it. Perhaps, you may consider the Definition of

Ready is an integral part of the backlog refinement activity,

instead of using the Definition of Ready as a sequential and

phase-gate checklist. Backlog refinement is an ongoing

process, therefore it’s not restricted to an event but

considered an activity.

Definition of Done: DOD

The definition of Done is structured as a list of items, each

one used to validate a user story or PBI, which exists to

ensure that the

Development Team agree about the quality of work they’re

attempting to produce. It serves as a checklist that is used to

check each Product Backlog Item (aka PBI) or User Story for

completeness. Items in the definition of “Done” are intended

to be applicable to all items in the Product Backlog, not just a

single User Story. It can be summarized as following:

DoR and DoD are practices that are needed while improving a
product. To ensure that the product meets customer
expectations, certain features and ideas have to be added to
it from time to time, and defining the criteria for the features
to be added is absolutely necessary and that's when the DoR
and DoD come into play.
Question 15 – Explain

Prioritization Techniques

and MVP – 3 Marks Ans.

Prioritization of requirements is an important aspect of all

software development approaches, but it is especially

important in Agile software development. When we talk

about some of the Product Owner's activities in Scrum

products, such as "Ordering items in the Product Backlog

to best achieve mission and objectives", "Demonstrate

what the Scrum Team would work on next", and

"Streamlining the quality of the work the Developers

performs", we are actually talking about workload

prioritization. All we're attempting to do is prioritize the

issues in the backlog. In essence, we are attempting to

discover the user's priority tasks and rank them

accordingly, while also taking into account certain

additional characteristics. For example, we may utilize five

priority factors to rank user stories, such as the

importance users place on product vision, urgency, time

restrictions, technical difficulty, and stakeholder interests.

Projects must be correctly prioritized for both the overall

project objectives and the individual activities that will

fulfill the objectives in order to be successful. As a result,

we address the prioritizing issue on two levels:

Product level: Evaluate which elements of the product might contribute

more to the project's major aims.

Tasks level: Specify which work items must be completed

and in what sequence during the software product
development cycle.

Types of Agile Prioritisation Techniques.

MoSCoW Agile Prioritization Techniques

MoSCoW analysis is a business analyst prioritizing

approach advocated in the IIBA BABOK and derived from

the DSDM (dynamic software development method).

According to this strategy, a collection of needs or user

stories should be divided into four categories:

M: Must. Describes a criterion that must be met in the final solution for it
to be judged successful.

S: Should. Represents a high-priority component that, if

feasible, should be included in the solution. This is

frequently a vital criterion, but it can be met in other ways

if absolutely required.
C: Could. Describes a criterion that is desirable but not

required. If time and resources allow, this will be added.

W: Will not. Represents a demand that stakeholders have

decided will not be executed in a particular release but will

be addressed in the future.

After categorizing the needs into four groups, they are rated in order of
priority within each category.

Priority Poker -Priority poker is a simple design game for ranking objects in
order of importance. Priority poker is named from the fact that it is quite
similar to arranging poker (a technique for evaluating the costs of the user
stories widely used in Agile development projects).

Before the game begins, the moderator collects all of the individuals who
need to be engaged in the prioritizing process, such as stakeholders, product
managers, strategists, programmers, domain experts, and sometimes even
consumers. The moderator must also prepare a list of tasks to prioritize as
well as a collection of priority cards to distribute to each player. The volume
of cards in this set is determined by how many degrees of priority are useful
in this specific instance. In certain circumstances, a 5 point scale (e.g., very
high priority, high priority, medium priority, low priority, very low priority), a
3 point scale (e.g., high urgency, medium urgency, low urgency), or even a
10 point scale may be used. The number of cards matches to the scale's
numbers.

The supervisor then reviews a piece of functionality (user

story). Each participant selects the card that they believe

represents the best ranking for that assignment and sets it

face down on the table. After each player has made their

selection, all of the cards are turned over at the same time.
The disparities are addressed, and the game continues

until the estimations are roughly equal.

Cost of Delay - This

Agile prioritization technique is a concept that assists you in
determining the amount of money you risk losing if certain features are
unavailable. Essentially, you are putting yourself in the path of those who are
combating fires. As a result, it is a proactive struggle to guarantee that there
is no money- bleeding situations.

You may estimate how urgent they are by calculating how

much money the organization would lose every day if the

feature or job is delayed. Therefore, you will have a well-

planned timetable that will contribute to total budget savings.

As a result, this prioritizing strategy is motivated only by

financial considerations and has nothing to do with user

experience or customer happiness.

Although these factors may be considered when calculating

the Cost of Delay, they are not the primary goal of these Agile

prioritization methods. The benefits of employing this priority

technique in conjunction with others would be both financially

and emotionally justifiable.

Conclusion:

These Agile prioritization methods are critical components of project

planning and management. You may wind up losing a lot of money on the
project if you don't have appropriate Agile prioritization techniques in place.
Furthermore, the initiative may have little influence on the intended clients.
As a result, it is critical to employ an objective prioritizing grading system
that adds to the success of an Agile product development project.

MVP (Minimum Viable Product), the Core of the Agile

Methodology. An MVP is a concept from agile scrum that
refers to a product that has just enough features to satisfy the
needs of early customers and, more importantly, give them
something to provide feedback on to shape the future of the
product.

Question 16 – Difference between Business

Analyst n Product Owner – 3 Marks

-
Product Owner The Product Owner has a vision of the product keeping
the domain/industry experience and the market need. Their job is to ensure
that the product meets the market and stakeholder needs; they conduct
market analysis followed by an enterprise SWOT analysis to come up with
the product vision.

The PO also works on the go-to-market strategy for the product. The PO tries
to leverage their experience in the domain, need of the market, the industry
or the domain, the organization's market position, and the customer
expectation of the product.

Critical Responsibilities for Product Owner

● Market Analysis
● Analysis of market need/demand
● Availability of similar products in the market
● Underserved customer needs
● Potential trends in synergy with current offerings.
● Enterprise Analysis
● SWOT analysis
● Due diligence on the market opportunity
● Product offering decision based on the due diligence report
● Product Vision and Roadmap
● Product vision keeping the need analysis in mind
● Product roadmap with high-level features and timeline
● Managing Product Features
● Managing stakeholder expectations and prioritizing needs
● Prioritization of the epics, stories, and features
based on criticality and ROI involved
● Managing Product Backlog
● Prioritization of user stories
● Reprioritization based on stakeholders' needs
● Epics planning
● Managing Overall Iteration Progress
● Sprint progress review
● Reprioritization of sprints and epics if needed
● Sprint retrospectives with Business Analyst

Business Analyst :As we know, Business Analysts are the change-

makers, problem solvers, questioners, facilitators, the bridge between the
users/stakeholders and the Agile team. They question assumptions and
requirements, assess the needs, find gaps, and work closely with the
stakeholders/SMEs to detail the requirements, features, user stories, and
understand/elicit the requirements.

They work closely with the Product Owners to manage the user stories and
epics.

• Requirements modeling and elicitation

• Data flow diagrams
• Business rules
• Dependency mapping
• Smooth execution of the sprints
• Requirements clarification to the team
• Maintaining the dependency map and the traceability matrix.
• Facilitation support for users in UAT
• Requirements elicitation
• Modeling
• Requirements walkthroughs
• Requirements workshops
• Acceptance criteria
• Often the Business Analyst is considered a Proxy Product
Owner. This allows the Agile team to have a higher
amount of access to the Product
Owner's perspectives.
Critical Responsibilities for Business Analysts

• Managing User Stories

• Prioritizing the user stories
• Clearing the impediments if any
• Detailing the Requirements as per the Stakeholders’
Needs and Expectations
• Requirements elicitation
• Business rules
• Modeling
• Requirements walkthroughs
• Requirements workshops
• Acceptance criteria
• Clarifying the details of requirements with stakeholders
• Coordinating with the development team to get the stories
developed
• Day to day support in requirements clarifications and business
rules
• SPOC for the agile team for all requirements related queries
• Impact Analysis for Changes
• Maintaining the traceability matrix and dependencies.
• Components mapping
• Impact analysis for changes
• Work closely with the PO on the Sprint Execution
• A representative of the PO in the Agile team in clarifying
questions and issues.
• Assists the PO in managing the sprint and the product backlog
• Take a lead role in the sprint retrospectives

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

Owner

Answer:

Name: Aditya Sharma

Phone: +91-9876543210
Email: [email protected]
Location: Hyderabad, India
LinkedIn: linkedin.com/in/priyasharma
Professional Summary

Certified Product Owner with 3 years of experience in Agile environments,

skilled at managing product backlogs, defining user stories, and
collaborating with cross-functional teams to deliver customer-centric
products. Adept in Scrum practices, stakeholder management, and driving
continuous improvement.

Skills

 Agile/Scrum Methodology
 Product Backlog Management
 User Story Writing & Prioritization
 Sprint Planning & Execution
 Stakeholder Communication
 JIRA, Confluence, Trello
 MVP Definition
 Product Roadmapping
 Wireframing (Balsamiq, Figma)

Certifications

 Certified Scrum Product Owner (CSPO) – Scrum Alliance

 Agile Business Analyst – COEPD (2024)

Professional Experience

Product Owner
Scrum Foods Pvt. Ltd., Hyderabad
Mar 2022 – Present

 Owned and managed the product backlog for a food delivery

application.
 Defined Epics, User Stories, and Acceptance Criteria aligned with
business goals.
 Collaborated with UI/UX teams for feature designs and wireframes.
 Prioritized backlog using MoSCoW and Kano models for MVP planning.
 Facilitated daily scrums, sprint planning, reviews, and retrospectives.
 Worked with QA to define test cases and UAT scenarios.
 Increased delivery efficiency by 25% through effective backlog
grooming.

Associate Product Owner

AgriMart Solutions, Bengaluru
Feb 2021 – Feb 2022

 Supported the senior PO in managing the online agriculture store

platform.
 Conducted requirement elicitation sessions with stakeholders and end-
users.
 Maintained sprint burndown charts and participated in all Scrum
ceremonies.
 Translated business requirements into functional and non-functional
requirements.
 Monitored development progress and removed impediments with the
Scrum Master.

Education

B.Tech – Information Technology

Osmania University, Hyderabad – 2020