You will also need to have an appreciation of how to score a bridge match (referred to as a round in the product). The following website will help you understand match point scoring. Be sure you understand the features implemented in the product.
The following user stories are from the plan for Sprint 1. You will need to add these user stories to the product and sprint 1 backlogs of your Taiga project.
User Story 1 Enter Pairs
As Jeff, the Bridge league organiser, I want to be able to allocate names to a match pair number so the we can distribute match result percents and ranks.
• We should be able to specify the pairs for any round in any league
• The number of pairs, including a possible missing pair, should be correctly determined using the round’s chosen movement
• Only valid players can be specified in a pair
• A table of the match results should be generated listing the percents and ranks beside the names in each pair
User Story 2 Enter Board Scores
As the Bridge league organiser, I want to be able to enter the board scores for a match so that the match points can be calculated and distributed to players.
• The number and configuration of each board should be determined using the round’s chosen movement
• The boards should not accept board scores for missing pairs
• The match results should depend on the board scores
User Story 3 Change Movements
As the Bridge league organiser, I want to be able to change the movement of a match (or round) so that we can play a match with different numbers of players.
• Should only be able to select valid movement types for a round
• Changing the movement type should update the number of pairs and board configurations for a round
User Story 4 Substitute players
As the Bridge league organiser, I want to be able to specify substitute players in case only one partner in a league pair turns up
• Must be to specify which partner the substitute is for
The following user story s in the product backlog, but was not in Sprint 1 backlog.
User Story 5 Missing pair
As the Bridge league organiser, I want to be able to specify an optional missing pair so that I can more easily deal with different numbers of players
• Any valid pair number based on the movement type can be selected as the missing pair so that I can have flexibility in my table arrangements
With the written permission of the unit coordinator, you may work on an alternative project for, for example, your work or hobby.
1. Update Taiga plan to reflect project progress
The project expects to run 3 sprints. The first sprint has already been completed; you will plan and review the second sprint and make recommendations for the third sprint.
You are provided with a rough project plan and development files of an ICT project representing progress made in the project at the end of its first sprint, that is, Sprint 1. You will need to create a Taiga plan to reflect the project status at the end of Sprint 1. You can use Taiga.io to create a Taiga plan. You will need to complete tasks such as the following:
• Perform acceptance testing to check which of the user stories in the sprint plan have been successfully completed. You will update the Taiga plan to reflect this progress.
• Identify issues related to Quality and Risks and create plans to deal with the issues. Add the issues, risks and controls you plan to implement to the Sprint Issues section on the sprint taskboard in your Tiaga project. Although your group will not be developing during this assignment, you should identify issues as though your group was the development team for Sprint 1 and will be the development team for the remainder of the project.
2. Create Sprint 2 Plan You need to:
• Create at least 5 additional user stories and add them to the product backlog. Pairs should create at least 8 additional user stories. Groups of 3 should create at least 10 additional user stories. Your user stories should:
o Adhere to Moore’s template o Possess INVEST properties o Contain appropriate acceptance criteria
o Include a story point effort estimation and monetary value • Decompose user stories into subtasks
• Prioritise the product backlog.
• Choose user stories for the sprint backlog for Sprint 2 with due consideration of the team’s velocity.
In Week 4, you will submit your Taiga plan to the unit website. Export your project from Taiga and upload the project file to the unit website. You will not receive formal feedback for this plan until after your presentation.
3. Present Sprint Review
In Week 5, you will be provided with a new set of development files representing the product at the end of Sprint 2. To prepare for your presentation, you will need to update the Taiga plan that you submitted in Week 4 to reflect the progress made in the project.
In Week 6, you will present a review of Sprint 2 which should cover aspects such as:
• Acceptance testing: each member of the team should demonstrate a different, completed user story by performing a walkthrough showing that the acceptance criteria for the user story have been met. Please demonstrate your own Sprint 2 user stories if possible, otherwise, you may demonstrate Sprint 1 user stories.
• Scope management, for example,
o Present and discuss your Taiga’s product and Sprint 2 backlogs: which user stories passed and did not pass acceptance testing
o Discuss your size estimates for each user story
o Present and discuss your Taiga Kanban table for Sprint 2 detailing how you broke down each user story into subtasks. o Present and discuss your Taiga burndown chart, your choice of velocity for Sprint 2 and determine what velocity you would use for Sprint 3
• Quality and Risk management, for example, present and discuss your Taiga sprint issues related to quality and risks including any management plans regarding either Sprint 1 or 2.
You do not need to create a Sprint 3 plan.
Each team member should talk for between 3 to 5 minutes each.
Oncampus student will present their sprint reviews in the Week 6 class. The lecturer might record presentations for moderation purposes. Groups must be prepared to present even if one or more team members are not present at the Week 6 class. Students who do not present will receive 0 marks for the presentation components of the assessment.
Distance students will present their sprint reviews in an online Zoom session. Distance students who are working in groups can present their components of their sprint review to their group. Distance students who are working alone must form groups of at least two for the presentation. You will present your sprint reviews to your group members and record the presentation including the video feeds of all group members and your shared desktops. In Week 6, you will submit a link to a cloud hosted copy of your video.
controls, between groups will be considered plagiarism. If you are in doubt about whether you can share something, first obtain email consent from your lecturer.
Plagiarism will dealt with according to University policy. Plagiarism penalties and academic misconduct charges may apply to all group members. Your assignment might be assigned a zero grade or reported for further action.
You may complete this assignment alone or in a group of up to three people. You will form your own teams.
This assignment has assessment due in Weeks 4 and 6.
In Week 4, you are to export your Taiga project plan and submit it to the unit website. All team members should be added as Members of the Taiga project plan using Admin Members New Member. All group members must submit the Taiga project file.
Oncampus students will present their sprint reviews in the Week 6 class.
In Week 6, distance students are to submit a link to videos containing their presentations. All distance students must submit.
If one student receives an extension, all students in the group will receive the same extension.
Incomplete submissions, for example, due to insufficient permissions or corrupt files, might not be marked or a late penalty might be applied.
You will not receive formal feedback for the plan you submit in Week 4 until after your presentation.
Informal feedback may be provided during in-class presentations. Your marks and formal feedback will be returned in Week 7.