Search

What Are The Main Differences Between CSM & PSM Certification?

Scrum is an Agile framework that helps teams collaborate to achieve success in a development environment where the requirements are rapidly evolving.Teams following Scrum methods are encouraged to work in a transparent manner, self-organize while working on a problem, and continually improve themselves through self-reflection.LeadingIT-based organizations and companies are looking to hire candidates who are familiar with the Agile and Scrum framework, principles and processes. A recent article published by Forbes Magazine says that IT professionals with certifications are earning an average of $17,000 more per year than the median IT certification salary. From an employee perspective, certifications let you demonstrate additional qualifications on your resume in addition to getting hired faster. The demand for certified Scrum professionals is on the rise, and the Certified ScrumMaster® (CSM®) and Professional Scrum Master (PSMTM) are the two industry-recognized certifications that can add value to your Scrum career. Let’s understand what the differences between the two are, so that you can make an informed choice between the two. Accrediting Bodies  The Certified ScrumMaster® (CSM®) is a credential from Scrum Alliance®; a non-profit organization that provides guidance on agile practices, principles, and values. The Professional Scrum Master (PSMTM) is offered by Scrum.org, an organization that was founded by Ken Schwaber, the co-creator of Scrum; and seeks to improve professionalism in Scrum training across the world.  Duration of Training  Both CSM and PSM training courses have a duration of 2 days (14 to 16 hours) each. The CSM course is led by a Certified Scrum Trainer® (CST®), while the PSM course is led by a Professional Scrum TrainerTM (PST).  Levels of Training  The CSM credential has one level only, while the PSM is offered at two levels; PSM I and PSM II.   Learning Outcomes  As a CSM, you will be well equipped to help the Scrum team perform at their maximum capability, overcoming obstacles and guiding them on the Scrum framework. A CSM is considered a ‘servant leader’, who leads through example and essentially facilitates the team members to achieve project success.  People who have successfully achieved the PSM I demonstrate a foundational level of Scrum mastery and are well versed in the terminology and approach to Scrum. Passing the PSM II acknowledges a deeper understanding of Scrum principles and the ability to apply Scrum in complex situations.  Certification Process CSM®  You will be required to attend a live online or in-person course taught by a Certified Scrum Trainer® (CST®), or get coached by a Certified Agile Coach (CAC). The duration will be 14 to 16 hours of training.  On course completion, you will need to take the 50 question CSM test. To achieve the passing score, you must answer 37 out of the 50 questions correctly within the 1 hour time limit.  On passing the CSM test, you will be asked to accept the CSM License Agreement and complete your Scrum Alliance membership profile. You will get the membership for a duration of 2 years.  PSMTM  Taking a course is not mandatory, and if you feel you already have the required level of Scrum knowledge, you can apply to write the PSM I Exam. However, undertaking the course will get you well prepared to pass the exam at your first attempt.  Study well, and check the resources available on to help you in your preparation.  The PSM I Assessment contains 80 questions to be answered in a time limit of 1 hour. If you pass the assessment, you will receive the PSM I certification and a logo.  What is the passing grade? To pass the CSM exam, you must secure at least 37 out of 50 possible marks. This is considered to be easier to achieve than a passing grade in the PSM exam.  In PSM I, the passing criteria are quite tough, as you will have to complete 80 questions and achieve at least 85% (this is not accurately defined by Scrum.org) to get the Professional Scrum Master certificate.  Exam Format   While CSM contains multiple choice questions, the PSM certifications are a mix of multiple-choice questions, multiple-answer questions, and some true/false questions. The PSM I will test you on the facts of Scrum as well as some scenario-based questions.   Difficulty level of the exam: It is generally understood that the Certified ScrumMaster test is relatively easier than the PSM 1 and PSM 2. To appear for the CSM, attending a 2 day training is mandatory and you will get adequately prepared to sit the exam and achieve a passing score. However, PSM does not have a mandatory requirement of attending training classes, and many students who have not attended a training workshop therefore find that their preparation is inadequate. How much does it cost?     There is no standard fee for the CSM exam, as typically the exam attempt is clubbed with the course.  However, the fee range for the course is typically from 1000 to 1400 USD.  The PSM costs $150 USD per exam attempt.If you join a training course, then your first exam attempt is free.  What is the Renewal Duration? You have to renew your CSM credential every two years, by collecting 20 SEUs and paying the renewal fee of $100.  On the other hand, there is no need to renew your PSM credentials. Once you get the PSM credential, it has a lifetime validity.  How consistent is the training content?  The CSM program content varies from trainer to trainer, as Scrum Alliance only provides broad guidelines for the Curriculum and trainers are free to interpret it in their own ways. PSM comes with a standard agenda which must be followed across all training institutes.  Conclusion: Knowledge of Scrum is one of the most sought-after skills in recent times, and both the CSM and PSM are highly respected credentials in the Scrum world.  While the CSM is preferred by manyas it is considered an easier exam to pass, it requires renewal of the credential every two years. The PSM, though it comes with a slightly more difficult assessment, is valid for a lifetime.  We hope we’ve helped you to make an informed choice! If you still can’t make up your mind, do connect with any of our counsellors and get the answers you are seeking. Either way, you can’t go wrong. Good luck on your Agile journey!

