Search

How SAFe®️ Core Values Quicken The Progress Of An Agile Team

What is Scaled Agile Framework (SAFe®️)?The Scaled Agile Framework (SAFe®️) helps businesses address the significant challenges of developing and delivering enterprise-class software and systems in the shortest sustainable lead time. It is an online, freely revealed knowledge base of proven success patterns for implementing Lean-Agile software and systems at enterprise scale.Developed in the field, SAFe®️  draws from three primary bodies of knowledge: Agile development, systems thinking, and Lean product development. It synchronizes alignment, collaboration, and delivery for large numbers of Agile teams. Scalable and configurable, SAFe®️ allows each organization to adapt it to its own business needs. It supports smaller-scale solutions employing 50–125 practitioners, as well as complex systems that require thousands of people. Why use  SAFe®️ ?SAFe®️ combines the power of Agile with systems thinking and Lean product development. It synchronizes alignment, collaboration, and delivery for multiple Agile teams. As a result,  SAFe®️ provides dramatic improvements to business agility, including productivity, time to market, quality, and employee engagement, and more.SAFe®️ is improving business outcomes for companies of all sizes across the world. It has produced dramatic increases in time to market, employee engagement, higher quality, higher customer satisfaction, and overall improved economic outcomes. It also helps create cultures that are more productive, rewarding, and fun.QualityBuilt-In Quality practices increase customer satisfaction and provide faster and more predictable value delivery. They also improve the ability to innovate. Without quality, the Lean goal of the maximum value in the shortest sustainable lead time cannot be achieved. ProductivityWhen productivity increases, system development economics improves, as does employee engagement. For team members, productivity is a critical, personal need. Everyone feels better when they’re contributing more and doing less wasteful work.Employee EngagementAccording to the Society of Human Resource Management (SHRM), employees with the highest level of commitment perform 21 percent better and are 65 percent less likely to leave the organization. Clearly, employee engagement is directly linked to business performance.Faster Time to MarketLean-Agile frameworks allow businesses to deliver value to the market more quickly. Companies that adopt Agile development practices routinely gain first-mover advantages and enjoy the higher gross margins afforded to market leaders. SAFe®️ enterprises typically see a 30–75 percent (as much as 3x!) improvement in time to market.SAFe®️ configurationsSAFe®️ supports the full range of development environments with four out-the-box configurationsEssential SAFe®️Portfolio SAFe®️Large Solution SAFe®️Full SAFe®️Essential SAFe®️The Essential SAFe®️ configuration is the heart of the Framework and is the simplest starting point for implementation. It’s the basic building block for all other SAFe®️ configurations and describes the most critical elements needed to realize the majority of the Framework’s benefits.  Together, the Team and Program Levels form an organizational structure called the Agile Release Train (ART), where Agile teams, key stakeholders, and other resources are dedicated to an important, ongoing solution mission.Large Solution SAFe®️The Large Solution SAFe®️ configuration is for developing the largest and most complex solutions that typically require multiple Agile release trains and Suppliers, but do not require portfolio-level considerations. The Solution Train organizational construct of the Large Solution Level helps enterprises that face the biggest challenges—building large-scale, multidisciplinary software, hardware, and complex IT systems. Building these solutions requires additional roles, artifacts, events, and coordination. Portfolio SAFe®️The Portfolio SAFe®️ configuration helps align portfolio execution to the enterprise strategy, by organizing Agile development around the flow of value, through one or more value streams. It provides business agility through principles and practices for portfolio strategy and investment funding, Agile portfolio operations, and Lean governance. Full SAFe®️The Full SAFe®️ configuration is the most comprehensive version of the Framework. It supports enterprises that build and maintain large integrated solutions, which require hundreds of people or more and includes all levels of SAFe®️: team, program, large solution, and portfolio. In the largest enterprises, multiple instances of various SAFe®️ configurations may be required. Scaled agile framework core values  - SAFe®️  SAFe®️ is broad and deep and based on both Lean and Agile principles as its foundation.Importance of core valuesCore values are the fundamental beliefs of a person or organization.The core values are the guiding principles that speak behavior and action.Core values can help people to know what is right from wrong.It helps companies to determine whether they are working on the right path or not.SAFe®️ upholds four Core Values: alignment, built-in quality, transparency, and program execution, as illustrated in Figure below and described in the following sections.1. AlignmentAlignment ensures that many people act as one unit or team, all pulling in the same direction. Alignment in SAFe®️ is achieved when everyone in the portfolio, and every team member on every ART, understand the strategy and the part they play in achieving it.SAFe®️ delivers alignment by orchestrating strategic themes, vision, roadmap, and PI planning. Economic prioritization and the visible flow of work through the various Kanban systems and backlogs provide visibility and transparency.2.Built-in QualityBuilt-in quality is one of the important core values of SAFe®️. The enterprise’s ability to deliver new functionality with the fastest sustainable lead time and to be able to react to rapidly changing business environments is dependent on solution quality. But built-in quality is not unique to SAFe®️. Rather, it is a core principle of the Lean-Agile mindset, where it helps avoid the cost of delays associated with recall, rework, and defect fixing. The Agile Manifesto is focused on quality as well: “Continuous attention to technical excellence and good design enhances agility.”The following sections summarize recommended practices for achieving built-in quality.SoftwareSAFe®️’s software quality practices—many of which are inspired by Extreme Programming (XP)— help Agile software teams ensure that the solutions they build are high quality and adaptable to change. The collaborative nature of these practices, along with a focus on frequent validation, creates an emergent culture in which engineering and craftsmanship are key business enablers. Test-Driven DevelopmentTest-Driven Development (TDD) is a philosophy and practice that recommends building and executing tests before implementing the code or a component of a system. By validating them against a series of agreed-to tests, TDD—an Agile Testing practice—improves system outcomes by assuring that the system implementation meets its requirements. TDD, along with Behavior-Driven Development (BDD), is part of the ‘test-first’ approach to Build Quality into development. Writing tests first creates a more balanced testing portfolio with many fast, automated development tests and fewer slow, manual, end-to-end tests. Acceptance Test Driven DevelopmentAcceptance Test Driven Development (ATDD) is a practice in which the whole team collaboratively discusses acceptance criteria, with examples, and then distills them into a set of concrete acceptance tests before development begins. It’s the best way to ensure that all have the same shared understanding of what it is we are building. It’s also the best way to ensure we have a shared definition of Done.Behavior-Driven DevelopmentBehavior Driven Development (BDD) is a Test-First, Agile Testing practice that provides Built-In Quality by defining (and potentially automating) tests before, or as part of, specifying system behavior. BDD is a collaborative process that creates a shared understanding of requirements between the business and the Development Team. Its goal is to help guide development, decrease rework, and increase flow. Without focusing on internal implementation, BDD tests are business-facing scenarios that attempt to describe the behavior of a Story, Feature, or Capability from a user’s perspective. When automated, these tests ensure that the system continuously meets the specified behavior even as the system evolves. That, in turn, enables Release on Demand. Automated BDD tests can also serve as the definitive statement regarding the as-built system behavior, replacing other forms of behavioral specifications.Continuous IntegrationThis is the practice of merging the code from each developer’s workspace into a single main branch of code, multiple times per day. This lessens the risk of deferred integration issues and their impact on system quality and program predictability. Teams perform local integration at least daily. But to confirm that the work is progressing as intended, full system-level integration should be achieved at least one or two times per iteration.RefactoringRefactoring is “a disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior.” A key enabler of emergent design, refactoring is essential to Agile. To maintain system robustness, teams continuously refactor code in a series of small steps, providing a solid foundation for future development.Pair WorkSome teams follow pair programming, but that may be too extreme for many. More generally, pair work may couple developers and testers on a story. Still, others prefer more spontaneous pairing, with developers collaborating for critical code segments, refactoring of legacy code, development of interface definition, and system-level integration challenges.HardwareHardware quality is supported by exploratory early iterations, frequent system-level integration, design verification, modeling, and set-based design. The Agile architecture supports software and hardware quality.1.System IntegrationDifferent components and subsystems—software, firmware, hardware, and everything else—must collaborate to provide effective solution-level behaviors. Practices that support solution-level quality include:Frequent system and solution-level integrationSolution-level testing of functional and Nonfunctional RequirementsSystem and Solution Demos2.ComplianceSAFe®️ enterprises that build high assurance systems define their approved practices, policies, and procedures in a Lean Quality Management System (QMS). These systems are intended to ensure that development activities and outcomes comply with all relevant regulations and quality standards, as well as providing the required documentation to prove it.3.TransparencyTransparency builds trust. Trust, in turn, is essential for performance, innovation, risk-taking, and relentless improvement. Trust exists when the business and development can confidently rely on another to act with integrity, particularly in times of difficulty. Without trust no one can build high-performance teams and programs, nor build (or rebuild) the confidence needed to make and meet reasonable commitments.  And without trust, working environments are a lot less fun and motivating.Here are few SAFe®️ practices which enable trust:ARTs have visibility into the team’s backlogs, as well as other Program Backlogs.Teams and programs commit to short-term, visible commitments that they routinely meet4. Program ExecutionSAFe®️ places an intense focus on working systems and business outcomes. History shows us that while many enterprises start the transformation with individual Agile teams, they often become frustrated as even those teams struggle to deliver more substantial amounts of solution value, reliably and efficiently. That is the purpose of the ART, and that is why SAFe®️ focuses implementation initially at the Program Level. In turn, the ability of Value Streams to deliver value depends on the ability of the ARTs and Solution Trains.ConclusionThe four Core Values of alignment, built-in quality, transparency, and program execution represent the fundamental beliefs that are key to SAFe®️ effectiveness. These guiding principles help dictate behavior and action for everyone who participates in a SAFe®️ portfolio. Successful teams and programs implementing  SAFe®️ have aligned their organizations along these core values and getting many benefits—employee engagement, productivity, quality, and time to market. 

