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

User Story No:13 Tasks2 Priority Highest

AS A CUSTOMER

User
I WANTStory No:14
REGISTER Tasks 2
IN SCRUM FOODS Priority Highest
SO A
AS THAT I CAN LOGIN IN SCRUM FOODS APPLICATION
CUSTOMER

I WANT LOGIN IN SCRUM FOODS

BV: 100 CP: 2
SO THAT I CAN USE THE SCRUM FOODS APPLICATION

ACEPTANCE CRITERIA
BV: 200
REGISTRATION SCREEN
CP: 4

Text Boxes forCRITERIA

ACEPTANCE User Name, Password, Mobile No, Email, Address,

Phone
LOGIN Number.
SCREENClick on Register Button. Send Successful Notification to the user

User Story
Text Boxes No:15
for User Tasks
Name, Password, Mobile2No, Email,
Priority Highest
Address,

Phone Number. Click on Register Button. Send Successful Notification to the user
AS A CUSTOMER
User Story No:16 Tasks 2 Priority Highest
I WANT LOGIN IN SCRUM FOODS
AS A CUSTOMER
SO THAT I CAN USE THE SCRUM FOODS APPLICATION
I WANT SEARCH OPTION IN SCRUM FOODS APPLICATION

SO THAT I CAN SEARCH FOR RESTURANTS TO ORDER FOOD

BV: 200 CP: 4

BV: 200 CRITERIA

ACEPTANCE CP: 4
LOGIN SCREEN
ACEPTANCE CRITERIA
Text Boxes for User Name, Password, Mobile No, Email, Address,
LOGIN SCREEN
Phone Number. Click on Register Button. Send Successful Notification to the user
Text Boxes for Search Menu, show Restaurant details.

Enable Search option to display list of restaurants to order foods

User Story No:17 Tasks 2 Priority Highest
AS A CUSTOMER

User
I WANTStory No:18
TO VIEW Tasks
RESTURANTS MENU 2
IN SCRUMPriority Highest
FOODS APPLICATION

SO THAT
AS A I CAN SELECT FOOD TO ORDER FROM RESPECTIVE RESTAURANT
CUSTOMER

I WANT TO ORDER FOOD FROM RESTURANTS LISTED IN SCRUM FOODS

BV: 200
APPLICATION CP: 4
SO THAT I CAN SELECT FOOD TO ORDER FROM RESPECTIVE RESTAURANT
ACEPTANCE CRITERIA

BV: 200
View list CP: 50
of restaurants and Menu cards in Tabular Form.

Show available Menu card of Restaurants

ACEPTANCE CRITERIA

Login, Show list of available restaurants, Display Menu cards,

Enable the customer to select item and place order in application.

User Story No:19 Tasks 3 Priority Highest
AS A CUSTOMER

I WANT TO MAKE ONLINE PAYMENT

User Story No:20 Tasks 3 Priority Highest
SO THAT I CAN MAKE ONLINE ADVANCE PAYMENT
AS A CUSTOMER
BV: 500
I WANT TO TRACKING OPTION CP: 100

SO THAT I CAN
ACEPTANCE TRACK MY ORDER ONLINE
CRITERIA

Login, Show Payment options Net banking, UPI Payments, Credit card.
BV: 500 CP: 100
Enable the customer to select the mode of payment and proceed with the payment option.
ACEPTANCE CRITERIA

Show Status of delivery with the location details, and the expected time of delivery.

Enable the customer to track the delivery of placed orders and expected time of delivery.

User Story No:21 Tasks 3 Priority Highest

AS A CUSTOMER

I WANT THE CANCEL OPTION

User Story No:22 Tasks 2 Priority Highest
SO THAT I CAN CANCEL THE ORDER IN CASE OF REASON
AS A CUSTOMER
BV: 500
I WANT THE FEEDBACK OPTION CP: 100

SO THAT I CAN
ACEPTANCE RATE GIVE FEEDBACK AND RAINGS
CRITERIA

Text Box for cancel option, order can be canceled mentioning the reason of cancellation.
BV: 500
Display CP:
the status as canceled and process for refund 100 in case payment received.
to customer

ACEPTANCE CRITERIA

Text Box for feed back option, option to rate the delivery agent.
User Story No:23 Tasks 3 Priority Highest
AS A DELIVERY BOY

I WANT TO REGISTER
User Story No:24 Tasks 3 Priority Highest
SO THAT I CAN ACCEPT THE ORDER AND DELIVERY.
AS A DELIVERY BOY
BV: 500
I WANT CP: 100
TO LOGIN IN SCRUM FOODS APPLICTION

SO THAT I CAN
ACEPTANCE VIEW AND ACCEPT THE ORDER FOR DELIVERY.
CRITERIA

Text Boxes for User Name, Password, Mobile No, Email, Address,
BV: 500 CP: 100
Phone Number. Click on Register Button. Send Successful Notification to the user
ACEPTANCE CRITERIA

