Sequencing dependent Agentforce Financial Services stories across sprints
Key Takeaway
Dependencies decide sprint order before priority does. Platform setup runs Financial Services Initial Setup first, then the manual steps, then the optional steps. Data loads start with individuals, then relationship groups such as households, and financial accounts and holdings come later.
Sequencing dependent stories means ordering work across sprints so that a story's prerequisites come first. The product owner orders the product backlog by priority. The team pulls the top, ready items into each 2-week sprint and decides how much it can take on. In an Agentforce Financial Services project, platform setup and initial data loading each follow a set order. Those orders decide which stories go into earlier sprints, even when the product owner ranks a later step highest.
The product backlog
The product backlog holds these kinds of work:
- Project work
- Support or maintenance work
- Nonfunctional requirements
- Research
The product owner owns the product backlog and prioritizes its items. Higher-priority items carry more detail, so they are work-ready. The team constantly refines the backlog as it learns new information about the product.