What Are The Main Differences Between CSM & PSM Certification?

16K
  • by Richard Paul
  • 18th Apr, 2017
  • Last updated on 27th Apr, 2021
  • 7 mins read
What Are The Main Differences Between CSM & PSM Certification?

Scrum is an Agile framework that helps teams collaborate to achieve success in a development environment where the requirements are rapidly evolving.Teams following Scrum methods are encouraged to work in a transparent manner, self-organize while working on a problem, and continually improve themselves through self-reflection.LeadingIT-based organizations and companies are looking to hire candidates who are familiar with the Agile and Scrum framework, principles and processes.

Scrum Framework

A recent article published by Forbes Magazine says that IT professionals with certifications are earning an average of $17,000 more per year than the median IT certification salary. From an employee perspective, certifications let you demonstrate additional qualifications on your resume in addition to getting hired faster.

The demand for certified Scrum professionals is on the rise, and the Certified ScrumMaster® (CSM®) and Professional Scrum Master (PSMTM) are the two industry-recognized certifications that can add value to your Scrum career. Let’s understand what the differences between the two are, so that you can make an informed choice between the two.

CSM VS PSM

Accrediting Bodies 

The Certified ScrumMaster® (CSM®) is a credential from Scrum Alliance®; a non-profit organization that provides guidance on agile practices, principles, and values. The Professional Scrum Master (PSMTM) is offered by Scrum.org, an organization that was founded by Ken Schwaber, the co-creator of Scrum; and seeks to improve professionalism in Scrum training across the world. 

Duration of Training 

Both CSM and PSM training courses have a duration of 2 days (14 to 16 hours) each. The CSM course is led by a Certified Scrum Trainer® (CST®), while the PSM course is led by a Professional Scrum TrainerTM (PST). 

Levels of Training 

The CSM credential has one level only, while the PSM is offered at two levels; PSM I and PSM II.  

Learning Outcomes 

As a CSM, you will be well equipped to help the Scrum team perform at their maximum capability, overcoming obstacles and guiding them on the Scrum framework. A CSM is considered a ‘servant leader’, who leads through example and essentially facilitates the team members to achieve project success. 

People who have successfully achieved the PSM I demonstrate a foundational level of Scrum mastery and are well versed in the terminology and approach to Scrum. Passing the PSM II acknowledges a deeper understanding of Scrum principles and the ability to apply Scrum in complex situations. 

Certification Process


How to get certified

CSM® 

  • You will be required to attend a live online or in-person course taught by a Certified Scrum Trainer® (CST®), or get coached by a Certified Agile Coach (CAC). The duration will be 14 to 16 hours of training. 
  • On course completion, you will need to take the 50 question CSM test. To achieve the passing score, you must answer 37 out of the 50 questions correctly within the 1 hour time limit. 
  • On passing the CSM test, you will be asked to accept the CSM License Agreement and complete your Scrum Alliance membership profile. You will get the membership for a duration of 2 years. 

PSMTM 

  • Taking a course is not mandatory, and if you feel you already have the required level of Scrum knowledge, you can apply to write the PSM I Exam. However, undertaking the course will get you well prepared to pass the exam at your first attempt. 
  • Study well, and check the resources available on to help you in your preparation. 
  • The PSM I Assessment contains 80 questions to be answered in a time limit of 1 hour. If you pass the assessment, you will receive the PSM I certification and a logo. 

