• Clear vision for products and services
  • Maximize business value by responding flexibly to change
  • Strategic Thinking and Passion
The product owner plays an important role in guiding the project and ensuring its success.

In order to achieve fast releases of marketable products, it is essential to have a product owner. First, what is the difference between a Product Owner and a Scrum Master?

Both have the same goal of adding value to project management, but with different responsibilities. The Scrum Master concentrates on the team and its operations, while the Product Owner thinks about the project from the customer’s perspective.

The Product Owner works with many stakeholders to understand the vision and help the team realize it.

They are also responsible for managing stakeholder requests and feedback, but in many cases the product owner must say “no.” Because time and budget are always limited, the team cannot implement every idea or feedback that stakeholders have. Therefore, the product owner must have a clear vision, prioritize, and lead the team correctly.

Let’s understand the responsibilities of the product owner and learn tips to help you succeed.

Joe Justice has taught Scrum at major global companies and educational institutions in more than 20 countries around the world.

In Japan, companies such as Toyota Motor Corporation, Rakuten Group, Toshiba Group, NTT Group, and Mercari have also participated in training.Based on this experience, we are training ScrumProduct Owners  to further promote the adoption of Agile Scrum in Japan.

  • Have a clear vision of the product or service
  • Flexibility to adapt to change and maximize business value
  • Have strategic thinking and passion

    If you are interested in becoming such a Scrum Product Owner, please let me help you a little. I will be happy to teach you how to put the Scrum skills I have developed into practice in my Certified Scrum Product Owner class.

JoeJustice direct lectures

  • Questions Welcome!
In Joe's "Certified Scrum Master" class, he also answers various questions from the students.
Scrum is rapidly being adopted in Japan, and we will be happy to answer questions and concerns that come from the actual works such as the following;

I am wondering how to find a balance between agile development and quality.
I would like to market in quickly, but I am also concerned about the risk of glitches.

If I want to break a task into smaller story points, what is an acceptable amount of time to spend on this?
When I have a large PBI that does not fit in one sprint and it is difficult to divide it in terms of user stories, should I forcefully divide it by dividing the PBI by tasks, etc.?


Joe will reply in real time with clear answers that can be applied to the field!

Students can bring that back to their own work, which accelerates the speed of growth of the team.

  • Coordination of multi-team and large scale projects
  • Quick and effective decision-making strategies
  • Agile Contracts
  • Vision Strategy
  • Seven key personas
  • How to create a user story
  • Importance of estimating and prioritizing value
  • Release Plan
  • How to split backlog items
  • How to build up a backlog through refinement

  • This is an online class that utilizes Zoom.

    Teams will be formed in breakout rooms, and students will be invited to participate in a workshop-style lecture.

    Students will learn through experiences by practicing Scrum in teams using a virtual board created in Miro.

  • CSPO certification

    This seminar includes all curriculum required for certification.

    Upon completion of the 2-day training, the trainer will recommend and the Scrum Alliance will grant certification.

    The course fee includes Scrum Alliance certification. *Unlike CSM, there is no test.
Scrum Basics

What is Scrum?

Scrum” is one of the Agile methodologies used by many companies.
The project is divided into short periods of time, approximately a few weeks, and a series of tasks from planning, execution, and testing to completion are performed within that short period of time. This is a framework for completing a project in stages, repeating the process of completing parts of the project.
Leveraging scrum increases flexibility, allowing for quicker response to market needs and accelerated innovation in the organization.

Roles in Scrum

・Product Owner
Responsible for maximizing the value of the product and prioritizing work.
・Scrum Master
Responsible for promoting and supporting the scrum.
Create a usable increment.

Scrum Events

A short cycle of activities from project planning to completion. An increment is always completed at the completion of a sprint. (A sprint is an event that encompasses the following four)
The entire scrum team will participate. Developers create a sprint backlog to complete the highest priority product backlog items.
The Product Owner reviews the objectives to be achieved in the sprint and the product backlog items.
This is the shortest meeting to re-plan the day’s work for optimal output.
At the end of the sprint, the increment is inspected and, if necessary, the product backlog is scrutinized. The scrum team and stakeholders review the sprint results.

Review the status of the scrum team and the areas for improvement for the next sprint. This is done after the sprint review and before the next sprint planning begins.

Scrum Artifact

A list of every single sprint-sized project, product, or service. The product owner is responsible and the team helps.
A plan for the developer to work on the top product backlog items within the scope of the sprint to meet the completion definition and acceptance criteria.
A project or product or service in working and usable condition.

Scrum Accessories

