Search

Start Sooner Implement Better: Agile Principles Revisited

Principle #3: Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. I can’t tell you how many times a day or in my career I have heard “Why are we not moving faster?” or the ever-popular “What has the team been doing since <insert_random_qualifier>”. Of course, those that are on the project know why things have not moved faster, because leadership has been engaged in bureaucratic administrative budgeting for six months, making sure the requirements are 100% accounted for which has taken another four months. Then final approval and sign off by a tribe of 30 or more people has taken another two months and of course a date was already committed to before the budgeting process began, so when the team can actually start work, provided other projects are not taking up their time, everyone is screaming “HURRY UP!”.  The time to hurry was months and months ago, not once the team can actually start solving the customer’s problem.    In this installment of “Agile Principles Revisited” we will take a look at how a team can deliver sooner. Deliver This should be self-explanatory right? I have coached teams that have argued about getting credit for a half-done story in a sprint because they got a few tasks associated to the story completed, but the story itself was not done.  If the story cannot be demonstrated or validated as a slice of the overall goal, then you did not deliver value, you just logged hours.  This is why we talk about vertical slices of functionality, INVEST criteria and splitting stories so that the focus can be on actually delivering within a time box rather than “working on” stuff for multiple sprints.  Working Software While we want to focus on delivering as frequently as our environment and processes allow, what we deliver should actually work and moreover, solve a problem thus adding value; however, this is where it can be a bit tricky depending on how the term “working” is defined given the context.  I will sometimes refer to MVP as a vertical slice of functionality that can be validated at a defined feedback moment, such as the sprint review and will refer to a batch that can be released to customers as the MMF (Minimal Marketable Feature).  I do this to help teams understand how much effort and complexity needs to go in each story depending on the given goal.  If we are attempting to validate a proof of concept idea, we can use a prototype, dummy data or mock details up and have a low fidelity design.  This meets the definition of “working” because we are attempting to validate a theory or conceptual functionality, not releasing to our actual customer base at this point. Before we open up the product to customers to generate incremental ROI, we would, of course, be more robust in the approach and reach a higher quality definition of “working” and “done”.  It is always best to set expectations upfront on what working means during the course of your product delivery approach. The Disciplined Agile Delivery site has a great breakdown of the different views you can take with product increments Frequently: Shorter timelines create urgency, urgency creates action.  Delivering small, independent features are much more efficient than large, tightly coupled bundles of features.  The reasons we want to deliver more frequently are to increase the feedback cycle times and reduce the opportunities for a requirement to change, or be able to accommodate a change with little impact.  The shorter the window of time between the time a Product Owner talked to a stakeholder, created the story for the team to develop and deliver, the lower the likelihood of that requirement changing and the higher the probability we can get feedback if we are building the right thing.  Preference to the Shorter Timescale: If you can deliver software in two weeks, then you don’t have to decide on what to do until 2-3 weeks before you deliver. If you deliver software every 12 months, then you have to take longer to decide on what to do, and that opens the opportunity for your customer to change their mind in that window of time. Shortening your delivery cycle allows you to decide as late as possible on which direction to take, which is a competitive advantage.  In 1983, Lenscrafters changed the eyewear market by having your glasses ready in an hour. This did not allow the customer the opportunity to go browsing at another company and cancel their order and it met the “need it now” emotional aspect. The timescale here needs to be understood and defined as well.  There is the sprint timescale (1-4 weeks) and there is the release time scale (3-4 months for new feature releases).  The team should set aggressive goals in improving the timescale cadence until you reach a more predictable pace.  There are practices that support a team reaching shorter timescales such as; Continuous Integration: The ability to automate the building and testing of code every time a team member commits to provide immediate feedback on what should be addressed to eliminate downstream affects customer experience and spend less time tracking down issues.   Test Automation: This really goes hand in hand with CI practices and should be a part of any development team’s practices.  I will often get teams started with just Selenium and cucumber as means to start illustrating automation thoughts and practices. While this may not address the long-term enterprise needs, it does address the question- “How do we get started”.  Start simple with a few steps until they no longer meet the needs and grow from there. Those are only a few of the obvious practices that a team would perform to help shorten feedback loops and build in quality.  Researching DevOps would identify many more that a team should investigate into improving their environment. What does that mean to us? Don’t Make the Customer Wait: The fundamental measurement of a queue is cycle time.  The whole reason a work item enters a queue is to accomplish something and the longer it waits for resources to complete the work, the more time is spent waiting.  Waiting in a queue is wasted time, opportunity and revenue (Poppendieck, 2003). Customers expect rapid delivery today in all channels and if you are not meeting their expectations of that delivery cycle, there will be rapid communication of the bad experience through social channels. Communicate Quickly To Your Customer: When you can go online and search for any amount of information that tends to increase your expectations when making an inquiry with a company on a request or product.  Customers expect companies to have data available to answer their questions as quickly as they can send a tweet out.  Email and phone calls are falling lower in the channels of communication as customers require instant answers either through chat or social channels.  Your delivery cycle should be able to address these channels quickly.  Make Use of Gemba: The Japanese word for “the actual place” is perfect in the discovery and feedback processes of software usability as it means you are with the actual people using the product and collecting feedback. This also illustrates empathy so that customers begin to feel like they are being listened to and thus are more likely to provide feedback if they feel like they are a part of the solution.  Principles and sensemaking #agile #change #orgdesignhttps://t.co/Mt5Qwiih1x — John Cutler (@johncutlefish) June 26, 2017 Enemies of the (to be) State: Over-Engineering:  Keep it simple.  In our second installment we touched on “Gold Plating” or putting in extra features, you just “know” the customer wants. This takes time and time increases your queue, which causes wait time.  You should be sensing a theme by now.   Over Processing: Adding additional bureaucratic gates, processes or documents reduces trust, and increases the wait time for a product to reach the market and rarely adds value beyond someone wanting to check a box.  That is not to say all processes are bad, merely, we should be inspecting whether or not they add quantifiable value or add agility to our product development process. Point-Based Design: How many of you have attempted to schedule a meeting starting at 9 am only to get responses from people stating they can’t make it at that time, and then you start an endless cycle of emails and declines to finally arrive at an agreed upon time 3 days later.  This is point-based design.  You focus on one option and one option only which limits your choices and ability to deliver and react.  Whereas using a set-based design approach you allow options to be available and make decisions as late as possible to allow for more flexibility and to respond in a more efficient manner using real feedback.  Using the meeting example, you will get more positive feedback if you send a list of options with windows of times to schedule a meeting and you can quickly schedule a meeting based on these options rather than trying to herd folks down only one path. If you are not quick in today’s competitive environment, then you are playing catch up to the competition instead of leading the pack and making them play your game.  However, if you hurry, you run the risk of doing things poorly, which will detract from the positive experience we are trying to build for our customers. Finding the balance can be hard, but through small batch experimentation and validated learning you can find the balance that works for you. Being able to deliver small batch experiments quickly, allows you to start sooner and allows teams the ability to respond in a leaner more result-oriented fashion.  

