Search

What Are the 4 Core Values of Safe

The foundation of SAFe is its 4 core values and it is important to understand these before  jumping into the concepts of SAFe. So, what is SAFe? SAFe is a model for scaling Agile.Agile development is based on iterative and incremental development, in which requirements and solutions evolve through team collaboration. It recommends a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a theoretical framework and does not specify any particular practice that a development team should follow. Agile uses short iterations of 1 to 4 weeks so that the development process is aligned with the changing business needs. Instead of a single-pass development of 6 to 18 months where all the requirements and risks are predicted upfront, Agile adopts a process of frequent feedback where a workable product is delivered after 1 to 4-weeks of iteration.SAFe is particularly well-suited for complex projects that involve multiple large teams at the project, program, and portfolio levels. It enables larger organizations to manage projects with a higher degree of agility, and helps in getting feedback faster from multiple stakeholders across the globe. This accelerated feedback loop leads to higher engagement levels, increased productivity and improved work quality.Core Values of SAFe® Model:-  SAFe has defined 4 core values as part of their framework, which are as follows: Alignment- alignment means that the whole organization has a clear vision of where it’s going, and how it’s working to reach that goal. The whole company has a clear destination, and purposefully moves toward that destination. When a company is misaligned, on the other hand, it’s unlikely to reach its destination, even if it thinks it knows where it’s going. What’s worse is that an organization lacking in alignment doesn’t respond well to changes in direction. In any organization multiple teams contribute to a program to ensure that all the people in the team act as one and are moving in the same direction. Alignment means that the strategic themes and product backlogs are aligned with the vision, roadmap, and backlogs.  Built-in Quality- Built-in quality also means that each team views quality as an enabler of speed and ensures that every product increment reflects the best quality standards. Quality is not added later but rather it’s built in. Transparency- The main reason transparency is crucial is because it makes organizations more robust and resistant to failures. When things go wrong, trust and openness of information make troubleshooting and fixing problems easier. Transparency is an essential ingredient of a healthy organization. This is because it leads to healthy relationships based on trust, which makes for happier and more productive team members. Program execution- Program execution is at the heart of SAFe. Since multiple teams work and integrate a product, SAFe places intense focus on working systems and business outcomes.Flow- Flow can be achieved by test first and continuous delivery pipeline. Agile teams carry out tests at every stage; from the feature, user stories and the code. Right from the time the item was created, testing is done for both functional and non-functional requirements. In order to ensure faster delivery, the team automates the scripts and executes them, ensuring that the test will run faster.  This also helps in continuous delivery pipeline, which means releasing the product much faster and providing the ability to release on demand. Architecture & Design quality- A well designed system’s architecture determines how well the current system supports the current and future business and also helps in making future requirements easier to implement and deliver. While designing, it is always good to apply good coupling/cohesion and with appropriate abstraction/encapsulation which helps in making implementations easier to understand and modify for future requirements. Always ensure that the system must be flexible enough to easily support new requirements. An effective usage of Design Patterns helps in well-known ways to support these principles and provide a common language to ease understanding and readability. It’s advised to explore multiple solutions to arrive at the best design choice, and not just go with the first choice. Code quality- We will achieve code quality by following the below practices: Unit Testing, where developers write test cases by breaking the code into several smaller parts and execute those parts as automated test cases, which in turn help the developer write the code in an effective manner and provide better built-in quality deliverables.  Pair Programming, where 2 developers work on the same station and on the same user story. One will write the code and the other will be the reviewer providing real time feedback. This helps the developers to think about the problems in a broader perspective, even including some unknown edge cases which may come in. This helps in effective built-in quality deliverables.  Coding Standards – Collective ownership should be there with the team for the work that is being delivered. This will reduce the inter dependencies within the team and help individuals add functionality, fix any errors, refactor the code and improve the design. Always following the standard coding standards helps in consistent deliverables. System quality- Design and coding ensures that the underlying system and its artifacts, and the system/product quality are as they should be with no surprises and everyone agrees that the delivered system/product is working as expected producing the desired results and the business value. Release quality- As an organization we must focus on release on demand. Focus should be on the new functionality that is incrementally released for production based on customer demand. Always target smaller/incremental changes for production, which ensures faster, frequent and defect free / riskless release.Transparency - As per SAFe it is best to ensure open communication across all levels of the team. Right from the top to the bottom of the team, there should be clear and open communications about the road map. This can be done by providing PI objectives and ensuring access to everyone on the Jira, Kanban boards, backlogs and to new upcoming initiatives.Program execution- SAFe focuses on working systems and business outcomes and ensures that teams deliver more substantial amounts of solution value, reliably and efficiently. Things always go wrong and do not work out as planned. There must be openness within the team/organization. To ensure openness, trust is required, and trust only exists when the business and development can confidently rely on another to act with integrity, particularly in times of difficulty. Without trust we cannot build high-performance teams or programs. Again, the core value of program execution is key for a successful SAFe implementation. Yes, aligning, checking quality and being transparent cannot be possible as the team cannot execute and deliver the value constantly. An Overview of its Core Values, Principles, Implementation & Program execution:The four Core Values of alignment, built-in quality, transparency, and program execution represent the fundamental key beliefs of SAFe effectiveness.  SAFe provides guiding principles and helps in directive behaviour and action for everyone who participates in  SAFe. Successful teams and programs who implemented SAFe had aligned their organizations along these core values and gained many benefits including employee engagement, productivity, quality, and time to market. How SAFe Core Values stabilize and accelerate the progress of agile teams:SAFe Core Values are responsible for ordering the behaviour and action of an organization working in a SAFe portfolio. Determining core values of an organization is an essential part of its success. Adhering to these values makes the path to accomplishing your business objectives consistent and creates a unified thriving culture.SAFe is essential for Agile Teams and it should be incorporated to help achieve our business goals as it encourages quick adaptability to changes in technology and economic conditions. SAFe promotes collaboration and transparency between the development and the top management with an active interaction between the development team from top to bottom and ensures we attain business value within sustainable time.Regardless of the size of the enterprise, SAFe allows scalability and configurability that suits our business needs, and helps in focusing on delivering working software after every two weeks. Agile Release Train (ART) brings together multiple agile teams on a consistent routine every 8-12 weeks in what is known as a Program Increment (PI). Planning cadence based sessions where agile teams come together to define the goals they wish to achieve is next fixed and time bound. PI planning is a face to face, collaborative, interactive and innovative session that builds team spirit and synergy and promotes the sharing of strategy, common vision and architecture amongst development and the managerial teams.Continuous integration and validation among the teams and constant feedback from customers helps maintain a successful business relationship leaving room for improvement throughout the entire process; which in turn provides significant improvement in business productivity, quality, employee engagement and time to market. Conclusion:SAFe Core Values are responsible for ordering the behaviour and action of an organization working in a SAFe portfolio. Determining core values of an organization is an essential part of its success. SAFe is an industry-proven, value-focused method for scaling Agile at the Enterprise level. SAFe helps teams in large organizations to meet the organization's strategic goals, not just individual project goals.The framework offers the ability to maintain and create a centralized strategy to deliver value. The SAFe model has four levels that centralize the strategic themes of an organization. Centralized strategy is combined with the decentralized agile development execution. Adhering to these values makes the path to accomplishing your business objectives consistent and creates a unified thriving culture for all participants. 