What is the passing grade?


What is CSM & PSM Passing grade

To pass the CSM exam, you must secure at least 37 out of 50 possible marks. This is considered to be easier to achieve than a passing grade in the PSM exam. 

In PSM I, the passing criteria are quite tough, as you will have to complete 80 questions and achieve at least 85% (this is not accurately defined by Scrum.org) to get the Professional Scrum Master certificate. 

Exam Format

CSM & PSM exam format 
While CSM contains multiple choice questions, the PSM certifications are a mix of multiple-choice questions, multiple-answer questions, and some true/false questions. The PSM I will test you on the facts of Scrum as well as some scenario-based questions. 

 Difficulty level of the exam:

How Difficlut is the exam

It is generally understood that the Certified ScrumMaster test is relatively easier than the PSM 1 and PSM 2. To appear for the CSM, attending a 2 day training is mandatory and you will get adequately prepared to sit the exam and achieve a passing score. However, PSM does not have a mandatory requirement of attending training classes, and many students who have not attended a training workshop therefore find that their preparation is inadequate.

How much does it cost?
 

CSM & PSM Exam Certification Cost

 

There is no standard fee for the CSM exam, as typically the exam attempt is clubbed with the course.  However, the fee range for the course is typically from 1000 to 1400 USD. 

The PSM costs $150 USD per exam attempt.If you join a training course, then your first exam attempt is free. 

What is the Renewal Duration?

  • You have to renew your CSM credential every two years, by collecting 20 SEUs and paying the renewal fee of $100. 
  • On the other hand, there is no need to renew your PSM credentials. Once you get the PSM credential, it has a lifetime validity. 

How consistent is the training content? 

The CSM program content varies from trainer to trainer, as Scrum Alliance only provides broad guidelines for the Curriculum and trainers are free to interpret it in their own ways. PSM comes with a standard agenda which must be followed across all training institutes. 

Conclusion:

Knowledge of Scrum is one of the most sought-after skills in recent times, and both the CSM and PSM are highly respected credentials in the Scrum world. 

While the CSM is preferred by manyas it is considered an easier exam to pass, it requires renewal of the credential every two years. The PSM, though it comes with a slightly more difficult assessment, is valid for a lifetime. 

We hope we’ve helped you to make an informed choice! If you still can’t make up your mind, do connect with any of our counsellors and get the answers you are seeking. Either way, you can’t go wrong. Good luck on your Agile journey!

Richard

Richard Paul

Blog Author

Richard Paul is seasoned professional of the project management domain. He during his tenure has to his credit many successful projects. In his leisure time, he writes and educates his audience on the latest in project management. He can be contacted for coursework assistance by following him on social media channels.

Join the Discussion

Your email address will not be published. Required fields are marked *

4 comments

Subramanian Kaushik 16 Feb 2018 1 likes

Nice post !! Thanks for sharing the differences....

kritesh anand 05 Mar 2018

Thanks for sharing scrum professional work which will helps you to make csm certification easily.

Nivedita Telang 08 Jun 2018

Hi, It was a very good article for CSM / PSM. I got good information related to PSM certification. Although I have one question here that where can I get PSM material or how can I avail this course.

KnowledgeHut Editor 24 Dec 2018

Hi Nivedita, Thanks for your feedback on the article. You can checkout our course here: https://www.knowledgehut.com/agile-management/psm-certification-training. And for PSM materials and other queries please get in touch with us.

VK 25 Aug 2018

Thanks for the blog, keep this updated.

Suggested Blogs

Combination Of Agile & DevOps – The Roots