Start Sooner Implement Better: Agile Principles Revisited

2K
  • by Bruce Nix
  • 02nd May, 2018
  • Last updated on 09th Mar, 2020
Start Sooner Implement Better: Agile Principles Revisited

Principle #3: Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

I can’t tell you how many times a day or in my career I have heard “Why are we not moving faster?” or the ever-popular “What has the team been doing since <insert_random_qualifier>”. Of course, those that are on the project know why things have not moved faster, because leadership has been engaged in bureaucratic administrative budgeting for six months, making sure the requirements are 100% accounted for which has taken another four months. Then final approval and sign off by a tribe of 30 or more people has taken another two months and of course a date was already committed to before the budgeting process began, so when the team can actually start work, provided other projects are not taking up their time, everyone is screaming “HURRY UP!”.  The time to hurry was months and months ago, not once the team can actually start solving the customer’s problem. 
 


In this installment of “Agile Principles Revisited” we will take a look at how a team can deliver sooner.

Deliver This should be self-explanatory right? I have coached teams that have argued about getting credit for a half-done story in a sprint because they got a few tasks associated to the story completed, but the story itself was not done.  If the story cannot be demonstrated or validated as a slice of the overall goal, then you did not deliver value, you just logged hours.  This is why we talk about vertical slices of functionality, INVEST criteria and splitting stories so that the focus can be on actually delivering within a time box rather than “working on” stuff for multiple sprints. 