What Are the 4 Core Values of Safe

8K
What Are the 4 Core Values of Safe

The foundation of SAFe is its 4 core values and it is important to understand these before  jumping into the concepts of SAFe. So, what is SAFeSAFe is a model for scaling Agile.

Agile development is based on iterative and incremental development, in which requirements and solutions evolve through team collaboration. It recommends a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a theoretical framework and does not specify any particular practice that a development team should follow. 

Agile uses short iterations of 1 to 4 weeks so that the development process is aligned with the changing business needs. Instead of a single-pass development of 6 to 18 months where all the requirements and risks are predicted upfront, Agile adopts a process of frequent feedback where a workable product is delivered after 1 to 4-weeks of iteration.

SAFe is particularly well-suited for complex projects that involve multiple large teams at the project, program, and portfolio levels. It enables larger organizations to manage projects with a higher degree of agility, and helps in getting feedback faster from multiple stakeholders across the globe. This accelerated feedback loop leads to higher engagement levels, increased productivity and improved work quality.Core Values of SAFe® Model

Core Values of SAFe®Model:-  SAFe has defined 4 core values as part of their framework, which are as follows: 

  • Alignment- alignment means that the whole organization has a clear vision of where it’s going, and how it’s working to reach that goal. The whole company has a clear destination, and purposefully moves toward that destination. When a company is misaligned, on the other hand, it’s unlikely to reach its destination, even if it thinks it knows where it’s going. What’s worse is that an organization lacking in alignment doesn’t respond well to changes in direction. In any organization multiple teams contribute to a program to ensure that all the people in the team act as one and are moving in the same direction. Alignment means that the strategic themes and product backlogs are aligned with the vision, roadmap, and backlogs.  
  • Built-in Quality- Built-in quality also means that each team views quality as an enabler of speed and ensures that every product increment reflects the best quality standards. Quality is not added later but rather it’s built in. 
  • Transparency- The main reason transparency is crucial is because it makes organizations more robust and resistant to failures. When things go wrong, trust and openness of information make troubleshooting and fixing problems easier. Transparency is an essential ingredient of a healthy organization. This is because it leads to healthy relationships based on trust, which makes for happier and more productive team members. 
  • Program execution- Program execution is at the heart of SAFe. Since multiple teams work and integrate a product, SAFe places intense focus on working systems and business outcomes.
  • Flow- Flow can be achieved by test first and continuous delivery pipelineAgile teams carry out tests at every stage; from the feature, user stories and the code. Right from the time the item was created, testing is done for both functional and non-functional requirements. In order to ensure faster delivery, the team automates the scripts and executes them, ensuring that the test will run faster.  