How SAFe®️ Core Values Quicken The Progress Of An Agile Team

5K
How SAFe®️ Core Values Quicken The Progress Of An Agile Team

What is Scaled Agile Framework (SAFe®️)?

The Scaled Agile Framework (SAFe®️) helps businesses address the significant challenges of developing and delivering enterprise-class software and systems in the shortest sustainable lead time. It is an online, freely revealed knowledge base of proven success patterns for implementing Lean-Agile software and systems at enterprise scale.

Developed in the field, SAFe®️  draws from three primary bodies of knowledge: Agile development, systems thinking, and Lean product development. It synchronizes alignment, collaboration, and delivery for large numbers of Agile teams. Scalable and configurable, SAFe®️ allows each organization to adapt it to its own business needs. It supports smaller-scale solutions employing 50–125 practitioners, as well as complex systems that require thousands of people.

 Why use  SAFe®️ ?

SAFe®️ combines the power of Agile with systems thinking and Lean product development. It synchronizes alignment, collaboration, and delivery for multiple Agile teams. As a result,  SAFe®️ provides dramatic improvements to business agility, including productivity, time to market, quality, and employee engagement, and more.

SAFe®️ is improving business outcomes for companies of all sizes across the world. It has produced dramatic increases in time to market, employee engagement, higher quality, higher customer satisfaction, and overall improved economic outcomes. It also helps create cultures that are more productive, rewarding, and fun.

