Scrum.org Professional Scrum with Kanban level I (PSK I)

The Professional ScrumTM with Kanban level I (PSK I) assessment is available to anyone who wishes to validate their knowledge of how Scrum Teams can use Scrum with Kanban to support value creation and delivery.

Taking a course is not required. While taking a Professional Scrum with Kanban course is highly recommended, if you feel you already possess a high level of knowledge about Professional Scrum with Kanban, you have the option to take the PSK I assessment directly. The PSK I assessment is grounded in the Professional Scrum with Kanban subject areas: Kanban Practices, Agile Metrics, and The Scrum Framework.

The assessment is in place to ensure you understand how Scrum Teams can use Kanban.  Many questions ask the test-taker to think about or interpret the meaning from the Kanban Guide for Scrum Teams and the Scrum Guide and/or to apply content from the PSK subject areas and in some cases, apply their own experience.

Scrum.org Professional Scrum with Kanban level I (PSK I)

Prepare for the Assessment

The PSK I assessment is grounded in the Professional Scrum with Kanban subject areas. The assessment is exhaustive and rigorous. Many questions ask you to think about or interpret the meaning from the Kanban Guide for Scrum Teams and the Scrum Guide, apply content from the PSK subject areas, and in some cases, apply your own experience. Find additional information to help you prepare for the PSK I Assessment and ways to learn about Scrum.  

Scrum.org PSK I Exam Summary:

Exam Name	Scrum.org Professional Scrum with Kanban level I
Exam Code	PSK I
Exam Fee	USD $200
Exam Duration	60 Minutes
Number of Questions	45
Passing Score	85%
Format	Multiple Choice, Multiple Answer and True/False
Books / Trainings	Professional Scrum with Kanban
Sample Questions	Scrum.org PSK 1 Exam Sample Questions and Answers
Practice Exam	Scrum.org Certified Professional Scrum with Kanban level I (PSK I) Practice Test

Scrum.org Professional Scrum with Kanban Syllabus Topics:

Topic	Details
Understanding and Applying the Scrum Framework	Empiricism ◉ A cornerstone to Scrum and Agile. A practitioner will be able to apply the concepts of the empirical process to the problems they encounter. That means they can describe problems in terms of learning, break problems down into the smallest increments that will generate valuable evidence, and execute in an empirical way. By learning and practicing the skills in this Focus Area, a practitioner will become an expert in the application of scientific methods to complex problems, understanding why and how to apply an empirical process. Scrum Values ◉ For agility to thrive, the culture of the organization must support the fundamental concepts of agility. A practitioner will understand both the Scrum Values - Focus, Respect, Openness, Commitment, and Courage - and demonstrate that they can apply them in the reality of organizations whose values do not match those of Scrum. By living the Scrum Values and helping others to apply them, learners will create an environment where empirical process, self- organization, and continual improvement will be more successful. Scrum Team ◉ The Scrum Team consists of one Product Owner, one Scrum Master, and Developers. The skilled practitioner will understand how accountability is shared amongst team members and how they take on work in the context of their Product Goal. Events ◉ The Scrum framework describes 5 events: The Sprint, Sprint Planning, Daily Scrum, Sprint Review, and the Sprint Retrospective. All events are time-boxed and enable progress through adaptation and transparency. The practitioner will understand the events and be able to practice each event, but more importantly be able to apply these events in complex situations and at scale. The events are used to uphold empirical process control, through the three pillars of Scrum: transparency, inspection, and adaptation. Artifacts ◉ The Scrum framework describes 3 artifacts. The Product Backlog, Sprint Backlog, and Increment. These artifacts provide the team with a minimal set of materials to plan, execute, and review the Sprint. The Practitioner will understand these artifacts and how to implement them in complex, real-world situations. They will also understand the relationship of these artifacts relative to other practices and techniques and how to integrate them into an organization's own process. Done ◉ The objective of each Sprint is to deliver an Increment. The Definition of Done (DoD) provides a way for the team to make what done means transparent. In this Focus Area, the practitioner will be able to describe what a DoD is, apply it to their particular context, and understand how the DoD enables the benefits of agile. They will also be able to describe the implications of the necessary trade-offs and compromises required to deliver Increments within their organization. Scaling ◉ Scrum is designed to work at the team, product, and organization level. The practitioner will be able to apply Scrum in increasing levels of complexity and scale. They will be able to demonstrate when to scale and when not to scale and appreciate scaling practices and complementary frameworks that help organizations scale Scrum. The ultimate level of proficiency within this Focus Area is the ability to know what, and what not, to compromise in pursuit of a scaling approach by understanding the trade-offs and benefits of particular concepts and practices. Ultimately, the practitioner will demonstrate that they can scale Scrum and still keep its essential qualities of empiricism, self-organization, and continuous improvement. The practitioner should also be able to demonstrate the results of good scaling practices from both an organization and business perspective.
Complementary Practices	Kanban Practices ◉ Questions in this focus area test your knowledge of the Kanban practices listed in the Kanban Guide for Scrum Teams. Agile Metrics for Kanban ◉ Questions in this focus area test your knowledge of the required metrics listed in the Kanban Guide for Scrum Teams and how to use them effectively.