Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)
Do you know a possible contact person to reach out (from the other team)?
Validation Rules? (If yes, list here)
DoR for User Story:
[ ] Do we have a prioritized Sprint Backlog?
[ ] Defects, user stories and other work the team has committed to are contained in the sprint backlog?
[ ] Any hidden work?
[ ] All team members availability (days) & capacity (in SP) is known for the Sprint?
[ ] All users stories meet the DoR?
Definition of Ready:
[ ] Does User Story have full flow of business rules, happy and alternate paths, etc.?
[ ] Requirements & expected behavior included in the User Story?
[ ] Are the dependencies known/ understood?
[ ] Dev team accepts user experience artifacts
[ ] If there are validation rules, are they defined (UI, Data, Role-Action)?
[ ] Does this User Story needs stakeholder approval?
[ ] Is this user story small enough to be completed in a Sprint?
[ ] What do we possible have to do re Change Management? - a) GCPE, …?
Definition of Done:
1) [ ] Check Requirements against completed tasks
2) [ ] Completed stories verified in Dev and Test
3) [ ] Confirm Test cases built and succeeding
4) [ ] No regression test failures
5) [ ] Test coverage acceptable by Product Owner???
6) [ ] Ticket merged to master or story branch
7) [ ] Developer to list Config changes/ Update documents and designs
8) [ ] Design / Solution accepted by Product Owner
9) [ ] UX Approved
10) [ ] Can be demoed in Sprint Review
11) [ ] Release ticket is created and this US is linked to it
lmullane
commented
4 years ago
Description:
UI Task (Frontend) – as INPUT for Relationships
CONTENT will be delivered by Relationships
Discuss with Loren for more
As a (type of user)
I want (goal)
so that (reason/ why/ value)
Acceptance Criteria
Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)
Validation Rules? (If yes, list here)
DoR for User Story:
Definition of Ready:
Definition of Done: 1) [ ] Check Requirements against completed tasks 2) [ ] Completed stories verified in Dev and Test 3) [ ] Confirm Test cases built and succeeding 4) [ ] No regression test failures 5) [ ] Test coverage acceptable by Product Owner??? 6) [ ] Ticket merged to master or story branch 7) [ ] Developer to list Config changes/ Update documents and designs 8) [ ] Design / Solution accepted by Product Owner 9) [ ] UX Approved 10) [ ] Can be demoed in Sprint Review 11) [ ] Release ticket is created and this US is linked to it