Working Software While we want to focus on delivering as frequently as our environment and processes allow, what we deliver should actually work and moreover, solve a problem thus adding value; however, this is where it can be a bit tricky depending on how the term “working” is defined given the context.  I will sometimes refer to MVP as a vertical slice of functionality that can be validated at a defined feedback moment, such as the sprint review and will refer to a batch that can be released to customers as the MMF (Minimal Marketable Feature).  I do this to help teams understand how much effort and complexity needs to go in each story depending on the given goal.  If we are attempting to validate a proof of concept idea, we can use a prototype, dummy data or mock details up and have a low fidelity design.  This meets the definition of “working” because we are attempting to validate a theory or conceptual functionality, not releasing to our actual customer base at this point. Before we open up the product to customers to generate incremental ROI, we would, of course, be more robust in the approach and reach a higher quality definition of “working” and “done”.  It is always best to set expectations upfront on what working means during the course of your product delivery approach. The Disciplined Agile Delivery site has a great breakdown of the different views you can take with product increments


Frequently: Shorter timelines create urgency, urgency creates action.  Delivering small, independent features are much more efficient than large, tightly coupled bundles of features.  The reasons we want to deliver more frequently are to increase the feedback cycle times and reduce the opportunities for a requirement to change, or be able to accommodate a change with little impact.  The shorter the window of time between the time a Product Owner talked to a stakeholder, created the story for the team to develop and deliver, the lower the likelihood of that requirement changing and the higher the probability we can get feedback if we are building the right thing. 

Preference to the Shorter Timescale: If you can deliver software in two weeks, then you don’t have to decide on what to do until 2-3 weeks before you deliver. If you deliver software every 12 months, then you have to take longer to decide on what to do, and that opens the opportunity for your customer to change their mind in that window of time. Shortening your delivery cycle allows you to decide as late as possible on which direction to take, which is a competitive advantage.  In 1983, Lenscrafters changed the eyewear market by having your glasses ready in an hour. This did not allow the customer the opportunity to go browsing at another company and cancel their order and it met the “need it now” emotional aspect. The timescale here needs to be understood and defined as well.  There is the sprint timescale (1-4 weeks) and there is the release time scale (3-4 months for new feature releases).  The team should set aggressive goals in improving the timescale cadence until you reach a more predictable pace.  There are practices that support a team reaching shorter timescales such as;

  • Continuous Integration: The ability to automate the building and testing of code every time a team member commits to provide immediate feedback on what should be addressed to eliminate downstream affects customer experience and spend less time tracking down issues.  
  • Test Automation: This really goes hand in hand with CI practices and should be a part of any development team’s practices.  I will often get teams started with just Selenium and cucumber as means to start illustrating automation thoughts and practices. While this may not address the long-term enterprise needs, it does address the question- “How do we get started”.  Start simple with a few steps until they no longer meet the needs and grow from there.

Those are only a few of the obvious practices that a team would perform to help shorten feedback loops and build in quality.  Researching DevOps would identify many more that a team should investigate into improving their environment.


What does that mean to us?

Don’t Make the Customer Wait: The fundamental measurement of a queue is cycle time.  The whole reason a work item enters a queue is to accomplish something and the longer it waits for resources to complete the work, the more time is spent waiting.  Waiting in a queue is wasted time, opportunity and revenue (Poppendieck, 2003). Customers expect rapid delivery today in all channels and if you are not meeting their expectations of that delivery cycle, there will be rapid communication of the bad experience through social channels.

Communicate Quickly To Your Customer: When you can go online and search for any amount of information that tends to increase your expectations when making an inquiry with a company on a request or product.  Customers expect companies to have data available to answer their questions as quickly as they can send a tweet out.  Email and phone calls are falling lower in the channels of communication as customers require instant answers either through chat or social channels.  Your delivery cycle should be able to address these channels quickly. 

Make Use of Gemba: The Japanese word for “the actual place” is perfect in the discovery and feedback processes of software usability as it means you are with the actual people using the product and collecting feedback. This also illustrates empathy so that customers begin to feel like they are being listened to and thus are more likely to provide feedback if they feel like they are a part of the solution. 


Enemies of the (to be) State:

Over-Engineering:  Keep it simple.  In our second installment we touched on “Gold Plating” or putting in extra features, you just “know” the customer wants. This takes time and time increases your queue, which causes wait time.  You should be sensing a theme by now.  

