This Festive Season, enjoy 10% discount on all courses Use Coupon NY10 Click to Copy

Search

Think Big - Act Small: A New Way For Agile Teams?

We all love planning. And planning big is what we do. Don’t you have great visions for your life when you start a brand new year? You identify a great big list of New Year resolutions and set yourself some goals to achieve within the year. When you are soon after your primary education you research and end up planning big on what academic and professional qualifications to achieve and within what timeframe.Even Google has become a part of your elaborate planning! So much so that, even before you key in your exact query on planning, it readily comes up with so many suggestions!Basically, even the search engine giant has got one thing right about you. You always plan big!!But, Agile tells us to think big and not to plan big. Thinking big has a deep meaning. When you embark on a journey you need to think and clarify the bigger picture of the whole journey. For example, if your employees embark on their annual trip you need to set a bigger picture for the staff on the objectives of the trip. Is it merely a journey to somewhere far away, chill and come back the next day? Or are your objectives for the staff to bond a bit better, communicate and build team spirit that can create a positive atmosphere at your workplace?Think big for your Agile projects as well. Identify the bigger picture for the solution that you are trying to develop. Spend time to understand the business outcomes that the solution is trying to achieve and know the key principles for high-performing Agile teams.Is it a solution to improve efficiency?Is it to improve collaboration and convenience?Is it to increase profitability and market share of the organization through better reach?Think about where the solution will be deployed and who will be using it. How will the solution get operationalized and what impact would it have on the Stakeholders. Try to draw forth as much information as possible to identify above aspects of the solution.Thinking big is not only from the business perspective. Think big in terms of the entire solution landscape, the context and the entire solution architecture as well. There is no need to identify a comprehensive solution design and architecture right at the inception. But always keep the entire solution and the key components in mind when you do the design. Make it and evolving architecture by building in the capability to plug in components as and when required. Technology and client needs are changing and hence adaptability is a key.Though you think big you must always make sure to take small baby steps at a time. Acting small means to identify the smallest piece of work or task that needs to be done to make sure that the project progresses forward. Think of a driver that has met with a car accident and is confined to a wheelchair. He will have to go through hours of physiotherapy just to be able to stand up on his two feet again. Then he will start taking one step at a time in his quest of walking again.Concepts that can be measured while thinking Big1) Working in a team incrementally and iteratively  The product size determines how many increments it will take to complete the work. The notion behind working in iterations is to get the status of work at the end of the long stage. e.g. For Development stage, it may take two week cycles over the period of 3 months.Working in increments shows doing a group of tasks at a time, then adding another group in the next iteration. At the end of each iteration, you can show the completed task to the client. This way helps to get early feedback, can update the changes, test out ideas, and deploying before the timeline.  Dedicated teams are nothing new to creative land, what is different, is that it means that they are really dedicated to the project full-time, rather than working on a bunch of other projects at the same time.Now, we know in agency land, this can be hard to pull off, since we have a tendency to move resources around as needed, because of skill-level or other resource issues.Now, you can still manage teams as a dedicated resource by, keeping all of the related projects with one team. All of the pieces are then prioritized (working with the client to decide). This gives you big idea on building a successful Agile team. The big idea is that you work in a dedicated team, and at the end of each iteration, or time period, you have something of value to show the client. In the first time period, the client decides what should get worked on, and with each iteration you add things in the order they are of value (incrementally), and then repeat the process through multiple interactions till the work is done.2) Change should be embracedThe client asks for change, team produce a change, and charge for it. In traditional methodology, teams were preventing change. For software development projects embracing the client’s changes early and updating before the deployment date can be very impactful.Planning plays a crucial role in Agile. Though your end product is outstanding, how to deal with the market demands and conditions is critical part for embracing opportunity and change.In Agile methodology, the Stakeholder and the team prioritize and chooses the highest-priority work to be completed during that iteration. Being flexible at an iteration stage, the client should not ask for the changes during this time. But your team can maintain the scope-of-work by working in 1 or 2 week intervals. If any changes needed then those changes can be pushed to the next iteration. There are some characteristics of new Agile teams that includes limit to what team can accomplish during a fixed period of time. Things can go out of the scope, resources and costs can still change.Agile software development projects are exactly like that. You first think big to identify all components of the solution and the tasks that the team members need to work on as Product backlog items. These are initially at a really high level – may be as epics.Now you can groom the stories and break them down into smaller stories or tasks that can be assigned to individual team members. Remember the 1-2-3-4 rule? One or two implementation team members should complete a story or task taken to the sprint within 3 to 4 days. Acting small will help the team develop something visual and demonstrable as soon as possible so that it can be sent for feedback as early as possible.Think big, act small are 4 simple words with a great deep meaning which leads in creating new Agile teams. For an Agile team to become a successful robust team these are key principles for high performing Agile teams that can be preached and followed diligently.So, do you think big but act small?
Rated 4.5/5 based on 3 customer reviews

