Hello ,
Welcome to KACHIN Tec.
Before officially entering the team, we will take you through the process and operation of Scrum.
Please read the content of each task carefully, complete the task accurately, and successfully pass this scrum pre-training.
Scrum Team
Scrum, a simple framework of project management, was developed by Jeff Sutherland and Ken Schwaber. Later they published the methodology as “Scrum Software Development Process.”
Product Owner
Agile teams are, by design, flexible and responsive, and it is the responsibility of the product owner to ensure that they are delivering the most value. The business is represented by the product owner who tells the development what is important to deliver. Trust between these two roles is crucial.
Scrum Master
Scrum masters are the facilitators of scrum, the lightweight agile framework with a focus on time-boxed iterations called sprints. As facilitators, scrum masters act as coaches to the rest of the team. “Servant leaders” as the Scrum Guide puts it. Good scrum masters are committed to the scrum foundation and values, but remain flexible and open to opportunities for the team to improve their workflow.
Development Team
The development team are the people that do the work. At first glance, you may think the “development team” means engineers. But that’s not always the case. According to the Scrum Guide, the development team can be comprised of all kinds of people including designers, writers, programmers, etc.
Scrum Process
Scrum, a simple framework of project management, was developed by Jeff Sutherland and Ken Schwaber. Later they published the methodology as “Scrum Software Development Process.”
*Hover on any specific step to get more details
Product Owner
Product Backlog
The product backlog gives an overview of the entire product,is a prioritized list of work for the development team that is derived from the roadmap and its requirements.
The most important items are shown at the top of the product backlog so the team knows what to deliver first.
Daily Scrum
As the name suggests, this meeting happens every day during a Sprint. It is a short, time-boxed event and serves to update the rest of the team about individual progress and impediments.
Team member
Sprint Planning
The Sprint planning is an event in scrum that kicks off the sprint. The purpose of sprint planning is to define what can be delivered in the sprint and how that work will be achieved.
Sprint planning is done in collaboration with the whole scrum team.
Sprint
This occurs before every Scrum sprint. Here the Scrum team works together to determine the goal of the sprint and establish details around capacity and workload.
Scrum Master
Sprint Backlog
The sprint backlog is a list of tasks identified by the Scrum team to be completed during the Scrum sprint.
It gives a closer focus on the work of the product during a specific time period.
Sprint Review
Team members gather around a desk for informal demos and describe the work they’ve done for that iteration. It’s a time to ask questions, try new features, and give feedback.
Sprint Retro
The purpose of the sprint retrospective is to increase the quality and effectiveness of the next sprint by reviewing the issues that arose from the previous sprint. This enables teams to improve and overcome any process obstacles that proved tricky during the sprint.
Product Backlog
Daily Scrum
Sprint Planning
Sprint
1 -4 weeks
Sprint Backlog
Sprint Review
Sprint Retro
As a Product Owner
You need to have the ability to clearly identify the product needs. Please refer to the first and second user stories below to complete the third user story.
Document Status
In progress
Team
CASHKACHIN
Product Owner
Jira
F2E WEEK 3
User Story/Jira Issue
Acceptance Criteria
Notes
1
I learned about the different roles and responsibilities involved in Scrum.
- Need to explain the job description of Product Owner, Scrum Master and Development Team.
2
I can understand the Sprint process from the webpage
- Relevant understanding of Product Backlog, Sprint Planning, and Sprint Backlog
- Ability to identify the correct job role responsible for each process.
3
- Basic understanding on how to use Jira and Confluence.
Enter your own user story in this row.
As a Scrum Master
You need to know how to properly manage the Product Backlog to ensure that the tasks in the Product Backlog are sorted accordingly by value and priority. Please complete the task according to the mission requirements.
PLANNING
CASHKACHIN
Board
Roadmap
Backlog
Backlog
Report
Backlog
F2EWEEK3
FF
F2E-2320
3
Scrum(CASHKACHIN)
20/Oct/2022
I can understand the kno...
F2EWEEK3
CC
F2E-1981
0.5
Scrum(CASHKACHIN)
20/Oct/2022
I can use jira and confluen...
F2EWEEK3
FF
F2E-1987
1
Scrum(CASHKACHIN)
20/Oct/2022
I can interact with the scru...
F2EWEEK3
DH
F2E-785
3
Scrum(CASHKACHIN)
20/Oct/2022
I can understand the Sprin...
F2EWEEK3
FF
F2E-1902
2
Scrum(CASHKACHIN)
20/Oct/2022
Sprint (14/10/2022-28/10/2022)
FF
DH
CC
[Mission]
Please drag the tasks "Backlog" to the current "Sprint" and rank
them according to their prioritization from 3 (highest) to 0.5
(lowest). Make sure that there are no tasks remaining in the
"Backlog".
[What is Story Point]
Story Points are metrics used in Agile product development and management to guess how difficult it will be to implement a user story. Put another way, it’s a numeric value that helps the development team understand how challenging the story is.
Daily Scrum
Now as a team member (product designer), during the course of a week, you need to complete a total of 40 hours of work, wherein you must complete 8 hours of work each day.
Today is the second day of sprint, you need to report to everyone the status of the project at hand. Please arrange your task accordingly and drag the tasks from “TO DO” to “TO BE HANDLED” or “IN PROGRESS”.
Sprint (14/11/2022-21/11/2022)
DONE 2
[UI] Last Section Design
19-Nov-2022
2h
Feature-2320
FF
[UI] Entry Page Design
16-Nov-2022
4h
Feature-2320
FF
[UX] User Flow
17-Nov-2022
2h
Feature-2320
FF
[UI] Font Guideline
19-Nov-2022
2h
Feature-2320
FF
[UI] Last Section Design
19-Nov-2022
8h
Feature-2320
FF
[UI] First Section Design
20-Nov-2022
6h
Feature-2320
FF
[UI] Color Guideline
19-Nov-2022
1.5h
Feature-2320
FF
[Meeting] CC 1-1
19-Nov-2022
0.5h
Feature-2320
FF
[Meeting] Daily Scrum
19-Nov-2022
1.25h
Feature-2320
FF
[Meeting]
19-Nov-2022
4.75h
Feature-2320
FF
[UI] Wireframe
17-Nov-2022
4h
Feature-2320
FF
[UX] Content
20-Nov-2022
4h
Feature-2320
FF
Sprint Review
Sprint review meetings are conducted on the last day of every sprint, and serve as a means of showing the outcome and reviewing the projects completed during the sprint.
Sprint Review
Attendees:
FF DH CCReview Goals of the Sprint
- Potential contestant want to get F2E event information from the homepage of the website
- Training to improve design speed, communicate with engineers, and learn to write marking documents
Feedback & Notes
- Training to improve design/coding speed, communicate with teammate, and learn to write/read marking documents
Action Item
- Finish Week3 challenge
- Join F2E event on 2023
Release Demo - Responsive Web Design
Release Demo - Scrum Training
Sprint Retro
In this phase, team members will discuss what went well, what needs improvement, and what next steps should be taken for the following sprint.
Sprint (14/11/2022-21/11/2022)
Good
Can Be Better
Let’s Do
[Mission]
Please put memos containing words of affirmation onto the board.
The project is well scheduled
Everyone is so lazy
Thanks to DH do a lot of user interviews
Being too anxious when facing problems
Insufficient time for QA
Our scrum master is not efficient enough
Start filling out the documents properly
I want to quit my job
Make good estimate of the task point
Congrats! .
You have successfully completed the training.
Now that you understand what scrum is about, we are so grateful to have you as part of our team.
Use Atlassian software to to collaborate faster:
