Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
12 views37 pages

Agile Project Management With Scrum Framework

The document provides an overview of Agile Project Management using the Scrum framework, focusing on Scrum artifacts such as the Product Backlog, Sprint Backlog, and Product Increment. It emphasizes the importance of backlog prioritization based on criteria like business value, urgency, opportunity enablement, and development effort. Additionally, it introduces techniques for backlog estimation and prioritization, including Weighted Shortest Job First (WSJF) and relative estimation methods.

Uploaded by

rahul prasad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
12 views37 pages

Agile Project Management With Scrum Framework

The document provides an overview of Agile Project Management using the Scrum framework, focusing on Scrum artifacts such as the Product Backlog, Sprint Backlog, and Product Increment. It emphasizes the importance of backlog prioritization based on criteria like business value, urgency, opportunity enablement, and development effort. Additionally, it introduces techniques for backlog estimation and prioritization, including Weighted Shortest Job First (WSJF) and relative estimation methods.

Uploaded by

rahul prasad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 37

AGILE PROJECT MANAGEMENT WITH SCRUM FRAMEWORK

SESSION – VII: SCRUM


Sunday, 21 July 2024 INSTRUCTOR: DR. RAHUL SINDHWANI / DR. SHWETA SINGH 1
SESSION
FLOW
Product
SCRUM Backlog
Prioritization
Artifacts

Product
Backlog

7/21/2024 10:53 PM 2
Scrum Artifacts
• Something that is created by ones in
SCRUM framework.
• Artifacts in SCRUM represents work
and value.
• It is key to information needed during
Product Backlog
product development.
• It is the details related to product and Sprint Backlog
process which is used by scrum team and
stakeholders.
• It provides transparency, inspection and Product Increment
adaptation
• SCRUM guide defines 3 artifacts
Product Backlog
.

• Backlog is an accumulation of unfinished work.


• Product Backlog is undone things related to product (like to-do-list).
• It is ordered list of everything needed in the product.
• Contains new features, improvements and fixes.
• The list is never final, it is emergent and constantly changing.

Product Backlog
Feature 1 Feature 1
• Description
Feature 2 • Order
• Size
Feature 3 • Value
• Acceptance
Improvement Criteria

Fixes Product Owner


Example: We want to go for vacation
.

Product Backlog Items in the list are in random order


Find a destination
Book a flight What would be the Product Backlog
1st things that you Leave approval
Leave approval
should do??
Book a hotel Find a destination
Book a hotel
Book a rental car
Book a flight

Book a rental car


Example: Product goal is to reach 10,000 online orders in next 6 months
.

Product Backlog Item (PBI) 1. PBI don’t means a lot


2. Product owner work together with
developers to add more details
1. Create short page 3. Product backlog described and
2. Display one product decided by SCRUM Team.
3. Order form 4. Product backlog have product
4. Display multiple products description, order, size, acceptance
5. Add to cart criteria (done by creating user
6. Create payment options stories)
Features of PB
.

• Items can be added to list at any time


Living Artifact • PB evolves throughout life cycle of project
• Act as central guide for team

PB is owned and adjusted by PO (sole


PO is accountable
person accountable for PB)

• New features or information added as per its


importance.
Prioritized List • Items at top is more specific and well defined
followed by vague items in bottom
Product Backlog
Backlog Prioritization
Product Backlog Prioritization
• The process of figuring out the size of an item is called sizing or estimation.

• With the help of the sizing or estimation, we will come on Backlog Prioritization.

• This is not the part of mandatory scrum events.

• The team works on details, size, and order of PB.

• The size of the item not only shows how big or small the effort of doing work is but also
considers other factors such as risk, business value, and urgency to complete the task.

https://www.knowledgehut.com/blog/agile/product-backlog-refinement-scrum
4 Criteria used for Prioritization

Business value or
Urgency
Economic value

Opportunity enablement/
Development effort
or risk reduction
Business value

Is this feature capable of bringing more money for the business?

Can it prevent the business from losing money moving forward?


Urgency

How urgently do we need to Is this feature a part of promise or Is there a clear deadline or window
deliver this feature? a contract? of opportunity coming up?
Opportunity Enablement or Risk Reduction

Is this item bringing revenue immediately, or will it benefit in the


long run?

For example, In PB, there could be some items that may help you
eliminate technical or legal risk, and save your money later.
Development effort required