SAFe®️  Benefits

Quality

Built-In Quality practices increase customer satisfaction and provide faster and more predictable value delivery. They also improve the ability to innovate. Without quality, the Lean goal of the maximum value in the shortest sustainable lead time cannot be achieved. 

Productivity

When productivity increases, system development economics improves, as does employee engagement. For team members, productivity is a critical, personal need. Everyone feels better when they’re contributing more and doing less wasteful work.

Employee Engagement

According to the Society of Human Resource Management (SHRM), employees with the highest level of commitment perform 21 percent better and are 65 percent less likely to leave the organization. Clearly, employee engagement is directly linked to business performance.

Faster Time to Market

Lean-Agile frameworks allow businesses to deliver value to the market more quickly. Companies that adopt Agile development practices routinely gain first-mover advantages and enjoy the higher gross margins afforded to market leaders. SAFe®️ enterprises typically see a 30–75 percent (as much as 3x!) improvement in time to market.

SAFe®️ configurations

SAFe®️ supports the full range of development environments with four out-the-box configurations

  • Essential SAFe®️
  • Portfolio SAFe®️
  • Large Solution SAFe®️
  • Full SAFe®️

Essential SAFe®️

The Essential SAFe®️ configuration is the heart of the Framework and is the simplest starting point for implementation. It’s the basic building block for all other SAFe®️ configurations and describes the most critical elements needed to realize the majority of the Framework’s benefits.  Together, the Team and Program Levels form an organizational structure called the Agile Release Train (ART), where Agile teams, key stakeholders, and other resources are dedicated to an important, ongoing solution mission.

