Course Discount

Search

Value Proposition of Agile Development

Value Proposition of Agile Development The benefits of Agile development have been extolled extensively across the web and almost every one of us is well aware of those benefits. Some of the inquisitive members have taken the efforts to research and study the Agile development framework to understand why those benefits are the products of this framework under discussion. I have no intention of going in that direction since it requires a detailed discussion that is possible in a classroom setting [reach out to your KnowledgeHut support to ask for one].   Through this article, I want to discuss the value propositions of Agile development with you i.e. in essence means, how the benefits of Agile play out for you on the ground during the execution time. What are those actual in-hand benefits that you and your team will reap because of the good thing in Agile development called Value proposition? That is what I want to share with you.   Visibility: The first value proposition that we are going to discuss is “Visibility”. The visibility to the product owner, project sponsors, managers, and engineering team about the current state of the project or product development and whether  we are headed in the right direction or not. Unlike waterfall model, where visibility is highest during requirement gathering phase then suddenly everything goes black and behind curtains with no idea about building the right thing, then suddenly we ship the product with the highest visibility. Alas, that is too late to correct anything if things have gone in the wrong direction. The value brought by Agile in this matter is that visibility remains high at all times; it slightly dips for a week or two during actual development, but it again picks up; so on an average, it remains consistent and at a higher level than waterfall model. This can be easily understood through the means of this graph where the dotted line shows how visibility into the project direction suddenly dips during the execution phase, but it remains constant for Agile.   Adaptability: The word adaptability refers to the ability to accept changes or changing business scenarios and move forward in the new direction with the same vigor and enthusiasm. In any project, adaptability is highest since the project is being kicked off, requirements are being collected so any direction, request or change can be easily accommodated. But things start to change in a traditional waterfall model soon enough and adaptability goes down considerably from the design stage and becomes lowest during shipping. Because once those things are finalized then there is no way to change them without starting all over again. Whereas in the Agile mode, though adaptability remains highest during the initial phase, it continues to hover around the same range through the project duration since every sprint is a chance to pick up something new or change direction as per business need. As you will see in the below diagram, adaptability looks  like this:   Business Value: How your project or product is delivered at the end or at regular intervals, and how it will help the business or your project owner is considered as business value. Because business does not get any value from your project until you deliver something that can be used by end consumers. Needless to say, business value is always available to be consumed at the end of project cycle or rather we should at the time of shipping. The shipping can be at regular intervals [as in the case of Agile] or in the end [as in case of traditional development methods]. In this sense, both Agile and Waterfall sound similar to us but in reality, they are not. Because they vary in the way of delivering business value. Since waterfall believes in shipping in the end or when the product is completely ready, so business value shoots up from 0 to highest suddenly towards the end. That part is obvious. Let us see how it evolves for Agile methodology. Here in Agile, we start delivering incremental versions of the product from the first sprint; so Business value starts getting generated from Sprint 1 and continues to go up until the last sprint or the time when product owner asks us to stop. This is clearly reflected in the graph shown below. Risk This is a remarkably interesting aspect of value proposition for any development model. We all want to avoid risks somehow; sometimes we succeed and sometimes we fail miserably, and our worst nightmares come true at those times. It is not my intention or objective here to dive into many ways to cut risks, but instead, analyze the concept of risk and how it varies according to the development model being followed by the team. It is a common sense that risk is highest in the initial phase of the project since we are dealing with the utmost unknown at that time. Any wrong action or decision by us will lead to failure and a complete wastage of resources. As we progress and start building something, the risk continues to go down and becomes 0 when we ship it. Because either we have succeeded by then or we have failed utterly. Agile allows us to cut down risks faster than the traditional methods because the visibility is maintained at a high level throughout, so if something is going wrong then it is addressed immediately, owing to high adaptability. If we pause and analyze for a while, we understand that high visibility, high adaptability and ability to deliver from early in the game allows us to have minimal risk score through the project rather than working hard for 1 year then finding out that you built something that was not required in first place. That is how Agile development helps us manage risks effectively as long as we execute Agile properly. Conclusion So, as we saw here, any development methodology, related to software field or manufacturing or service-based industry can be analyzed over 4 value proposition parameters, namely: Visibility, Adaptability, Business Value and Risk. In the above post, through means of graphical analysis, we compared Agile development methodology Versus Traditional waterfall and found that Agile development is much better to be followed in recent times with a condition that it has to be executed correctly. You can read my other blog post about “10 deadly myths of Agile and Scrum” whereby I have explained how wrong implementation of Agile and Scrum harms us more than benefit us. With this thought in mind, I take your leave and I hope that next time when you explain to your stakeholders about the need to use Agile, you have a better and stronger story to tell. All the best!
Rated 4.5/5 based on 20 customer reviews

