Tips to pass PSM II
Recently I had the opportunity to appear for PSM II and I cleared it with 100% score. I thought of sharing of sharing some tips to the aspirants of PSM II examination.
There are so many good blogs on how to prepare for PSM II. I am not trying to replace those or repeat whatever is already mentioned. You will get quite a lot of suggestions when you google.
Before we start, here is the basic information on the exam:
- Fee: $250
- Passing Score: 85 %
- Time limit: 90 minutes
- Number of questions: 30
- Difficulty: Advanced
- Format: Multiple Choice, Multiple Answer and True/False
- Mandatory course: None. Scrum.org’s PSM II class does provide a lot of learning and perspectives but it is not mandatory.
- Organization: Scrum.org
- Expiration date: none
What I am trying to do here is to provide some direct and blunt tips to answer maximum questions in the exam.
- Time : If you have appeared for PSM I, you would know how crucial time is. But, don’t worry. You will get plenty of time for PSM II. You will probably answer everything in an hour.
- Books : It is good if you are fond of reading books. But, personally, I don’t think it is a good idea to target completing certain books before you could appear for this exam in the next 2 or 3 weeks. All the questions are scenario-based. It might help if you have been reading a lot in the past. But, not keeping the exam in mind.
- Blogs : Read some blogs instead. Gunther’s blog on scrum values helps in the exam. Other blogs mentioned in the suggested reading for PSM in Scrum.org helps.
- Velocity : Stay away from velocity: Remember, velocity is only for the developers to forecast how much they think they could include in the sprint backlog.
- Self-organizing : The questions which I found hard were related to self-organizing. Read again what Scrum Guide tells about self-organizing. Remember keywords like creativity, how to to do etc.
- Product Owner: Only 1 Product Owner per Product. In certain cases, 1 PO can manage multiple Products while delegating some work.
- Nexus : When multiple teams are working, reducing Dependency is the key.
- Never choose answers that indicate Scrum Master solving anything, suggesting a solution. Leave it to the team.
- New Terms : Stay away from terms that are not mentioned in Scrum Guide. For example, ‘Definition of Ready’. In some questions, those would seem very convincing. But, don’t fall into the trap. Avoid such answers and suggestions.
- Sprinting never stops, no matter what. Unless the PO decides to stop the project or the Sprint Goal becomes obsolete. In some cases, the sprint duration might be shortened to receive faster feedback.
- Commitment: Gunther has explained this Scrum Value nicely in his blog. Scrum Teams commit to quality. Commit to learning. Commit to doing the best they can, every day again, from the commitment to work at a sustainable pace. They are committed to the Sprint Goal. They commit to act as professionals. Commit to self-organize. Commit to excellence. Commit to the Agile values and principles. Commit to creating working versions of the product that comply with the definition of Done. Commit to looking for improvements. Commit to the Scrum framework. Commit to delivering value. Commit to finishing work. Commit to inspect and adapt. Commit to transparency. Commit to challenge the status-quo. But, if they are unable to complete all the work that was forecasted in the sprint planning, it doesn’t mean they are NOT committed. Careful with the questions which say Scrum Team is committed to the task or stories.
- Last Tip : You are never fully prepared for such exams. So, gather enough courage and just decide a date & time and sit for the exam.