3 Takeaways After Writing a 6,000 Word Scrum FAQs

Scrum is founded on three essential pillars, and each leads the team to ask a critical question.

1. Transparency. How does this make things more visible?
2. Inspection. Where does this create space to evaluate?‍
3. Adaptation. When does this encourage growth?

Learn how to apply the three pillars of Scrum and then explore the most common terms in a Scrum glossary.

‍

There are five values critical to the practice of Scrum: commitment, courage, focus, openness, and respect.

1. Commit to achieving the goals of the Scrum Team.
2. Courage to do the right thing and work on challenging problems.
3. Focus on the Sprint's work and the Scrum Team's goals.
4. Open about all the work and the challenges with performing the work.
5. Respect each other to be capable, independent people

Learn how to align Scrum values with your organization and then explore the most common terms in a Scrum glossary.

The sprint goal encapsulates the product owner’s vision into a concrete statement for the development team to measure the sprint against. The sprint goal provides a theme for the sprint’s work helping the team see how all the parts come together. 

Learn more about the role of the sprint goal in scrum and explore the essential Scrum glossary.

The definition of done is a list of what must be true to consider a PBI done. The whole team creates and agrees to what is in the definition of done and is updated as needed for the team to function effectively. 

Learn to use the definition of done and explore acceptance criteria vs definition of done.

It is the next complete piece added to build the product. The increment is complete in the sense that it should be ready to release to the end-user even if the team chooses to wait.

Learn more about incremental and iterative development or explore the essential Scrum glossary.

Scrum is founded on three essential pillars leading teams to ask the following questions:

1. How does this make things more visible? (Transparency)
2. Where does this create space to evaluate? (Inspection)
3. When does this encourage growth? (Adaptation)

Further explore the definition of scrum. Then browse the most common terms in a Scrum glossary and learn what is Scrum.

This is because Scrum’s simplicity makes learning easy, but Scrum truly changes how you work, and that adjustment can be difficult. It changes power dynamics and expectations within the team and between the team and the rest of the organization.

You can explore further is Scrum hard to learn, along with the pros and cons of Scrum. Then browse the most common terms in a Scrum glossary and learn what is Scrum.

Scrum was initially used as a term related to project management in 1986 by Hirotaka Takeuchi and Ikujiro Nonaka in their paper “New New Product Development Game” In the Harvard Business Review. The first recorded Scrum project came a little later in 1993 from Jeff Sutherland.

You can learn more about Scrum’s backstory. Then browse the most common terms in a Scrum glossary and learn what is Scrum.

Learning Scrum for the first time can be overwhelming. There are a lot of new terms and concepts in Scrum. I’ve listed the most common terms in a Scrum glossary.

It forces clarity and prioritization, which provides the focus necessary for teams to be effective. Scrum embraces complexity and change by keeping many things simple and iteratively evaluating and adapting. 

You can learn more about why to use Scrum and three challenges Scrum solves. Then browse the most common terms in a Scrum glossary and learn what is Scrum.

Scrum isn’t always the best option for teams. Scrum can fail when there is a substantial mismatch between organizational culture and the Scrum values. It also depends on the nature of the work you do. If you work if very linear, predictable and tightly defined, you may not experience many benefits Scrum provides.

Find out more about aligning your organizational values with Scrum or how Scrum might fit in your context. Then browse the most common terms in a Scrum glossary and learn what is Scrum.

Scrum functions at its best when you have a dedicated team focused on developing a singular product. Its agility shines when there are time constraints combined with uncertainty. 

Explore the pros and cons of Scrum along with expectations vs. realities with Scrum. Then browse the most common terms in a Scrum glossary and learn what is Scrum.

Important factors include your team size and the type of work you do. Kanban is very process-oriented, so you should consider how defined, static, or long your process is? 

You can explore Scrum and other agile approaches. Then browse the most common terms in a Scrum glossary and learn what is Scrum.

Scrum forces clarity and prioritization, which are critical to organizational effectiveness. It provides a competitive edge by allowing teams to adapt as the market or priorities change. Teams operate more effectively because Scrum combines empowerment of the team members with alignment to top priorities.

