Agile Storyboarding impact on a Business Quarter



  • a) We have total 6 Sprints constituting a business quarter.

    b) We are releasing every 2 Sprints (or earlier) by means of CI/CD.

    c) We have to deliver a new feature in the next quarter for which we have a Theme/Epic.

    The storyboarding session for this theme/epic - We would like to host this during Sprint 6 this quarter, so that we can establish (or near accomplish) the shared understanding of our feature next quarter. However, we don't know if this is better done in Sprint 1 for next quarter.

    But our question here - Is this the correct approach for Storyboarding in our Sprints?



  • If the expected outcome of the storyboarding session is not only a common understanding of the theme/epic, but also a set of stories, and if you want to be able to work on those stories starting from Sprint 1 next quarter because that theme/epic is the most important thing for the business to work on, then you should definitely have the storyboarding session before the start of that first sprint.

    You might even plan that session even earlier than sprint 6, so that the team has enough time left to further refine the stories and create estimates for them.

    You should want to have things organized such that you have about 2 or 3 sprints worth of stories in a state that they can be picked up immediately and those should be the stories that are the most valuable to the business. That way, there is always something to pick up if the team completes the work faster than estimated, but you also don't have invested much time in work that is so far away that it gets affected easily by shifting priorities.



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2