Large Solution SAFe®️

The Large Solution SAFe®️ configuration is for developing the largest and most complex solutions that typically require multiple Agile release trains and Suppliers, but do not require portfolio-level considerations. The Solution Train organizational construct of the Large Solution Level helps enterprises that face the biggest challenges—building large-scale, multidisciplinary software, hardware, and complex IT systems. Building these solutions requires additional roles, artifacts, events, and coordination. 

Portfolio SAFe®️

The Portfolio SAFe®️ configuration helps align portfolio execution to the enterprise strategy, by organizing Agile development around the flow of value, through one or more value streams. It provides business agility through principles and practices for portfolio strategy and investment funding, Agile portfolio operations, and Lean governance. 

Full SAFe®️

The Full SAFe®️ configuration is the most comprehensive version of the Framework. It supports enterprises that build and maintain large integrated solutions, which require hundreds of people or more and includes all levels of SAFe®️: team, program, large solution, and portfolio. In the largest enterprises, multiple instances of various SAFe®️ configurations may be required. 

Scaled agile framework core values  - SAFe®️ 

 SAFe®️ is broad and deep and based on both Lean and Agile principles as its foundation.

Importance of core values

  • Core values are the fundamental beliefs of a person or organization.
  • The core values are the guiding principles that speak behavior and action.
  • Core values can help people to know what is right from wrong.
  • It helps companies to determine whether they are working on the right path or not.

SAFe®️ upholds four Core Values: alignment, built-in quality, transparency, and program execution, as illustrated in Figure below and described in the following sections.
Scaled agile framework core values

1. Alignment

Alignment ensures that many people act as one unit or team, all pulling in the same direction. Alignment in SAFe®️ is achieved when everyone in the portfolio, and every team member on every ART, understand the strategy and the part they play in achieving it.

SAFe®️ delivers alignment by orchestrating strategic themes, vision, roadmap, and PI planning. Economic prioritization and the visible flow of work through the various Kanban systems and backlogs provide visibility and transparency.

2.Built-in Quality

Built-in quality is one of the important core values of SAFe®️. The enterprise’s ability to deliver new functionality with the fastest sustainable lead time and to be able to react to rapidly changing business environments is dependent on solution quality. But built-in quality is not unique to SAFe®️. Rather, it is a core principle of the Lean-Agile mindset, where it helps avoid the cost of delays associated with recall, rework, and defect fixing. The Agile Manifesto is focused on quality as well:

 “Continuous attention to technical excellence and good design enhances agility.”

The following sections summarize recommended practices for achieving built-in quality.

Software

  • SAFe®️’s software quality practices—many of which are inspired by Extreme Programming (XP)— help Agile software teams ensure that the solutions they build are high quality and adaptable to change. The collaborative nature of these practices, along with a focus on frequent validation, creates an emergent culture in which engineering and craftsmanship are key business enablers.
  •  Test-Driven Development

    Test-Driven Development (TDD) is a philosophy and practice that recommends building and executing tests before implementing the code or a component of a system. By validating them against a series of agreed-to tests, TDD—an Agile Testing practice—improves system outcomes by assuring that the system implementation meets its requirements. TDD, along with Behavior-Driven Development (BDD), is part of the ‘test-first’ approach to Build Quality into development. Writing tests first creates a more balanced testing portfolio with many fast, automated development tests and fewer slow, manual, end-to-end tests.
  •  Acceptance Test Driven Development

    Acceptance Test Driven Development (ATDD) is a practice in which the whole team collaboratively discusses acceptance criteria, with examples, and then distills them into a set of concrete acceptance tests before development begins. It’s the best way to ensure that all have the same shared understanding of what it is we are building. It’s also the best way to ensure we have a shared definition of Done.
  • Behavior-Driven Development

    Behavior Driven Development (BDD) is a Test-First, Agile Testing practice that provides Built-In Quality by defining (and potentially automating) tests before, or as part of, specifying system behavior.
     
    BDD is a collaborative process that creates a shared understanding of requirements between the business and the Development Team. Its goal is to help guide development, decrease rework, and increase flow. Without focusing on internal implementation, BDD tests are business-facing scenarios that attempt to describe the behavior of a Story, Feature, or Capability from a user’s perspective. When automated, these tests ensure that the system continuously meets the specified behavior even as the system evolves. That, in turn, enables Release on Demand.
     
    Automated BDD tests can also serve as the definitive statement regarding the as-built system behavior, replacing other forms of behavioral specifications.
  • Continuous Integration

    This is the practice of merging the code from each developer’s workspace into a single main branch of code, multiple times per day. This lessens the risk of deferred integration issues and their impact on system quality and program predictability. Teams perform local integration at least daily. But to confirm that the work is progressing as intended, full system-level integration should be achieved at least one or two times per iteration.
  • Refactoring

    Refactoring is “a disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior.” A key enabler of emergent design, refactoring is essential to Agile. To maintain system robustness, teams continuously refactor code in a series of small steps, providing a solid foundation for future development.
  • Pair Work

    Some teams follow pair programming, but that may be too extreme for many. More generally, pair work may couple developers and testers on a story. Still, others prefer more spontaneous pairing, with developers collaborating for critical code segments, refactoring of legacy code, development of interface definition, and system-level integration challenges.