Value Proposition of Agile Development

1K
Value Proposition of Agile Development

Value Proposition of Agile Development


The benefits of Agile development have been extolled extensively across the web and almost every one of us is well aware of those benefits.

Some of the inquisitive members have taken the efforts to research and study the Agile development framework to understand why those benefits are the products of this framework under discussion.

I have no intention of going in that direction since it requires a detailed discussion that is possible in a classroom setting [reach out to your KnowledgeHut support to ask for one].


 

Through this article, I want to discuss the value propositions of Agile development with you i.e. in essence means, how the benefits of Agile play out for you on the ground during the execution time.

What are those actual in-hand benefits that you and your team will reap because of the good thing in Agile development called Value proposition? That is what I want to share with you.




 

Visibility:

The first value proposition that we are going to discuss is “Visibility”. The visibility to the product owner, project sponsors, managers, and engineering team about the current state of the project or product development and whether  we are headed in the right direction or not.

Unlike waterfall model, where visibility is highest during requirement gathering phase then suddenly everything goes black and behind curtains with no idea about building the right thing, then suddenly we ship the product with the highest visibility.

Alas, that is too late to correct anything if things have gone in the wrong direction.

The value brought by Agile in this matter is that visibility remains high at all times; it slightly dips for a week or two during actual development, but it again picks up; so on an average, it remains consistent and at a higher level than waterfall model.

This can be easily understood through the means of this graph where the dotted line shows how visibility into the project direction suddenly dips during the execution phase, but it remains constant for Agile.


 

Adaptability:

The word adaptability refers to the ability to accept changes or changing business scenarios and move forward in the new direction with the same vigor and enthusiasm. In any project, adaptability is highest since the project is being kicked off, requirements are being collected so any direction, request or change can be easily accommodated.

But things start to change in a traditional waterfall model soon enough and adaptability goes down considerably from the design stage and becomes lowest during shipping. Because once those things are finalized then there is no way to change them without starting all over again.

Whereas in the Agile mode, though adaptability remains highest during the initial phase, it continues to hover around the same range through the project duration since every sprint is a chance to pick up something new or change direction as per business need.

As you will see in the below diagram, adaptability looks  like this:


 


Business Value:

How your project or product is delivered at the end or at regular intervals, and how it will help the business or your project owner is considered as business value. Because business does not get any value from your project until you deliver something that can be used by end consumers.

Needless to say, business value is always available to be consumed at the end of project cycle or rather we should at the time of shipping. The shipping can be at regular intervals [as in the case of Agile] or in the end [as in case of traditional development methods].

In this sense, both Agile and Waterfall sound similar to us but in reality, they are not. Because they vary in the way of delivering business value.

Since waterfall believes in shipping in the end or when the product is completely ready, so business value shoots up from 0 to highest suddenly towards the end. That part is obvious. Let us see how it evolves for Agile methodology.

Here in Agile, we start delivering incremental versions of the product from the first sprint; so Business value starts getting generated from Sprint 1 and continues to go up until the last sprint or the time when product owner asks us to stop.

This is clearly reflected in the graph shown below.



Risk

This is a remarkably interesting aspect of value proposition for any development model. We all want to avoid risks somehow; sometimes we succeed and sometimes we fail miserably, and our worst nightmares come true at those times.

It is not my intention or objective here to dive into many ways to cut risks, but instead, analyze the concept of risk and how it varies according to the development model being followed by the team.