Think Big - Act Small: A New Way For Agile Teams?

416
Think Big - Act Small: A New Way For Agile Teams?

We all love planning. And planning big is what we do. Don’t you have great visions for your life when you start a brand new year? You identify a great big list of New Year resolutions and set yourself some goals to achieve within the year. When you are soon after your primary education you research and end up planning big on what academic and professional qualifications to achieve and within what timeframe.
ResearchEven Google has become a part of your elaborate planning! So much so that, even before you key in your exact query on planning, it readily comes up with so many suggestions!

Basically, even the search engine giant has got one thing right about you. You always plan big!!

But, Agile tells us to think big and not to plan big. Thinking big has a deep meaning. When you embark on a journey you need to think and clarify the bigger picture of the whole journey. For example, if your employees embark on their annual trip you need to set a bigger picture for the staff on the objectives of the trip. Is it merely a journey to somewhere far away, chill and come back the next day? Or are your objectives for the staff to bond a bit better, communicate and build team spirit that can create a positive atmosphere at your workplace?

Think big for your Agile projects as well. Identify the bigger picture for the solution that you are trying to develop. Spend time to understand the business outcomes that the solution is trying to achieve and know the key principles for high-performing Agile teams.

  • Is it a solution to improve efficiency?
  • Is it to improve collaboration and convenience?
  • Is it to increase profitability and market share of the organization through better reach?

Think about where the solution will be deployed and who will be using it. How will the solution get operationalized and what impact would it have on the Stakeholders. Try to draw forth as much information as possible to identify above aspects of the solution.

Thinking big is not only from the business perspective. Think big in terms of the entire solution landscape, the context and the entire solution architecture as well. There is no need to identify a comprehensive solution design and architecture right at the inception. But always keep the entire solution and the key components in mind when you do the design. Make it and evolving architecture by building in the capability to plug in components as and when required. Technology and client needs are changing and hence adaptability is a key.

Though you think big you must always make sure to take small baby steps at a time. Acting small means to identify the smallest piece of work or task that needs to be done to make sure that the project progresses forward. Think of a driver that has met with a car accident and is confined to a wheelchair. He will have to go through hours of physiotherapy just to be able to stand up on his two feet again. Then he will start taking one step at a time in his quest of walking again.

Concepts that can be measured while thinking Big
Concepts that can be measured while thinking Big1) Working in a team incrementally and iteratively  
The product size determines how many increments it will take to complete the work. The notion behind working in iterations is to get the status of work at the end of the long stage. e.g. For Development stage, it may take two week cycles over the period of 3 months.

Working in increments shows doing a group of tasks at a time, then adding another group in the next iteration. At the end of each iteration, you can show the completed task to the client. This way helps to get early feedback, can update the changes, test out ideas, and deploying before the timeline.  
Working in a team incrementally and iteratively  Dedicated teams are nothing new to creative land, what is different, is that it means that they are really dedicated to the project full-time, rather than working on a bunch of other projects at the same time.
Now, we know in agency land, this can be hard to pull off, since we have a tendency to move resources around as needed, because of skill-level or other resource issues.

Now, you can still manage teams as a dedicated resource by, keeping all of the related projects with one team. All of the pieces are then prioritized (working with the client to decide). This gives you big idea on building a successful Agile team.
 
The big idea is that you work in a dedicated team, and at the end of each iteration, or time period, you have something of value to show the client. In the first time period, the client decides what should get worked on, and with each iteration you add things in the order they are of value (incrementally), and then repeat the process through multiple interactions till the work is done.

2) Change should be embraced

The client asks for change, team produce a change, and charge for it. In traditional methodology, teams were preventing change. For software development projects embracing the client’s changes early and updating before the deployment date can be very impactful.
Change should be embracedPlanning plays a crucial role in Agile. Though your end product is outstanding, how to deal with the market demands and conditions is critical part for embracing opportunity and change.In Agile methodology, the Stakeholder and the team prioritize and chooses the highest-priority work to be completed during that iteration. Being flexible at an iteration stage, the client should not ask for the changes during this time.
 
But your team can maintain the scope-of-work by working in 1 or 2 week intervals. If any changes needed then those changes can be pushed to the next iteration. There are some characteristics of new Agile teams that includes limit to what team can accomplish during a fixed period of time. Things can go out of the scope, resources and costs can still change.

Agile software development projects are exactly like that. You first think big to identify all components of the solution and the tasks that the team members need to work on as Product backlog items. These are initially at a really high level – may be as epics.

