Repository navigation
BA Track Changes Concerning Refinements - #2044
Merged
Merged
Conversation
✅ Deploy Preview for cyf-common ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for cyf-curriculum ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
kfklein15
approved these changes
Nov 9, 2026
kfklein15
left a comment
Contributor
There was a problem hiding this comment.
All changes make sense. Thanks, @grogers99
Contributor
|
Also looks good to me! Thank @grogers99 |
Contributor
|
@grogers99, not sure what it is complaining about test tooling and consistency? And idea? |
skalinina
approved these changes
Nov 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

This PR contains amendments relating to the handling of the term Refinement in the BA Track. In particular:
Sprint 1: User Research
Removed the reference to Refinement added here in PR #2030, as we haven't formally defined Requirements at this stage.
Sprint 3: Epics
Updated this section to discuss Epics, Features and Stories and introduce the term Refinement in the sense of breaking down and detailing low-granularity requirements to derive higher-granularity requirements.
Sprint 5: Prioritisation
Updated this section to introduce the idea of a Refinement Session, where prioritised requirements are communicated to the development team and set to ready in preparation for the sprint.