Over Processing: Adding additional bureaucratic gates, processes or documents reduces trust, and increases the wait time for a product to reach the market and rarely adds value beyond someone wanting to check a box.  That is not to say all processes are bad, merely, we should be inspecting whether or not they add quantifiable value or add agility to our product development process.

Point-Based Design: How many of you have attempted to schedule a meeting starting at 9 am only to get responses from people stating they can’t make it at that time, and then you start an endless cycle of emails and declines to finally arrive at an agreed upon time 3 days later.  This is point-based design.  You focus on one option and one option only which limits your choices and ability to deliver and react.  Whereas using a set-based design approach you allow options to be available and make decisions as late as possible to allow for more flexibility and to respond in a more efficient manner using real feedback.  Using the meeting example, you will get more positive feedback if you send a list of options with windows of times to schedule a meeting and you can quickly schedule a meeting based on these options rather than trying to herd folks down only one path.

If you are not quick in today’s competitive environment, then you are playing catch up to the competition instead of leading the pack and making them play your game.  However, if you hurry, you run the risk of doing things poorly, which will detract from the positive experience we are trying to build for our customers. Finding the balance can be hard, but through small batch experimentation and validated learning you can find the balance that works for you. Being able to deliver small batch experiments quickly, allows you to start sooner and allows teams the ability to respond in a leaner more result-oriented fashion.  

Bruce

Bruce Nix

Blog Author

Bruce Nix, one of the highly experienced Agile coaches at Lokion, applies two decades of experience in information technology and innovation management to his projects. He trains and leads cross-functional teams in innovation practices, ensuring the best possible outcomes for teams. An avid researcher of leadership and innovation principles, he continually strives to make processes leaner and more efficient.
As a Scaled Agile Framework (SAFe) 4.0 Program Consultant, Certified Scrum Professional, and Scrum Master, Bruce provides improvements in processes and project delivery for clients. He has years of daily experience in Agile project management methodologies and helped found the Memphis Agile Practitioners Group.His deep experience in technical operations management and business analysis has allowed him to manage multiple projects involving enterprise scale ecommerce  initiatives, user experience, web and mobile design, and process improvement.

 

Join the Discussion

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

Suggested Blogs

How to Earn a Scrum Education Unit® (SEU®) From the Scrum Alliance

