After the refactoring iteration that broke up the large-cluster
BacklogItem now stands alone as its own Aggregate. It reflects the model presented in Figure 10.7. The team composed a collection of
Task instances inside the
BacklogItem Aggregate. Each
BacklogItem has a globally unique identity, its
BacklogItemId. All associations to other Aggregates are inferred through identities. That means its parent
Release it is scheduled within, and the
Sprint to which it is committed are referenced by identities. It seems fairly small.
With the team ...