Text Boxes for User Name, Password, Mobile No, Email, Address,

Phone Number. Click on Register Button. Send Successful Notification to the user

User Story No:25 Tasks 3 Priority Highest

AS A DELIVERY BOY

I WANT TO UPDATE THE ORDER STATUS

User Story No:26 Tasks 3 Priority Highest
SO THAT I CAN VIEW AND UPDATE THE DELIVERY.STATUS.
AS A DELIVERY BOY
BV: 500
I WANT TO UPDATE THE PAYMENT STATUS CP: 100

SO THAT I CAN
ACEPTANCE VIEW AND UPDATE THE PAYMENT STATUS FOR COD
CRITERIA

Text Box for updation of delivery status and feed back.

BV: 500 CP: 100

ACEPTANCE CRITERIA

Text Box for updation of delivery status and feed back.

User Story No:28
No:27 Tasks 2 Priority Highest
AS A DELIVERY RESTAURANT
BOY OWNER

I WANT TO LOGIN
VIEW DETAILS

SO THAT I CAN VIEW ORDERS

CUSTOMER
AND
FEEDBACKS
ACCEPT IT

BV: 500 CP: 100

ACEPTANCE CRITERIA

Text Boxes
Box forfor
updating
User Name,
the customer
Password,
feedbacks,
Mobile No,
andEmail,
viewing
Address,
access to delivery boy.

Phone Number. Click on Register Button. Send Successful Notification to the user
User Story No:29 Tasks 2 Priority Highest
AS A CUSTOMER

User
I WANTStory No:30 DETAILS
TO PAYMENT Tasks 2 Priority Highest
SO THAT
AS A I CAN VIEW
BUSINESS OWNERMY ORDERS AND PAYMENTS RECEIPTS

I WANT TO RESGISTER
BV: 500 CP: 100
SO THAT I CAN LOGIN IN SCRUM FOOD APP
ACEPTANCE CRITERIA
BV: 500 for reports of placed orders and paymentsCP:
Text Boxes 100
done.

ACEPTANCE CRITERIA

Text Boxes for User Name, Password, Mobile No, Email, Address,

Phone Number. Click on Register Button. Send Successful Notification to the user

User Story No:32

No:31 Tasks 2 Priority Highest
AS A BUSINESS OWNER

I WANT TO LOGIN

SO THAT I CAN UPDATE

VIEW ORDERS
THE PAYMENTS
AND OTHER
FOR
DETAILS
RESTAURANTS.

BV: 500 CP: 100

ACEPTANCE CRITERIA

View
Text Boxes
Order,for
Display
User Name,
List of orders
Password,
in theMobile
tabularNo,
Form
Email, Address,

Enable
Phone Number.
to updateClick
the payments
on Register
to Button.
restaurants
Send Successful Notification to the user
User Story No:33 Tasks 2 Priority Highest
AS A ADMIN

I WANT TO LOGIN

SO THAT I CAN VIEW THE RESTAURANTS

User Story No:34 Tasks 2 Priority Highest

BV: 500 CP: 100
AS A ADMIN

IACEPTANCE CRITERIA
WANT TO VIEW REPORTS

SO THAT I CAN VIEW THE REGIONAL REVENUES

Text Boxes for User Name, Password, Mobile No, Email, Address,

Phone Number. Click on Register Button. Send Successful Notification to the user
BV: 500 CP: 100

ACEPTANCE CRITERIA

Generate the reports of orders and payment and calculate the revenue.

User Story No:35 Tasks 2 Priority Highest

AS A CUSTOMER

I WANT TO RAISE ISSUES

SO THAT I CAN UPDATE THE COMPLAINTS OF DELIVERY AGENTS OR RESTURANTS

User Story No:36 Tasks 2 Priority Highest

BV:A DELIVERY
AS 500 BOY CP: 100
I WANT TO LOGIN
ACEPTANCE CRITERIA
SO THAT I CAN VIEW DELIVERIES REPORTS AND REVENUE GENERATED
User Story No:37 Tasks 3 Priority Highest
Enable to add comments for customer regarding the ratings or any complaints regarding the
delivery boys or restaurants.
BV:
AS A 500
RESTUARANT CP: 100
I WANT TO LOGIN
ACEPTANCE CRITERIA
SO THAT the
Generate I CAN UPDATE THE LIST OF FOODS AND AVAILABILITY
reports
View Deliveries report and view revenue generated.

BV: 500 CP: 100

ACEPTANCE CRITERIA

Text Boxes for User Name, Password, Mobile No, Email, Address,

Phone Number. Click on Register Button. Send Successful Notification to the user

Update the available foods and the status of availability.

 User Story No:38 Tasks 3 Priority Highest
AS A CUSTOMER

I WANT TO UPDATE THE ADDRESS