This also helps in continuous delivery pipeline, which means releasing the product much faster and providing the ability to release on demand. 

  • Architecture & Design quality- A well designed system’s architecture determines how well the current system supports the current and future business and also helps in making future requirements easier to implement and deliver. While designing, it is always good to apply good coupling/cohesion and with appropriate abstraction/encapsulation which helps in making implementations easier to understand and modify for future requirementsAlways ensure that the system must be flexible enough to easily support new requirements. An effective usage of Design Patterns helps in well-known ways to support these principles and provide a common language to ease understanding and readabilityIt’s advised to explore multiple solutions to arrive at the best design choice, and not just go with the first choice. 
  • Code quality- We will achieve code quality by following the below practices: 
    • Unit Testing, where developers write test cases by breaking the code into several smaller parts and execute those parts as automated test cases, which in turn help the developer write the code in an effective manner and provide better built-in quality deliverables. 
    •  Pair Programming, where 2 developers work on the same station and on the same user story. One will write the code and the other will be the reviewer providing real time feedback. This helps the developers to think about the problems in broader perspective, even including some unknown edge cases which may come in. This helps in effective built-in quality deliverables. 
    •  Coding Standards  Collective ownership should be there with the team for the work that is being delivered. This will reduce the inter dependencies within the team and help individuals add functionality, fix any errors, refactor the code and improve the design. Always following the standard coding standards helps in consistent deliverables. 
  • System quality- Design and coding ensures that the underlying system and its artifacts, and the system/product quality are as they should be with no surprises and everyone agrees that the delivered system/product is working as expected producing the desired results and the business value. 
  • Release quality- As an organization we must focus on release on demand. Focus should be on the new functionality that is incrementally released for production based on customer demand. Always target smaller/incremental changes for production, which ensures faster, frequent and defect free / riskless release.
  • Transparency - As per SAFe it is best to ensure open communication across all levels of the team. Right from the top to the bottom of the team, there should be clear and open communications about the road map. This can be done by providing PI objectives and ensuring access to everyone on the Jira, Kanban boards, backlogs and to new upcoming initiatives.
  • Program executionSAFe focuses on working systems and business outcomes and ensures that teams deliver more substantial amounts of solution value, reliably and efficiently. Things always go wrong and do not work out as planned. There must be openness within the team/organization. To ensure openness, trust is required, and trust only exists when the business and development can confidently rely on another to act with integrity, particularly in times of difficulty. Without trust we cannot build high-performance teams or programs. Again, the core value of program execution is key for a successful SAFe implementation. Yes, aligning, checking quality and being transparent cannot be possible as the team cannot execute and deliver the value constantly. 

An Overview of its Core Values, Principles, Implementation & Program execution:

The four Core Values of alignment, built-in quality, transparency, and program execution represent the fundamental key beliefs of SAFe effectiveness.  SAFe provides guiding principles and helps in directive behaviour and action for everyone who participates in  SAFe. Successful teams and programs who implemented SAFe had aligned their organizations along these core values and gained many benefits including employee engagement, productivity, quality, and time to market. 

How SAFe Core Values stabilize and accelerate the progress of agile teams:

SAFe Core Values are responsible for ordering the behaviour and action of an organization working in a SAFe portfolio. Determining core values of an organization is an essential part of its success. Adhering to these values makes the path to accomplishing your business objectives consistent and creates a unified thriving culture.

SAFe is essential for Agile Teams and it should be incorporated to help achieve our business goals as it encourages quick adaptability to changes in technology and economic conditionsSAFe promotes collaboration and transparency between the development and the top management with an active interaction between the development team from top to bottom and ensures we attain business value within sustainable time.

Regardless of the size of the enterprise, SAFe allows scalability and configurability that suits our business needs, and helps in focusing on delivering working software after every two weeksAgile Release Train (ART) brings together multiple agile teams on a consistent routine every 8-12 weeks in what is known as a Program Increment (PI). Planning cadence based sessions where agile teams come together to define the goals they wish to achieve is next fixed and time bound. PI planning is a face to face, collaborative, interactive and innovative session that builds team spirit and synergy and promotes the sharing of strategy, common vision and architecture amongst development and the managerial teams.

