...
- The user stories are large and comprised of many independent and dependent pieces of value. Multiple stories should be able to completed in a
- The active sprint shows that each user story is linked to a feature and most of them are assigned to a version.
- Each story is also assigned to a team member and is estimated in story point. There are stories with the size "0". It would be important to understand why or the rationale behind it.
- Acceptance criteria read as tasks and include inter-team collaboration
- Notes and tasks are referenced that are not included as a user story
- Value statements missing juxtapose internal and external users and value statement
- Acceptance criteria are broad and not binary
- Story titles are vague at times. This could be due to:
- The LACE not knowing your work well
- The scope of the stories is too large