The only negative factor that ranks the items in the backlog.

The cost of necessary person hours is one of main factors that


determine the amount of return we receive on our investment.
Relative Estimation

Plain Area Normal Mountain Mount Everest


Relative
Estimation
Methods

Weighted
T- Shirt Size Shortest Job
First (WSJF)
Relative Estimation
T- Shirt Size

It requires 2 among 4 criteria of


prioritization

1. Business value
2. Development effort
T-Shirt Sizes
.

Compare all tasks


L
M with Medium

XL
Fix one task that requires Medium effort
M

Fixed
Business stakeholders Development team

Backlog Business Value Development Effort


Feature A XL S
Feature B M L
Feature C L XS
Feature D XS S
Feature E XL M
Feature F S L
Feature G L S
Observations by the Product Owner
Business stakeholders Development team

Backlog Business Value Development Effort


Feature A XL S
Feature B M L
Feature C L XS
Feature D XS S
Feature E XL M
Feature F S L
Feature G L S
Prioritized Backlog
Business stakeholders Development team
Backlog Business Value Development Effort
Feature A XL S
Feature E XL M
Feature C L XS
Feature G L S
Feature B M L
Feature F S L
Feature D XS S
If 2 features in the backlog comes out with the same T-Shirt size, it may become difficult to
decide, which one to do first
Weighted Shortest Job First (WSJF)

WSJF means prioritizing activities that provide a higher value in less effort.
This technique makes use of all four criteria
1. The business value
2. Urgency
3. Opportunity enablement/risk reduction
4. Development effort

• It is a tool in the Scaled Agile Framework (SAFe)


• The score suggests the priority of items more accurately.
• The higher the WSJF score, the higher would be the priority of the feature
• The scale used here is from the Fibonacci series
Fibonacci Series
0,1,1,2,3,5,8,13,21,34,55,89..............................................∞

1 2 3 5 8 13 21 34

Usually, the team adapts numbers up to 89


Modified
Fibonacci
Example:
.
Effort to consume
different fruits
.

5 3 3

1 13 2
Estimation
using Planning
Poker

https://www.youtube.com/watch?v=3apRqd67hrQ&list=PLL-72IrJnz2w_8JyHQVlWSw2w3eP9tL76&index=2
Planning
Poker

https://www.youtube.com/watch?v=3apRqd67hrQ&list=PLL-72IrJnz2w_8JyHQVlWSw2w3eP9tL76&index=2
Weighted Shortest Job First (WSJF)

Cost of Delay = The Business Value + Urgency + Opportunity Enablement

WSJF Factor =

The Business Value + Urgency + Opportunity Enablement

Development Effort
WSJF
Business stakeholders Development team
Backlog Business value Urgency Opportunity Dev effort WSJF (COD/
Dev effort)

Feature A 5 8 5 3 (5+8+5)/3= 6

Feature B 3 5 8 8 2

Feature C 8 5 3 5 3.2

Feature D 2 3 8 2 6.5

Feature E 3 2 3 3 2.6

Feature F 13 2 5 3 6.6

Feature G 1 3 3 5 1.4
WSJF
Business stakeholders Development team
Backlog Business value Urgency Opportunity Dev effort WSJF (COD/
Dev effort)

Feature A 5 8 5 3 (5+8+5)/3= 6

Feature B 3 5 8 8 2

Feature C 8 5 3 5 3.2

Feature D 2 3 8 2 6.5

Feature E 3 2 3 3 2.6

Feature F 13 2 5 3 6.6

Feature G 1 3 3 5 1.4
Prioritization

This prioritization exercise does not set the order of backlog


items in stone.
This is not a commitment.
We do not have a release backlog plan yet.
Prioritization helps to understand what is worth considering for
future investigation.
More analysis, detail, refinement, discussion, and work to
build the release plan is needed.
Exercise: Launch New Summer Collection on Myntra

• Description: Develop and execute a comprehensive plan to launch Myntra's new


summer clothing collection. This includes preparing the product pages, creating
marketing materials, setting up promotional campaigns, and ensuring a seamless
customer experience.
PBI:
1. Create a product pages
2. Develop a Digital Marketing Strategy
3. Set Up Promotional Campaigns
4. Prepare Logistics and Inventory
5. Establish Performance Metrics
“Work hard, be kind,
and amazing things
will happen."

Conan O'Brien

7/21/2024 10:53 PM 37

You might also like