Continuous integration and validation among the teams and constant feedback from customers helps maintain a successful business relationship leaving room for improvement throughout the entire process; which in turn provides significant improvement in business productivity, quality, employee engagement and time to market. 

Conclusion:

SAFe Core Values are responsible for ordering the behaviour and action of an organization working in a SAFe portfolio. Determining core values of an organization is an essential part of its success. SAFe is an industry-proven, value-focused method for scaling Agile at the Enterprise level. SAFe helps teams in large organizations to meet the organization's strategic goals, not just individual project goals.

The framework offers the ability to maintain and create a centralized strategy to deliver value. The SAFe model has four levels that centralize the strategic themes of an organization. Centralized strategy is combined with the decentralized agile development execution. Adhering to these values makes the path to accomplishing your business objectives consistent and creates a unified thriving culture for all participants. 

KnowledgeHut

KnowledgeHut

Author

KnowledgeHut is an outcome-focused global ed-tech company. We help organizations and professionals unlock excellence through skills development. We offer training solutions under the people and process, data science, full-stack development, cybersecurity, future technologies and digital transformation verticals.
Website : https://www.knowledgehut.com

Join the Discussion

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

Suggested Blogs

What is a Scrum Master - Everything You Need to Know

What is a Scrum Master?A deep understanding of Scrum roles is critical to implementing Scrum.Many times, this gets widely overlooked when organizations adopt Scrum for the first time. Even before Scrum can be useful for any team, a clear perception of “what is a Scrum Master” is important.Simply put, a Scrum Master is the coach and facilitator of a Scrum team. The Scrum guide describes Scrum Master as a person chiefly responsible for promoting and supporting Scrum. As rightly stated in the guide, a Scrum Master helps everyone understand the Scrum theory, practices, rules, and values. A converter of “doing Agile” to “being Agile” is what defines a Scrum Master. Essentially, a Scrum Master is a servant leader responsible for facilitating Scrum processes.That being said, a Scrum Master also helps people outside the Scrum team understand which of their interactions with the Scrum team are useful. This, in turn, helps the Scrum teams maximize the value created by them.According to Wikipedia, Scrum Master is a facilitator of the team responsible for removing the impediments to deliver the project target. The Scrum Master is not a traditional project manager and acts as a buffer between the team and any distracting influences.  What a Scrum master is “NOT”A better perception of “what is a Scrum Master” demands an understanding of “what a Scrum Master is not”. If you are in it for the long haul, this will help you become aware of the generic misconceptions around who a scrum master actually is.Well, a Scrum Master is not a:Project managerProduct OwnerA position (it is a role)Role above the teamIn this regard, it is also important to note that a Scrum Master is not an active participant in the daily scrum activities but only a moderator.So what is it that a scrum master does for real? Let us try to understand.What exactly does a Scrum Master do?Being a Scrum Master entails a lot more than the list of priority activities of a Scrum Master you come across nearly everywhere. In addition to moderating the team activities, a Scrum Master has to help teams live by Scrum values.A typical day in the life of a Scrum Master looks somewhat like below-Moderates team activitiesHelps organize meetingsKeeps scrum processes movingKeeps the team focused on current sprintEnsures a power balance among management, Product Owner, and the teamActively works with the PORemoves impedimentsHelps the team achieve sprint goalsMaintains transparency in processesHelps improve performanceEnsures quick delivery of the final productPromotes a constructive feedback cultureIdentifies hidden issues and helps prioritize and address themHelps build self-organizing teamsEncourages teams to learn from experienceWe shall discuss the roles and responsibilities of a Scrum Master in further details in the upcoming sections.What are the top qualities of the successful Scrum Masters?To be an effective Scrum Master, one has to be a Scrum enabler first. If you have had the chance to work with highly successful Scrum Masters, there a few patterns you must have observed. These are nothing but the key attributes seen in Scrum Masters of high-performing teams.Scrum Masters with these top qualities are found to lead their teams to success-1. Communication:Effective communication is one of the top skills for any role. A Scrum Master, however, should be adept in two-way communication. (S)he should be a good speaker and listener. An efficient Scrum Master should be able to listen, comprehend, repeat, summarize, energize, observe, write, simplify, critique, suggest, assert, chat, and present with equal ease.2. Responsibility and Ownership: Scrum Master is a representative of the Scrum team. As a Scrum Master, if you are capable of building and gaining trust among the team members, you should be able to represent them in their success or failure.3. Acknowledgment and appreciation: Genuine leadership entails valuing your colleague's efforts and enabling them to advance their performance. This is one of the top qualities of a Scrum Master, who happens to be a servant leader as well.4. Good leader, not a ruler A Scrum Master should not follow a command-and-control leadership. Instead, he should adhere to the principles of servant leadership, wherein decisions are made only after discussion with the team members instead of being directly imposed.5. Multitasker: As a Scrum Master, you should be able to juggle parallel tasks and manage important scrum events within defined timeframes. Assuming an ideal Scrum team of 6-9 members, you are responsible for managing today’s tasks and planning for tomorrow’s tasks along with arranging the Scrum events for the team members to resolve their queries, planning for the next Sprint, and release. Multitasking, in fact, is one of the top qualities of a Scrum Master.6. Resolve the obstacles and keep the team on track: The Scrum Master always focuses on keeping the team on track and resolving the obstacles that are blocking their way to deliver a quality product. These obstacles may include unwanted meetings, unwanted procedural complexity, work environment or any other challenge. He/She ensures that the team is away from the distractions that are hindering the project success.7. Encourage collaboration: A Scrum Master has to look into the daily activities of the team members. Also, the Scrum Master can share his/her experiences through seminars. conferences, and meetings with the team members. A good Scrum Master should encourage collaboration with the help of planning sessions, daily stand-ups, sprint planning, and sprint review meeting sessions.  8. Initiating latest technologies: A Scrum Master can use automated builds, simple designs, multi-level testing, automated development, and pair programming to reduce time and efforts while developing the project. He/she can also make use of the latest technologies and best practices that can help you in the early completion of the project.   9. Good coach for the team: A successful Scrum Master should understand the different phases that his/her team is undergoing and the importance of team building. The Scrum Master coaches the team members by building self-organizing teams, tracking the project, implementing simple methodology rules, and by creating project vision. Other than being a coach to the team to explain Scrum processes clearly and enforcing the practice for Agile, the Scrum Master should have basic technical and project management knowledge.10. Effective collaboration with the Product Owner: This is regarded as one of the key qualities of a Scrum Master. An effective Scrum Master should be able to collaborate with the Product Owner. While the role of a PO is to convey the user requirement to the Scrum team and push the team towards it, a Scrum Master facilitates a seamless execution of the processes. Together, the Scrum Master and Product Owner build a strong relationship with the team to provide the best results.11. Empathy: A Scrum Master develops many skills while working with team members. He/She builds his/her skills to develop emotions and to learn what the team members feel. This way, (s)he builds a strong connection with the team and understands their problems while also suggesting effective solutions.  12. A strong understanding of servant leadership and facilitation:The role of the Scrum Master is not to assign the tasks to the team, it is all about supporting the team members in achieving the project goals. Servant leadership, which is one of the fundamental qualities of a Scrum Master plays a key role here. By serving and encouraging the team in every way possible, a good scrum master always helps the team members attain their full potential. Needless to say, this has a direct positive impact on the business value they create as a team.13. A relentless approach to continuous delivery:A successful Scrum Master always tries to improve the way a team works. The best way to do this is to arrange the retrospective, where each team member identifies what went well and what went wrong in the initial Sprint. The team members learn from the mistakes and this leads to continuous improvement.14. A good relationship with the team:A Scrum Master may act as a team leader, but he/she doesn’t have the authority of a true manager. Eventually, a Scrum Master has to be cordial with the team members, if he/she wants to influence specific actions.15. Product, market, and domain knowledge:A Scrum Master need not have end-to-end technical knowledge and domain skills. However, a fundamental understanding of the product, markets, and software development processes, makes it easier for them to address challenges in project delivery.16. Encourage a self-organizing team:A scrum master should know when to express his views and should mostly allow the team to be self-organizing. That said, he should be actively listening to the team members’ inputs and learning points and guide the team to perform better in subsequent sprints.What are the essential skills of a Scrum Master?Though the Scrum Master role is complex and challenging, a diverse skill set allows them to become a great Scrum Master. Here are the Scrum Master competencies that help him/her succeed in the project:1. Organizing the teamKnowing the rules of the ScrumCommunicating internally and externallyReporting the status of the team membersCollecting the team members in the Sprint PlanningGuiding clearlyResolving the impedimentsEfficient facilitationImplementing collaborative engagement tools and techniques2. Improving the teamForming a good teamManaging the technical debtImproving team members’ activities by providing feedback and motivationImplemented continuous validated learningResponsible for making a change3. Establishing a self-organising teamDisplaying a servant leadershipExecuting the Scrum valuesDecide according to Agile methodologyOwing to the team members’ responsibilitiesInvolving every team member in planning4. Planning bigDiscussing with the team membersFinding and fixing the cross-team problemsImproving the cross-team technical practicesRoles and Responsibilities of a Scrum MasterThe Scrum Master’s role is pivotal to the success of a team. He/she is a process leader who helps the team understand Scrum values, principles, and practices. Some organizations practice rotation of Scrum Master roles among the team members; this is, once again, up to each Scrum Team.However, the roles of the Scrum Master include:The Agile framework custodian and process owner for the team.A facilitator and Servant Leader who never discourages but encourages and expects self-organization from the Agile development team.Build close collaboration across roles and functions in the organization, works on matters collectively and is not individualistic.Protect the team from distractions which include both external and internal.Remove impediments, so the team can focus on the development of work and tasks.Scrum Master is not typically a manager or lead, but he/she is an influential leader who does not do direct command and control.Scrum Master is a coach and advisor to the team and discussed issues encountered.Scrum Master should be equipped with basic technical and project management know-how, this is so that he/she understands the problems and is able to provide proper guidance and advice to the team.With Scrum gaining widespread attention in just about every sector, top industry majors like Microsoft, Honeywell, Ericsson, Bank of America, Cox Automotive, KPMG, etc. are focusing on the integration of Scrum into their existing frameworks. This trend has prompted more industries to invest in Agile and Scrum training.  Let’s see some more benefits of having a certified Scrum Master on a project.Why should you be interested in getting a Scrum Master Certification?Scrum has become the finest choice of organizations to deliver more value to the customers. In State of Scrum 2018 survey, 85 percent of the respondents say Scrum continues to improve the quality of work life. At the same time, 81% of Scrum Masters who received certification agreed that it has significantly helped improve their practice.Listed below are the reasons and benefits of having a Scrum Master certification (CSM).1. In-depth knowledge of Scrum:If you have not implemented Scrum before, earning the certification will help you to learn the Scrum skills effectively. With this certification, you can level-up your knowledge with the basics of Scrum and you will be able to:Make customers happy and satisfiedDeliver better quality product in less timeMaintain team collaborationLesser defectsFlexible working strategyTake a quick decision on an issue2. A number of companies moving to Agile:Nowadays, organizations are required to speed up their product development process to deliver fast according to the changing needs of the customers. This helps organizations to stay viable. Scrum produces in iterations and its self-organizing teams deliver products of maximum value. Due to this reason, a number of companies are shifting to Agile.      3. New career opportunities on the go:A CSM certification will bring more new career opportunities as more companies are migrating to the Agile approach and they need a professional who will guide a team to follow the Scrum approach. Being a certified Scrum Master, your chances of getting hired by the top employers with fair salary are more.    4. Increases collaboration:When it comes to working on a complex project, it needs collaboration among the team members. As a certified professional on a team, you can build and reinforce the basic understanding of Scrum to produce a value.  5. Switch to the Agile mindset:You need to develop an Agile mindset if you have to work with Agile methodologies. As a certified person on a team, you need to start thinking in an Agile way that will avoid differences in opinions and lead to successful projects with better team collaboration.    7. Organizations yield more:It is tough for any organization to accept new processes easily as it affects the complete structure of the organization. It affects processes, management, people, and clients. In this regard, you need a knowledgeable person in your team who will make the adoption a smooth process. Being a certified Scrum Master, you will be facilitating the tasks for the team members.  8. Enter the Scrum experts community:After taking a Certified ScrumMaster certification, an individual will get a chance to be a part of the Scrum experts community of Scrum Alliance. This community offers knowledge in a way to stay updated, find the events, and provide instructions to the certified members.Scrum Master vs. Project ManagerOnce we enter the industries, we often come across the term Project Manager along with the Scrum Master. These two roles are distinct from each other though they contribute to the projects. This creates confusion between the Scrum Master and Project Manager roles when an organization is undergoing an Agile transformation.A Scrum Master works on the Agile project associated with Scrum project management principles whereas a Project Manager’s work is based on the traditional disciplined project management principles. Let’s see the differences between a Scrum Master and Project Manager. Also, if you are serving as a Project Manager and willing to become a Scrum Master or vice versa, this information will help you to take a stand on this. Before going further, let's see the roles of the Scrum Master and Project Manager in brief.1. Scrum Master duties:Scrum Master responsibilities to the Product Owner (PO)-Helps the PO in managing the product backlogHelps the PO to convey the product requirement clearly to the team members  Facilitate Scrum events to the POScrum Master responsibilities towards the development team-Guiding and coaching the teams to follow Scrum rulesRemoves roadblocks that are inhibiting the project’s progressHelps to maintain team dynamics and high-value resultFacilitate the Scrum events and arrange Scrum meetingsDirecting the team in Scrum implementationMentor the team members who are new to Scrum adoption2. Project Manager roles:The Project Manager is responsible for:Delivering the product according to the project’s requirementsDefining the project scope and planning the project activities accordinglyEnsuring that the responsibilities assigned to team members are according to their skills and expertiseReporting the progress of the project to the stakeholdersTracking the project performance against the timelines and ensuring an effective project qualityMaking sure that the project documentation is properPlanning the tasks for the team members and ensuring that the team understands their roles in the projectPreparing a project budget and getting it approved from the senior managementManaging the StakeholdersMonitoring and controlling the risks in the projectDelivering the project on time with the project constraints like scope, the budget, time, and efficient resourcesLet’s figure out the major differences between a Scrum Master and Project ManagerScrum MasterAttributesProject ManagerMakes sure that the team members are well trained to follow Agile practices appropriately. Also, SM coaches the Scrum teams and mentions the timeline to finish the projectGoalsHas defined goals like-Completing the project on time, planned a budget, and scopeSM assures the quality and knows the importance of quality.Quality AssurancePM also knows the importance of quality, but doesn’t know how to achieve it. A consultant is usually hired to fix the errorsScrum Master always tries to keep things smaller. They like to work in small teams irrespective of budget.Team SizeProject Managers like to make things large. PM works with more people and a huge budget. In this way, they improve to Program ManagerThe average salary of a Certified ScrumMaster® is $116,659 per year.Average SalaryThe average salary of a Project Manager is $75,474 per yearCertified Scrum Master (CSM)®Advanced-Certified Scrum Master (A-CSM)®Certified Scrum Professional- Scrum Master (CSP-SM)®Professional Scrum Master (PSM I, PSM II, PSM III)Agile Scrum Master (ASM)Scrum Master Certified (SMC)SAFe® Scrum Master (SSM)SAFe® Advanced Scrum Master (SASM)CertificationsAgile Certified Practitioner (PMI-ACP)®Project Management Professional (PMP)®Certified Associate in Project Management (CAPM)®Certified Project Manager (IAPM)CompTIA Project+Certified Scrum Master (CSM)- Scrum AllianceAdvanced-Certified Scrum Master (A-CSM)- Scrum AllianceCertified Scrum Professional- Scrum Master (CSP-SM)- Scrum AllianceProfessional Scrum Master (PSM I, PSM II, PSM III)- Scrum.orgAgile Scrum Master (ASM)- EXINScrum Master Certified (SMC)- SCRUMstudySAFe® Scrum Master (SSM)- Scaled Agile Inc (SAI)SAFe® Advanced Scrum Master (SASM)- Scaled Agile Inc (SAI)Accreditation bodiesAgile Certified Practitioner (PMI-ACP)®- PMIProject Management Professional (PMP)®- PMICertified Associate in Project Management (CAPM)®- PMICertified Project Manager (IAPM)- International Association of Project ManagersCompTIA Project+- CompTIAEfficient Scrum Master = Great OrganizationThe role of a Scrum Master may vary from one project to another or one organization to another but the importance of Scrum Master in a team will always be the same. The role of the Scrum Master in general is very challenging. It goes without saying that hiring a Scrum Master is the wisest decision for an organization undergoing a real transition to Agile!Know more about what is a Scrum Master.
10971
What is a Scrum Master - Everything You Need to Kn...