Now you can groom the stories and break them down into smaller stories or tasks that can be assigned to individual team members. Remember the 1-2-3-4 rule? One or two implementation team members should complete a story or task taken to the sprint within 3 to 4 days. Acting small will help the team develop something visual and demonstrable as soon as possible so that it can be sent for feedback as early as possible.
Cost of change curveThink big, act small are 4 simple words with a great deep meaning which leads in creating new Agile teams. For an Agile team to become a successful robust team these are key principles for high performing Agile teams that can be preached and followed diligently.

So, do you think big but act small?

Rumesh

Rumesh Wijetunge

Chief Innovation Officer - Zaizi Limited, Chief Operating Officer - LearntIn (Pvt) Ltd., Director /

Rumesh is an IT business leader with over 12 years of industry experience as a business analyst and project manager. He is currently the CIO of Zaizi Limited, a UK based data management company heading the operations in Sri Lanka, the COO of LearntIn, a global training institute based in Sri Lanka and is also a lecturer / trainer at multiple private universities on management, IT, business analysis and project management subjects. He is the current president of the IIBA Sri Lanka chapter and is one of the most qualified and sought after trainers in Sri Lanka. Refer his LinkedIn profile for more details and to see more articles he has written on linkedin

Join the Discussion

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

Suggested Blogs

Agile Scrum Roles And Responsibilities

Agile, Scrum, Waterfall, Kanban are different project management frameworks which are helping the companies to increase the productivity. These frameworks were created by the IT companies and especially web and application development companies because they needed a path but on which each and every employee can perform his daily tasks. However, out of these four frameworks, the Scrum is the most widely used framework in all the companies despite their nature of work. That is why in this article we are going to discuss the Scrum in detail to give you a better idea about this iterative framework which is making easier for the companies to complete their project. Scrum Objective: The basic objective of the Scrum is to keep the entire team on the same page throughout the project. The scrum framework allows the cross-functional work of the team of 4 to 10 members to provide the regular details and information sharing liberty so they can produce the best result. Scrum is a more like philosophical than the technical. It is a framework that can only be used as the guidance and there is no constant in it. All the success of the Scrum depends on the interactions among the stakeholders as it does the process. Scrum roles and responsibilities: The techniques of Scrum has become very popular and now considered to be the most important thing to do before starting any project. That is why the demand of the scrum masters and other professions related to the scrum has also increased, and people now are searching about the term scrum more. The scrum is a very specific and précised framework that is why it comprised on the following roles. Scrum Master Product Owner Scrum Team Stakeholders   Because the term Agile is often get associated with the project managers that is why many people believe that the Scrum Master is also a term for the project managers. However, the Scrum Master serves very different purposes than the project manager. The Scrum Master works as a facilitator rather than the authoritative person who is responsible for the project delivery. The Scrum Master is a coach, motivator and problem solver who can only assist the team by using all his experience of Scrum framework. According to many Scrum Masters, applying Scrum within an organization is not the actual scrum process. You have to make the organization to accept your new role and then change its culture which is the most difficult thing to do in any company. The prominent role of every Scrum Master should be to enhance the power of the team by committing them to the sprint goals without any interference from the management. Let’s discuss the major roles of all the above points separately. Scrum Master: The Scrum Master is considered to be the top-dog in every organization because companies usually hire them and don’t treat them as permanent employ that is why they are with no authority. It is their duty to remove all the hindrance or obstruction in the way of achieving any goal. It is also their role to enforce scrum ceremonies and processes. They are the ones who commit to goals and deadlines on behalf of the team. Product Owner: The product owner is responsible for conveying the vision of the stakeholders to the team. They have the authority to alter the scope. The Product Owners are responsible for the return on investment (ROI) that is why they occupy an authoritative position in the firm. Because they convey the vision of the stakeholders that is why they are the voice of the stakeholders. Not only with the team, but they also communicate with the stakeholders about progress and problems. Scrum Team: The Scrum Team is responsible for all the activities that lead them towards their sprint goals. They have to work with the Scrum Master to prioritize the items from the product backlog in the sprint planning. Once committed, it is their responsibility to fulfil the commitment and deliver the agreed results on time with great quality. The Scrum Master is not responsible for keeping his team organized that is they it is the duty of the Scrum Team to get self-organized. They have to be agile in the office and have to attend every standup and other ceremonies. They have to participate in all the meetings despite their nature and have to ensure that all the findings of the meetings are getting practically addressed in the project. Stakeholders: The Stakeholder has to keep a healthy relationship with the Product Owner in order to share every detail regarding his project. The Stakeholder is responsible for conveying his wishes and concerns to the product owner or else the product owner would not be responsible for his project quality and time duration. The Stakeholder has to provide regular input to queries from the Product Owner. Prioritizing the work affectively with the Product Owner is another job that the Stakeholder has to do to ensure his project development. Keep taking updates or keep giving updates regarding any change in the plans.
Rated 4.0/5 based on 1 customer reviews
9509
Agile Scrum Roles And Responsibilities

