We often hear concerns from DX (Digital Transformation) promotion managers such as, "We want to introduce agile development, but we don't know the specific steps for implementing Scrum," or "We started Scrum development, but the roles and events have become mere formalities." In fact, Scrum is a framework that was inspired by product development methods used in Japanese manufacturing in the 1980s. Although it is a software development methodology, it is based on ideas that are well-suited to the manufacturing environment. In this article, we will organize the three roles, three deliverables, and five events that make up the basic structure of Scrum development, and explain the process, advantages, and disadvantages in an easy-to-understand way.
What is Scrum development?
Definition of Scrum | A methodology for agile development
Scrum development is a leading framework for practicing agile development. It divides projects into short periods called "sprints," and gradually builds working software by repeating the cycle of planning, developing, testing, and improving.
Its key feature is that it allows teams to autonomously continue development and improvement by following minimal rules such as defined roles, events, and deliverables.
For more information on agile development, please see here.
The origins of Scrum | A method that originated in Japanese manufacturing
The origin of Scrum is,1986In that year, Hirotaka Takeuchi and Ikujiro Nonaka published an article in the Harvard Business Review titledThe New New Product Development GameThis paper analyzes the product development processes of Japanese manufacturers such as Honda, Canon, and Fuji Xerox. Instead of simply passing on tasks sequentially, the process, involving members with diverse expertise working together as a team, is likened to a rugby "scrum."
Based on this idea,1990Scrum, as we know it today, was systematized in the 1970s by Jeff Sutherland and Ken Schwaber as a software development framework.
Differences from waterfall development
In contrast, the traditional waterfall development method proceeds in a unidirectional direction from upstream to downstream, following the sequence of requirements definition, design, implementation, testing, and delivery. Because each stage is completed before moving on to the next, it is difficult to change specifications midway through, and detailed requirements must be finalized in the initial stages.
On the other hand, Scrum development divides projects into small units and gradually develops the product by repeating the planning, development, testing, and improvement cycles in short increments. A major difference is that requirements can be reviewed along the way, and customer feedback can be continuously incorporated.
Three roles that support Scrum development
A Scrum team is a small, autonomous team that primarily consists of three roles.
The first is the "Product Owner." They are responsible for maximizing the value of the product and deciding which features should be prioritized for development.
The definition and role of a product owner are explained in detail in the following article, so please take a look.
The second role is "Scrum Master," who helps the team to internalize the Scrum philosophy and rules, enabling them to proceed with development smoothly.
The third group is "developers," the members who actually bring the product to life. They autonomously design, implement, and test features, utilizing their respective specialized skills.
List of documents required for Scrum development
Product backlog
This is a list of features and requirements necessary for development, prioritized and arranged accordingly. It is managed by the product owner and treated as a "living document" that is continuously updated as needed.
Sprint Backlog
This document summarizes the items decided to be addressed in that sprint from the product backlog, along with the plan for achieving them. Developers create this during sprint planning and update it as needed during the sprint.
Increment
This refers to the accumulation of usable deliverables completed by that sprint. A key concept in Scrum is to always aim for a release-ready state by combining the deliverables created in previous sprints.
How to proceed with Scrum development
In Scrum development, development progresses by repeating multiple events within a short period of time.
A sprint is the basic unit of development, typically set at around 1 to 4 weeks (2 weeks being the most common), during which the planning, development, testing, and improvement cycle is carried out. The other four events take place within one of these sprints.
This is the planning meeting held at the beginning of the sprint. The product owner outlines the business value to be achieved this time, and the development team considers which features to build and which tasks to prioritize from the product backlog.
These are short meetings, lasting about 15 minutes, held once a day. Developers share progress and coordinate their work schedules for the day.
This is a forum to share the results of the sprint with stakeholders. We review the developed features, receive feedback, and incorporate it into the plan for the next sprint.
This is a retrospective session held at the end of each sprint. We review the development process and teamwork during that sprint and decide on specific actions to improve the next sprint. By repeating this cycle, we can rapidly and continuously iterate on development and improvement.
Advantages and disadvantages of Scrum development
merit
The major advantages include the ability to flexibly incorporate customer feedback and market changes during development, the ease with which results can be seen due to repeated small releases, and the promotion of team learning and improvement.
Its resilience to change, high flexibility, and speed of implementation make it well-suited for projects with a high degree of uncertainty.
Demerit
One disadvantage is that it's difficult to forecast schedules and costs because plans change frequently.
Furthermore, since continuous adjustments and close communication within the team are essential, it's important to note that if roles and the intent of the event are not properly understood, it can easily become a mere formality.
Projects that are well-suited to Scrum development
For large-scale projects or government contracts where strict control over procedures and quality is required, the waterfall model is suitable. However, if you want to incorporate user feedback into the development process and require easily measurable results, Scrum development is a better choice.
This method is particularly well-suited for new businesses where requirements are not yet fully defined, and for product development where you want to flexibly revise features in response to market changes.
[Video Explanation] Content for Practical Learning of Scrum Development
To ensure that roles and events are implemented effectively without becoming mere formalities, practical learning using actual projects is essential. Macnica produces video content for IT/DX promotion personnel that teaches the Scrum development process and the role of the product owner.
[Video Content Overview]
- The concept of agile development in comparison to the waterfall model.
- Scrum team structure and development process
- Responsibilities and required skills for a product owner
- Practical methods for creating product visions and documentation processes.
For more details, including the practical Scrum development section, please click the form below to view the video.
[DX Talent Development] Introduction to Product Ownership Course: From Scrum Basics to Writing PO Documents
This introductory course uses videos to teach you everything from the basics of Scrum to the role of a Product Owner and how to write documentation.
*Registration is required to view.
Frequently Asked Questions about Scrum Development
Projects are divided into short periods called "sprints," and the product is built step by step by repeating the cycle of planning, developing, testing, and improving according to defined roles, deliverables, and events.
Agile methodologies include other techniques such as Kanban, but Scrum is characterized by its clearly defined roles, events, and deliverables.
On the other hand, if the division of roles and the purpose of events are correctly understood and established within the team, this method can reduce the burden of responding to changes and rework, making it easier to proceed with development at a sustainable pace.
In the initial stages of implementation, incorporating guidance and training from experienced individuals is key to ensuring consistent adoption while minimizing the burden on participants.
The name is derived from the rugby term "scrum," representing the team working together to advance development.
Furthermore, it's important to note that roles and events can easily become meaningless if their purpose isn't properly understood, making continuous adjustments and close communication within the team essential.
For practical application of Scrum and Agile development, and talent development, please consult Macnica
Scrum development is a framework that enables resilient and flexible product development by repeating the planning, development, testing, and improvement cycle according to defined roles, deliverables, and events. However, to fully realize its benefits, it is essential not only to implement the system but also to cultivate personnel who understand the agile way of thinking and the intent behind the roles and events.
Macnica 's strength lies not only in technical support but also in providing personalized support centered on "people," and it has approximately [number missing in original text] in Japan. 100 Company 300 More than [number] smart factories/manufacturing companies DX Based on our track record of support, DX Human resource development and CoE We provide comprehensive support, from establishing the (promotion organization) to implementation.
If you are struggling with implementing Scrum/Agile development or developing product owner talent, please feel free to contact us.