Hardware

Hardware quality is supported by exploratory early iterations, frequent system-level integration, design verification, modeling, and set-based design. The Agile architecture supports software and hardware quality.

1.System Integration

Different components and subsystems—software, firmware, hardware, and everything else—must collaborate to provide effective solution-level behaviors. Practices that support solution-level quality include:

  • Frequent system and solution-level integration
  • Solution-level testing of functional and Nonfunctional Requirements
  • System and Solution Demos

2.Compliance

SAFe®️ enterprises that build high assurance systems define their approved practices, policies, and procedures in a Lean Quality Management System (QMS). These systems are intended to ensure that development activities and outcomes comply with all relevant regulations and quality standards, as well as providing the required documentation to prove it.

3.Transparency

Transparency builds trust. Trust, in turn, is essential for performance, innovation, risk-taking, and relentless improvement. Trust exists when the business and development can confidently rely on another to act with integrity, particularly in times of difficulty. Without trust no one can build high-performance teams and programs, nor build (or rebuild) the confidence needed to make and meet reasonable commitments.  And without trust, working environments are a lot less fun and motivating.

Here are few SAFe®️ practices which enable trust:

  • ARTs have visibility into the team’s backlogs, as well as other Program Backlogs.
  • Teams and programs commit to short-term, visible commitments that they routinely meet

4. Program Execution

SAFe®️ places an intense focus on working systems and business outcomes. History shows us that while many enterprises start the transformation with individual Agile teams, they often become frustrated as even those teams struggle to deliver more substantial amounts of solution value, reliably and efficiently. That is the purpose of the ART, and that is why SAFe®️ focuses implementation initially at the Program Level. In turn, the ability of Value Streams to deliver value depends on the ability of the ARTs and Solution Trains.

Conclusion

The four Core Values of alignment, built-in quality, transparency, and program execution represent the fundamental beliefs that are key to SAFe®️ effectiveness. These guiding principles help dictate behavior and action for everyone who participates in a SAFe®️ portfolio. Successful teams and programs implementing  SAFe®️ have aligned their organizations along these core values and getting many benefits—employee engagement, productivity, quality, and time to market.

 



Mukundan

Mukundan Bashyam

Program/Project Manager

Mukundan Bashyam has more than 15 years of IT experience working in different roles such as Agile Coach, Scrum Master, and Product Owner. He is a certified Project Management Professional (PMP), Certified Scrum Master(CSM) and Certified Agile Coach from ICAgile. He is an accomplished Agile trainer for many organizations and a contributing author for KnowledgeHut. Mukundan has a Bachelor’s degree from Indian Institute of Technology (BHU)-Varanasi and a Master’s degree in Industrial Management from National Institute of Industrial Engineering (NITIE), Mumbai. He has worked with startups and large companies like Hewlett Packard(HP), Target Corporation India, Diageo, and Robert Bosch.  

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?  
15042
The Career Path of a Certified Scrum Master: Found...

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

Useful links