SO THAT I CAN UPDATE THE NEW ADDRESS AS CURRENT ADDRESS.

BV: 500 CP: 100

ACEPTANCE CRITERIA
User Story No:39 Tasks 3 Priority Highest
AS A ADMIN
Modify the Address and set as current location.

IUpdate
WANT the
TO details
ACCESS andOF FOOD APP
store.

SO THAT I CAN ADD OR DELETE THE DELIVERY BOYS

User Story No:40 Tasks 3 Priority Highest

BV:A REGIONAL
AS 500 ADMIN CP: 100
I WANT TO VIEW REPORTS
ACEPTANCE CRITERIA
SO THAT I CAN VIEW REGIONAL REVENUE

User box to update the comments for addition or deletion of the delivery boys.
BV: 500
Update the details and store.
CP: 100

ACEPTANCE CRITERIA

Generate the reports regional wise and view reports

Update the details and store.

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

Ans : EPIC is the set of user stories or the big user story consisting the number of small user stories to
complete the mile stone known as EPIC.

EPIC can be said as the set of user stories completed to achieve one task.

1. RESGIATRATION

AS A CUSTOMER I WANT TO REGISTER IN SCRUM FOOD APP SO THAT I CAN LOGIN AND
PLACE ORDER.

2. LOGIN

AS A CUSTOMER I WANT TO LOGIN IN SCRUM FOOD SO THAT I CAN ORDER THE FOOD AND
MAKE PAYMENT.

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.

What is sprint Duration: 2 Weeks - Your sprint Value _

Scrum is a sub unit of Sprint. What is scrum Duration: 1 day – Your scrum Value________________?
PBI: Product Backlog Item Task: Unit of Work done by 1 Developer in 1 Scrum WIP: Work In Progress

Sprint Backlog

PBI TASKS WIP DONE

Registratio 3 2 1
n
2 2 0
Login

Add 3 2 1
Resturants
3 0 3
Order Food

3 3 0
Make
Payment
3 3 0
Track
Delivery
3 3 0
Cust
Feedback
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 :

The sprint backlog is a subset of the product backlog. The sprint backlog comes from the product backlog, but it contains only the product backlog items that can be completed

during each agile sprint. Think of it as the marching orders for the team as they go off on their short sprint.

The complexity of the project will determine the sprint backlog, but overall the idea is to dedicate the team only to those tasks that can be completed during the sprint. Of

course, if it is a complex project the sprint backlog can also grow in complexity and length.

Unlike the product backlog, though, the sprint backlog is unchanged during the period of the sprint. It can be changed, but only during the sprint planning meeting. Once

agreed upon, the items and steps to complete them are frozen for the length of 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.

a sick team member

Lack of system knowledge

lack of management support

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

Sprint Burn Charts

Product Burn Down Charts

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 are 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. As a consequence, 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

ANS:

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 – 3 Marks

Ans :

Harshad Kharate
[email protected]
9890609611

Objective

Motivated and forward-thinking product owner with 3+ years of experience.

Eager to support team with leadership and guidance over a wide range of
product development efforts. In previous roles reduced the delivery time by
20% and was able to coordinate 95% of product completion in line with the
company roadmap.

Work Experience

Agile Product Owner

Deutsche Bank Pune
2017
 Acted as liaison between business, sales and IT teams to refine the
product and incorporate features based on market demands.
 Partnered with IT and product leadership to drive and manage the
solution development process and ensure the product team
understands the direction and vision.
 Collaborated with teams to discover and deliver the best solution to the
market presented by the product team lead and the business.
 Created and maintained the solution vision, roadmap, and backlog of
work through the project's life cycle.
 Translated features into user stories within the team’s backlog while
managing, ranking, and prioritizing this backlog to reflect stakeholder’s
requirements.
 Key achievement:
 Effectively negotiated sprint goals with the team, which resulted in
slashing delivery time by 20% in a single quarter.

Scrum Product Owner

 Collaborated with stakeholders to understand business problem

statements and convert them into user stories.
 Articulated product vision and user stories in a way clearly
understandable to development teams.
 Managed backlog of user stories for 2 products simultaneously.
 Established user story acceptance criteria and refined stories with
Scrum teams.
 Created Sprint Release Plans with input from development teams.
 Applied Agile methods and processes to promote a disciplined and
transparent project management process.
 Key achievement:
 Planned and estimated 2-week sprints in a realistic yet time-efficient
manner that allowed the teams to deliver 97% of the MVP according to
the company roadmap.

 Education
B.Sc., Computer Science
Pune

Key Skills

 Conceptual skills
 User-centered design processes
 Design quality standards
 Service and product design methodologies
 Agile and Scrum
 Conducting design sprints
 User validation
 Analytical skills
 Collaboration and teamwork
 Communication

Certifications

 Certified SAFe® Product Owner.