Scenario 2: Quality Assurance analysis
The team decided to have a detailed sprint task approach where the development tasks are specified reflecting Acceptance Criteria (ACs): as the content of most user stories in the product backlog for this project is nontrivial, it would be incorrect for the team to follow a lightweight approach with a general development task approach.
The team decided that the information radiator will be an Excel spreadsheet with a Product backlog, and for each sprint, they are going to create an Excel spreadsheet with a Sprint backlog (all spreadsheets shared with all team members in OneDrive, with edit rights).
When preparing for the Sprint 1 planning meeting, the team also created Acceptance Criteria (ACs) for a number of high-priority items, including PBI-13.
PBI 13. As a customer, I want to select whether I will pay for my order with a credit card or PayPal, so thatI have the flexibility of payment.
Note: This functionality covers only the selection among the options. The actual payment functionalities will be presented by PBI-14 and PBI-15.
The ACs for PBI-13 have been specified as follows:
AC12.1
Given the customer is on the cart page of the application
When the customer selects the option “payment with credit card” or the option “payment with PayPal”,
Then the payment option for this order will be stored as “CreditCard” and the application will present to the customer a screen “Please enter details of your credit card” with fields to enter the credit card number, the name on the card, the expiration date of the card and the CVV number.
Please note that the team, Product Owner and Scrum Master agreed to the following Definitions of Done for the functionalities to be developed for customer users:
· Unit testing passed (code coverage 80%)
· Code peer reviewed
· Functional testing based on ACs passed (manual testing)
· Usability testing passed (Chrome 134.0, Safari 17.6)
· Regression testing passed
· Approved by the Product Owner
The below screenshot (of a part of a Trello card) presents the sprint tasks the team has specified:
Interview tasks for Scenario 2:
Scenario 2 will provide you a Definition of Done for the project, a screenshot presenting sprint tasks as well as a specification of acceptance criteria for an item.
Task 2.1 - ACs: You need to analyse the specified Acceptance Criteria, explain what issues you identified and demonstrate how exactly they should be fixed (create and present a corrected version of Acceptance Criteria).
Task 2.2 – Sprint tasks: You need to analyse the sprint tasks, explain what issues you identified and demonstrate how exactly they should be fixed (create and present a corrected version of the sprint tasks for this PBI).
Task 2.3B – Testing (Variant for Bachelor students): You need to specify test cases for a sprint tasks that aims to cover the following item of the Definition of Done: Functional testing based on ACs passed (manual testing). Please use the templates provided in Canvas.
Task 2.3M – Testing (Variant for Master students): For Functional testing based on ACs passed (manual testing), you need to specify test cases for a sprint tasks (please use templates provided in Canvas). For all other items of the Definition of Done, please explain briefly how you will conduct testing and what artefacts will be created as result.
Scenario 3: Product Backlog Analysis
A Scrum team, Product Owner and Scrum Master agreed to the following Definitions of Done, where DoD1 was specified to cover staff functionality, and DoD2 was specified to cover customer functionality:
DoD1:
· Unit testing passed (code coverage 85%)
· Code peer reviewed
· Functional testing based on ACs passed
· Usability testing passed (Chrome 134.0, Safari 17.6)
· Regression testing passed
· Approved by the Product Owner
DoD2:
· Unit testing passed (code coverage 80%)
· Code peer reviewed
· Functional testing based on ACs passed
· Usability testing passed (Chrome 134.0, Safari 17.6)
· Regression testing passed
· Approved by the Product Owner
An extract of a Product Backlog is presented below. This extract covers only the customer functionality, which will be the focus of the tasks within Scenario 3.
For the analysis of the PBIs' statuses, you have to assume that the team is currently at the end of Sprint 0.
|
PBI ID
|
User Story
|
Owner
|
Priority
|
Efforts
|
Status
|
DoD
|
|
PBI-1
|
As a customer, I want to see information about Melbourne Handmade Soap and photos of their shop on the “About” page, so that I know more about the company
|
Alex Bell
|
High
|
13
|
In Progress
|
DoD1
|
|
PBI-30
|
As a customer, I want to see the full range of soaps produced by coffee4U on “Our soap” page, so that I know what I can order
|
Wei Wei
|
High
|
5
|
In Progress
|
DoD1
|
|
PBI-31
|
As a customer, I want to select among the soap items, so that I can order the item of the right size. Note: the soap sizes are sample (50g), medium (100g) and large (150g).
|
Kelly Lee
|
High
|
5
|
To-Do
|
DoD1
|
|
PBI-3
|
As a customer, I want to add soap items of a selected size to my cart, so that I can buy these items.
|
Alice Long
|
High
|
5
|
To-Do
|
DoD1
|
|
PBI-4
|
As a customer, I want to adjust the quantity of each soap item in my cart, so that I can buy these items.
|
Lukas Knight
|
High
|
3
|
To-Do
|
DoD1
|
|
PBI-5
|
As a customer, I want to remove soap items from my cart, so that I have the flexibility to change my mind.
|
Alex Bell
|
High
|
1
|
To-Do
|
DoD1
|
|
PBI-6
|
As a customer, I want to select whether the order will be delivered by Australian Post or picked up from the shop during the shop’s business hours (currently Monday-Friday 9:00am – 4pm, Saturday 9am – 12pm), so that I have flexibility or ordering.
|
Wei Wei
|
High
|
2
|
To-Do
|
DoD1
|
|
PBI-7
|
As a customer, I want to proceed to check out, so that I can buy items in my cart.
|
Kelly Lee
|
High
|
2
|
To-Do
|
DoD1
|
|
PBI-8
|
As a logged-in customer, I want to select a payment method (PayPal or credit card), so that I can click on the corresponding button.
|
John Ngo
|
High
|
2
|
To-Do
|
DoD1
|
|
PBI-9
|
As a logged-in customer, I would like to pay with PayPal, so that my order is finalised.
|
Alice Long
|
High
|
5
|
To-Do
|
DoD1
|
|
PBI-10
|
As a logged-in customer, I would like to pay with a credit card, so that my order is finalised.
|
Lukas Knight
|
High
|
5
|
To-Do
|
DoD1
|
|
PBI-11
|
As a logged-in customer, I want to receive email confirmation of a successful payment for my order, so that I can keep a record of my orders.
|
Alex Bell
|
High
|
3
|
To-Do
|
DoD1
|
|
PBI-13
|
As a logged-in customer, I want to see the history of my orders, so that I can keep a record of my orders.
|
Wei Wei
|
Medium
|
5
|
To-Do
|
DoD1
|
|
PBI-12
|
As a customer, I want to register in the system, so that I can log in.
|
Kelly Lee
|
Medium
|
3
|
To-Do
|
DoD1
|
|
PBI-5
|
As a customer, I want to log in so that I can pay for the items in my cart.
|
John Ngo
|
Medium
|
1
|
To-Do
|
|
|
PBI-14
|
As a customer. I want to increase the quantity of an item in my cart, so that I can adjust my selection.
|
Alice Long
|
High
|
1
|
To-Do
|
DoD1
|
|
PBI-16
|
As a customer, I want to decrease the quantity of an item in my cart, so that I can adjust my selection.
|
Lukas Knight
|
High
|
1
|
To-Do
|
DoD1
|
|
PBI-17
|
As a customer, I want to pay for my order without logging into the system, so that I can enjoy the flexibility of payment.
|
Lukas Knight
|
High
|
5
|
To-Do
|
DoD1
|
|
PBI-18
|
As a customer, I want to see the history of my orders, so that I can quickly re-order them.
|
Lukas Knight
|
Low
|
12
|
To-Do
|
DoD1
|
|
PBI-25
|
As a customer, I want to re-order my previous order, so that I can save time on ordering.
|
Lukas Knight
|
Low
|
3
|
To-Do
|
DoD1
|
|
PBI-20
|
As a customer, I want to log in using Google / Facebook, so that I don’t need to register.
|
Lukas Knight
|
Low
|
3
|
To-Do
|
DoD4
|
Interview tasks for Scenario 3:
In this scenario, a product backlog will be provided to you. You need to analyse the provided product backlog with respect to the Notes made during the initial requirements elicitation interviews (these notes have bee provided to you in A2: Team-based Assignment: Scrum Project Planning). Assume in this scenario that the Scrum team consist of five members: Alex Bell, Wei Wei, Kelly Lee, John Ngo, Alice Long. Alex Bell is also the Scrum Master. The Product Owner for this project is Lukas Knight.
Task 3.1 – IDs, priorities, sorting, statuses, owners: Analyse PBI IDs, priorities and sorting of the provided product backlog, as well as statuses and PBI owners. Explain whether you identified any issues there (and demonstrate how exactly you fixed these issues). Present the results of your analysis in the following order:
1. Analysis of IDs
2. Analysis of priorities and sorting
3. Analysis of statuses
4. Analysis of PBI owners
Task 3.2 – Efforts and DoD: Analyse the efforts of the PBIs and explain what issues you identified (and how exactly you will fix them) there. Analyse the DoD column of the PBIs and explain what issues you identified (and how exactly you will fix them) there. Analyse both DoD1 and DoD2 with respect to the Notes made during the initial requirements elicitation interviews.
Task 3.3B – Functional requirements (Variant for Bachelor students): Analyse user stories in the provided product backlog and explain what issues you identified (and how exactly you will fix them) there.
Task 3.3M – Functional requirements (Variant for Master students): Analyse user stories in the provided product backlog and explain what issues you identified (and how exactly you will fix them) there. Select one user story out of the product backlog and demonstrate how you would specify the corresponding functional requirements if the project were conducted using traditional (Waterfall-like) methodology.
3. Video (up to 5 minutes long), where you present your solutions for Scenario 3 tasks. Please name this file sXXXXXXX-Scenario3, where sXXXXXXX should be replaced by your student ID.
The format of the videos must be avi, mp4, mov, wmv, mpg, webm. The videos should contain both, screen capture and camera capture of you (clearly presenting your face), the camera capture should be provided for the whole duration of the presentation.
Note: Only files submitted in Canvas → Assignments in the required format will be considered for marking. Any files uploaded to external resources (e.g., Google Drive, team’s co-work space in Canvas, etc.) or links to Trello, github, etc. cannot be considered for marking.