ALII1 Member since 2007 3 posts
Posted: 3 years ago
Last activity: 3 years 8 months ago

Managing BA activities in Scrum

Scrum teams rely on a continuous supply of refined (implementable) user stories in order to plan and execute Sprints.  Consumption, development and testing of these stories are typically tracked on Scrum boards until they meet the Definition of Done.  In order to replenish the supply of "next batch" stories for subsequent Sprints, Backlog refinement activities is both essential and critical to keeping the Sprint train moving.  Different approaches have been used to address this but I am curious what others think?

  1. Should BA backlog management tasks be defined and tracked on the Scrum board?  Why so or why not?  
  2. Do you consider BAs part of the Scrum team?  Why so or why not?
  3. What are the key set of tasks that BAs should be engaged in?
Project Delivery
Moderation Team has archived post
Share this page LinkedIn