The PMI has now published the Agile Certification Examination Content Outline, you can download it here. It outlines the “Tools and Techniques” and “Knowledge and Skills” areas that the exam will be broken into. As we have it now, 50% of the examination marks will be awarded for Tools and Techniques and 50% for Knowledge and Skills.
As part of the Steering Committee it was interesting to take part the discussions around these weightings. As recent as a month ago the split being suggested for the exam weighting was 70% of the exam would be based on Tools and Techniques with just 30% on Knowledge and Skills. We had steering committee members suggest a 60, 40% split the other way, but in the end the 50%, 50% split was selected.
Doubtless people are reading through these categories trying to get a handle on the scope of the exam. My recommendation would be to focus less on these divisions (that overlap anyway) and focus on the domains that underpin them.
As an example we see Knowledge and Skills Level 1 mentions “Building Empowered Teams”, Level 2 has “Building High Performance Teams”, and the Tools and Techniques section has items for “Communications” including “daily stand-ups” and “collaboration”. These are obviously all closely related, but listed in separate areas which could be confusing, but if you adjust your view to focus on the domains, there is a better separation into logical areas.
I am hoping that there will be a reissue of the Examination Content Outline, since the current form needs word-smithing. The text we generated for it was our short hand notes. For instance Domain 1 Task 1 reads:
“Define features and project work in terms of end-user and stakeholder value by focusing on maximizing value delivered and minimizing non-value-added activities in order to keep the delivery team focused on maximizing the value developed.” Is quite the mouthful that made sense to us, but could perhaps be restated along the lines of:
“Define project features and work items in terms of end-user and stakeholder value, by always looking for and clarifying the business value. Focusing on maximizing value delivered by the project and try to eliminate any non-value-added activities. This keeps the delivery team focused on maximizing the business value and reduces the likelihood of wasteful activities, feature bloat and gold-plating.” While this is longer, hopefully it is in easier to absorb chunks.
Anyway, as the categories evolve and the questions get developed I will keep readers updated here.