Learn more about scrum’s impact on organizational culture. Then browse the most common terms in a Scrum glossary and learn what is Scrum.

Scrum is more of a framework than a methodology, and it helps teams adhere to Agile principles and get stuff done. Scrum provides basic rules but doesn’t prescribe how to do the work. It provides principles, values, rules, and some core structure but still leaves a lot undefined.

Learn more about scrum as a framework. Then browse the most common terms in a Scrum glossary and learn what is Scrum.

When people say “agile,” they usually refer to it as a mindset. Scrum is a framework for how to organize people and work in an agile way. If you’re practicing Scrum, you’re working in an Agile way.

Learn more about the relationship between scrum and agile. Then browse the most common terms in a Scrum glossary and learn what is Scrum.

Are you looking for a challenge to motivate yourself to learn scrum better? Are you looking to land a specific job?

If you just want to take the next step in learning, the PSM has a low barrier to entry and should open some doors to allow you more opportunities to practice the scrum master role.

If you’re trying to land a job then it really depends on what that job is looking for certification-wise.

Here is my experience with certifications as a path to growth.

Want to learn the essential Scrum terms.

If you’re looking for your first scrum certification, the CSM and CSPO are the most common. Both require you to take a class by a certified instructor and cost around $1,000.

• The CSM - Certified Scrum Master requires a test at the end of the course to earn the certificate.
• The CSPO - Certified Scrum Product Owner does not require a test, as completing the course provides you with the certificate.

Here is my experience with certifications as a path to growth.

Want to learn the essential Scrum terms or how to pass the PSM exam.

The CSM and PSM are the two most common certifications for a scrum master:

• CSM Certified Scrum Master from Scrum Alliance. 
• PSM Professional Scrum Master from Scrum.org.

The CSM is more common than the PSM but also more expensive. Both offer multiple levels of certification.

You are required to take a class by a certified instructor for the CSM, which will cost you around $1,000. The CSM class includes the test cost and is comparable in difficulty with the PSM test.

The PSM recommends but doesn’t require a course. So you can take the self-study route and then take a cheaper test ($200). This level of affordability can make the scrum.org certifications a more attractive first step for people exploring scrum certifications.

Here is my experience with certifications as a path to growth.

Want to learn the essential Scrum terms or how to pass the PSM exam.

The PMI-ACP is in its own class regarding scrum certifications. It requires both documented experience as well as knowledge across multiple agile domains.

The test is long and comprehensive. I would place it as similar difficulty to the PMP as compared to the CSM or PSM.

This certification certainly demonstrates much higher agile and scrum competency. However, I don’t see it listed often on job requirements.

Here is my experience with certifications as a path to growth.

Want to learn the essential Scrum terms or how to pass the PSM exam.

The PMP is kind of the grandfather of project management certifications. It’s a beast of a test and requires memorizing a ton of information. However, it’s rooted primarily in waterfall rather than agile approaches.

Unless you plan to work in a domain where waterfall is dominant, the PMP probably isn’t the best certification option for those getting started in project management, and certainly not for those getting started with scrum.

Here is my experience with certifications as a path to growth.

Want to learn the essential Scrum terms or how to pass the PSM exam.

The most common certifications for a scrum master are:

• CSM Certified Scrum Master from Scrum Alliance. 
• PSM Professional Scrum Master from Scrum.org.

The CSM is more common than the PSM but also more expensive. Both offer multiple levels of certification.

You are required to take a class by a certified instructor for the CSM, which will cost you around $1,000. The CSM course includes the test cost and is comparable in difficulty with the PSM test.

The PSM recommends but doesn’t require a course. So you can take the self-study route and then take a cheaper test ($200). This level of affordability can make the scrum.org certifications a more attractive first step for people exploring scrum certifications.

Here is my experience with certifications as a path to growth.

Also be sure to check out the essential Scrum glossary.

The best way to learn to be a scrum master is through practice. However, earning a certificate can provide helpful instruction, and some companies list it as a requirement for scrum master roles. 

