Agile Analysis Tips
A healthy backlog
()
Who writes backlog items?
()
Know your agile business analyst (BA) and product owner roles
()
Effective prioritization
()
Making feedback loops a focus
()
Focus on customer experience
()
Collaborate on testing
()
Agile planning: Five levels
()
Keep the user at the center
()
Keep the user action precise
()
Work the acceptance criteria
()
Collaborate with others
()
Make user stories feedback-able
()
Definition of ready/done
()
Personas
()
Primary personas
()
Product hierarchy
()
What needs to be documented?
()
Experiments
()
Hypothesis
()
User journey mapping
()
Story mapping
()
Understanding pain points
()
Defining what success looks like
()
Force rank prioritization
()
Identifying user empathy
()
Stay ahead of backlog refinement
()
Working the scrum master relationship as a product owner
()
Saying no to stakeholders
()
Leveraging user feedback
()
When to let the team ponder
()
Asking the team for alternatives
()
Information radiators for product owners
()
Metrics product owners care about
()
Visual backlog management for product owners
()
Swarming on current work
()
Making your roadmap and release plan visual
()
Observing customers
()
Dealing with user story creep
()
User story splitting patterns
()
Delivering value over staying busy
()
Solving problems over building features
()
Needs vs. guesses
()
Planning with stakeholders (mid to long term)
()
Encouraging swarming and finishing
()
Focus on the problem or outcome, not the solution
()
Managing stakeholder expectations of MVP
()
Analyzing story maps for gaps
()
Outcomes over outputs
()
Defining good outcomes
()
Create an agile project charter
()
Test early and often, even as a product owner
()