Activity Log
Title: Short descriptive Name (verb + noun)
Description:
- As a public or staff user
- I want an activity log for all of the actions taken my members of an account
- so that I can view the status of work and track who did what
Acceptance Criteria
- GIVEN ... (you or your condition)
- WHEN ... (what you do)
- THEN ... (what you see)
Dependencies? (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:
- [ ] 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:
- [ ] Check Requirements against completed tasks
- [ ] Completed stories verified in Dev and Test
- [ ] Confirm Test cases built and succeeding
- [ ] No regression test failures
- [ ] Test coverage acceptable by Product Owner???
- [ ] Ticket merged to master or story branch
- [ ] Developer to list Config changes/ Update documents and designs
- [ ] Design / Solution accepted by Product Owner
- [ ] UX Approved
- [ ] Can be demoed in Sprint Review
- [ ] Release ticket is created and this US is linked to it
@zac-broitman What else did we need to do for this epic?
I have a task to perform a review of the activities we're currently capturing in the log and see if anything may be missing. I'll be making tickets once I get that completed (John has informed it is lower priority so we've been focusing on other points recently).
Closing for now as main work is complete. Additional stories can be logged at a later date if the need arises.