In the world of Agile, SEUs® stands for Scrum Education Units® (SEUs®), issued by the Scrum Alliance. It marks your participation, educational experience and continued proficiency in the underlying principles and practices of Scrum, while at the same time to maintain your certification. You can earn Scrum Education Units® (SEUs®) via completing various learning opportunities or educational training.  The process to earn SEUs® is easy and it will help you stay relevant as well as competitive in the market.Why do I need to earn SEUs®?SEUs® are required to renew foundational, advanced and professional-level certifications, which include CSM®, A-CSM®, CSP-SM®, CSPO®, A-CSPO®, CSP-PO®,  CSD®, and CSP®.SEUs® follow a ratio of 1:1, which means that for every hour spent in preparation or participation, you earn one SEU®.In order to maintain your certification for two more years, you need to submit an established number of Scrum Education Units® (SEUs®) along with a renewal fee.There are six categories from which you can choose from when selecting SEUs®, which has been discussed later in the blog.The following SEU® requirements have been in effect since February 4, 2019, with no change in the renewal fee.Certification TypeCertification (2-year term)SEUs RequiredRenewal Fee Per TermFoundationalCSM®, CSPO®, CSD®20$100AdvancedA-CSM®, A-CSPO®30$175ProfessionalCSP-SM®, CSP-PO®, CSP®40$250What are the different ways to earn SEUs®?There are six categories that you can choose from while selecting SEUs®:Category I: Scrum Alliance Scrum GatheringsParticipate in Scrum Alliance Global Gatherings, Scrum Alliance Regional Gatherings, Scrum Coaching Retreats, and Scrum Alliance-Sponsored Events, and Scrum Alliance-Endorsed User Group activities and events and earn SEUs®.Per day, a maximum of 8 SEUs® can be earned.The following are a few options for Scrum Alliance Scrum Gatherings:Attending Global Scrum GatheringAttending Regional Scrum GatheringAttending Scrum Alliance user group activityAttending Scrum Coaching RetreatAttending Scrum Alliance pre-event or post-event workshopAttending Scrum Alliance-sponsored eventAttending Scrum Alliance CSP Retreat  Category II: Scrum Alliance Courses or CoachingWork with Scrum Alliance CSTs, CTCs, CECs, and REPs to earn SEUs®. You can earn a maximum of 8 SEUs® after attending a full day training.Additional SEUs® can be earned by:Acquiring continuing education in advanced Scrum topics.Attending training courses conducted by CST®, like webinars, e-learning, recorded training, face-to-face courses.Attending training courses which are provided by Scrum Alliance® Registered Education Provider (REP).Participating in small or one-on-one group coachings provided by a CEC or CTC.Note: The CSTs, CECs, CTCs, or REPs should be verified as per the Member Directory on the Scrum Alliance website.The following are a few options for Scrum Alliance Courses or Coaching:Receiving CSM trainingReceiving CSPO trainingReceiving CSD trainingReceiving training from a CST (can be video training or eLearning)Receiving training from a Scrum Alliance REPReceiving coaching conducted by a CEC or CTCCategory III: Outside EventsYou can earn SEUs® by participating in other relevant events as well, other than the ones that are sponsored by Scrum Alliance. It includes Agile conferences, training from someone who is not a CST, regional meetings, or a REP course that does not fit according to the Category II.  Unlike Category II, activities in Category III include activities and services that you are receiving rather than providing.The following are a few options for Outside Events:Receiving face-to-face training outside of Scrum AllianceReceiving coaching or mentoring outside of Scrum Alliance vAttending user group events outside of Scrum AllianceAttending Scrum/Agile events outside of Scrum AllianceCategory IV: Volunteer ServiceScrum Alliance encourages you to give back to the community.  Therefore, you can earn SEUs® by providing non-compensated professional Scrum services, that is, you will be asked if you are not compensating for your volunteer work for your employer or another party.Category V: Independent LearningYou can earn SEUs® via independent learning activities such as preparing presentations, authoring relevant books, blogs or articles; watching a training video; reading books in-depth and then describing their benefits as a Scrum practitioner.The following are a few options for Independent Learning:Preparing a Scrum presentation (not delivering)Author a book, blog or articleWatch a Scrum/Agile video by an instructor other than a Scrum Alliance CSTRead a book on Scrum/AgileOther independent learningCategory VI: Other Collaborative LearningYou can earn SEUs® via various other collaborative learning activities with other Scrum practitioners. This category might not include submissions which belong to Category B or C.The following are a few options for Collaborative Learning:Co-training with the objective of learningReceiving training via live webinar which is delivered by any trainer other than a CSTOther collaborative learningWhat is the process for submitting SEUs®  for renewal? The following is the step-by-step process for SEUs® renewal:Log into your account on the Scrum Alliance page, https://www.scrumalliance.org/login.Click on the ‘My Settings’, which can be found on the upper right-hand area of your screen.Select ‘Certification Dashboard’.Under the ‘My Credentials’, go to the grey ‘Manage SEUs®’ button.Choose your SEU® category from the ‘Enter a Scrum Education Unit’  drop-down menu.Fill in all the details of all the required fields. Note: You cannot reuse an SEU® if it has been used to submit a prior renewal of certification or CSP® application.  Also, all of the SEUs® that is being used for renewal should be earned within the past two years. 
20638
How to Earn a Scrum Education Unit® (SEU®)...

In the world of Agile, SEUs® stands for Scrum Edu... Read More

Scrum master- The Legend of Daily Scrum