・Not ready / NOT READY
A column or list just to the left of the product backlog allows you to review options for future work.
・Product Backlog Refinement?
At a meeting attended by everyone, items in the “not ready” column are scrutinized and prioritized in the product backlog. That product backlog meets the definition of ready.
It is usually located just to the left of the Not Ready column. The more than 80% chance that a particular product backlog item will complete its work within a sprint, the lower the risk, with minimal clarity and business integrity.
Where to place work that is waiting for external dependencies, such as another team, vendor, or robotic process outside of the team’s control.
The team’s commitment is that any work completed must meet its defined quality standards.
・Completed Board / DONE BOARD
Column for each sprint, scrolling back four or more sprints, meeting the definition of completion and accepted by the team’s customers in each previous sprint.
It is usually located above the sprint backlog. Indicates what was agreed upon by team members. The list is usually? s, but less than 10 items in order to be able to remember and use them.

Time chart showing what items met the definition of completion and when they were completed. Sprint burndown charts can quickly answer the question of when a particular scope will be completed.
A time chart showing when and what met the definition of completion in the current and past sprints when working in small increments toward a larger product.
Usually located just to the right of the completion board, it shows users, purchasers, maintainers, purchasing influencers, those funding the project, or internal stakeholders or compliance officers who may influence or be likely to influence the release or use of the product. The following is a list of the most common problems with the system. Each persona is given a short name, a picture to visualize, a short list of what they want from the product or service they are building, and any related dislikes or sources of dissatisfaction. Create a backlog to assess value and to please each persona to mitigate risk. Ensure that the benefit is maximized for every persona.
・Relative size estimation References
By referring to recently completed projects, the team can quickly and accurately predict the effort and complexity of the next project. Then, by projecting completion times according to completion definitions and acceptance criteria, teams can know when they will be completed and whether they are speeding up or slowing down.
・Relative Value Estimation References
Reference projects are considered by how much revenue they ultimately generated or how much impact they ultimately had on the company’s mission, mitigated risk, or learned new capabilities. This creates a value score. Using a value score that can be referenced from past projects, the product owner can quickly assess the rough value to the company. After taking that into account the size of the effort and the technical dependencies, the most valuable and least labor intensive work is tackled first.
It is a large board with rows for each team that is working and columns where you can see each sprint completed by each team. This shows the KPIs needed to run the entire business. In practice, these KPIs are usually the amount of money or resources each team consumed in that sprint and the amount of money or resources the output of that sprint brought to the company. The number of points of work completed by that team in that sprint, the quality issues and quality scores in the output of that sprint, and what specifically is completed in that sprint.

Certified Scrum Product OwnerR?

What is a Certified Scrum Product Owner?

Certified Scrum Product Owner/Certified Scrum Product OwnerR? is a certification offered by the Scrum AllianceR?.

What are the roles and responsibilities of a Certified Scrum Product Owner?

The main roles and responsibilities of the Scrum Product Owner are
・Prioritize the work of the scrum team
・Prioritization of products
・Selection and approval of work
・Keep clients up-to-date on status and obtain feedback

What is the difference between a Product Owner and a Scrum Master?

Product Owner and Scrum Master are different roles in the Scrum (Agile) development model. However, both have the same goal of adding value to project management. The ScrumMaster concentrates on the team and its operations, while the Product Owner thinks about the project from the customer’s perspective. The Product Owner is responsible for managing the product backlog and making it visible at all times. The Scrum Master, on the other hand, is responsible for motivating the team and helping to remove obstacles in order to facilitate project progress.

What is the process to become a Certified Scrum Product Owner?

The process to become a Certified Scrum Master is as follows
1. Attend in-person or online classes from a certified Scrum Trainer.
2. Upon completion of the class course, the Scrum AllianceR? will grant you a CertifiedScrumProductOwnerR? certificate.
*There is no test.

CSPO Class Training

I have no experience in scrum, can I participate?

This class provides training in the essential fundamentals for both experienced ScrumMasters and those who will become ScrumMasters.

Who should attend CSPO training?

・Those who plays a product owner role at work
・Those who want to build a career as a product owner.
・Those who want to prioritize and facilitate Scrum development for their Scrum team.
・Those who want to maximize the benefits of their Scrum projects.
・Team Manager

Can I pay by invoice?

Yes, it is possible. If you wish to pay by invoice, please contact us here.

Can I get a receipt?

Normally, a credit card statement will be used in place of a receipt, but if you need one, please contact us.

Can I cancel?

Cancellations can be made up to one day prior to the course date. No cancellation fee will be charged. A refund will be made minus a handling charge. Rescheduling is possible, so please let us know if you would like to reschedule.

An introductory course for those closest to the “business side” of the project.
Learn about the Scrum framework and understand the embodiment of the product vision.