Agile, Scrum, Waterfall, Kanban are different proj... Read More

Best ways to implement Leading SAFe 4.5 in organizations

SAFe stands for Scaled Agile Framework. This framework is mostly used by the corporate bodies which need to scale from smaller organizations to larger ones. So SAFe is also known as an enterprise-scale development methodology. This framework was coined by Dean Leffingwell. It is an ‘information base’ which is freely available, and allows you to apply Lean-Agile practices at an organization level.   Scaled Agile Framework (SAFe) is referred as the Agile framework for software development. It renders an ease of operation for the development team. SAFe 4.5 is the most updated version introduced to match the needs of the organizations. This version consists of some new features as follows:  Fastest delivery with scalable DevOps and Continuous delivery  Quick testing using the Lean Startup cycle and User Experience (UX)  Improved Portfolio performance with Lean Portfolio Management (LPM) and Lean Budgets Additionally, SAFe 4.5 allows organizations to transform from the traditional approach to Lean-Agile methodology with the new Implementation Roadmap. Implementation Roadmap of SAFe 4.5 is a guide for the organizations. Reasons to switch to SAFe 4.5: ●  The updated version of SAFe 4.5 supports the range from simplest to the most critical development environment. SAFe 4.5 is able to mould according to the organizational needs. SAFe has four new   configurations as follows:  1. Essential SAFe - an initial phase which starts just after realizing the benefits. 2. Portfolio SAFe - adds portfolio level, strategy and investment funding, guidance on Agile programs, and Lean governance as a scenario. 3. Large Solution SAFe - for building large systems that involve Agile Release Trains and Suppliers 4. Full SAFe - for the largest firms those are seeking the benefits of the Lean-Agile enterprise.   ● SAFe 4.5 works by integrating Lean Startup Cycle and Lean UX, which creates an environment to form Minimum Viable Product (MVP). It fosters quick innovation. ● SAFe 4.5 has concentrated on the feature of rapid delivery using the techniques like Scalable DevOps and Continuous Delivery Pipeline. ● SAFe 4.5 has provided a guide in the form of a 12 article series, given a name as ‘SAFe Implementation Roadmap’. Based on the Change Management technique in the organization, the roadmap       guides on the critical steps that an organization can take to achieve long term goals.  ●  SAFe 4.5 is completely backward compatible. In SAFe 4.5, you just need to adopt the advanced principles, keeping old versions in place.                                                                                                  How is SAFe 4.5 Implemented? SAFe Implementation Roadmap provides guidance to the organizations in the form of a twelve-article series which describes effective strategies and a set of activities to implement SAFe at an organizational level. Let me illustrate the 12-article series below-   Reaching the tipping point.  Train Lean-Agile change agents  Train Executives, Managers and Leaders  Create a Lean-Agile Centre of Excellence  Identify Value streams and ART’s  Create the Implementation plan  Prepare for ART Launch   Train Teams and Launch ART   Coach ART Execution   Launch More ARTs and Value Streams  Extend to the Portfolio   Sustain and Improve SAFe is a pivotal framework as it helps to achieve business benefits at an organizational level. In order to understand the outcomes of Leading SAFe implementation, organizations must embrace and understand the Lean-Agile principles. Based on the Change Management strategies in the organization, the SAFe Implementation Roadmap guides on the critical steps that an organization can follow to achieve long term goals.   
Rated 4.0/5 based on 20 customer reviews
6347
Best ways to implement Leading SAFe 4.5 in organiz...

SAFe stands for Scaled Agile Framework. This frame... Read More

CSM®️ or PSM™ - Which certificate is more valuable?

IntroductionWhat 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: minimum 69%Passing gradePassing score: minimum 85%- The test is taken anytime after attending the course- There's no time limitExam durationTime limit: 60 minutesEvery 2 yearsCertification renewal durationNo expiration (Lifetime certification)Fee: $1295 per attemptCertification costFee: $150 per attemptThere's no practice exam available. In general, after attending and learning during a two-day CSM course, you should be able to pass the exam without issues.Level of the examDifficulty: Intermediate$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 what companies and organizations ask in terms of Certified Scrum Master Course, 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 the 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.
Rated 4.0/5 based on 19 customer reviews
5095
CSM®️ or PSM™ - Which certificate is more val...

IntroductionWhat is Scrum?The source of a correct ... Read More

other Blogs