Agile and DevOps are two notions that originate from the same schools of thought, but whose paths now have digressed. However, a major amount of confusion still remains within the IT services industry with regards to the relationship between the two and has emerging agile & devops trends in 2017. Hence, it is of value to look at the origins of each and to clarify the disparities between them. ‘Tell me what you want, what you really really want!!’ Does the tune ring a bell? Back in the 1990s, the Spice Girls were expressing to the world what they really really wanted, and similarly business owners and corporate leaders were doing pretty much the same, indicating what they wanted to software developers who were working on enabling these organizations through technology. Unfortunately, these business owners were not as lucky as the Spice Girls. More often than not they really didn’t get what they wanted. By the time business requirements were properly understood, validated and finally realized through software products the business requirements more or less had changed.  This was mainly due to the ‘application delivery lag time period’ that sometimes went up to three years. The result of the aforementioned delay from concept to realization meant that a large proportion of projects were stopped before completion. Even then, those that eventually reached the finish line more often than not did not meet the end users’ expectations.  The introduction of Agile – The change-driven management approach The search was on for a more lightweight approach to solution delivery and the result was ‘agile’ – a project management approach with a series of new concepts with regards to collaboration between business owners and the implementation team including UI / UX engineers, developers and even QA engineers. Instead of eliciting, documenting and signing off all the requirements up front and getting it signed off before work began, the focus shifted to delivering value through increments of functional software that would evolve over time. The results indicated that the software implementation team had become more productive, businesses could be more responsive in responding to queries of the implementation team, and user demands could be met more efficiently. However, problems remained. The agile approach didn’t always deliver on the promise of continuous, seamless software development. Blockers continued to exist. So, what is DevOps? The first thing to note is the fact that DevOps is not an individual tool or a suite of solutions but more of a philosophy whose primary purpose is to reduce the distance between the worlds of software development and IT operations. It defines how the original concepts of agile have moved downstream to the level of infrastructure and operations. The DevOps concept sounds relatively straightforward, but in reality it is a little bit more complicated. Software development and IT operations have historically had very different approaches. Software developers appreciate the ability to change things quickly and often they do end up changing things rapidly. In the meantime IT operators focus on stability and on minimizing alteration. This philosophical disparity has often resulted in conflicts. Thus, one of the main challenges of DevOps is to ensure that this conflict decreases before it affects the businesses. Importance of DevOps Principles For this very reason indicated above, it is very important to consider and act up on the core principles of DevOps. They are, Close collaboration and communication between developers, system operators and software testers Continuous integration that requires developers and operators to commit to changes more frequently Continuous delivery to increase the team’s speed and efficiency while enabling early detection of bugs Continuous deployment to ensure new developments can be released without system downtime The DevOps philosophy goes hand-in-hand with the delivery processes described in ITIL Framework in terms of support and IT services management. DevOps can therefore be seen as a way to implement ITIL processes in such a manner that meets the demands placed on systems today.  
3323
Combination Of Agile & DevOps – The Roots

Agile and DevOps are two notions that originate fr... Read More

Metrics that matters for DevOps Success

DevOps is generally introduced for the development teams to speed up the software delivery. DevOps is considered as a step beyond Agile. Many enterprises accepted DevOps as a part of software delivery process from planning, developing, deploying and updating an application, according to reviews. In this competitive world, DevOps allows businesses to speed up with the rapid pace of demands by the customers.Here are the top Ways to Obtaining Business Benefits of DevOps. Customers of today demand quality as well as security based products. DevOps, making the best use of its principles, provides superior quality and lowers the risk. On the contrary, in traditional software development approach, increased speed often results in poor quality and increased vulnerabilities. Why are metrics essential? Most organizations implement DevOps because of the demand for quality, time improvement and the need for defect-free products. Since DevOps has no specified framework, there exist a few standard ways to measure DevOps success. How do you find out how well it can work? How will you come to know whether it is working or not? The answer to this question, and the solution to all the existing problems, is the use of Metrics. Metrics are essential to stay in sync with DevOps. DevOps will be used extensively which therefore requires continuous treatment. But if you are not measuring its outcomes, you cannot understand how to incorporate DevOps in your organization. The focus of DevOps metrics is on deployment, operations, and support (feedback). Let us have a look at the Devops metrics which will lead to improved delivery performances. People: People are the major elements of the DevOps process. People-oriented metrics measure the things like yielding, capacity and response time. People are the hardest element of DevOps. So always start with the phase ‘People’. Process: In some ways, DevOps is considered as a process of  continuous deployment. There are many process-oriented metrics. Development to deployment is a large process-oriented metrics. Process metrics can be the measurement of speed, appropriateness and effectiveness. Technology: Technology metrics also plays a major role in DevOps. It measures the things like uptime (time during which the computer performs operations), network and support, and failure rate. Deployment (or Change) Frequency: DevOps metrics includes continuous deployment. Updated software deployment in every few days can be possible with fast feedback and piecemeal development. In a DevOps environment, deployment frequency can be measured in terms of the response time, the teamwork, the developer capacities, development tools and the overall efficiency. Change Lead Time: Change lead time is the time period between the initialization phase to the deployment phase. In DevOps, it is a measure of development process efficiency, code and the development systems’ complexity, and also of team capabilities. A protracted ‘change lead time’ is an indicator of an inefficient deployment system. Change Failure Rate: One of the main goals of DevOps is to do frequent deployment with less failure rates. Failure rates metrics should be decreased over time, as the experience and the capabilities of the team and developers get increased. If the frequency of failure is very high, it is definitely a red flag, as it gives rise to problems in the overall DevOps process. Mean Time to Recover: Time taken between ‘recovering the failure’ from the ‘failure’ is known as Mean Time to Recover (MTTR). It can be fragmented into three phases- detection, diagnosis and recovery phases. MTTR metrics is the sign of a good teamwork which identifies how effectively the teams handle the changes, and also, how collaboratively they do so. By all means, this metric is becoming a trend for DevOps to remodel organizational processes in a better way.
Metrics that matters for DevOps Success