It is a common sense that risk is highest in the initial phase of the project since we are dealing with the utmost unknown at that time. Any wrong action or decision by us will lead to failure and a complete wastage of resources.

As we progress and start building something, the risk continues to go down and becomes 0 when we ship it. Because either we have succeeded by then or we have failed utterly.

Agile allows us to cut down risks faster than the traditional methods because the visibility is maintained at a high level throughout, so if something is going wrong then it is addressed immediately, owing to high adaptability.

If we pause and analyze for a while, we understand that high visibility, high adaptability and ability to deliver from early in the game allows us to have minimal risk score through the project rather than working hard for 1 year then finding out that you built something that was not required in first place.

That is how Agile development helps us manage risks effectively as long as we execute Agile properly.



Conclusion

So, as we saw here, any development methodology, related to software field or manufacturing or service-based industry can be analyzed over 4 value proposition parameters, namely: Visibility, Adaptability, Business Value and Risk.

In the above post, through means of graphical analysis, we compared Agile development methodology Versus Traditional waterfall and found that Agile development is much better to be followed in recent times with a condition that it has to be executed correctly.

You can read my other blog post about “10 deadly myths of Agile and Scrum” whereby I have explained how wrong implementation of Agile and Scrum harms us more than benefit us.

With this thought in mind, I take your leave and I hope that next time when you explain to your stakeholders about the need to use Agile, you have a better and stronger story to tell.

All the best!

Abhinav

Abhinav Gupta

Blog Author

PMP, has 12+ years of experience working in Information technology sector and has worked with companies like Infosys and Microsoft in various capacities. He started his career as a manual tester for a world renowned software product and grew on to become automation champion in both functional as well as UI. He has worked with Healthcare units providing various software solutions to companies in North America and has worked with search engine based groups to enhance their experience and provide more bang for buck to their customers.

Join the Discussion

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

Suggested Blogs

Writing Effective User Stories in JIRA

User stories are one of the main methods of communicating requirements to developers/development team in an Agile project. It is important for the individual tasked with documenting the requirements to be able to write effective and detailed enough user stories. The user stories are required to be comprehensive enough to enable the developer/development team to start analyzing, designing and developing the required functionality, feature or requirement stated in the user story.     This article while intending to guide individuals on how to write effective user stories is also intended to advise on the best practices of creating user stories using JIRA as a requirements management tool for creating stories and tasks. What is a User Story?   User stories are short, simple descriptions of a feature in the system under development told from the perspective of the person who desires this new capability. This person is normally a user of the system or even a customer who pays for the solution.  User stories typically follow a simple template as below. As a , I must be able to so that I can .  User stories are often written on index cards or sticky notes and pasted on an information radiator or in other words a scrum board. This article is however on maintaining user stories using JIRA and on how the tool can be used to ensure regular conversation.  Writing user stories on an index card is actually the ‘Card’ part of the 3 C’s in user stories. It is said that a user story should be long enough to fit into an index card and be detailed enough to arouse discussion. Writing user stories in JIRA A new user story in JIRA can be created by selecting the option to create a new issue of type ‘Story’ as shown below.  The user story in the format listed above can be written in the summary field of the new issue creation screen.  User story definition should satisfy the INVEST criteria which implies that the user stories should be: Independent (of all other user stories and be able to exist on its own) Negotiable (not a specific contract for features but be able to be used to facilitate discussion among relevant stakeholders) Valuable (create some business value) Estimable (to a good approximation) Small (so as to fit within an iteration) Testable (in principle, even if there isn’t a test for it yet)   Trace your Customer Requirements to user stories in Agile through the integration with JIRA. https://t.co/esXyAJykZy pic.twitter.com/DZoa1tJrjL — Visure Solutions (@VisureSolutions) 21 November 2017   JIRA also provides the option to set priority of user stories which might have been done based on the MoSCoW criteria, due dates, assign the story to a team member of the project, allocate a story point/hour based effort estimation for the story, tag the user story to a component level feature or in other words ‘Epic’ and be able to assign the story to a sprint during which the story is required to be implemented. Adding description to user stories The 2nd C of the 3 C’s in user stories that is ‘Confirmation’ is used to specify the acceptance criteria of the user story. An acceptance criterion is used to ascertain when a particular user story can be marked as done and is normally used by the product owner to validate the same. The acceptance criteria also help the development team implement the business rules, functionality and will be the single point of reference for the Quality Assurance Team. The description field in JIRA issue creation provides space for the user to specify the acceptance criteria.   Gearset’s Jira Self-hosted (on-prem) and Jira Cloud integration lets you automatically post deployment updates to your tickets & keep up-to-date with the progress of your user stories. https://t.co/qvDlNK5LLr pic.twitter.com/yh8RmUL1Gm — Gearset (@GearsetHQ) 29 January 2018 Enabling discussion Another main aspect of writing requirements as user stories is to enable conversation about the feature among relevant stakeholders. This is known as the ‘Conversation’ component of user stories which is the 3rd C in the 3C’s.  Often user stories are accompanied with a process diagram, UI wireframe or a mockup, data dictionary etc. which can be added as attachments in JIRA or even be associated with the story as comments, wiki page links maintained in confluence. Conclusion Writing user stories is an easy method of maintaining requirements in a dynamic environment of an Agile project. JIRA, as explained above, provides a powerful and rich set of features which helps manage requirements in an efficient and convenient manner.    
Rated 4.5/5 based on 18 customer reviews
4288
Writing Effective User Stories in JIRA

