- 註冊時間
- 2024-3-5
- 最後登錄
- 2024-3-5
- 閱讀權限
- 10
- 積分
- 5
- 精華
- 0
- 帖子
- 1
|
They shared some things that they were especially glad to incorporate! ■Speaker profile Shogo Ishikura Manager of Workship development team and customer support team. After working as a customer support officer at SAP, which develops social games, he became an engineer and gained experience building large-scale payment systems and e-commerce web services. He joined GIG in 2018. What the Workship team worked on for “Kaizen” Before the coronavirus pandemic, GIG's team environment allowed for face-to-face conversations such as ``I want you to do this'' and ``I want you to do this.
'' However, with the introduction of remote work, issues arose, such as making it difficult to see the overall schedule and not being able to reflect detailed nuances that are Phone Number List difficult to grasp through communication alone on chat tools. Therefore, the Workship team Scrum development and Jira implementation Label your pull request Inquiry status report Introducing Kaizen such as This time, I will introduce the procedure, the intention behind introducing it, and the good things I actually experienced after implementing it.
1. “Scrum” is a “framework for working in a team . ” Specifically, we organize the team's tasks into development periods called "sprints," and we hold "daily scrums" (morning meetings) to check progress with the entire team. In the Workship team Separate sprints (development periods) Implementation of morning meeting (daily scrum) Implementation of regular (sprint review) KPT (Sprint Retrospective) We introduced "Scrum development" divided into four stages. Let's take a closer look at each.
|
|