DevOps is generally introduced for the development... Read More

Agile and DevOps Or Agile vs DevOps: Differences

Agile is the standard in today’s application development world. Development teams are adopting it over the last 10 years, as it has been proved to be more efficient methodology of getting quality software. Agile has improved user experience by frequently rewarding with focussed goals and quick delivery. In addition to this, the broad use of DevOps in Agile methodology has made it a more compelling approach for IT commercials. In this context, it is important to know that Agile is not DevOps, and DevOps is not Agile. It is difficult to achieve success in DevOps, if Agile practices are not followed. While Agile can make sense independent of DevOps, it can be more complete when accompanied by DevOps practices.Here are the emerging Agile and DevOps Trends. Many people have set their minds about Agile, that Agile means Scrum and DevOps means continuous delivery. This simplification creates unnecessary confusion between Agile and DevOps, making people think that they are perfectly compatible. So, let us have a look at the practical connections between Agile and DevOps. Planning for Unplanned work: In the DevOps circle, those using Agile acknowledges that Scrum is used to track the planned work. Tasks like releasing updated system, performing system upgrades etc, can be planned. On the other hand, the operations like performance spikes, system expiry, and standard security, can be unplanned. These types of tasks need immediate response. You cannot wait for the next sprint planning session. For this reason, many organizations embrace DevOps (more than Scrum and Kanban), which helps to track both kinds of work. Before, there were priorities from multiple masters, but now a single set of priorities are in use. Similarly, for a long list of assigned work, the time period is planned to accomplish the work. These lightweight management practices by Scrum make a huge difference for a team. Speed vs Risk: Teams using Agile with or without DevOps have to remember that, to support the rapid change, a sound application structure and a solid foundation are mandatory. Applications must have good underlying framework that must be used constantly by the team members. In the DevOps context, the teams must make sure that the changes which are made to the architecture should not introduce any risk. Also, there should not be any hidden side-effects associated with the changes, because the iterative process consists of regular changes in the architecture. So you should be concerned about the risks associated with each and every change made. Only with this type of work will you get rapid delivery without any risk. Agile and Quality: Both Agile and DevOps help develop an application fast, keeping sound structure and risk-free application.  But neither of them concentrates on the quality of the product. Mostly, IT organizations rely on the ‘fail fast’ principle- “ Early failures cost less to fix”. But with this, only fast deployments can be maintained, not quality. Agile produces applications that fit better with the desired requirements and can adapt quickly to respond to the requirement changes made on time, during the project life. DevOps, along with the automation and early bug removal, contributes to creating better quality. Developers must follow Coding and Architectural best practices to  embed quality in the applications. Agile and DevOps should try reach the next level to become highly effective within the organizations. They must conform to the industry standards using Agile and DevOps practices, to allow the development team to improve quality, make delivery faster and avoid software risks.
1442
Agile and DevOps Or Agile vs DevOps: Differences

Agile is the standard in today’s application dev... Read More

Useful links