User stories are one of the main methods of commun... Read More

Scrum Master and Product Owner: Understanding the Differences

According to the State of Scrum report 2017-2018 based on the data collection initiated in 2013. This survey represents the real world implementations of Scrum.     Agile methodology imparts the easy and convenient path to work. Scrum is one of the renowned Agile methodologies. The agile methodology consists of 4 main roles, viz. Product Owner, Scrum Master, Scrum team and Stakeholder. Each role has its share of responsibilities. These roles are all about commitment.   Scrum Master and the Product Owner are the two vital roles in the Scrum software development methodology. Since they both are working on different areas of the project, they are indispensable for the project. Scrum Master is a mediator between the Product Owner (PO) and the Development Team.     Let’s see how a Scrum Master is different from a Product Owner. Difference between the Product Owner and Scrum Master-   Though the Product Owner and the Scrum master vary in their roles, they complement each other. Scrum master should support the Product Owner in every step possible. There should be an amicable relationship between the Product Owner and the Scrum master. Disputes may happen between them if the roles are not clarified. Let us have a look at the differences in roles between the Product Owner and the Scrum Master. The Scrum Master concentrates on the project success, by assisting the product owner and the team is using the right process for creating a successful target and establishing the Agile principles.   Skills of the Scrum Master (SM): Removes the impediments and keep the team on track The Scrum Master helps the team to strictly adhere to the Scrum practices and helps them in reaching the target. The Scrum Master find out the distractions that are hindering the team from delivering the product quality. The distractions include unwanted meetings, complexity in the procedure, work environment etc. Encourages Collaboration The Scrum Master notices the daily activities of the team members. Also, the SM share his/her experiences with the team members via meetings, conferences, and seminars. The Scrum Master encourages the collaboration through the stand-up meetings, the release of planning sessions, iteration planning, and demo sessions. Good listening and Communication power The Scrum Master should have good communication skills in order to discuss the ideas and plan with the team. Good communication helps to deliver messages to customers, teams, and target audiences. Also, listening to the team members will help them share their ideas with the Scrum Master. So, Scrum Master should be a good listener also. Mentors the team as a Coach A successful Scrum Master understands the importance of the team working in collaboration. He/She mentors the team members as a Coach to implement the Scrum practices.    Flexibility for adopting the change The Scrum Master should be flexible for adopting any change. While implementing the Agile methodology, the team members may face the problems. So, the Scrum Master should be able to help the team members to adopt the changes. The Scrum Master facilitates the daily Scrum meetings for the team members to discuss their issues that are hindering the project growth.     Partnership with the Product Owner Scrum consists of three roles – Product Owner, Scrum Team and Scrum Master. The Scrum Master acts as a mediator between the development team and the Product Owner. The two roles- Product Owner and Scrum Master are valuable for the team, as they build a perfect relation with the team and thereby delivering the best results. Servant Leadership quality The Scrum Master provides collaboration. Scrum Master is also known as a Servant Leader.  He/She guides the team members on how to follow the Scrum approach to motivate the team members to deliver the best. To know the price bracket of the CSM certification across the globe refer the link: CSM Certification Cost Responsibilities of the Scrum Master:   Scrum Master facilitates team for better vision and always tries to improve the efficiency of the teams. Scrum Master manages Scrum processes coordinating with the Scrum team in the Agile methodology. Scrum Master removes impediments for the Scrum team. Scrum Master arranges daily quick stand-up meetings to ensure quick inspection and proper use of adaptation processes. Scrum Master helps Product Owner to shape the product backlog and make it ready for the next sprint. Conducting retrospective meetings. Scrum Master organizes and facilitates the sprint planning meeting. Most importantly, the Scrum Master removes the impediments that hindering the project success. Scrum Master keeps the team away from the distractions. The Product Owner’s responsibility is to focus on product success, to build a product which works better for the users and the customers and to create a product which meets business requirements. The Product Owner can interact with the users and customers, Stakeholders, the Development team and the Scrum Master.   Skills of the Product Owner (PO): Product Owner should have an idea about the business value of the product and the customers’ demands. Certified Scrum Product Owner Certification (CSPO) will be beneficial for the sales team. The development team consults the Product Owner, so he should always be available for them to implement the features correctly. Product Owner should understand the program from the end-user point of view. Marketing is discussed on the sales level in most of the Organizations. So it is the Product Owner’s duty to guide the marketing persons to achieve the goals successfully. Product Owner is responsible for the product and the ways to flourish a business. Product Owner has to focus on the proper production and ROI as well. Product Owner should be able to solve the problems, completing trade-off analysis and making decisions about business deliverables. After Certified Scrum Product Owner course, Product Owner can work with the project managers and the technical leads to prioritize the scope for product development. Sometimes Product Owner and the Customers are same, sometimes Customers are thousands or millions of people. Some other skills are as follows: 1.Communication Skills Communication is the key factor for any team member to be successful.  The team should be open to working together to achieve a common project target. It is very important that everyone on the team should communicate effectively. Most probably, the Product Owner should possess good communication skills. As the Product Owner needs to work with the customers’ to understand their needs and conveying that to the development team to bring it to reality. If they could not able to communicate effectively, it may affect the organization value. 2.Commitment The Product Owner should be committed to the project target, product vision, team, and the business. They have to attend all the meetings and work with all the team members. So, it is very important for them to collaborate with everyone. Furthermore, the Product Owner must be accountable for the process and be committed to the success of the project 3. Vision The Product Owner should be able to clearly communicate the product vision between the backlog items and the large project goals. They check whether the product vision is aligned with the company’s vision and needs. 4.Curious about what they work Concerning that “bad product owner” is so often the excuse for bad product. I coach towards product leadership and team ownership. My worst case is product owner telling the team exactly what to build, and team not taking ownership of the outcome. That’s what “bad” looks like. https://t.co/Um4rgvJ7yk — Jeff Patton (@jeffpatton) April 4, 2018 The Product Owner (PO) need to be curious always to ask ‘Why’ from the client (about his/her requirements) and ‘How(to the development team). But before asking the questions to the team, they should understand the rules and able to create a clear vision of the final product. Responsibilities of the Product Owner: Product Owner has to attend the daily sprint planning meetings. Product Owner prioritizes the product features, so the development team can clearly understand them. Product Owner decides the deadlines for the project. Product Owner determines the release date and contents. Product Owner manages and creates the product backlog for implementation, which is nothing but the prioritized backlog of user stories. Product Owner defines user stories to the development team. Spending some time to prioritize the user stories with a few team members. The Product Owner and Scrum Master Relation     This question is highly debatable in an Agile world. Many say that there needs to be a clear contrast between these the Scrum Master and Product Owner and therefore needs two individuals to manage these two roles. The Product Owner should have an overall vision of the client’s requirements. Due to this reason, the Scrum Master needs the Product Owner. Whereas the project team requires the Scrum Master to work maintaining the velocity and capacity of the team. Choosing the best The Product Owner has to get involved in grabbing the project details. But, along with that, the Product Owners expect an experienced Scrum Master should work and guide his/her team members to work efficiently yielding good results. The Scrum Master and the Product Owner have mostly overlapping roles and responsibilities and skills as well. Every one of them requires an alternate level of communication and mindset.
Rated 4.0/5 based on 2 customer reviews
7254
Scrum Master and Product Owner: Understanding the ...

