- Type: PDF file (Downloadable)
- Page: 33 pages
- Access: One year
- Language: English
- Difficulty: Intermediate
- Version: 4.0
- Last Update: 04/2020
A tips and tricks training manual for passing the Scrum.org PSM I (Professional Scrum Master) exam.
Scrum.org offers the Professional Scrum Master (PSM I) certification. All candidates should pass PSM I exam to get certified. It is highly recommended that all Scrum Team players certify themselves.
But we found that there is a gap between preparation resources for Scrum.org exams in the market and tricky level of the exams’ questions. Most resources that Scrum.org suggested for preparation are books. These books just establish fundamental knowledge and insight, but usually, do not prepare candidates for the tricky questions. So most people do not prepare as enough for the exam as possible and find the exams risky.
On the other hand, related courses are expensive for many people and according to Scrum.org rules these courses are not mandatory and candidates can prepare themselves through self-study. Therefore, we decided to produce a product to prepare candidates through tips and tricks training manual to take the real exams with more confidence. Our competitive advantage is broad and extensive content as a reliable learning source with an implicit tricky approach in it. We worked hard to prepare this quality content and we believe it can fill the mentioned gap.
So, we invite you to take the PSM I exam with confidence through our high-quality tips and tricks training manual.
Sample content of manual
What happens for the project manager role in Scrum?
According to the Scrum rules, there are just three roles in a Scrum team as the Scrum Master, the Product Owner, and the Development Team, and nothing else. The project manager’s duties are distributed among three pre-defined roles.
What is the difference between the Definition of Done and Acceptance Criteria?
Definition of Done is a concept with a set of requirements that should be applied to a feature in order to be called as complete. On the other hand, Acceptance Criteria or Conditions of Satisfaction contains a list of scenarios that should be passed to ensure that the feature is working as expected. The difference is that there is one Definition of Done for the product and is common for all features while there is a separate and specific Acceptance Criteria for each feature. Passing Acceptance Criteria would be an item of the Definition of Done.
Why does the Scrum Team always need a Scrum Master?
The Scrum Master has two main responsibilities. First taking care of implementing the Scrum framework properly and help the Team to be mature about using Scrum. Second removing impediments. Although it may seem that when a Team becomes mature, they will not need a Scrum Master, according to the second responsibility that every time impediments could occur even when the Team becomes mature, the Team always need a Scrum Master.
Which position or role in Scrum is responsible for the Product quality?
All members of the Development Team are developers and there is no title such as programmer, tester, etc. These are skills that each member might have some of them and accountability of the product quality belongs to the whole team, not a special member.
How does adding a new member affect the Team?
Adding new resources to the team will lead to a temporary reduction in productivity because new member needs time to be familiar with team’s environment, culture and the product and old members need to collaborate on new member’s on-boarding. Furthermore, a bigger Team does not mean that it can create more value. It is better to change Team composition at the beginning of the Sprints.
Which types of Sprints are there in the Scrum?
Absolutely there is just regular Sprint in Scrum within which the Development Team tries to create releasable Increment. Therefore, there are no such things as Sprint Zero, Hardening Sprint, Stabilization Sprint, Integration Sprint, Release Sprint, etc.
How do new emerged tasks during the Sprint change the Sprint Backlog?
In Scrum, task and work are two keywords with the same meaning that break down the PBIs. Tasks are the activities that the Development Team should do in order to create usable and releasable Increments. As explained, Scrum is founded on an adaptive approach and the Development Team should inspect and adapt its work continuously. Therefore, each time they find a new task or work for each PBI in the Sprint Backlog they can add that task to the Sprint Backlog.
The Development Team owns the Sprint Backlog so the Scrum Master and the Product Owner should not change it.
For more information you can read this blog post: