Skip to main content

Suggested Reading for PSD I™

Prove Your Knowledge of Applying Scrum for Software Development

PSD I includes questions from the following Focus Areas as defined in the Professional Scrum Competencies. Approximately 85% of the questions will be selected randomly from the following Focus Areas.

Additionally, approximately 15% of the questions will be selected randomly from the Focus Areas listed below. These questions are designed to validate your knowledge around the core concepts of Scrum. First and foremost, read and understand the Scrum Guide. You might also benefit from reviewing material found on the PSM I Suggested Reading page.

Where to begin

Blogs and Articles


Cross-Functional, Self-Managed Development

Developers in Scrum are self-managing. Self-management requires not only the availability of the right development skills, but also collaboration, team commitment, joint problem ownership, shared goals and creativity. The Developers autonomously make all decisions on how to do the work that they have forecast to complete in a Sprint.

Backlog Refinement

Creating great software includes understanding the needs of users, stakeholders and the marketplace. In today’s highly complex markets with many unpredictable changes, details are added to requirements last minute, and even while programming. The Developers and the Product Owner collaborate on the software expectations in creating, clarifying, and estimating items in the Product Backlog.

Design, Architecture, and Programming

Scrum has an iterative-incremental approach to software development and the focus is on shippable software at the end of every Sprint. In the domains of software design and architecture this leads to a major shift, i.e., from prescriptive and upfront to emergence. Designs and architectures grow and change as applications and products grow and change. As part of incremental development, Scrum places quality before scope. Writing high-quality code is an art in itself. It requires skills, dedication, mastery, agreed practices, and agreed on standards.


It is considered a good agile development practice to think through requirements before writing functional code. It helps to consider work in terms of how it will be tested, but it also helps to eliminate other wasteful activities that are traditionally part of upfront requirements specification processes. The ability to deliver shippable software by the end of every Sprint requires different testing strategies, where testing activities are to be done as part of development.


Find a Class        Take an Assessment

What did you think about this content?