What is a Scrum Master?A deep understanding of Scr... Read More

Agile Contracts or Agile Statement of Work - Must-Haves

In IT with the Agile boom, everyone wants to get into Agile Development. Be it the customers, organizations, and even developers, everyone wants to get into Agile Development. Customers want to follow Agile so that they can get to see the Product early and the changes can be incorporated without any cost. In other words, they want fixed price, variable scope. But, organizations need to be cautious in order to define how much variable scope is included in contract clauses. Organizations want to keep themselves up-to-date and follow Western culture blindly. Statements like these often come “Everyone is going Agile, why aren’t we yet?” They have to understand, every environment, every team, and every client is different. We just cannot keep on copying everyone else. Developers, of course, will have “Agile” word in their resumes which will help them grow and find jobs.   The number of agile contracts [by govt] amounts to a coat of agile paint on a giant waterfall HT @RachelProsser https://t.co/IEOPRRFFM5 — (((Dave Moskovitz))) (@davemosk) October 9, 2017 So, in desperation, companies (small or medium organizations) ONLY follow what customers say. What they end up is – with an agreement that has clauses of Waterfall model and they tell clients that we will follow Agile. These clauses might be like having fixed scope or fixed price which will be given by end of phase like requirement gathering or planning or UAT done etc. But we forget, that in Agile, every iteration has these phases and we should be targeting the contract in such a manner that it is win-win for both the parties at end of every iteration. Below figure distinguishes between the Traditional Pyramid and Agile Pyramid. Traditional pyramid has fixed scope while Agile one has the Estimated scope, to be considered while negotiating the contract.   Lawyers and Sales team need to be taught that if we are following Agile, we need to follow the terms and conditions for Agile contracting and not of Waterfall.   #agile contracts, however, are not the silver bullet: few of them delivered the right client benefits. @WC_REFSQ pic.twitter.com/8MSb0okXQ7 — Samuel Fricker (@samuelfricker) March 15, 2016 Apart from including changes like, Product Backlog (instead of BRD), Key roles in Project, the Agile methodology, below are few MUST HAVES that should be mentioned clearly in the contracts and need to be communicated to the customers, during the contract negotiation: 1. Pricing Model: It is unrealistic to expect any development project or product, to be delivered on a Fixed price basis. We all know that there will ALWAYS be changes in scope which will affect the original price. If the customer has a fixed budget, this can be managed within an Agile project by focusing on the development of high-priority items first, allowing the Customer to remove low-priority items from scope. All such issues must be taken into account when negotiating the Pricing Model for the project. Below are a few potential pricing models: a. Fixed Price per user story – Be cautious here, too long user stories need to be broken up.  b. Fixed Price per iteration – Make sure that all iterations range to similar story points. Remember, we have to create win-win for both parties. c. Fixed Price for the agreed number of features – Describe the feature well in advance. d. Time & Material (our favorite) - Customer continues to pay during an agreed-upon time period. The customer pays till a point he sees value being added. In case he sees that no value is being added, the customer stops paying and the contract ends. 2.Spikes for high-risk elements: In case the project has specific, high risk elements, e.g. technical challenges or business issues that are absolutely first timers or have never been solved before, these MUST be communicated up-front. Such Programming spikes where we attack only the riskiest coding in the project must be included in the contract. These spikes give customers a realistic view of the project ahead for the least amount of money and avoid conditions of "Fast failure". The main goal here is to uncover any weaknesses in the proposed development and hence be ready with the new plan and strategy in order to make the project successful. 3. Define Scope, but no need to mention delivery items: Product backlog defined at the high level MUST be attached to the contract as one of the appendices. Though the scope is variable and will change during the course of the project, high-level scope must be included in the contract. Delivery Items will change post discussion with PO on every iteration, but the high-level scope remains the same. Emphasize on process rather than on dates and items. This will keep the team’s mindset collaborative. 4. Settle on Definition of Done at high level: While negotiating the contract, the “Definition of Done” should ideally be defined and attached as an appendix. The clauses for “Definition of Done” that needs to be included are: a. During every Sprint Planning, PO and the development team will review the “Definition of Done” for the items that are included in that particular Sprint. b. In case of disputes, there should be appropriate resolution techniques in place between the parties.   Concluding the article by revisiting one of the values of Agile Manifesto: Customer collaboration over contract negotiation. Contracts matter to those who have signed it. Customers do face problems and you will be able to see them only when you talk to them. Once you see and understand their problems for which they have hired you to provide the solution, you need to COLLABORATE with them and get to it. Despite all the clauses in the contract, the motto should be “LET’S DO IT !!”.  
2335
Agile Contracts or Agile Statement of Work - Must-...

