Assignment 5

week 5 assignment

Uploaded by

idealideas09

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PPTX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

6 views9 pages

Assignment 5

week 5 assignment

Uploaded by

idealideas09

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PPTX, PDF, TXT or read online on Scribd

You are on page 1/ 9

Assignment 5

by Vincent

1
Assignment
What is INVEST acronym for a user story?

Define Cadence with respect to Agile Teams

Define Team Velocity with respect to Agile Teams

What is a Gantt chart, create an illustration

2
• 1.Agile INVEST is an acronym that helps Agile teams assess the quality of a user
What is INVEST acronym for a user story?

story. It is used to ensure that user stories are well defined and of high quality.
• I – Independent: The user story should be self-contained and not dependent on
other stories to be completed. This is to avoid prioritization and planning issues
that may arise from having too many user stories in the same area that are
dependent on each other.
• N – Negotiable: The user story should be flexible and allow for discussions and
changes during the development process.
• V – Valuable: The user story must deliver value to the customer or end-user.
• E – Estimable: The story should be small enough to estimate how long it will
take to complete.
• S – Small: The story should be small enough to complete within a sprint, usually
within 2 to 5 days.
• T – Testable: There should be clear acceptance criteria to verify that the story
has been successfully implemented. 3
2. Define Cadence with respect to Agile Teams

User Story: As a user, I want to reset my password so

that I can regain access to my account if I forget.
Given the user is on the login page
And the user clicks on the "Forgot Password" link
When the user enters their registered email address
And clicks the "Reset Password" button
Then a password reset link is sent to the user's email
And the user sees a confirmation message on the
screen.
4
3. Briefly explain 3 popular methods of
prioritizing user stories? Give example
• Three Popular Methods of Prioritizing User Stories
1.MoSCoW Method
Must have: Critical features that are essential to the system.
Should have: Important features that are not vital but add significant value.
Could have: Features that are nice-to-have but not necessary.
Won’t have (this time): Features that are not a priority in the current iteration
but may be considered in the future.
Example:
1. Must have: User login and registration
2. Should have: Profile customization
3. Could have: Social media integration
4. Won’t have: Advanced analytics dashboard
5
3b. methods of prioritizing user stories? Give example
• Kano Model – is a framework developed to help businesses understand and prioritize customer
needs and preferences.
- Basic Needs (Must-Haves): Without these, the product is unusable. e.g, A smartphone’s ability to
make calls or send texts. Without these functions, the phone would be useless but having them
doesn’t impress customers because they are expected.
- Performance Needs.(Satisfiers): features that correlate directly with customer satisfaction. As the
performance of these features improves, customer satisfaction increases. E.g. Battery life on a laptop.
The longer the battery lasts, the more satisfied the customer becomes. Shorter battery life would
cause frustration.
- Delighters (Exciters): Features that surprise and delight the user but are not expected. E.g. A car that
offers a self-parking feature. Customers may not expect it, but it brings delight and a "wow" factor
when it’s available.
- Indifferent Attributes – these are features that customers cannot decide if they are good or bad. E.g.,
The color of a laptop charger. Most customers likely don’t care what color it is as long as it works.
- Reverse Attributes – these features can be high quality or performance, but not increase satisfaction
levels. E.g., A smartphone with too many complex settings and options. Some users may feel
overwhelmed and prefer a simpler interface, while others may appreciate the additional customization.6
3c. methods of prioritizing user stories? Give example
RICE
• RICE framework is a method used to rank features, projects, or tasks based on four key
factors: Reach, Impact, Confidence, and Effort. The RICE score is calculated using the formula:
= (Reach × Impact × Confidence) / Effort
• Reach: measures how many people or users will be affected by the initiative within a specific
time frame. Example: “How many customers will engage with a new feature in a month”.
• Impact: measures how much the initiative will affect each person it reaches. It’s usually rated
on a scale like; 3 = Massive, 2 = High, 1 = Medium, 0.5 = Low, 0.25 = Minimal. Example: "We
expect this feature to have a high impact on user satisfaction, so we rate it as a 2."
• Confidence: reflects how sure you are about your estimates for Reach and Impact. It’s also
rated on a scale: 100% = High confidence, 80% = Medium confidence, 50% = Low confidence.
Example: "Based on data from similar projects, we are 80% confident that this feature will
deliver the expected reach and impact”.
• Effort: measures the resources required to complete the initiative. It is typically estimated in
person-months (how long it will take the team to build, test, and launch the feature).Example:
"This feature will take 2 months of work from 3 engineers, so the effort is 6 person-months."
7
3c. methods of prioritizing user stories? Give example
RICE Example:
Let’s say a team is deciding whether to prioritize Feature A or Feature B for a mobile app
update.
Feature A:Reach: 1,000 users per month. Impact: 2 (High), Confidence: 80% (Medium
confidence), Effort: 5 person-months.
RICE Score for Feature A = (1,000 × 2 × 0.8) / 5 = 320
Feature B: Reach: 500 users per month, Impact: 3 (Massive), Confidence: 90% (High
confidence), Effort: 4 person-months.
RICE Score for Feature B = (500 × 3 × 0.9) / 4 = 337.5
Conclusion: In this case, even though Feature A has a higher reach, Feature B scores higher
overall due to its stronger impact and slightly lower effort.
Therefore, Feature B would be prioritized first based on the RICE score.
Summary: RICE provides a clear way to balance the benefits of an initiative (Reach, Impact)
with the effort required to implement it, helping teams make strategic decisions about8 what
to focus on.
4. What is user story estimation? Give example

User story estimation is the process of evaluating the effort, time, or complexity required to
complete a user story. Teams use estimation techniques to gauge how much work is involved
in developing a feature, typically using relative measures like story points.
Story point estimation is the process of assigning story points to a product backlog item or a
user story. Estimation and Story Points Are Related to Effort, Not Hours.
This helps in sprint planning and allocating resources efficiently.
How to Do Story Point Estimation
Example
User Story: As a user, I want to be able to search for products by category so that I can
quickly find items that interest me.
Estimation: Estimated as 3 story points (assuming it's a medium-complexity feature,
considering the search algorithm, database query, and UI design involved).
Other methods for estimation include: Fibonacci sequence: 1, 2, 3, 5, 8, 13, etc., where
larger numbers represent increasing complexity.
T-shirt sizing: Small (S), Medium (M), Large (L), Extra-Large (XL). 9