This is a short guide for anyone aiming to pass Scrum PSD Certification. Provided links are just an example. Based on that I managed to pass the exam. I spent around a week on learning. If you have any questions or seek any tips – please leave a comment.
Basics of Scrum PSD Guide
Get familiar with Agile Principles including both 4 core values and 12 principles. Later read and understand Scrum Guide. Make sure to go through PSD Glossary. For better understanding, I propose reading Chapter 1 from “Professional Scrum Development with Microsoft Visual Studio 2012” by Richard Hundhausen.
Also worth noticing will be Nexus Guide, which will give us quick insight on how to scale Scrum.
Good practices are what define the developer in comparison to a coder. They are covered widely in AltexSoft article. During reading pay attention to the following things:
- Pair programming
- Continuous Integration
Habits of a good developer
Learning things which good developer with a Scrum PSD certification should do daily is another part of this guide.
- Code review is an important practice if we are having common code ownership. Read more about Better code review and also on Why code review matters?
- Get familiar with test types: Unit, Integration, Performance, Smoke, Exploratory, Functional, etc. The good resource to start with is this list of Types of Software tests.
- Dependency Injection – one of the major advantages of it is that it can make testing lots easier. And since testing is something we put great emphasis on, you should be familiar with it. It is well described in Stack Overflow discussion and shortly on GT’s Blog.
- Code smells are generally something you should be aware of. I found Source Making site at a very good source of knowledge. Speaking of code smells consider reading about metrics. Start with Cyclomatic Complexity – just read about it on Guru 99
There are many tools that should be familiar to the good developer, even if they are not strictly connected with developing:
- Planning Poker
- Creating good stories – it is briefly described in Creating good user stories blog post.
- Definition of done (also get familiar with similar ideas as “Acceptance criteria” or “Definition of ready”).
Cooperation in terms of Scrum PSD
Agile development is built upon cooperation. This is crucial for anyone who aims to pass Scrum PSD. so I found useful to do the following things:
- Get confident when it comes to questioning “why teams should be self-organized”?
- Go through workshops that show why Pull is better than Push. (Planes factory workshops)
- Get familiar with Tuckman’s stages of team formation: Forming – Storming – Norming – Performing