Agile in Salesforce
- January 29, 2024
User story creation
- INVEST criteria for good stories – independent, negotiable, valuable, estimable, small and testable
-
User story has three essential parts:
- Summary (User story/feature name)
-
Description (Value statement):
- As a <User(s)> — Persona
- I want to <Action> –The ‘what’
- So that <Benefit> –The ‘why’
-
Acceptance Criteria (Set of conditions to be fulfilled)
- Testable
-
Have three parts
- ‘Given’- An initial condition
- ‘When’- The action is carried out
- ‘Then’- Result should be obtained
User story example
Summary: [Sales Process]: Capture the region on opportunities.
Description
As a sales representative, I want the ability to capture the region of my opportunities, so that I can view and manage my opportunities by region.
Region: EMEA, North America, LATAM, APAC
Acceptance criteria
- Given that I’m a sales representative, when I view my opportunities, I should be able to see the region to which the opportunities belong.
- Given that I’m a sales representative, when I edit my opportunities, I should be able to update the region.
Tools to plan, track, report and release great products
- Jira
- Trello
- Azure devops (TFS)
- Asana
User story prioritization
Arriving at Minimum Viable Product (MVP):
Separate PBI in 4 buckets using MoSCoW Analysis:
- Must have
- Should have this if possible
- Could have this if possible
- Won’t have this at this time but would like in the future
Key considerations
- Business value
- Dependency (relationship with other product backlog Items)
- Solution approach (prerequisite / dependencies should be taken care of)
- Risk
Story estimation
- Unit for sizing: Story points (relative sizing)
-
Consideration:
- Complexity
- Magnitude of work
- Risk
- Dependency
- Uncertainties
Estimation values
- T-Shirt Sizing: XS, S, M, L, XL, XXL, XXXL etc.
- Fibonacci: 1,2,3,5,8,13 etc.
For user story estimation
- Understand the user story fully. Ask questions!
- Identify base stories
- Relatively size other stories in backlog
- Reach consensus among team
- If a user story is big (>8 USP), break it down to smaller user stories
— By Rashmi