SIT223-SIT753
Pass Group Task:
Sprint Planning in Trello
Sprint Planning in Trello
This is a Group Pass task.
Overview
This task is to plan your group project and your sprint planning for the first sprint that you will be working on your GIT project (Task 4.1GP). This task relates to the activities you have done during the class in week 3.
Prerequisite
Attend the class in Week 3 and complete the activities listed on the Week 3 class activity sheet on CloudDeakin. You will need to form a group of three members with students from your unit before Week 3 and will be required to work as part of the team to plan your group project in the following weeks. For the group formation process on OnTrack, please refer to this link.
Project Description
The Deakin University Website Redesign Project aims to redesign the university's current website to create a modern, user-friendly, and responsive website that caters to the needs of the university's students, staff, and faculty members. The project will involve the development of new features and functionalities while maintaining the existing content of the website. The website should have the following functionalities at the minimum:
1. The new website should have a visually appealing home page design that represents our university's brand.
2. The website should be easy to navigate, and users should be able to find the information they need quickly.
3. The website should have a search feature that allows users to quickly find information on the website.
4. We need a news section that provides up-to-date information about the university's events, news, and activities.
5. The website should have a student portal that provides easy access to academic records, course materials, and other important information.
6. The website should have a staff portal that provides easy access to HR information, payroll, and other important information.
7. The website should provide information about our university's programs, courses, and units including undergraduate, graduate, and research programs.
Please note that you are not required to implement or code the above tasks yourself. In the Week 4 task, you will receive the necessary HTML and CSS code to develop some of these requirements.
The primary goal of 3.1GP is to familiarise you with agile concepts, including sprint planning, user story definition, story point estimation, task allocation, and agile meetings (standups, sprint reviews, and retrospectives). In 4.1GP, you will gain hands-on experience with Git. During Week 4 (Sprint 1), you will partially implement today's first activity: sprint planning (populating your Trello board).
|
Task requirements
You are required to submit 1 file as part of this task as follows.
1. Sprint planning in Trello: Take screenshots of your sprint planning in Trello (for items
d and e, you might want to use a table in your word document). You need to submit the screenshots of your Sprint planning at the beginning and at the end of Sprint 1 (which runs from Week 4 to Week 6) to show that the product backlog has been regularly updated throughout the project, with tasks moved from the backlog to the "in progress" and "done" columns after completing your Task 4.1GP.
Your sprint planning should include the following:
a. Activities related to at least one sprint (Task 4.1GP).
b. Features/User Stories/Tasks to be investigated/implemented.
c. Members of the team assigned to user stories or tasks.
d. User stories
i) At least three user stories need to be defined.
ii) Include one cybersecurity-related user story or task.
iii) All possible tasks should be extracted from user stories.
e. Story points
i) Each user story or task needs to be assigned a story point.
ii) Discuss how you have come up with and assigned user story points.
iii) Need to clearly specify what your definition of “1 point” is and what s the difference between for example a user story with 2 points and a user story with 4 points.
iv) There should be a balance of user story points assigned to users, i.e., all users must have close to similar total user story points assigned to them for the duration of each sprint. Hence, clearly specify how many story points have been completed by each member in this sprint.
2. Sprint 1 Review demonstration. You are required to run your sprint review towards the end of week 6 (end of your sprint 1) within the group at your own time/group meetings. Summarise key points and progress from that meeting and record a 5—10- minute video demo. Your sprint review demo should include the following:
I. You will have 5-10 minutes for your recorded demo. Your demo will be timed.
a. Upload your demo video on a shared drive or perhaps YouTube or Deakin Air and put the link to the video in a PDF document. Please make sure the link works and your marking tutor with the link has access to the file.
II. At the very least, your demo should include:
a. Introduction: Sprint 1 backlog
b. Overview of your group activities in Sprint 1.
c. Introduction of project logistics: tools and resources (communication, MS Teams Trello, GitHub).
d. Identify user stories and introduce the tasks extracted from each of the user stories related to the Sprint 1.
e. Details of your sprint planning on Trello including tasks and roles. How all the tasks are distributed to Sprint 1 and different members. Include a screenshot of the Trello board.
f. Issues you have faced during your first sprint (what worked for you and what did not), and advice for other teams.
g. How did your team consider user privacy, accessibility, and security when planning the project?
Prepare the demo like you are pitching to the client and project manager at the same time. At a high level, you will need to show a good understanding and planning of the project.
3. Teamwork reflection. As a group, you need to provide a reflection on your experience working in a team that applies the Week 5 Borton model (what, so what, now what framework). Your reflection should also reflect on your group communication and teamwork. Write a (500–700 word) essay that includes the following elements:
a. Describe the roles and responsibilities of each team member.
b. Did each member fulfill their roles and responsibilities? If not, how did it affect the team's progress?
c. Reflect on the team dynamics. How did the team communicate and collaborate? Were there any challenges in the communication process? How were they addressed?
d. Describe any conflicts that arose during the project/assignment. How were they resolved?
e. Discuss the strengths and weaknesses of the team. What were the team's strengths that contributed to the success of the project/assignment? What were the weaknesses that hindered the team's progress?
f. What could the team have done differently to improve the outcome of the project/assignment?
g. What did you learn from working in a team? How will you apply these lessons to future team projects?
h. If you had to choose between delivering a feature quickly or ensuring it was ethically and securely implemented, what would your team prioritise?