关键词 > ISYS1106/1108
ISYS 1106/1108 SE Project Management A2
发布时间：2024-06-05
Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: daixieit
ISYS 1106/1108 SE Project Management
A2: Individual work (on-demand interview) – Scenario
Scenario 1: Team’s progress presented on burndown charts
The team is working on a Scrum project in fortnightly sprints, the project is planned for 5 sprints. The Sprint 1 has been started on 4 March. In your analysis, please take into account that the following days are public holidays in Victoria:
- 11 March (Monday, Labour Day)
- 29 March (Good Friday)
- 1 April (Easter Monday)
- 25 April (ANZAC Day, Thursday)
At the beginning of the project (just before the team started Sprint 1) The overall sum of story points in the product backlog was 137.
Please take the following information regarding the efforts of the following High priority PBIs (Product Backlog Items), specified in story points:
- PBI-1: 8 story points
- PBI-2: 2 story points
- PBI-3: 5 story points
- PBI-4: 3 story points
- PBI-5: 1 story point
- PBI-6: 8 story points
- PBI-7: 3 story points
- PBI-8: 2 story points
- PBI-9: 8 story points
- PBI-10:3 story points
- PBI-11: 2 story points
- PBI-12: 8 story points
The product backlog doesn’t contain any Critical priority items, but it contains several other High and Medium priority items. At the end of Sprint 0, it also contains only three Low priority items:
- PBI-39 estimated as 13 story points
- PBI-40 estimated as 21 story points
- PBI-41 estimated as 13 story points
You also need to take into account the following events of the scenario:
At the sprint planning meeting for Sprint 2, the Product Owner requested to add to the Product Backlog two low priority items: PBI-42 and PBI-43. The team and Scrum Master agreed to this change, the team estimated the efforts for them as 5 story points each.
At that meeting, the Product Owner decided to remove PBI-24 and PBI-25 from the Product
Backlog (previously, PBI-24 was estimated as 3 story points, and PBI-25 was estimated as 1 story point). Both items have been previously assessed as medium priority items. The team and Scrum Master agreed to this change as well.
The team had the following progress over Sprint 1 and Sprint 2:
|
|
Monday |
Tuesday |
Wednesday |
Thursday |
Friday |
|
Sprint 1, Week 1 |
Design tasks and implementation tasks for PBI-1 have been completed |
Unit testing and code peer review for PBI-1 have been completed (passed) |
All tasks for PBI-1 have been fully completed (including QA tasks) |
All tasks for PBI-2 have been fully completed (including QA tasks) |
All development tasks for PBI-3 have been completed, Functional testing based on ACs has been almost completed |
|
Sprint 1, Week 2 |
Public holiday |
All tasks for PBI-3 have been fully completed (including QA tasks) |
All development tasks for PBI-4 have been fully completed, but testing revealed issues in the implementation of PBI-2 |
PBI-2 has been fixed and re-tested as per DoD, PBI-4 has been also fully completed (including QA tasks) |
All tasks for PBI-5 have been fully completed (including QA tasks) |
|
Sprint 2, Week 1 |
Design and front-end tasks for PBI-6 and PBI-7 have been completed |
Back-end tasks for PBI-6 and PBI-7 have been completed |
All tasks for PBI-6 and PBI-7 have been fully completed (including QA tasks) |
All tasks for PBI-8 fully completed (including QA tasks) |
Design and front-end tasks for PBI-9, PBI- 10 and PBI-11 have been completed |
|
Sprint 2, Week 2 |
Back-end tasks for PBI-9, PBI-10 and PBI-11 have been completed, but testing revealed issues in the implementation of PBI-8 |
PBI-8 has been fixed and re-tested as per DoD, QA tasks for PBI-9, PBI-10 and PBI-11 are in progress |
All tasks for PBI-9 and PBI-11 have been fully completed (including QA tasks) |
All tasks for PBI-10 have been fully completed (including QA tasks), design task for PBI-12 has been completed |
Public holiday |
Interview tasks for the video on burn-down chart (based on Scenario 1):
You need to create the corresponding burndown chart for the project (as it should be at the very end of Sprint 2, after the Sprint review meeting) and record video, where you need to present it. You can selected here between two options:
• Option 1: classical burn-down chart
• Option 2: calendar-based burn-down chart
In the presentation, you need to cover the following points (please don't forget to mention which of two options you selected to create - a classical or a calendar-based burndown chart):
Task 1: Explain how you created the ideal burndown – how you decided what should be its top point, how you calculated the number of working days in the project and the ideal daily velocity, how/whether the decisions announced by the Product Owner on Sprint 2 Planning and Review meetings influenced your calculations.
Task 2: Explain how your real burndown was evolving day by day over the duration of sprints.
Task 3 (Variant for Bachelor students): Calculate ideal, acceptable and real velocities for the provided scenario. Explain what you can conclude from the results of calculations.
Task 3 (Variant for Master students): Analyse the chances of the team to complete the project successfully, if they continue with the same real velocity and capacity as at the end of Sprint 2.
Please note that the video should contain both, screen capture and camera capture of you, for the whole duration of presentation.
Scenario 2: Quality Assurance analysis
The team decided to have 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 general development task approach.
The team decided that information radiator will be an Excel spreadsheet with a Product backlog, and for each Sprint they are going to create Excel spreadsheet with a Sprint backlog (all spreadsheets shared with all team members in OneDrive, with Edit-rights).
When preparing to the Sprint 1 planning meeting, the team also created Acceptance Criteria (ACs) for a number of high-priority PBIs. The ACs for
PBI 15. As a customer, I want to select whether I will pay for my order with credit card or PayPal, so that I have flexibility of payment.
have been specified as follows:
AC13.1
Given the customer is on the cart page of the application
When the customer selects the option “ payment with credit card”,
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 credit card number, name on the card, and the expire date of the card.
The below screenshot (of a part of a Trello card) presents sprint tasks they specified:
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 123.0, Safari 17.4.1)
• Regression testing passed
• Approved by the Product Owner
Interview tasks for the video on QA analysis:
Task 1: 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: 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 sprint tasks for this PBI).
Task 3 (Variant for Bachelor students): You need to specify test cases for a sprint task that aims to cover the following item of the Definition of Done: Functional testing based on ACs passed
(manual testing).
Task 3 (Variant for Master students): You need to specify test cases for a sprint task that aims to cover the following item of the Definition of Done: Functional testing based on ACs passed
(manual testing). Gou also need to discuss what would be different in your activities if this item of
the Definition of Done would be formulated as Functional testing based on ACs passed (automated testing using Selenium).
Please note that the video should contain both, screen capture and camera capture of you, for the whole duration of presentation.
Scenario 3: Product Backlog analysis
The Product Backlog (as per the end of Sprint 0) is presented below. The 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 80%)
• Code peer reviewed
• Functional testing based on ACs passed
• Usability testing passed (Chrome 123.0, Safari 17.4.1)
• Regression testing passed
• Approved by the Product Owner
DoD2:
• Unit testing passed (code coverage 75%)
• Code peer reviewed
• Functional testing based on ACs passed
• Usability testing passed (Chrome 123.0, Safari 17.4.1, Mozilla Firefox 117.0)
• Regression testing passed
• Approved by the Product Owner
The Product Backlog (as per the end of Sprint 0) is presented below.
Interview tasks for the video on PB analysis:
You need to analyse the provided product backlog with respect to the Notes made during the initial requirements elicitation interviews (provided to you in Assignment 1).
Task 1: Analyse
o PBI priorities,
o user stories,
o PBI statuses,
o PBI owners, as well as
o efforts,
and explain what issues you identified there and how exactly you will fix these issues.
Task 2: Analyse PBI IDs and sorting of the provided product backlog, explain whether you identified any issues there (and demonstrate how exactly you fixed these issues).
Task 3 (Variant for Bachelor students): Analyse the DoD column of the product backlog wrt. the provided Definitions of Done.
Task 3 (Variant for Master students): Analyse the DoD column of the product backlog wrt. the provided Definitions of Done. Analyse both DoD1 and DoD2 with respect to the Notes made during the initial requirements elicitation interviews.
Please note that the video should contain both, screen capture and camera capture of you, for the whole duration of presentation.
