I would like to prepare guide for anyone aiming to pass Scrum PSD Certification. Provided links are just an example. I don’t find them best source existing or only one true. Those links are just something I’ve gone through and I found them valuable.
Get familiar with Agile Principles including both 4 core values and 12 principles. Later read and understand Scrum Guide. For better understandment 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 developer in comparision to coder. They are covered widely in altexsoft artice. During reading pay attention to following things:
- Pair programming
- Continous Integration
Habits of good developer
- Code review is an important practice if we are having common code ovnership. 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. 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 very good source of knowledge. Speakign 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 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 blogpost.
- Definition of done (also get familiar with similiar ideas as “Acceptance criteria” or “Definition of ready”).
Agile development is build upon cooperation so I found usefull to do following things:
- Get confident when it comes to question “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