Scrum is a crucial part of software development. It is designed for the teams having at least 10 individuals. The development cycle consists of two-weeks of Sprint cycle. Also, it can be called Daily Scrum. This approach can be used to scale Scrum to the larger organizations involving Large-Scale Scrums and “Scrum of Scrums”. Scrum is an incremental, step-wise agile software development. The Scrum framework provides a flexible way to the team members to work collaboratively to reach a common goal. In Daily Scrum, meetings are arranged at the same place and time each day. Ideally, this meeting is held in the morning, as it is suitable to decide the work for the day. These Daily Scrums last up to 15 minutes. Though, this discussion is brisk, it unfolds more relevant information about work.  We all know that Scrum teams are incomplete and loosely defined without the Scrum Masters. The role of the Scrum Master is fairly diversified. A good Scrum Master facilitates relays all critical aspects to the teams and has the ability to apply them depending on the situation. So you can consider Scrum Master as a facilitator between the team members. The different roles of the Scrum Master can be well identified from the following diagram.        Scrum Master as a Facilitator:  You can call Scrum Master as a facilitator. Let us see what exactly the Facilitator means! The Facilitator can be defined as- “someone who helps the individuals to understand the work, choosing implementation strategy to achieve the goals”. It can be well understood by the key elements: ●    Assisting team members in achieving their objectives, ●    Like ‘neutral’, not at particular side, ●    Supports everyone to achieve the best’ ●    Allows collaboration and interaction over the work, Participants of the Daily Scrum- ●    Product Owner ●    Team Members ●    Scrum Master It is not an obligation for the Scrum master to personally attend all the Scrum events. But Scrum Master should ensure that some of the following tasks are done: ●    The use of the Sprint should be well, to create a ‘done’, useful, releasable built. ●    There be a proper use of the Daily Scrum, to inspect the team’s progress. ●    Sprint Planning is in use to discuss, plan and agree on the deliverables which can be done on the same day. ●    Sprint Review is in use, to inspect the developed build. ●    Finally, Retrospective can be used properly to ensure continuous delivery and discuss the existing constraints. How does the Scrum Master facilitate within the Scrum Framework? Lyssa Adkins offers a good description in her book ‘Coaching Agile Teams’: “A Scrum Master should facilitate by creating a “container” for the team to fill up with their ideas and innovations. The container, often a set of agenda questions or some other lightweight (and flexible) structure, gives the team just enough of a frame to stay on their purpose and promotes and environment for richer interaction, a place where fantastic ideas can be heard. The coach creates the container; the team creates the content.” A great facilitator should be able to: ●    Facilitate the Scrum process to the team members and look for continuous improvement in the process ●    Facilitate the team in achieving their objectives towards the project ●    Listen to understand the scenario ●    Plan and govern a meeting with responsibility ●    Facilitate friendly relationship between the teams  ●    Integrate the Scrum teams ●    Help things to happen confidently In case, Scrum Master fails to remove barriers like technical issues directly himself/herself, he/she can forward this responsibility to one of the trusted team members. The majority of teams conduct Daily Scrums by playing ‘poker activity’. In this, each individual has to pick one poker card to decide the priority of work. Accordingly, the task is assigned to the teams. Facilitating for the teams require mastering the Scrum Master skills. Grabbing the skills require time, continuous analysis, practice and continuous improvement. To enable best Scrum practices in organizations, you can get certified from a reputed training institute.
Scrum master- The Legend of Daily Scrum

Scrum is a crucial part of software development. I... Read More

The Career Path of a Certified Scrum Master: Foundational & Advanced Certifications

