Professional Scrum Competency: Understanding and Applying the Scrum Framework

Understanding and Applying the Scrum Framework IconOne of the first steps a Scrum practitioner should take is to learn about the Scrum framework. The Scrum Guide is the foundational body of knowledge for the Scrum framework. The Nexus Guide builds upon that foundation as the body of knowledge for the Nexus scaling framework.

To help practitioners advance their use of Scrum, the Understanding and Applying the Scrum Framework dives deeper into Scrum theory and the Scrum framework. The Focus Areas in this Competency explore the purpose of each of these elements and provide practical advice on how to use Scrum to increase the effectiveness of individuals, teams and organizations.

 

Key Focus Areas

This competency has the following key focus areas: 

Learning Series
In Scrum, empiricism refers to the idea that solving complex problems, or doing complex work, can only be done using an exploratory process rather than relying on predetermined plans. Learn about empiricism and complex work. Explore why trust is important for empiricism to thrive.
Module
For agility to thrive, the culture of the organization must support the fundamental concepts of agility. The Scrum Values - Focus, Respect, Openness, Commitment, and Courage - create an environment where empiricism, self-management and continual improvement are more successful.
4.7 from 39 ratings
Learning Series
The Scrum Team is a small unit of professionals focused on attaining the Product Goal. Scrum Teams consist of a Product Owner, Scrum Master and Developers. Each has a clear set of accountabilities. Learn more about the Scrum Team, accountabilities, responsibilities and why these aren’t called “roles.”

 

Learning Series
The five Scrum Events provide regular opportunities for enacting the Scrum pillars of Inspection, Adaptation and Transparency. In addition, they help teams keep aligned with the Sprint and Product Goals, improve Developer productivity, remove impediments and reduce the need to schedule too many additional meetings.
Module
In archeology, an artifact is an object of cultural significance. In medicine, artifacts are something not normally present, or unexpected. In Scrum, our use of the word “artifact” is closer to the way software developers use it: important information needed during the development of a product. ...
4.3 from 10 ratings
Learning Series
The Definition of Done describes the quality standards for the Increment. Learn why getting to Done is so important, what undone work is, if it’s okay to show work that isn’t done to stakeholders, can you present undone work at the Sprint Review and what’s the difference between the DoD and Definition of Ready or acceptance criteria.

 

 

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.

 

Back to Overview