By holding a regular meeting at the end of a sprint

Separate sprints (development periods) By separating the development period with the words, “This week, I will develop Clarify tasks. It's now easier to know which task to start on. A morning meeting was held in which the entire team grasped the implementation progress of the morning meeting (daily scrum) . In addition to checking the progress of each team member's tasks, by providing opportunities to casually talk every day, you can share small concerns that you thought didn't need to be posted on a chat tool. This will lead to a speedy solution.

Implementing a regular (sprint review)  and sharing sprint progress and release information, you will be able to understand the release content that was handled by someone Phone Number List other than yourself, and you will be able to review it in the next sprint. It is now possible to share things. KPT (Sprint Retrospective) KPT is a retrospective framework consisting of " Keep ", " Problem ", and " Try ". By clarifying what we should continue to do in the future (Keep), the problems we are currently facing (Problem), and what we want to try next (Try), we are now able to make improvements within the team.




Ishikura: "The Workship team in particular has been able to take proactive action on KPT's 'T', and this has led to the activation of the next sprint." Another point of note is the introduction of "Jira" in conjunction with Scrum development . Jira is software that allows you to plan, track, and manage development projects. The Workship team visualizes schedules and tasks using the ``roadmap function'' that allows you to create a Gantt chart of the entire schedule, and the ``board function'' that allows you to create a task management board for each sprint .