This article provides an overview of Project Sprint and helps you understand the content of individual documents in “Let’s Get Ready,” “Let’s Try,” and “Let’s Improve”.

Project Sprint is a “project promotion method” that enables diverse members to produce complex outputs in uncertain environments and situations.

In Project Sprint, the activities to promote a project are divided into three categories.

Project Sprint Conceptual Diagram

Project Sprint Conceptual Diagram (Project Sprint CODE Essentialsより引用)

  • Progress: Activities that focus on the deliverables and goals of the project
  • Process: Activities that focus on the procedures that drive the project forward
  • Teaming: Activities that focus on the relationships among team members

The basic mechanism of Project Sprint is “to make progress and teaming ideal through process.” So, what exactly is the “ideal state” of progress and teaming?

The “ideal state” of progress is the state in which the goals of the project have been achieved. The first step is to define the goals of the project that you want to achieve in the future. Then, we define the deliverables needed to achieve those goals and the path to create those deliverables (called milestones), and follow them. However, project goals and milestones are not absolute; rather, they change flexibly in response to changes in the environment, so it is necessary to consider that they can be constantly reviewed.

The “ideal state” of teaming, on the other hand, is a state in which the expectations of team members regarding the roles they should play (this is called roles) are aligned. In other words, when a team member thinks, “He will do this”, the team member also thinks, “This is what I should do.” The “ideal state” of teaming does not have a definite form. The reason is that it is difficult to determine “If we achieve this level, we are an ideal team!” is difficult to determine. Therefore, in Project Sprint, we always aim for “a better team state than the current one.”

To achieve the ideal state of progress and teaming, we use “process”.

Process is based on regular meetings and discussion of the agenda there.

In Project Sprint, meetings are used as “a place where all team members can share space and time to quickly and efficiently make decisions that everyone agrees on,” and agendas are used as “a way to share and recognize the activities of team members in a project with other team members.” In addition, the agenda is positioned as “something that is clearly stated so that the activities of team members in the project can be shared and recognized by other team members.”

Through these meetings, we can share the progress of the project, continuously improve the way the project is carried out, review milestones toward the project goal, and confirm each other’s roles.


Project Sprint CODE