If you're entering the world of scrum or trying to transfer your skills from one domain to another, having a certification like the CSM can help you get in the door.

Here is my experience with certifications as a path to growth.

Want to learn the essential Scrum terms.

Unlike the PMP (Project Management Professional), most scrum certifications don’t require experience. There are pros and cons, though. It makes earning the certifications easier but also makes them a little less valuable. 

A typical CSM course will last between 3 and 5 days, depending on how much instruction is done each day. The PSM doesn’t require a course, so if you already have a solid understanding of scrum, you can just take the test today. 

To really be a Scrum Master your'e going to need practice.

Here is my experience with certifications as a path to growth.

Also be sure to check out the essential Scrum glossary.

Scrum certifications are a great way to both grow and demonstrate your knowledge. The most common certifications for a product owner are:

• CSPO Certified Scrum Product Owner from Scrum Alliance. 
• PSPO Professional Scrum Product Owner from Scrum.org.

The CSPO is more common than the PSPO but also more expensive. Both offer multiple levels of certification.

You are required to take a class by a certified instructor for the CSPO, which will cost you around $1,000. There is no test for the CSPO. Completing the class earns you the certification.

The PSPO recommends but doesn’t require a course. So you can take the self-study route and then take a cheaper test ($200). This level of affordability can make the scrum.org certifications a more attractive first step for people exploring scrum certifications.

Here is my experience with certifications as a path to growth.

Also be sure to check out the essential Scrum glossary.

Like becoming a scrum master, the best way to grow as a product owner is through practice. The CSPO class is helpful as it provides several practical facilitation techniques. 

I’ve seen it listed as a requirement for various product owner or product manager roles. It can be beneficial if all other things are equal, but I don’t think it’s a game-changer for landing a PO job.

Here is my experience with certifications as a path to growth.

Want to learn the essential Scrum terms.

There are actually two backlogs, the product backlog and the sprint backlog. They each contain the definitive list of work to be done. The product owner keeps the backlog ordered by priority. 

Learn to use the backlog in Scrum and check out the sprint backlog vs product backlog in Scrum.

The product backlog prioritizes the features needed in the product. It is a singular visible source of requirements for the product.

The sprint backlog represents the work to do in a given sprint. It is a definitive list of all the scrum team is being asked to produce for the sprint. 

Learn more about the sprint backlog vs product backlog in Scrum.

Each item in the backlog represents precise work and value to deliver. Often these PBIs are written using both user stories and acceptance criteria. The PBIs are what gets refined during the backlog refinement session, and if one is too large, it may be broken down into smaller PBIs.

Learn more about how backlogs are used in scrum, the sprint backlog vs product backlog in Scrum and explore the essential Scrum glossary.

The Scrum sprint backlog is a prioritized list of items from the product backlog that the development team plans to complete during the upcoming sprint.

It is a plan for the Sprint and is created during the Sprint Planning meeting where the Development Team decides on how to build the functionality that meets the Sprint Goal. The Sprint Backlog typically includes user stories, bugs, technical work, and other items that the development team needs to work on during the sprint. Each item in the Sprint Backlog has a clear definition of done, so the team knows when the item is considered complete.

The Development Team is responsible for creating and updating their Sprint Backlog throughout the Sprint, making sure they are on track to meet the Sprint Goal. The Sprint Backlog is a working document that helps the Development Team visualize their progress and make any necessary adjustments to their plan as they go along. The Sprint Backlog is also transparent, allowing stakeholders to see what work is being done during the Sprint.

Learn more about the backlogs of Scrum.

In Scrum, the product backlog is a prioritized list of features, bugs, technical work, and other product-related items that need to be addressed by the development team.

It serves as a single source of truth for what needs to be done on the product.

The items in the product backlog are ordered based on their importance to the product owner and the value they bring to the end-user. As the project progresses, the product backlog is constantly updated to reflect new priorities, changes in requirements, and feedback from stakeholders.

The product backlog is a living document that evolves throughout the project's lifecycle. It provides transparency and enables collaboration among all members of the Scrum team.

Learn more about the backlogs in Scrum.