In IT with the Agile boom, everyone wants to get i... Read More

Why Should I Care About Professional Scrum Master (PSM) For Scrum Master Job?

Professional Scrum Master (PSM) is training and certification workshop is managed by Scrum.Org. Scrum.Org is a scrum training and certification organization started by Ken Schwaber (Co-Creator of Scrum Framework) after moving away from Scrum Alliance in 2010. Today, there are more than 80,000 Professional Scrum Master worldwide and more than 75 get added every day. PSM is recognized as most sought certification for Scrum Master and agile coach worldwide due to credible exam, best quality trainers and consistent course material. Many companies only consider PSM holders for Scrum Master role. How to become Professional Scrum Master (PSM)? There are 2 possible ways to achieve it. 1st – Write exam without training if you are already practicing Scrum. 2nd – Attend professional Scrum Master (PSM) training in your area before writing exam. If you are planning to write exam yourself without training then follow below instructions to clear exam in 1st attempt. Buy exam from Scrum.org website after paying $150. Read Scrum Guide  Try Open assessment  DON’T take training from non-PSTs (Professional Scrum Trainers) – Trainer may not be having understanding about Scrum and Test as per Scrum.org expectation. DON’T take test on any other website – Exam may not be up to date as per Scrum.Org syllabus. DON’T take online Scrum Training – It may not be aligned with Scrum.Org learning objective. Always attend licensed trainer’s workshop. PSTs are well groomed and given license to teach after going through rigorous process. Advantages of attending Professional Scrum Master (PSM) training before writing exam. Exam fee is already covered in training fee so no need to pay exam fee separately Opportunity to learn from licensed Trainers 50% discount on second attempt (Applicable to India and Subcontinent) 40% discount on PSM –II (next level after PSM-I) Copy of course material maintained by Scrum.org
4785
Why Should I Care About Professional Scrum Master ...

Professional Scrum Master (PSM) is training and ce... Read More