FOI Online Application Process- Tutorial Flow

[KaraBeach]

• As an applicant • I want to navigate through the online FOI application process • so that I only see the tutorial screens relevant to user choice

Assumptions & Scope What are the assumptions for this story?

• The back and forward button functions for all pages
• When a user hits the back button on a single page then it goes back
• When a user hits the next button on a single page then it goes forward

What is IN scope?

What is NOT in scope?

Acceptance Criteria

Scenario 1: Tutorial –First Page

• GIVEN an applicant is on the have you submitted request page https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097401
• WHEN they click on FOI Process Information
• THEN they will be taken to the first page of the tutorial https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097402

Scenario 2: Tutorial –Second Page

• GIVEN an applicant is on what fee can I expect when submitting an FOI Request page https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097402
• WHEN they click on next
• THEN they will be taken the second page of the tutorial https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097403

Scenario 3: Tutorial –Third Page

• GIVEN an applicant is on are the records you are looking for available elsewhere page https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097403
• WHEN they click on next
• THEN they will be taken to the third page of the tutorial https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097404

Scenario 4: Tutorial –Fourth Page

• GIVEN an applicant is on the how long will my FOI request take page https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097404
• WHEN they click on next
• THEN they will be taken to the fourth page of the tutorial https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097405

Scenario 5: Tutorial –Fifth Page

• GIVEN an applicant is on what will your records look like page https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097405
• WHEN they click on next
• THEN they will be taken to the fifth page of the tutorial https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097406

Scenario 6: Tutorial –Sixth Page

• GIVEN an applicant is on types of requests page https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097406
• THEN the applicant will have the option to submit a General or Personal Request

Scenario 7: Returning User

• GIVEN an applicant is on the have you submitted request page https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097401
• WHEN they click on Skip to Submit Request
• THEN they will be taken to the fifth page of the tutorial https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097406
  • AND the applicant will have the option to submit a General or Personal Request

Scenario 8: Back Button ( all screens)

• GIVEN an applicant is on any screen of the online tutorial
• WHEN they click the back button 
  • THEN they will be taken back to the page prior to the one they are on

...

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)

Design @xxx - please link the Design here

Definition of Ready

1. [ ] Is there a well articulated User Story?
2. [ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
3. [ ] If there is a user interface, is there a design?
4. [ ] Does the user story need user research/validation?
5. [ ] Does this User Story needs stakeholder approval?
6. [ ] Design / Solution accepted by Product Owner
7. [ ] Is this user story small enough to be completed in a Sprint? Should it be split?
8. [ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
9. [ ] Has the story been estimated?

Definition of Done

1. [ ] Passes developer unit tests
2. [ ] Passes peer code review
3. [ ] If there's a user interface, passes UX assurance
4. [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
5. [ ] Confirm Test cases built and succeeding
6. [ ] No regression test failures
7. [ ] Test coverage acceptable by Product Owner
8. [ ] Ticket ready to be merged to master or story branch
9. [ ] Developer to list Config changes/ Update documents and designs
10. [ ] Can be demoed in Sprint Review
11. [ ] Tagged as part of a Release
12. [ ] Feature flagged if required
13. [ ] Change Management activities done?

[KaraBeach]

@m-prodan - for your review.

[m-prodan]

Hi Kara - I think I get what you were trying to do here, but it's a bit outside of the typical gherkin template (Given, when, then) - to give an example, for the first page, I would write it as:

• GIVEN an applicant is on the have you submitted request page https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097401
• WHEN they click on FOI Process Information
• THEN they will be taken to the first page of the tutorial https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097402

I would then repeat this for each subsequent page, and change the title of the page/buttons pressed and update the links. There will be a good number of scenarios, but it shouldn't take too long once you use the one template and go from there.

[KaraBeach]

@m-prodan - updated. Ready for Review