“When business goals are constantly varying, stepping on the right career path can be a tricky and on-going target.”So, you completed your 2-days of CSM certification training and serving as a Scrum Master in the organization! What is your next career move then? Is your part done once you receive CSM certification? Or you will think about adding more boosters to level-up your Scrum career? Go through this article to know more about numerous career options available for you today! Being a Scrum Master, you need to strengthen your Scrum knowledge on a regular basis. Typically, the very first move in the career of the Scrum Master includes serving one team, so that all the issues are faced by the team members can be resolved to deliver the end result very quickly.    A great Scrum Master always look for additional challenging roles. Often, the next logical step of the Scrum Masters is to work with multiple teams and at the scaled level concurrently. A Scrum Master, who manages to work under complex conditions can make an easy transition from good to great and this gives rise to the reality that- Success is often rewarded on accepting more challenges.  Level-up your Scrum Master skills to play various challenging roles in the organizations implementing a Scrum framework. Let’s take a look at the various certifications and requirements needed to earn those certifications after CSM certification. Given below is the list of various Scrum certifications that Certified ScrumMaster can take to upskill his/her career.Advanced Certified ScrumMaster® (A-CSM®)Certified Scrum Professional®-ScrumMaster (CSP-SM)Certified Team CoachSM (CTC)Certified Scrum Trainer® (CST)Certified Enterprise Coach℠ (CEC)Certified Scrum Product Owner® (CSPO®)Certified Scrum Developer® (CSD®)ICP-ACC CertificationFoundational LevelPrerequisiteNext Career MoveCSPONoneA-CSPOCSDNoneCSPAdvanced LevelPrerequisiteNext Career MoveA-CSMActive CSMCSP-SMElevatedPrerequisiteNext Career MoveCSP-SMActive A-CSMCTC, CEC, CSTExpert/ProfessionalPrerequisiteNext Career MoveCTCActive CSP-SM, CSP-PO, or CSPCoaches the team members on ScrumCECActive CSP-SM, CSP-PO, or CSPHelp organizations to become an Agile organizationCSTActive CSP-SM, CSP-PO, or CSPTrains individuals on ScrumICP-ACCActive CSMMentors the team in Agile adoption1. Advanced Certified ScrumMaster® (A-CSM®)A-CSM certification is an immediate Scrum Master certification that can be earned just after the CSM certification. This certification will help an individual to facilitate smooth communication between the customers and the Stakeholders increasing engagement. Further, as an A-CSM certified individual, you can not only increase your Scrum implementation skills but showcase your value as a highly-skilled Agile professional to the potential employer.  Prerequisites to grab A-CSM certificationYou just need to hold an active CSM certification from Scrum Alliance and you have at least 12 months of experience working as a Scrum Master.What next after Advanced Certified ScrumMaster (A-CSM) certification?Once you have upgraded your skills with the Advanced Certified Scrum Master (A-CSM) certification, you are ready to master in Certified Scrum Professional ScrumMaster® (CSP-SM®).  2. Certified Scrum Professional®-ScrumMaster (CSP-SM):Certified Scrum Professionals always aims to improve the ways of applying Agile and Scrum principles. They exhibit their experience, knowledge earned during the Scrum training. If you are looking to elevate your Scrum career to the next level, get ready to earn Certified Scrum Professional®-ScrumMaster (CSP®-SM) certification. After attaining  CSP certification, an individual will get the following benefits:A candidate will be able to attend CSP events with other leadersAn individual will get chances to earn more and recruited by the top-giant companiesPrerequisites to grab CSP-SM certificationAn individual should hold an active Advanced Certified ScrumMasterSM (A-CSMSM ) certification from any of the Scrum Alliance approved training center. Also, he/she should have at least 24 months of work experience as a Scrum Master. What next after CSP-SM certification?CSP-SM certification is a gateway towards achieving the Certified Scrum Trainer® (CST®), Certified Enterprise Coach℠ (CEC), or Certified Team Coach℠ (CTC) certifications.3. Certified Team CoachSM (CTC):The Certified Team Coach (CTC) is a guide level certification, usually works with the management, Scrum teams, and Stakeholders. As the name says, the CTC works at the team level. Organizations hire Certified Team Coach (CTC) to train, coach, mentor, remove obstacles, and lead the team to leverage value delivery, team collaboration, and continuous development across multiple teams. Prerequisites to grab CTC certificationAn active Certified Scrum Professional certification 1,000 hours of Agile coaching experience in the last 2 years without considering your role as Scrum MasterCoaching experience in at least 2 organizations Must be actively participated in a minimum of 5 Agile eventsPractical experience of Scrum implementation and coaching experience in Agile and Scrum framework.What next after CTC certification?Certified Team Coaches (CTCs) can initiate coaching, mentoring, and training the professionals on Agile and Scrum processes once they earn CTC certification. Also, they can recommend up to 50 individuals yearly for whom they have given 25-hours of in-person training or small group training to achieve Certified ScrumMaster® and Certified Scrum Product Owner® certifications. In this way, a CTC certified can contribute to creating a healthy environment of the organizations by coaching the team members on Scrum.      4. Certified Scrum Trainer® (CST)Scrum Alliance offer only one trainer-centric certification in the form of Certified Scrum Trainer®  (CST) certification. This is the most sought-after certification and those who wish to transform the working way of the teams can be a part of this training. Prerequisites to grab CST certificationTo become a Certified Scrum Trainer (CST), you need to have:Detailed knowledge of the Scrum concepts, practices, and principlesAn active Certified Scrum Professional ScrumMaster™ (CSP-SM™) certification from Scrum AllianceHands-on experience in implementing the Scrum framework as a ScrumMaster, Product Owner, or Development team memberTeaching experience in partnership with any Certified Scrum Trainer (CST) or independently-Taught to at least 100 candidatesHosted at least 10 or more days ScrumMaster training sessions Respective certifications in order to train professionals on the courses (e.g. if want to train on CSPO, an individual should hold an active CSPO certification.  What next after CST certification?As a CST, you can teach Scrum to the students who want to work in a Scrum environment. Scrum Alliance considers CST as an active member in the Scrum community who actively takes part in the events and user groups, blogging, and in online discussions.    5. Certified Enterprise Coach℠ (CEC):The Certified Enterprise Coach (CEC) exhibits their years of experience in Scrum transformations at an enterprise level. They also show their in-depth understanding of implementing Scrum practices and principles. The CECs are skilled at Scrum (both theoretically and practically) and guide organizations during their Agile transformation journey.Prerequisites to grab CEC certificationThe individuals aspiring Certified Enterprise Coach (CEC) credential must possess:Knowledge of Scrum practices, proven leadership, and coaching skills An active CSP-SM™ or CSP-PO™ or CSP® certification Working experience in Scrum team rolesCoaching experience in at least three organizations2,000 hours over the past 3 years of work experience as a Coach.What next after CEC certification?Being a CEC certified, an individual can help organizations to become an Agile organization using the Scrum framework to transform the world of work. Also, they can recommend up to 50 individuals yearly for whom they have given 25-hours of in-person training or small group training to achieve Certified ScrumMaster® and Certified Scrum Product Owner® certifications. In this way, a CTC certified can contribute to creating a healthy environment of the organizations by coaching the team members on Scrum.   6. Certified Scrum Product Owner® (CSPO®)The Product Owner (PO) creates the product vision, prioritize the product backlog, and help the team in delivering what customers intuitively looking for. The CSPO®  is the certification for the Product Owners that will help an individual in handling the business side of the project. Prerequisites to grab CSPO® certificationThere is no prerequisite to attend  CSPO® training. However, in order to earn this certification, an individual need to attend 2-days of CSPO® course taught by Certified Scrum Trainer®  (CST). What next after CSPO® certification?After taking CSPO certification, you can go for advanced-level certification of CSPO which is an Advanced Certified Scrum Product Owner® (A-CSPO®) course from Scrum Alliance. 7. Certified Scrum Developer® (CSD®)The  CSD® certification proves that an individual has skills of building the software using Scrum as a part of the Scrum team. With CSD® , you can strengthen your technical skills in Agile software development. Prerequisites to grab CSD® certificationAny programmer (having coding knowledge) can attend CSD® course. To achieve this, an individual needs to undergo at least 5-days of the formal CSD training course by a Scrum Alliance Registered Education Provider (REP) and a Scrum Alliance Authorized Instructor. In addition to this, the CSD® certification offers the privilege to the CSM certified candidates. They can skip the first 2 days and directly join from the 3rd day of the technical training.What next after CSD® certification?After CSD® certification, an individual can level-up his/her skills with Certified Scrum Professional® for Developers (CSP- D) certification. The CSP certification help teams to constantly improve the ways of implementing Agile and Scrum practices and principles.   8. ICAgile Certified Professional in Agile Coaching (ICP-ACC) CertificationICP-ACC certification in Agile Coaching certification aims to achieve an Agile mindset. After this certification, an individual can easily be able to differentiate between the facilitation, mentoring, professional coaching and teaching and will get to learn the skills like team collaboration and conflict resolution to form a healthy organizational environment.Prerequisites to grab ICP-ACC certificationAn individual with CSM certification and 2-3 years of working experience as a Scrum Master, is eligible to achieve ICP-ACC certification training. What next after ICP ACC certification?Being a certified Agile Coach, you can play the role of the mentor to the Agile team by facilitating Agile practices and empowering teams to reach their goals. More specifically, an Agile Coach can is a guide to the team members who help the team in Agile adoption. Career Roles of a Scrum MasterThe Scrum Master is the heart of the Scrum process who plays a diverse set of roles in the team. Let's have a glimpse of the various roles that Scrum Master can play after the CSM certification:Agile CoachProduct OwnerManager SAFe Scrum MasterConcluding ThoughtsThe Scrum Master role should not be an end itself. There is always a scope of consistent improvement. So, for all the Scrum Masters, ‘What’s your next career path?’ Being a Scrum Master, try not to keep yourself restricted to limited skills. Try to advance your Scrum skills always by taking more advanced Scrum certifications.    So, are you ready to take the plunge with other advanced Scrum certifications after earning CSM certification?  
15041
The Career Path of a Certified Scrum Master: Found...

“When business goals are constantly varying, ste... Read More

Useful links