According to the State of Scrum report 2017-2018 b... Read More

CSM®️ or PSM™ - Which Certificate Is More Valuable?

What is Scrum?The source of a correct definition of Scrum is the official Scrum Guide, authored and maintained by Jeff Sutherland and Ken Schaber. Scrum has its roots in software development, but nowadays Scrum is applied in several contexts and industries.From the Scrum Guide:“Scrum is a framework for developing, delivering, and sustaining complex products. Scrum is not a process, technique, or definitive method. Rather, it is a framework within which you can employ various processes and techniques. Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment."The latest update to the Scrum Guide also lists possible uses for Scrum:- Research and identify viable markets, technologies, and product capabilities;- Develop products and enhancements;- Release products and enhancements, as frequently as many times per day;- Develop and sustain Cloud (online, secure, on-demand) and other operational environments for product use; and,- Sustain and renew products.Origin of ScrumScrum is a process framework that has been used to manage work on complex products since the early 1990s. Ken Schwaber and Jeff Sutherland worked on Scrum until 1995, when they co-presented Scrum at the OOPSLA Conference in 1995. This presentation essentially documented the learning that Ken and Jeff gained over the previous few years, and made public the first formal definition of Scrum.The Scrum Guide documents Scrum as developed, evolved, and sustained for 20-plus years by Jeff Sutherland and Ken Schwaber.  Both, Jeff Sutherland and Ken Schwaber were present at the event when the Agile Manifesto was written.Scrum was one of the several lightweight processes presented at that gathering in 2001. The Scrum Alliance - a non-profit organization promoting Scrum, was also founded in 2009.Throughout the years Scrum has evolved, and in fact, has been become simpler, but therefore not more easy to apply and practice. In case you're interested, you can look at the Scrum Guide revision history, and see the changes since 2010. To me personally, the beauty of Scrum lays in its simpleness, although some people would advocate they still find Scrum too complicated in terms of process.Scrum Alliance vs Scrum.orgIn 2001, Ken Schwaber left the Scrum Alliance and found Scrum.org. There was a bad impression of the Scrum Master about implementing a Scrum in the organization. The Scrum Masters misinterpreted that the 2-day Scrum Alliance CSM®️ certification course is enough to certify them as a Scrum Master.  Even organizations took amiss that those who attended 2-day training are the Scrum experts.The PSM™  certification of Scrum.org is different than CSM®️ certification. For PSM™ certification, attending a workshop is not mandatory. But, it is little harder to clear the PSM™  assessments which at least assures a precise level Scrum understanding. Note: The Scrum.org assessments are based on the Scrum Guide (fabricated by Ken Schwaber and Jeff Sutherland).Let’s see these two certifying bodies in details and figure out the difference between the Scrum Alliance and Scrum.org.Scrum Alliance- The CSM®️ certifying BodyFounded in 2001, Scrum Alliance® is the largest membership and certification organization in the Agile community. The Scrum Alliance is a non-profit organization and is governed by the Board of Directors. The Scrum Alliance has certified more than 750,000 practitioners worldwide, clearly contributing a lot to the spreading of Scrum worldwide. But, the Scrum Alliance is not simply a company providing training. The Scrum Alliance also organizes twice a year a global gathering and several regional gatherings and supports agile community events.From the Scrum Alliance website:"Scrum Alliance’s vision is to “Transform the World of Work” with a mission to guide and inspire individuals, leaders, and organizations with practices, principles, and values that create workplaces that are joyful, prosperous, and sustainable."Scrum Alliance certificationsAs there are 3 roles in Scrum, the Scrum Alliance offers 3 entry-level (foundational) certifications - there are CSM®️ (Certified Scrum Master), CSPO (Certified Scrum Product Owner), and CSD (Certified Scrum Developer). Next, you could apply for a Certified Scrum Professional (CSP), after indicating your practical experience with Scrum.Recently, the Scrum Alliance has changed the certification path and added an "advanced" certification and course. Today, the Certified Scrum Professional is specific for either Scrum Master, Product Owner, or Developer.These are the certifications:- Certified Scrum Master: CSM®️ --> Advanced CSM®️ --> CSP-SM- Certified Scrum Product Owner CSPO --> Advanced CSPO --> CSP-PO- Certified Scrum Developer (CSD)Next, you can obtain so-called "elevated" certifications, which involves a more rigorous screening and test to validate your knowledge, experience.The elevated certifications target to be an accredited trainer or coach:- CST (Certified Scrum Trainer) - people with this certification can provide official training in Scrum, on behalf of the Scrum Alliance. Trainers go through a rigorous process of co-training, and an application in order to pass the bar of becoming a CST.- CTC (Certified Team Coach) - to be recognized and accredited as a coach on the team level- CEC (Certified Enterprise Coach) - to be recognized and accredited as a coach on the enterprise levelThe coaching certifications involve more than Scrum, but agile & lean coaching in general.The Scrum Alliance also provides an Agile Leadership track - this is relatively new and split into two levels:- Certified Agile Leadership I- Certified Agile Leadership IIThe Agile Leadership courses increase your leadership effectiveness and learn how to be a better leader, no matter what your role.The Scrum Alliance provides also "extended" continuing education, courses.The Scrum Alliance is taking a broad view of how to transform the world of work (e.g. also applications of Scrum outside IT).Scrum.org- The PSM™  certifying BodyIn 2002, Ken Schwaber with others founded the Scrum Alliance and set up the Certified Scrum accreditation series.  Ken Schwaber left the Scrum Alliance in late 2009 and founded Scrum.org which oversees the parallel Professional Scrum accreditation series.On the Scrum.org website, there's a page called "Why Scrum.org?" explaining Ken Schwaber's motivation to separate from the Scrum Alliance and found Scrum.org. These are the motivations as formulated by Ken Schwaber:- I would create a new organization, Scrum.org, to continue developing and sustaining the Scrum Developer program.The program would lead to assessments and certifications based on a body of knowledge.- I would also redevelop a new, more advanced version of the Scrum courseware. This courseware, called Scrum-In-Depth, would focus on how to use Scrum in advanced circumstances. I would publish the Scrum body of knowledge on Scrum.org and formulate beginner, intermediate, and advanced assessments and certifications based on this body of knowledge.- I would form a new group of Scrum Trainers who welcomed openness and transparency.Scrum.org  aims to improve the Profession of Software Delivery and targets its courses and certifications in that area. The Scrum Alliance focuses on Scrum, and takes a broader view, as the Scrum Alliance's slogan is to "transform the world of work".Scrum.org certificationsThe certifications provided by Scrum.org are similar to the certifications of the Scrum Alliance. The certifications are called "Professional" The certification path is as following:- Professional Scrum Master: PSM™  level I --> level II --> level III- Professional Scrum Product Owner: PSPO- Professional Scrum Developer: PSD- Scaled Professional Scrum (SPS), based upon Scrum.org Nexus framework for scaling Scrum- Professional Scrum with Kanban (PSK I): to validate knowledge of how Scrum Teams can use Scrum with Kanban ability to support value creation and delivery. Kanban is a lean method to streamline work. Scrum has its foundations in lean, so it does make a lot of sense for teams to learn and apply Kanban. In fact, agile & lean are blending philosophies.- Professional Agile Leadership (PAL-I): Agile Leadership trackThere’s an optional (non-mandatory) PAL-E (Professional Agile Leadership - Essentials). The workshop provides a foundation for the role that leaders play in creating the conditions for a successful agile transformation.In summary,In a comparison to Scrum Alliance, remember the following practical points when you consider one or the other certification:Scrum.org certifications have no expiration date.Scrum.org certifications can be obtained by taking an online test. Physically attending a classroom course is not required.Scrum.org offers “open assessments” which are interesting for anyone to validate your Scrum knowledge, regardless of if you intend to get certified or not.To know more about various Agile and Scrum certifications and paths to learning these certifications to make a career move, you can refer certification pathway.Choosing between the best Scrum Master Certifications: CSM®️ vs PSM™ Agile and Scrum are today’s latest trends. Not only IT-based organizations but also non-IT organizations hire individuals who know the concepts of Scrum framework and its applications. Scrum is the Agile framework, focuses on the complex projects.Initially, the Scrum framework was used for software development, but today it is used as any other projects to get the fastest results. So, there is a rising demand for Agile-Scrum professionals in the organizations.CSM®️ and PSM™  are two major Scrum Master certifications. CSM®️ stands for Certified Scrum Master. CSM®️ is a certification issued by the Scrum Alliance. CSM®️ is a first (entry-level) certification for the Scrum Master. PSM™  stands for Professional Scrum Master. PSM™  is a certification issued by Scrum.org. PSM™  and PSM™  both are the entry-level certifications for the Scrum Master.    PSM™  by Scrum.org has a different approach than CSM®️ by Scrum Alliance in the following ways:- According to Scrum.org, there's no need to attend a class, to be able to take an online test to get certified. A practice assessment is available online, called "Scrum Open"- According to Scrum.org, a certification is a proof of knowledge and therefore has no certification dateLet’s see the differences between the CSM®️ and PSM™  in the tabular form.Certified Scrum Master (CSM®️)FeaturesProfessional Scrum Master (PSM™)50 multiple-choice questions, usually with four possible answersExam Pattern- Number of Questions: 80- Format: Multiple Choice, Multiple Answer and True/FalsePassing score: 74%Passing gradePassing score: minimum 85%Time limit: 60 minutesExam durationTime limit: 60 minutesEvery 2 yearsCertification renewal durationNo expiration (Lifetime certification)Fee: $1000 (cost of training and 1 attempt)Certification costFee:PSM I- $150PSM II- $250PSM III- $500(1st free attempt is given to those who attend the PSM training)The exam is easy once you attend the two-day CSM®️ training program. Also, you can practice with CSM®️ practice test/mock test, to know which areas you need to improve and pass the test with a good score.Level of the examDifficulty: IntermediatePSM assessments are difficult to pass. But, attending PSM training is highly recommended in order to pass the exam with a fair score, though it is not mandatory. Also, prepare with the Scrum practice tests to get a fair idea on this.Attending a 2-day CSM®️ course taught by a Scrum Alliance's Certified Scrum Trainer (CST)®️PrerequisiteNo prerequisite for taking the test$119,040  per yearSalary$100,500 per yearFinal ThoughtA search on “Scrum Master”, in the job title with as prerequisite “Certified Scrum Master” gives more than 1000 jobs results. If you want to get an idea of what companies and organizations ask in terms of Certified Scrum Master, you can have a look at the AgileCareers website (by Scrum Alliance). (there are mainly USA based jobs listed)This is all about the comparison between the CSM®️ and PSM™  and various certifying bodies like Scrum Alliance and Scrum.org that offer these certifications.In the end, knowledge matters whether it is CSM®️ or PSM™  certification. Both certificates have the same value in the job market. Also, both programs are highly compatible. It is very crucial what you earned during the certification process and the trainer will definitely help you to make the difference there.To know in-detail about the Scrum master certification benefits, roles, salaries and many more refer: Scrum Master Certification - The Definitive Guide
Rated 4.5/5 based on 19 customer reviews
6085
CSM®️ or PSM™ - Which Certificate Is M...

What is Scrum?The source of a correct definition o... Read More

Useful links