Agile Leadership

Posted by Sawyer Conrady on January 12, 2023

Need help with Agile or SAFe? CLICK HERE to speak to an expert today!


Advice for Middle Managers part of an agile transformation

As agile methodology continues to become more and more popular in the business world, middle managers are playing an increasingly important role in the agile transformation. Agile methodology is a unique way of working that emphasizes collaboration and flexibility, and managers must understand how to support and manage their teams in this new way of working.

To assist middle managers in their efforts to support agile transformation, here are 8 of the best pieces of advice: 

1. Communicate the Purpose and Goals

It’s important for middle managers to ensure that their teams understand the purpose and goals of the agile transformation. Make sure to communicate the ‘why’ behind the change, and explain the expected benefits for the organization. 

2. Set Clear Expectations

Middle managers should set clear expectations for their teams regarding their roles and responsibilities in the agile transformation. Make sure to communicate how their individual work contributes to the team’s success and the organization’s goals. 

3. Foster Collaboration

Encourage collaboration between team members, and create an environment that encourages creativity and open dialogue. Agile methodology relies on collaboration, and middle managers should foster an environment where team members feel comfortable exchanging ideas and working together. 

4. Provide Training and Coaching

Offer training and coaching to help team members understand agile methodology and the tools they need to be successful. This will help ensure that everyone is on the same page and has the necessary skills to support the agile transformation. 

5. Break Down Silos

It’s important for middle managers to break down silos and encourage cross-functional collaboration. This will help teams become more efficient and effective in their work. 

6. Offer Support and Recognition

Middle managers should provide support and recognition to their team members to help them stay motivated and engaged in the agile transformation. 

7. Be Adaptable

Agile methodology is all about being flexible and adapting to change. Middle managers should be willing to try new things and be open to feedback from their team members. 

8. Celebrate Successes

It’s important for middle managers to celebrate successes and recognize achievements along the way. Celebrating successes will help keep everyone motivated and on track. 

By following these pieces of advice, middle managers can ensure that they are providing the necessary support to their teams during the agile transformation. With the right guidance, middle managers can help their teams become successful in the agile methodology.


The Importance of Decentralized Decision Making

Decentralized decision making is a process that allows for decisions to be made by individuals or small groups in a way that is independent of centralized authority. This means that decisions are not solely made by the top leadership of a company or organization, or by one person or group of people. Instead, everyone involved in the decision-making process has an equal say in the outcome. 

Decentralized decision making has become increasingly important in today’s business world. Organizations are recognizing that decisions which are solely made by the top leadership can be costly and inefficient, leading to poor decision making and poor outcomes. By allowing everyone involved to have a say in the decision making process, organizations can benefit from different perspectives and ideas. This leads to better outcomes, as well as an increased sense of ownership and responsibility from team members. 

Decentralized decision making also allows for faster decisions to be made by those closest to the work.  This is particularly important in situations that require quick decisions, such as when responding to an emergency or making a strategic decision. In addition, decentralized decision making encourages creativity and innovation. By allowing everyone to contribute to the decision making process, organizations can benefit from the different experiences and perspectives of team members, as well as new ideas that could potentially lead to better outcomes.

 Finally, decentralized decision making allows for greater collaboration and communication among team members. When everyone has a say in the decision-making process, team members are more likely to work together towards a common goal, leading to better outcomes.

Decentralizing decision making is an important step that can lead to better outcomes, faster decisions, increased creativity and innovation, and greater collaboration and communication among team members. Organizations that recognize the importance of decentralized decision making and implement it into their decision making process can benefit from these advantages.


How does HR (Human Resources) need to adapt the annual review process to support the agile transformation?

In an agile organization, the annual performance review process may need to be adapted to better align with the principles and values of agility. This may involve a shift from a traditional, top-down approach to performance evaluation, to a more collaborative and ongoing process. Some possible changes to the annual performance review process in an agile organization might include:

  • Moving away from a focus on individual performance, and instead emphasizing the performance of the team as a whole.

  • Using agile practices, such as regular feedback and reflection, to continuously assess and improve performance.

  • Involving the whole team in the performance review process, rather than just the manager or HR department.

  • Making the performance review process more transparent and open, so that everyone on the team has a clear understanding of how they are contributing to the organization’s goals.

The goal of the performance review process in an agile organization should be to support continuous learning and improvement, rather than to simply evaluate and judge individual performance.


How does diversity help agile teams?

Agile teams are built on the principles of collaboration, inclusion, and continuous learning, and a diverse team can help to support these principles. A diverse team brings together individuals with different backgrounds, perspectives, and experiences, which can lead to more creative and innovative solutions to problems. It is generally a good idea for product teams to strive to represent the diversity of their customers. This is because a diverse team is more likely to be able to understand and address the needs and preferences of a diverse customer base. A team that is composed of individuals with different backgrounds, perspectives, and experiences can provide a more well-rounded view of the customer, and can help to identify potential issues and challenges that may not be obvious to a team that is more homogeneous. Additionally, a diverse team can help to create a more inclusive and respectful work environment, which can improve morale and productivity. While it may not always be possible to perfectly reflect the diversity of the customer base, striving for diversity in product teams can be a valuable way to improve the quality and relevance of the products being developed.


How does agile help employees grow?

Agile practices can be motivating for employees because they often involve empowering employees to take ownership of their work and make decisions. This can give employees a greater sense of control and autonomy, which can be motivating in and of itself. Additionally, agile practices often involve regular feedback and collaboration, which can help employees feel more connected to their team and to the broader organization. The focus on continuous learning and improvement in an agile environment can create a culture of collaboration and innovation, which can be highly motivating for employees.

Agile practices can help grow your employees in several ways. First, they can help your employees develop new skills and improve their existing ones. For example, in an agile environment, employees may be encouraged to take on new roles and responsibilities, which can help them learn new things and expand their skill sets. Additionally, agile practices often involve regular feedback and collaboration, which can help employees learn from each other and improve their performance over time. The focus on continuous learning and improvement in an agile environment can help your employees grow and develop both personally and professionally.


How can managers leverage Kaizen?

Kaizen is a philosophy and set of practices that is focused on continuous improvement and the ongoing optimization of organizational processes. As a manager, you can leverage the concepts of Kaizen in a number of ways to improve the performance and effectiveness of your team or organization. Some potential strategies for leveraging Kaizen as a manager include:

Encourage a culture of continuous improvement

One of the key principles of Kaizen is the belief that there is always room for improvement, and that every member of the organization has the potential to contribute to that improvement. As a manager, you can encourage a culture of continuous improvement by creating an environment in which your team members feel empowered to identify and address problems and opportunities for improvement, and by recognizing and rewarding their efforts to do so.

Engage your team in problem-solving

Another key principle of Kaizen is the idea that problems should be addressed at the source, rather than allowing them to escalate or to be passed on to others. As a manager, you can engage your team in problem-solving by involving them in the identification and analysis of problems, and by providing them with the resources and support they need to develop and implement solutions.

Use data and metrics to drive improvement

A key aspect of Kaizen is the use of data and metrics to drive improvement. As a manager, you can leverage this principle by tracking and measuring key performance indicators (KPIs) that are relevant to your team or organization, and by using this data to identify areas for improvement and to evaluate the effectiveness of your improvement efforts.

Leveraging the concepts of Kaizen as a manager can help you to create a culture of continuous improvement, to engage your team in problem-solving, and to use data and metrics to drive improvement.


“See with your own eyes”

In the context of kaizen, the phrase “see with your own eyes” refers to the practice of going to the source of a problem or opportunity in order to observe and understand it firsthand. This is a key principle of kaizen, as it emphasizes the importance of gathering direct, empirical evidence in order to identify and address problems and opportunities for improvement.

By “seeing with your own eyes,” you can gain a deeper understanding of the problem or opportunity, and you can develop solutions that are more effective and sustainable. This can also help you to gain the support and buy-in of your team and other stakeholders, as they can see for themselves the problems and opportunities that you have identified.

“Seeing with your own eyes” is a key principle of kaizen, and it involves going to the source of a problem or opportunity in order to observe and understand it firsthand, in order to develop more effective and sustainable solutions.

You may not be able to hire the most talented engineering workforce if you are still using legacy methodologies

Many engineers, especially those who are experienced and highly skilled, prefer to work in organizations that have adopted agile practices. This is because agile can provide many benefits to engineers, such as more autonomy, flexibility, and opportunities for continuous learning and improvement.

Additionally, many engineers may be familiar with agile and may have experience working in agile environments. If your organization has not created an agile environment, you may find that some engineers are not as interested in working for you, since they may not be able to apply their agile skills and experience in your organization.

Engineers are more satisfied in their careers if they understand the business value of their solution and can celebrate progress via incremental delivery.  Engineers also value the fast feedback cycles that test automation and continuous integration offer to ensure their work is high quality.  If you are competing with other organizations that have already adopted agile, you should reconsider the impact of maintaining legacy processes and culture.


Kotterisms

Kotterisms are phrases or concepts that are associated with the work of Dr. John Kotter, a renowned organizational change expert and author. Some examples of Kotterisms include:

1. “Leading change is about dealing with people’s emotions.”

 This is a core principle of Kotter’s approach to change, which emphasizes the need to understand and address the emotional reactions of people to change in order to gain their support and buy-in.

2. “Change is a process, not an event.” 

This is another core principle of Kotter’s approach, which emphasizes the need to view change as a continuous process, rather than a one-time event. This helps organizations understand that change is ongoing and dynamic, and that they need to be prepared to adapt and evolve over time.

3. “The best leaders are change agents.” 

According to Kotter, the best leaders are those who are able to effectively lead and manage change in their organizations. These leaders have the skills, knowledge, and experience to guide and support their teams through the challenges and uncertainties of change.

 Some key lessons that we can learn from Kotter include:

  1. The importance of creating a sense of urgency. Kotter emphasizes the need for organizations to create a sense of urgency about the need for change, in order to motivate and inspire people to take action. Without a sense of urgency, people may be resistant to change or may not see the need for it, which can hinder the success of any change effort.

  2. The need for a clear vision and strategy. Kotter emphasizes the importance of having a clear vision and strategy for implementing change, in order to provide direction and focus for the effort. Without a clear vision and strategy, change efforts can become disorganized and chaotic, which can lead to confusion and failure.

  3. The importance of strong leadership. Kotter emphasizes the need for strong leadership in implementing change, in order to provide direction, guidance, and support to the people involved. Without strong leadership, change efforts can struggle to gain traction and may not be successful.

  4. The need to involve and engage people throughout the organization. Kotter emphasizes the importance of involving and engaging people throughout the organization in the change process, in order to gain their support and buy-in. 


Do you have a No-No Team?

The no-no team is a concept from the work of Dr. John Kotter, a renowned organizational change expert and author. The no-no team refers to a group of people who are resistant to change and who will do everything they can to prevent or block change from happening. These people may have a variety of reasons for their resistance, such as fear of the unknown, loss of power or control, or a lack of understanding or buy-in.

According to Kotter, the no-no team can be a major obstacle to successful change efforts, and organizations need to be prepared to deal with them in order to overcome their resistance. This can involve strategies such as engaging and involving the no-no team in the change process, addressing their concerns and objections, and providing them with the support and resources they need to adapt to the change.

The no-no team is a concept that highlights the importance of addressing resistance to change and overcoming the obstacles that can prevent organizations from successfully implementing change. By understanding and managing the no-no team, organizations can improve their chances of success in implementing change and achieving their goals.


5 Principles of Preventing Burnout

Agile can help to prevent burnout by encouraging a balanced and sustainable approach to work. Some of the ways that agile does this include:

1. Emphasizing collaboration and communication

In agile, team members are encouraged to work together and communicate openly and honestly. This can help to prevent burnout by reducing the sense of isolation and allowing team members to support and help each other.

2. Focusing on delivering value

Agile emphasizes delivering value to the customer, rather than just working long hours. This can help to prevent burnout by ensuring that team members are working on tasks that are meaningful and important, rather than just busy work.

3. Enabling estimation and planning

Agile helps teams estimate and plan over short periods of time which improves accuracy.  The team makes commitments based on data of past performance which helps them maintain a realistic perspective of what is possible.

4. Encouraging work-life balance

Agile emphasizes the importance of balancing work and personal life. This can help to prevent burnout by allowing team members to take breaks, recharge, and take care of their physical and mental health.

5. Allowing flexibility and adaptability

In agile, teams are encouraged to be flexible and adaptable, rather than sticking to a rigid plan or schedule. This can help to prevent burnout by allowing team members to adjust their work according to their own needs and preferences.

Agile can help to prevent burnout by encouraging a balanced and sustainable approach to work, and by allowing team members to work together, deliver value, maintain a healthy work-life balance, and be flexible and adaptable.


Human Resources – the frequently missed piece of the agile transformation

HR can play an important role in a company’s agile transformation by supporting and enabling the adoption of agile practices and principles by the organization’s teams and individuals. HR can play a critical role in a company’s agile transformation by providing training and education, developing agile HR policies and processes, supporting the formation of agile teams, and facilitating agile team development. 

Some of the ways that HR can be involved in the agile transformation include:

Providing training and education

HR can help to ensure that the organization’s teams and individuals have the knowledge and skills needed to successfully implement agile practices. This may involve providing training and education on agile principles and practices, such as Scrum or Kanban, or on related topics such as collaboration, communication, and continuous improvement.

Developing agile HR policies and processes

HR can help to align the organization’s HR policies and processes with its agile principles and practices. This may involve developing agile-friendly policies on topics such as work-life balance, performance management, and career development, and ensuring that these policies support the agile way of working.

Supporting the formation of agile teams

HR can support the formation of agile teams by helping to identify and assess the skills and expertise of potential team members, and by facilitating the formation of cross-functional, self-organizing teams.

Facilitating agile team development

HR can help to facilitate the development of agile teams by providing support and guidance on topics such as team dynamics, communication, and conflict resolution.

Chief People Officer

A chief people officer (CPO) can play a crucial role in helping an organization undergo an agile transformation. The CPO is responsible for overseeing all aspects of the organization’s human resources (HR) function, including recruiting, training, and development. In this capacity, the CPO can help the organization develop the skills and capabilities it needs to be successful in an agile environment. For example, the CPO can help identify and develop leaders who are adept at leading and managing in an agile way, and who can help the organization achieve its goals. Additionally, the CPO can help the organization develop a culture that is conducive to agility, such as fostering collaboration, communication, and continuous learning. By working closely with other members of the leadership team, the CPO can help ensure that the organization’s agile transformation is successful and sustainable.


Stop encouraging Heroism

In agile organizations, it is important to stop heroism and fire fighting for several reasons. First, heroism and fire fighting can create a negative work environment, as they often involve working long hours, sacrificing personal time and well-being, and taking on too much work. This can lead to burnout and turnover among team members, and can ultimately harm the organization’s productivity and success.

Second, heroism and fire fighting can undermine the principles and practices of agile, such as collaboration, adaptability, and continuous improvement. When team members are focused on fire fighting and heroics, they may not have the time or energy to engage in collaborative problem-solving, to adapt to changing circumstances, or to learn and improve.

Third, heroism and fire fighting can create a culture of blame and punishment, as team members may be blamed or punished for not being able to handle the excessive workload or for making mistakes. This can create a negative work environment, and can hinder the team’s ability to work together effectively.

It is important to stop heroism and fire fighting in agile organizations, in order to create a positive and sustainable work environment, to support the principles and practices of agile, and to avoid a culture of blame and punishment. By focusing on collaboration, adaptability, and continuous improvement, agile organizations can be more successful and resilient in the long term.


Enabling command and control Leaders: What you lose

Allowing command and control behaviors in an organization can lead to a number of negative outcomes. First and foremost, it can create an unhealthy and unproductive work environment. This type of management style often breeds fear and lack of trust among employees, which can lead to poor communication, low morale, and high levels of turnover. Additionally, command and control behaviors can stifle creativity and innovation, as employees may be hesitant to speak up or offer new ideas. This can lead to a lack of adaptability and competitiveness within the organization. Furthermore, relying on this type of management style can create a narrow, top-down decision-making process, which can be inefficient and ineffective in today’s rapidly changing business environment. Allowing command and control behaviors can hinder an organization’s ability to achieve its goals and be successful in the long term.


Ensure you are hiring life-long learners

Being a lifelong learner is an important quality for anyone who wants to be agile and adaptable in today’s fast-paced world. Lifelong learning involves a commitment to continuous learning and personal development, and it can help individuals stay current with new technologies, trends, and developments in their field. This type of learning can also help individuals develop new skills and expertise, which can make them more valuable and versatile in the workplace. Additionally, lifelong learning can help individuals stay engaged, motivated, and curious, which can lead to greater job satisfaction and personal fulfillment. Being a lifelong learner is an important part of being an agile and adaptable individual who is able to thrive in today’s rapidly changing world.


Do your hiring profiles represent an Agile mindset?

Agile practices can change the hiring profile in several ways. First and foremost, agile organizations typically place a greater emphasis on hiring individuals who have the right mindset and attitude, rather than just specific skills and experience. This means that agile organizations may be more likely to hire individuals who are adaptable, collaborative, and open to new ideas, even if they don’t have a perfect fit with the job requirements. Additionally, agile organizations often prioritize diversity and inclusion, which can broaden the pool of potential candidates and lead to more diverse hiring. Finally, agile organizations typically value ongoing learning and development, so they may be more likely to hire individuals who are committed to lifelong learning and personal growth. Agile practices can lead to a more diverse, adaptable, and dynamic hiring profile.

It is generally not advisable to hire people with certain characteristics for an agile organization, as these characteristics can hinder the success of an agile team. Some of the characteristics to avoid include:

  • Lack of adaptability

  • Lack of coachability

  • Lack of collaboration

  • Lack of emotional intelligence

  • Lack of curiosity and learning

  • Lack of accountability


Demonstrate Servant Leadership

There are several ways that you can demonstrate servant leadership in your agile organization. Some specific actions you can take include:

Focus on the needs of your team

As a servant leader, your primary focus should be on serving the needs of your team. This means listening to their concerns, providing support and guidance, and helping them to achieve their goals.

Empower your team

Servant leaders empower their teams to make decisions and take ownership of their work. This means giving them the autonomy and support they need to be successful, and trusting them to make the right decisions.

Foster collaboration and teamwork

Servant leaders promote collaboration and teamwork within their teams. This means encouraging open communication, fostering a culture of trust and respect, and helping team members to work together effectively.

Prioritize learning and development

Servant leaders prioritize the learning and development of their team members. This means providing opportunities for learning and growth, and helping team members to develop the skills and expertise they need to be successful.

Demonstrate humility and empathy

Servant leaders are humble and empathetic. This means being open to feedback and criticism, and treating others with kindness and respect.


Adopt situational leadership

Do you only have one style of leadership? Try a situational style of leadership. Wouldn’t that be more effective and… more agile?

Situational leadership is a leadership approach that involves adapting one’s leadership style to fit the specific needs and abilities of the team or individual being led. To demonstrate situational leadership, a leader must be able to identify the specific needs of the team or individual, and then adapt their leadership style to match those needs. This may involve shifting between different leadership styles, depending on the situation. Some specific ways to demonstrate situational leadership include:

Assessing the abilities and needs of the team or individual

To effectively demonstrate situational leadership, you must first understand the abilities and needs of the team or individual you are leading. This involves observing their performance, listening to their concerns, and asking for feedback.

Adapting your leadership style to fit the situation

Once you have assessed the abilities and needs of the team or individual, you can then adapt your leadership style to fit the situation. This may involve shifting between different styles, such as directive leadership when the team needs guidance, and supportive leadership when they need encouragement and support.

Providing support and guidance

As a situational leader, it is your responsibility to provide the support and guidance that the team or individual needs to be successful. This may involve providing feedback, coaching, and other forms of support to help them improve and grow.

Monitoring progress and adjusting your approach

Situational leadership is not a one-time event, but rather an ongoing process. As such, it is important to regularly monitor the progress of the team or individual, and to adjust your approach as needed to continue meeting their needs.

By demonstrating situational leadership, you can effectively adapt your leadership style to fit the needs and abilities of your team or individual, and help them be successful.


Employees need mission and purpose

One way that agile companies can promote employee retention is by fostering a sense of meaning and purpose in the work that their employees do. As mentioned previously, having a sense of meaning and purpose in one’s work can be a powerful motivator and can help to increase motivation and engagement among employees.

Agile companies can promote a sense of meaning and purpose in several ways. One approach is to ensure that employees have a clear understanding of the organization’s vision and mission, and how their work contributes to achieving these goals. This can help to give employees a sense of direction and purpose, and can help them to see the value and significance of their work.

Another approach is to encourage employees to take ownership of their work and to have a say in how it is done. This can help to promote a sense of autonomy and empowerment, which can increase employee satisfaction and motivation. Agile companies can also foster collaboration and teamwork, which can help to build a sense of community and can promote a positive work culture.

The key to promoting meaning and purpose in the workplace is to create an environment where employees feel valued and supported, and where they can see the impact of their work on the organization and its stakeholders. By doing this, agile companies can help to retain their employees and foster a positive, productive work environment.


5 Reasons Leaders are resistant to change

As an organizational leader, it’s important to recognize that change is a necessary part of growth and progress. Unfortunately, many leaders find themselves resistant to change, even when it’s clearly needed. Here are five of the most common reasons leaders are resistant to change: 

1. Fear of failure

Leaders are often worried that if they make a change, it will fail and they will look bad. This fear of failure can lead to a “better the devil you know” mindset, where the leader prefers to stick with the status quo rather than taking a risk. 

2. Lack of trust

If leaders don’t trust their team or the process of change, they are less likely to embrace it. Leaders need to have faith in their team and their ability to implement change in order to make it successful. 

3. Comfort zone

Many leaders are comfortable in their current role and processes and may be resistant to changing something that has been working well. It’s important for leaders to recognize when change is necessary and embrace the process of change in order to continue growing and developing.

 4. Lack of resources

If a leader doesn’t have the resources to make a change, they may be reluctant to try. It’s important for leaders to take the time to review their options and identify the resources they need in order to make a successful change. 

5. Resistance from stakeholders

Leaders can often face resistance from stakeholders when they try to implement change. This resistance can come from both internal and external stakeholders and can be difficult to overcome. Leaders need to be aware of this resistance and work to build relationships and trust with their stakeholders in order to ensure successful change. 

It’s important for leaders to recognize when change is necessary and be willing to embrace it. By understanding why they may be resistant to change, leaders can work to overcome those roadblocks and make successful changes that benefit their organization.


Assume Positive Intent

Assuming positive intent is an important principle to follow when working in an agile team because it helps to create a positive and productive work environment. When team members assume that their colleagues are acting with good intentions, they are more likely to be open-minded and willing to listen to and consider different viewpoints. This can lead to better collaboration and problem-solving, and ultimately to the development of higher-quality products.

Assuming positive intent also helps to foster trust and respect within the team. When team members trust that their colleagues are acting in good faith, they are more likely to feel comfortable sharing their ideas and concerns, which can help to identify and address potential problems more quickly.

Assuming positive intent is an important practice to follow when working in an agile team because it helps to create a positive and collaborative work environment that is conducive to effective problem-solving and continuous improvement.


Making crucial decisions – do a POC

A proof of concept (POC) is a test or demonstration that is designed to prove the feasibility or viability of an idea or concept. Here are a few tips for executing a POC in an agile environment:

Clearly define the scope and objectives of the POC

It’s important to have a clear understanding of what you are trying to prove or demonstrate with the POC. This will help to ensure that the POC is focused and that the results are meaningful and relevant.

Involve the right team members

Make sure to involve the right team members in the POC. This might include developers, testers, and other stakeholders who can contribute their expertise and help to ensure that the POC is successful.

Keep it small and focused

A POC should be small and focused, with a clear set of goals and objectives. This will help to ensure that the POC is completed in a timely manner and that the results are meaningful.

Use agile principles and practices

Agile principles and practices, such as iterative development and continuous improvement, can be especially useful when executing a POC. They can help the team to adapt to changes and to learn and improve as the POC progresses.

Communicate and document the results

Make sure to communicate and document the results of the POC to the relevant stakeholders. This will help to ensure that the results are understood and that any necessary next steps are taken.


4 Ways to find early adopters

Early adopters are individuals or groups who are among the first to adopt a new product, service, or way of working. Leveraging early adopters can be an effective way to support an agile transformation within an organization. Here are a few tips for leveraging early adopters in an agile transformation:

1. Identify early adopters

Identify the individuals or groups within your organization who are most likely to be open to and supportive of an agile transformation. These may include individuals who are already familiar with agile principles and practices, or those who are looking for ways to improve their work processes.

2. Engage with early adopters

Engage with early adopters to understand their needs and concerns, and to gain their support for the agile transformation. This may involve providing training, answering questions, and addressing any concerns they may have.

3. Involve early adopters in the transformation process

Involve early adopters in the transformation process by seeking their input and feedback. This can help to ensure that the transformation process is tailored to the needs and concerns of the organization, and that it has the support of key stakeholders.

4. Share success stories

Share success stories and examples of how early adopters have benefited from the agile transformation. This can help to build support for the transformation and encourage others to adopt agile principles and practices.

Leveraging early adopters can be an effective way to support an agile transformation within an organization. By identifying, engaging with, and involving early adopters in the transformation process, and sharing success stories, you can build support for the transformation and help to ensure its success.


Agile Coaches: Working together versus independently

“Coaching as a pack” refers to the SAFe® practice of agile coaches working together as a team to support an organization in its agile transformation. This approach involves coaches collaborating and sharing their knowledge and expertise, rather than working independently.

There are several benefits to coaching as a pack:

  • Greater expertise:

    By working together, coaches can leverage the collective expertise of the team, which can be especially valuable in complex or challenging situations.

  • Improved collaboration:

    Coaching as a pack promotes collaboration and communication between coaches, which can lead to better decision-making and problem-solving.

  • Enhanced learning opportunities:

    Working with a team of coaches can provide opportunities for learning and growth for individual coaches, as well as for the team as a whole.

  • Greater flexibility:

    With a team of coaches working together, there is more flexibility to support different areas of the organization, or to adapt to changing needs or priorities.

Coaching as a pack can be an effective way to support an organization in its agile transformation. By working together and leveraging the collective expertise of the team, coaches can provide more comprehensive support, facilitate better collaboration and learning, and be more flexible in their approach.


Agile Coaches: Establishing yourself as a trusted advisor

As an agile leader, one of your key responsibilities is to act as a trusted advisor to your team and organization. This involves being a source of guidance, support, and expertise, and helping your team make informed decisions that align with the organization’s goals and values.

To be a trusted advisor, it’s important to:

  • Develop a deep understanding of your team’s work, as well as the broader context in which it takes place. This includes understanding the business goals, industry trends, and technological landscape.

  • Be approachable and responsive to your team’s needs. Make yourself available to listen to their concerns and ideas, and provide timely and relevant feedback.

  • Be honest and transparent in your communication and decision-making. This means being open about your thoughts and reasoning, and being willing to admit when you don’t know something or have made a mistake.

  • Demonstrate your expertise and credibility through your actions and results. This means being a subject matter expert in your field, and consistently delivering high-quality work that meets the needs of your team and organization.

By following these principles, you can establish yourself as a trusted advisor and help your team and organization succeed in an agile environment.


Reinforcing Agile Learning

Agile learning is a continuous process of learning, adapting, and improving through collaboration and iteration. Here are some ways you can reinforce agile learning in your team or organization:

  1. Encourage a growth mindset: Encourage a culture of continuous learning and encourage team members to embrace challenges and failures as opportunities to learn and improve.

  2. Practice regular retrospectives: Hold regular retrospectives, either as part of your sprint review or as a separate meeting, to reflect on what went well, what could be improved, and what actions can be taken to improve in the future.

  3. Foster collaboration and communication: Encourage team members to collaborate and communicate regularly, both within the team and with other stakeholders. This helps to ensure that everyone is on the same page and working towards the same goals.

  4. Encourage experimentation: Encourage team members to try new things and experiment with different approaches to problem-solving. This helps to foster a culture of innovation and continuous improvement.

  5. Provide ongoing training and support: Provide ongoing training and support to help team members stay up-to-date with new techniques, technologies, and best practices. This can include things like workshops, webinars, and coaching sessions.

By implementing these strategies, you can create a culture of agile learning that fosters continuous improvement and helps your team to adapt and thrive in an ever-changing environment.


Do your agile leaders have charisma?

Charismatic leaders can be particularly effective in the agile environment because they are able to inspire and motivate their team members to embrace agile principles and practices. Charismatic leaders can create a sense of excitement and enthusiasm for the agile transformation, which can help to build buy-in and support among team members.

Charismatic leaders can also help to foster a positive and collaborative team culture, which is essential for successful agile teams. They can encourage open communication, transparency, and continuous learning, which are all key agile values.

In addition, charismatic leaders can be effective at building strong relationships with stakeholders and influencing others to support the agile transformation. This can be particularly important in situations where there may be resistance or skepticism about agile.

However, it’s important to note that charisma alone is not sufficient for effective agile leadership. Agile leaders should also possess other leadership qualities such as honesty, integrity, and a strong sense of purpose. They should also be skilled at facilitating collaboration, decision-making, and continuous improvement within their teams.


4 Agile Mindset Shift Tactics – Required!

Agile transformations often require significant mindset shifts in order to be successful. Here are a few examples of mindset shifts that may need to happen during an agile transformation:

1. From command and control to collaboration and empowerment

In traditional, hierarchical organizations, there may be a tendency for leaders to exert a high level of control over their teams. In an agile environment, it’s important to shift towards a collaborative and empowering leadership style. This means empowering team members to take ownership of their work and make decisions, and fostering a culture of trust and open communication.

2. From individual to team focus

In traditional organizations, individuals may be more focused on their own job duties and goals. In an agile environment, it’s important to shift towards a team-focused mindset, where the team works together to achieve common goals and objectives.

3. From predicting the future to adapting to change

In traditional organizations, there may be a tendency to try to predict and plan for the future in great detail. In an agile environment, it’s important to embrace a mindset of continuous learning and adaptability, and to be open to changing course as needed in response to new information and changing circumstances.

4. From perfection to continuous improvement

In traditional organizations, there may be a tendency to strive for perfection and to resist change once a plan is in place. In an agile environment, it’s important to shift towards a mindset of continuous improvement, where teams are encouraged to experiment, learn from their mistakes, and continuously improve their processes and outcomes.


Moving from Hierarchies to Networks

In traditional organizations, hierarchies are often used to define roles, responsibilities, and decision-making authority. In an agile environment, it may be more effective to shift towards a networked organizational structure, where teams are self-organizing and empowered to make decisions within their areas of expertise.

In a networked structure, teams are interconnected and able to communicate and collaborate with each other in a more flexible and dynamic way. This can facilitate a more agile and responsive approach to decision-making and problem-solving, as well as encourage a culture of continuous learning and improvement.

Moving from hierarchies to networks in an agile environment may involve reorganizing the structure of the organization, redefining roles and responsibilities, and empowering teams to make decisions within their areas of expertise. It may also involve fostering a culture of open communication and collaboration, and using agile tools and techniques to facilitate teamwork and decision-making.


Increase Transparency

In traditional organizations, there may be a tendency towards privacy and a focus on maintaining control over information. In an agile environment, it’s important to shift towards a culture of transparency, where information is shared openly and freely within the team.

Transparency can facilitate better collaboration and decision-making, as well as foster trust and accountability within the team. It can also help to create a more open and inclusive culture, where team members feel comfortable voicing their opinions and ideas.

To move from privacy to transparency in an agile environment, it may be necessary to:

  • Encourage open communication: Encourage team members to speak up and share their thoughts and ideas openly and honestly.

  • Use agile tools and techniques: Use agile tools and techniques such as daily stand-ups, retrospectives, and open-door policies to facilitate transparency and open communication.

  • Foster a culture of trust: Encourage a culture of trust and accountability within the team, and be open and transparent in your own communication and decision-making.

  • Encourage transparency in decision-making: Be open and transparent in your decision-making processes, and encourage team members to participate in decisions that affect them.

  • Share information openly: Share information openly and freely within the team, and encourage team members to do the same.


Let’s be honest – do you live in a culture of fear?

Building a culture of fear refers to the creation of an organizational culture in which employees are constantly afraid of making mistakes, speaking up, or expressing their opinions. This can be caused by a number of factors, including a lack of trust and transparency, a high-stress work environment, or a lack of support and resources.

There are several negative consequences of building a culture of fear within an organization. These can include:

  1. Decreased productivity:

    When employees are afraid to speak up or express their ideas, they may be less likely to take initiative or be innovative, which can lead to decreased productivity.

  2. High turnover:

    A toxic work environment can lead to high levels of employee turnover, as people leave the organization to find a more positive work culture.

  3. Decreased morale:

    A culture of fear can lead to low morale among employees, as they may feel unsupported and unvalued in their work.

  4. Poor communication:

    When employees are afraid to speak up, it can lead to a lack of open communication, which can hinder collaboration and decision-making.

It is important to avoid building a culture of fear within an organization because it can have negative impacts on both individual employees and the organization as a whole. A positive work culture, on the other hand, can lead to increased productivity, engagement, and overall success.


Employees strive for Autonomy & Mastery

Autonomy and mastery refer to two important principles that can help to foster a culture of innovation, creativity, and continuous improvement.

Autonomy refers to the degree of independence and self-direction that team members have in their work. In an agile environment, team members are often given a high degree of autonomy to choose how they approach their work and make decisions, within the broader framework of the agile values and principles. This can help to create a sense of ownership and responsibility among team members, and can foster innovation and creativity.

Mastery, on the other hand, refers to the ongoing pursuit of excellence and the desire to continually improve and learn new skills. In an agile environment, team members are encouraged to continually improve their knowledge and skills, and to take on new challenges and responsibilities as they arise. This can help to create a culture of continuous learning and growth, and can lead to higher levels of engagement and motivation among team members.

Together, autonomy and mastery can create a positive and empowering work environment that encourages team members to take ownership of their work, pursue excellence, and continuously improve their skills and knowledge. This can help to foster a culture of innovation and continuous improvement, which is essential for success in an agile environment.


Attention Leadership – this is what we are requesting from you to support the transformation

  1. Lead by example: d

    emonstrate agile values and behaviors in your own work, and encourage others to do the same.

  2. Communicate the vision:

    clearly articulate the benefits of agile and how it aligns with our overall business goals.

  3. Remove barriers:

    work with teams to identify and remove any obstacles that may be hindering their ability to adopt agile practices.

  4. Provide resources:

    ensure that teams have the necessary resources and clear priorities.


Considering Agile Transformation?  Things your CTO is thinking about…

Chief Technology Officers (CTOs) may have a variety of concerns about implementing agile transformation within their organizations. Some common concerns include:

  1. Disruptions to existing processes:

    Agile transformation can involve significant changes to how work is structured and managed, and this can be disruptive to existing processes and ways of working. CTOs may be concerned about the impact of these changes on the efficiency and effectiveness of their teams.

  2. Training and support needs:

    Agile practices require a shift in mindset and behaviors, and team members may need support and training to fully understand and adopt them. CTOs may be concerned about the resources needed to provide this training and support.

  3. Resistance to change:

    Change can be difficult for many people, and CTOs may be concerned about resistance from team members or other stakeholders to adopting agile practices.

  4. Integration with other systems and processes:

    Agile practices may need to be integrated with other systems and processes within the organization, and CTOs may be concerned about the complexity of this integration and the potential for disruptions.

  5. Measuring the benefits of agile:

    CTOs may be concerned about how to measure the benefits of agile and whether the investment in agile transformation is worthwhile.

CTOs may have concerns about the potential challenges and risks associated with agile transformation, but with careful planning and a commitment to continuous improvement, many organizations have successfully adopted agile practices and realized significant benefits.


Are you forcing your managers to adopt agile?

It is important to approach the process of converting managers to agile leaders with care and consideration. Some extreme measures that may not be effective in achieving this goal include:

  • Forcing managers to adopt agile practices:

    While it may be tempting to try to force managers to adopt agile practices, this approach is likely to be met with resistance and may not lead to lasting change.

  • Using punishment or negative consequences as a motivator:

    Using punishment or negative consequences to try to motivate managers to become agile leaders is likely to be counterproductive and may create a negative work environment.

  • Ignoring the concerns or objections of managers:

    It is important to listen to the concerns and objections of managers and address them in a respectful and collaborative manner. Ignoring these concerns is likely to lead to further resistance and may hinder the agile transformation process.

Instead, a more effective approach may be to provide training and support to help managers understand and embrace agile principles and practices. This could involve providing opportunities for them to learn about agile methodologies and tools, as well as offering coaching and mentorship to help them develop the skills and confidence needed to be effective agile leaders. It is also important to be patient and recognize that the process of converting managers to agile leaders may take time and may require ongoing support and development.


How Type A Personalities fit into Agile Teams

Type A personalities are often characterized by their high levels of ambition, competitiveness, and drive. While these traits can be valuable in some contexts, they may not be well-suited to agile environments, which prioritize collaboration, adaptability, and flexibility. Some specific challenges that Type A personalities may face in an agile setting include:

1. Difficulty with collaboration

Type A personalities may struggle to work effectively in team-based environments, as they may be more focused on their own goals and objectives than on the needs and goals of the team.

2. Resistance to change

Type A personalities may be resistant to change and may struggle to adapt to new approaches or ways of working.

3. Difficulty with delegation

Type A personalities may struggle to delegate tasks and trust in the abilities of others, which can hinder the effectiveness of the team.

4. Difficulty with open communication

Type A personalities may struggle to be transparent and open in their communication, which can hinder collaboration and trust within the team.

5. Difficulty with failure

Type A personalities may have a difficult time accepting failure or setbacks, which can be detrimental in an agile environment where iteration and continuous improvement are valued.

It is important to note that these challenges are not inherent to Type A personalities and that individuals with these traits can be successful in agile environments with the right support and development. However, it may be necessary for Type A personalities to make some adjustments to their approach in order to thrive in an agile setting.


CEO Checklist: Agile Leadership Skills

There are a number of agile leadership skills that a CEO should possess in order to effectively lead an agile organization. Some key skills include:

  1. Vision and strategic thinking:

    An agile CEO should have a clear vision for the organization and be able to think strategically about how to achieve that vision through agile practices.

  2. Adaptability and flexibility:

    An agile CEO should be able to adapt to changing circumstances and priorities, and be willing to pivot and adjust as needed.

  3. Collaboration and teamwork:

    An agile CEO should be able to foster a collaborative and teamwork-oriented culture within the organization.

  4. Empathy and emotional intelligence:

    An agile CEO should be able to understand and empathize with team members, clients, and stakeholders, and be able to effectively manage and resolve conflicts.

  5. Communication and transparency:

    An agile CEO should be an effective communicator and promote transparency within the organization.

  6. Learning and continuous improvement:

    An agile CEO should prioritize ongoing learning and improvement, and encourage the team to do the same.

  7. Customer focus:

    An agile CEO should prioritize the needs and wants of customers or stakeholders, and be able to effectively incorporate their feedback into the development process.

An agile CEO should be able to lead by example and inspire the team to embrace agile principles and practices in order to achieve the organization’s goals.


Emotional Intelligence is Critical and also Challenging to develop

Emotional intelligence, or the ability to recognize and manage one’s own emotions and the emotions of others, is a critical skill that is essential for success in both personal and professional contexts. However, despite its importance, emotional intelligence can be challenging to learn and develop.

One reason why emotional intelligence is hard to learn is that it requires self-awareness and self-regulation. To effectively manage one’s own emotions, it is necessary to be aware of what one is feeling and why, and to be able to regulate those emotions in a healthy and constructive manner. This can be difficult for many people, as emotions can be complex and difficult to understand, and it may take time and practice to develop the self-awareness and self-regulation skills needed to manage them effectively.

Another reason why emotional intelligence is hard to learn is that it requires empathy and the ability to understand and relate to others’ emotions. To be emotionally intelligent, it is necessary to be able to put oneself in others’ shoes and understand how they might be feeling. This can be challenging, as it requires being able to see things from different perspectives and being able to identify and understand a wide range of emotions.

In addition, emotional intelligence may be hard to learn because it is not always emphasized or taught in traditional education settings. While some schools and universities may offer courses or programs focused on emotional intelligence, it is not always a core part of the curriculum. As a result, many people may not receive the guidance and support they need to develop these skills.

Emotional intelligence is a complex and multifaceted skill that requires self-awareness, self-regulation, empathy, and the ability to understand and relate to others’ emotions. While it is a valuable skill to have, it can be challenging to learn and develop, and may require time, effort, and support.


4 Examples of unproductive pressures from leadership

Here are a few examples of management putting pressure on agile teams in unproductive ways:

1. Setting unrealistic deadlines

Setting unrealistic deadlines can create unnecessary pressure on the team and can hinder their ability to deliver value effectively.

2. Demanding unrealistic scope

Demanding that the team take on an unrealistic amount of work or scope can create unnecessary pressure and can hinder their ability to focus on the most important tasks.

3. Micro-managing the team

Micromanaging the team and constantly checking in on their progress can create unnecessary stress and can hinder their ability to work independently and make decisions.

4. Focusing on short-term goals

Focusing solely on short-term goals and disregarding the long-term vision and goals of the project can create pressure on the team to deliver immediate results, rather than focusing on building a solid foundation for the future.

It is important for management to provide support and resources to agile teams, rather than adding unnecessary pressure in unproductive ways.

Read More

Topics: Agile Leadership

Agile Technical Practices

Posted by Sawyer Conrady on January 12, 2023

Need help with Agile or SAFe? CLICK HERE to speak to an expert today!


Why should I invest in test automation?

There are several reasons why investing in test automation is a good idea. First, it can save you time and money in the long run by reducing the need for manual testing. This is because automated tests can be run quickly and repeatedly, allowing you to catch and fix bugs early in the development process. This can help you avoid costly delays and rework.

Second, automated tests are more reliable than manual tests because they are not subject to human error. This means that you can have more confidence in the results of your tests, and you can be sure that your software is working as intended.

Third, automated tests can help you improve the quality of your software by providing consistent and comprehensive testing. This can help you identify and fix bugs and other issues more quickly and effectively, resulting in a higher-quality product.

Investing in test automation can provide many benefits, including saving time and money, improving the reliability and quality of your software, and helping you to deliver a better product to your customers.


Why do you want to invest in TDD (Test-driven Development)?

Test-driven development (TDD) is a software development process in which tests are written for a piece of code before the code itself is written. This can be a valuable approach for several reasons.

First, TDD can help you to write better code by ensuring that your code is thoroughly tested. This means that you can have more confidence in the functionality and reliability of your code, and you can be sure that it is working as intended.

Second, TDD can help you to identify and fix bugs early in the development process. Because tests are written before the code is written, you can catch and fix bugs early on, which can save you time and effort in the long run.

Third, TDD can help you to improve the design of your code. Because tests are written before the code is written, you can use them to guide the design of your code, ensuring that it is modular and easy to maintain.

Investing in TDD can provide many benefits, including improving the quality and reliability of your code, catching and fixing bugs early, and improving the design of your code.


4 Benefits of pair programming

Pair programming is a software development technique in which two programmers work together at one workstation. One programmer writes the code while the other reviews each line of code as it is typed in. This technique has several potential benefits, including:

1. Improved quality

Having two sets of eyes on the code can help identify errors or potential problems that a single programmer might miss. This can result in higher-quality code.

2. Faster development

With two people working on the same code, it can be completed more quickly than if a single person were working on it.

3. Increased knowledge sharing

Pair programming can be an effective way for team members to learn from each other and share their knowledge and expertise.

4. Enhanced collaboration

Pair programming can foster collaboration and communication within a team, as the two programmers must work closely together and communicate effectively in order to complete the task.


Extreme Programming (XP)

Extreme Programming (XP) is a software development methodology that was first introduced in the late 1990s. It is based on a set of core values and principles that are designed to help teams deliver high-quality software in a fast, flexible, and efficient manner.

XP has evolved over time as the software development landscape has changed. Here are a few ways in which XP has advanced:

  • Integration with other methodologies:

    XP has been integrated with other agile methodologies, such as Scrum, to create hybrid approaches that combine the best practices of both methodologies.

  • Evolution of practices:

    Some of the practices that were originally part of XP, such as pair programming and test-driven development, have become widely adopted in the software development industry and are now considered best practices.

  • Emphasis on continuous improvement:

    XP has always placed a strong emphasis on continuous improvement, and this has only become more important as the software development landscape has become more complex and competitive.

  • Focus on delivering value:

    XP has always focused on delivering value to customers, and this focus has only become more important as the software development industry has become more customer-centric.

XP has evolved to meet the changing needs of the software development industry and to better support teams in delivering high-quality software in a fast, flexible, and efficient manner.


Refactoring to improve agility?

Refactoring is the process of improving the design of existing code without changing its behavior. By making the code easier to understand and modify, refactoring can improve the agility of a software development team. This is because refactored code is typically easier to work with and modify, which can make it easier for the team to make changes and add new features as needed.

Additionally, refactoring can help identify and remove code that is no longer needed, which can make it easier for the team to understand the code and focus on the most important parts. This can reduce the time and effort required to make changes, which can improve the team’s ability to respond to changing requirements and priorities.

Refactoring can improve the agility of a software development team by making the code easier to understand and modify, reducing the time and effort required to make changes, and helping the team focus on the most important parts of the code.


How frequently should we be integrating our code?

Agile teams typically integrate their code frequently, often multiple times per day. This is because one of the key principles of agile software development is to deliver working software early and often. By integrating code frequently, teams can ensure that their code works well with the rest of the codebase and that any potential problems are identified and resolved quickly.

Additionally, frequent code integration can help teams avoid large, complex merge conflicts, which can be difficult and time-consuming to resolve. By integrating code early and often, teams can avoid such conflicts and keep their codebase clean and up-to-date.

The frequency of code integration can vary depending on the team and the project, but in general, agile teams tend to integrate their code frequently in order to deliver working software early and avoid complex merge conflicts.


Tips for implementing CICD (Continuous Integration Continuous Deployment)

Some tips for implementing continuous integration and continuous delivery (CICD) include:

  • Automate as much as possible:

    CICD relies heavily on automation, so it is important to automate as many of the steps in the process as possible. This can include automated testing, code quality checks, and deployment processes.

  • Use a version control system:

    In order to manage and track changes to the codebase, it is important to use a version control system, such as Git. This will allow teams to easily collaborate on the code, track changes, and roll back to previous versions if necessary.

  • Set up a dedicated integration environment:

    In order to test and validate code changes, it is important to have a dedicated integration environment where code changes can be tested and deployed. This environment should be isolated from other environments, such as production, to avoid any potential disruptions.

  • Monitor and measure performance:

    In order to ensure that the CICD process is working as expected, it is important to monitor and measure the performance of the pipeline. This can include tracking the number of deployments, the time it takes to complete the pipeline, and any failures or errors that occur.

Implementing CICD can require significant effort and planning, but it can provide numerous benefits, including improved code quality, faster time to market, and increased collaboration and transparency within the development team.


Build core capabilities into your DevOps team

The core capabilities of a DevOps team typically include:

  • Collaboration:

    DevOps teams are typically highly collaborative, with members from different departments (such as development, operations, and quality assurance) working closely together to achieve common goals.

  • Automation:

    DevOps teams often use automation to streamline and accelerate the software development and deployment process. This can include tools for continuous integration, continuous delivery, and infrastructure as code.

  • Monitoring and measurement:

    DevOps teams typically use monitoring and measurement tools to track the performance and reliability of their systems. This can include metrics such as uptime, response time, and error rates.

  • Continuous learning and improvement:

    DevOps teams are typically focused on continuous learning and improvement, using data and feedback to identify areas for improvement and implement changes to improve the process.

The core capabilities of a DevOps team typically include collaboration, automation, monitoring and measurement, and continuous learning and improvement.


What drives the integration of security capabilities with DevOps workflows?

Security was added to DevOps because as organizations began to adopt DevOps practices, they realized that the rapid iteration and deployment of code made it more important than ever to ensure that the code and systems were secure. DevOps emphasizes collaboration and communication between teams, and this also applies to security. By including security as a core part of the DevOps process, organizations can ensure that security is considered at every stage of the development and deployment process, from design and implementation to testing and deployment.

Additionally, the focus on automation and continuous delivery in DevOps means that security controls must be automated and integrated into the overall process. This allows organizations to deploy code and systems securely and efficiently, without sacrificing speed or agility.

DevSecOps incorporates security practices and tools into the continuous integration, continuous delivery, and continuous deployment processes, with the goal of ensuring that code and systems are secure throughout the development and deployment process.

By incorporating security into the DevOps process, DevSecOps aims to reduce the time and effort required to implement and maintain secure systems, while also improving the security of the code and systems. This can be achieved through a combination of automation, collaboration, and continuous learning and improvement.


3 Tips for creating an agile architecture?

Agile architecture is a software development approach that focuses on creating flexible and adaptable architectures that can support the rapid iteration and evolution of software. In contrast to traditional architecture approaches, which often involve extensive upfront planning and design, agile architecture emphasizes iterative and incremental development, with a focus on delivering working software quickly and adapting to changing requirements and priorities.

Agile architecture typically involves a number of practices and principles, including:

1. Collaboration

Agile architecture emphasizes collaboration between teams, with members from different disciplines (such as development, operations, and architecture) working together to achieve common goals.

2. Incremental development

Agile architecture typically involves iterative and incremental development, with small, frequent releases of working software. This allows teams to quickly adapt to changing requirements and priorities.

3. Flexibility and adaptability

Agile architecture focuses on creating architectures that are flexible and adaptable, so that they can support the rapid evolution of software. This may involve the use of modular and component-based design approaches.

Agile architecture is a software development approach that focuses on creating flexible and adaptable architectures that can support the rapid iteration and evolution of software. It emphasizes collaboration, incremental development, and flexibility and adaptability.


Benefits of microservices in agile architecture

Microservices are a software architecture approach in which a single application is built as a suite of small, independent services. This approach has several potential benefits when used in an agile software development context, including:

  • Improved flexibility and scalability:

    Because each microservice is independently deployable, teams can more easily modify and evolve individual services without impacting the rest of the system. This can improve the overall flexibility and scalability of the application.

  • Enhanced collaboration:

    Microservices can make it easier for teams to collaborate, as each service can be developed and maintained by a separate team. This can reduce the complexity of the overall codebase and make it easier for teams to work together.

  • Faster time to market:

    By breaking down a large application into smaller, independent services, teams can develop and deploy new features and capabilities more quickly. This can help organizations to respond to changing market conditions and customer needs more quickly.

  • Improved resiliency:

    Because each microservice is independently deployable and scalable, a microservices architecture can make it easier to build resilient systems that can continue to operate even if individual services fail. This can improve the overall reliability and availability of the application.

The use of microservices in an agile development context can provide numerous benefits, including improved flexibility and scalability, enhanced collaboration, faster time to market, and improved resiliency.


What does building in quality mean?

Building quality into code means that quality is considered and incorporated at every stage of the development process, from design and implementation to testing and deployment. This means that agile teams should focus on writing high-quality code that is well-structured, maintainable, and efficient.

In an agile context, building quality into code also means that teams should prioritize activities that help to improve the quality of the code, such as writing automated tests, performing code reviews, and implementing static analysis tools. This can help to identify and fix potential problems early in the development process, which can save time and effort in the long run.

Additionally, building quality into code in an agile context means that teams should focus on continuous learning and improvement. This can involve regularly reviewing the codebase and identifying areas for improvement, as well as implementing processes and tools that can help to improve the quality of the code over time.

Building quality into code means that quality is considered and incorporated at every stage of the development process, and that teams should prioritize activities that help to improve the quality of the code. This can help to produce high-quality software that is maintainable, efficient, and meets the needs of users.


Developing your own definition of done

Some tips for developing a good definition of done for an agile team include:

  • Keep it simple and clear:

    The definition of done should be clear and concise, so that all team members understand what is required to consider a task complete.

  • Include all necessary criteria:

    The definition of done should include all of the necessary criteria that a task must meet in order to be considered complete. This may include testing, documentation, and code review requirements, among others.

  • Make it specific to the team:

    The definition of done should be specific to the team and the project, and should reflect the team’s processes, practices, and goals.

  • Revisit and update it regularly:

    The definition of done should be reviewed and updated regularly, as the team’s processes and goals evolve over time. This can help to ensure that the definition of done remains relevant and effective.

Developing a good definition of done for an agile team requires clarity, specificity, and regular review and update. By following these tips, teams can ensure that their definition of done is effective and supports the team’s goals and processes.


5 Tips for hosting a hackathon

A hackathon is an event in which people come together to collaborate on and develop software projects within a short time frame, often over the course of a day or a weekend. If you are planning to host a hackathon, there are several key steps you should follow, including:

1. Define the theme and goals of the hackathon

Before planning the event, it is important to define the theme and goals of the hackathon. This can help to focus the participants’ efforts and ensure that the event is successful.

2. Identify sponsors and partners

Hackathons typically require funding and support from sponsors and partners in order to be successful. It is important to identify and secure sponsors and partners who can provide the necessary resources and support for the event.

3. Plan the logistics

Once the theme and goals of the hackathon have been defined, the next step is to plan the logistics of the event. This can include securing a venue, arranging for food and refreshments, and setting up any necessary equipment or infrastructure.

4. Promote the event

In order to attract participants and generate interest in the hackathon, it is important to promote the event. This can include creating a website, sharing information on social media, and reaching out to potential participants and partners.

5. Coordinate the event

On the day of the hackathon, it is important to coordinate the event to ensure that everything runs smoothly. This can include managing the schedule, facilitating collaboration among participants, and providing support and assistance as needed.

Hosting a hackathon requires careful planning and coordination, but it can be a rewarding and valuable experience for participants and organizers alike. By following these steps, you can help to ensure that your hackathon is successful and achieves its goals.


3 Pros and Cons of mob programming

Mob programming is a software development approach in which a group of people work together at a single workstation to develop code. While this approach has its supporters, it also has its critics. 

Some potential benefits of mob programming include:

1. Improved collaboration

Mob programming can foster collaboration and communication within a team, as all members are working together on the same task. This can help to ensure that everyone is on the same page and working towards the same goals.

2. Faster development

With multiple people working on the same code, tasks can be completed more quickly than if a single person were working on them. This can help teams to deliver working software more quickly.

3. Increased knowledge sharing

Mob programming can be an effective way for team members to learn from each other and share their knowledge and expertise. This can help to improve the overall skill level of the team.

However, there are some potential drawbacks of mob programming. The cons of mob programming include:

1. Inefficiency

With multiple people working on the same code, it can be difficult for everyone to stay focused and avoid distractions. This can lead to inefficiency and lower productivity.

2. Lack of individual ownership

In a mob programming situation, it can be difficult for individual team members to take ownership of their work and feel responsible for the quality of the code. This can lead to a lack of accountability and motivation.

3. Difficulty scaling

Mob programming can be difficult to scale, as it requires a large number of people to be working on the same task at the same time. This can make it challenging to apply the approach to larger projects or teams.

Whether mob programming is good or not depends on the specific situation and the goals of the team. While it can provide some potential benefits, it also has some potential drawbacks that should be considered.


What is Business Driven Development (BDD)?

Business-driven development (BDD) is an approach to software development that focuses on aligning the development process with the business goals and needs of the organization. BDD is typically used when the organization has a clear understanding of its business objectives, and when the development team needs to deliver software that will help the organization achieve those objectives. BDD can be particularly useful when the organization is facing a rapidly changing market, or when it needs to quickly develop and deliver new software to respond to changing customer needs. By using BDD, organizations can ensure that their software development efforts are aligned with their business goals, and that they are delivering value to their customers.


5 Tips for speeding up code reviews in agile teams

Code reviews are an important part of agile development, but they can also be time-consuming. Here are some tips for speeding up code reviews in an agile environment:

1. Set clear expectations

Communicate the team’s standards and expectations for code reviews, and ensure that all team members are aware of these expectations. This can help to avoid misunderstandings and unnecessary delays.

2. Use automated tools

Use automated tools, such as code quality checkers and linters, to quickly identify potential issues with the code. This can save time and effort by allowing the team to focus on more complex or important issues.

3. Prioritize critical issues

Focus on the most critical or important issues first, and prioritize these over less important or minor issues. This can help to ensure that the most important issues are addressed quickly, without getting bogged down in less important details.

4. Use pair programming

Use pair programming, where two team members work together on the same code, to facilitate real-time feedback and collaboration. This can help to speed up the code review process by allowing for immediate feedback and collaboration.

5. Limit the scope of the review

Limit the scope of the code review to the most relevant and important parts of the code. This can help to avoid unnecessary or tangential discussions, and can speed up the review process.

By using these tips, teams can speed up their code review process and ensure that code is reviewed and feedback is provided in a timely and efficient manner. This can help to improve the quality of the code and support the team’s overall agile development process.


Agile methods for code reviews

Code reviews are an important part of the software development process, as they help to ensure that code is of high quality and meets the standards and requirements of the project. Here are a few agile ways to conduct code reviews:

Use a lightweight, iterative process

Instead of conducting a lengthy, formal code review process, consider using a more lightweight, iterative approach. This might involve reviewing small chunks of code as they are developed, rather than waiting until a feature is complete. This can help to identify issues early and make it easier to make necessary changes.

Involve the entire team

Code reviews don’t have to be limited to just developers. Consider involving other team members, such as testers or business analysts, in the review process. This can help to ensure that all perspectives are considered and can lead to a more holistic view of the code.

Use automation

There are tools and services available that can automate parts of the code review process, such as checking for style issues or identifying potential bugs. Using these tools can save time and help to ensure that code meets certain standards.

Encourage open, respectful communication

Code reviews can be an opportunity for team members to learn from one another and improve their skills. Encourage open, respectful communication during code reviews, and focus on finding solutions rather than assigning blame.

By following these agile principles, code reviews can be an effective and efficient part of the development process, helping to ensure that code is of high quality and meets the needs of the project.


What engineers new to agile development should know

Agile development is a collaborative and iterative approach to software development, and engineers play a crucial role in this process. Here are some tips for engineers who are working on agile teams:

  • Understand the agile framework:

    Familiarize yourself with the principles and practices of agile development, and understand how they apply to your work on the team.

  • Collaborate with the team:

    Work closely with other team members, including product owners, Scrum Masters, and other engineers, to share information, provide feedback, and collaborate on solutions.

  • Prioritize flexibility:

    Be willing to adapt to changes in priorities and requirements, and be open to new ideas and approaches.

  • Focus on quality:

    Strive to produce high-quality code that meets the team’s standards and practices, and take the time to review and improve your work.

  • Communicate effectively:

    Communicate clearly and effectively with other team members, and be responsive to feedback and suggestions.

By following these tips, engineers can effectively contribute to the success of their agile teams, and can help to ensure that the team produces high-quality software in a collaborative and iterative manner.


Steps for spending less time on bug fixing

If an agile team is spending too much capacity on fixing bugs, it can negatively impact their ability to make progress on new development and innovation. Here are some steps that can be taken to address this issue:

  • Identify the root cause:

    The first step is to identify the root cause of the high number of bugs. This may involve conducting a root cause analysis to identify the underlying issues that are contributing to the problem.

  • Prioritize bug fixes:

    Once the root cause has been identified, prioritize the most important and time-sensitive bug fixes, and allocate sufficient capacity to address these issues.

  • Improve testing practices:

    Another approach is to improve the team’s testing practices, in order to identify and fix bugs earlier in the development process. This can involve implementing more rigorous testing procedures, such as automated testing, to catch and fix bugs before they reach production.

  • Refactor the code:

    In some cases, the high number of bugs may be due to poorly designed or poorly written code. In these situations, it may be necessary to refactor the code to improve its quality and reduce the number of bugs.

  • Invest in training:

    Finally, investing in training and development for team members can help to improve their skills and knowledge, and can ultimately lead to fewer bugs and better-quality code.

Addressing the issue of too much capacity being spent on bug fixes requires a combination of identifying and addressing the root cause, improving testing practices, and investing in training and development. By taking these steps, teams can reduce the number of bugs and improve their ability to make progress on new development and innovation.


Do your teams have collective code ownership?

Collective code ownership is a software development practice in which all members of a team have equal responsibility and accountability for the codebase. This means that any team member can make changes to any part of the code, and is responsible for ensuring that the code meets the team’s standards and practices.

Collective code ownership has several advantages over more traditional approaches to code ownership. First, it promotes collaboration and teamwork among team members, as everyone is responsible for the quality and maintainability of the codebase. This can help to foster a sense of shared ownership and accountability, and can lead to better outcomes for the team and the project.

Second, collective code ownership can also help to improve the quality and maintainability of the code. By allowing all team members to make changes to any part of the code, the team can benefit from a wider range of perspectives and expertise. This can lead to more robust and well-designed code, and can ultimately lead to better outcomes for the project.

Third, collective code ownership can also support agile development practices, such as continuous integration and continuous delivery. By allowing all team members to make changes to the code, the team can more easily integrate new features and updates into the codebase, and can more quickly deliver new versions of the software to customers.

Collective code ownership is a valuable practice that can support collaboration, improve the quality and maintainability of the code, and support agile development practices. By adopting this approach, teams can benefit from the collective expertise and perspectives of all team members, and can ultimately deliver better outcomes for the project.


Facing a complex engineering challenge? – Use a Spike!

In agile software development, a spike is a time-boxed investigation into a specific technical issue or problem. The goal of a spike is to gather information and explore possible solutions to the issue, in order to provide the team with a better understanding of the problem and potential approaches to addressing it.

Spikes are typically used when the team is facing an uncertain or complex technical challenge, and needs more information in order to make informed decisions about how to proceed. For example, a spike might be used to explore a new technology or approach, or to conduct a proof of concept for a particular solution.

To use a spike, the team first identifies the specific technical issue or challenge that they are facing. The team then sets a time box for the spike, typically ranging from a few hours to a few days, depending on the complexity and scope of the issue. During the spike, the team members who are working on the spike focus exclusively on exploring the issue and gathering information, without being interrupted by other work.

At the end of the spike, the team reviews the information and insights that have been gathered, and uses this information to make informed decisions about how to proceed. This may involve selecting a specific solution to implement, or deciding to conduct additional spikes to explore other options.

Spikes are a valuable tool for agile teams that are facing complex or uncertain technical challenges. By providing a focused and time-boxed investigation into these challenges, spikes can help teams to gather the information and insights they need to make informed decisions and move forward with confidence.


When does manual testing still provide value?

Manual testing is still required for software in some cases, even when automated testing tools are available. There are several situations where manual testing may be necessary, including the following:

  • Exploratory testing:

    Manual testing can be useful for exploratory testing, where the goal is to test the software in an unstructured and open-ended manner. This can help to identify unexpected or hidden issues with the software, and can provide valuable insights into its behavior and functionality.

  • Usability testing:

    Manual testing can also be useful for usability testing, where the goal is to evaluate the user experience of the software. This can involve testing the software with real users, and observing how they interact with the software in order to identify areas for improvement.

  • Regression testing:

    In some cases, manual testing may be necessary for regression testing, where the goal is to ensure that changes to the software have not introduced new bugs or issues. This can be particularly important when changes to the software have a significant impact on its behavior or functionality, and automated testing may not be able to adequately cover all scenarios.

While automated testing can be a valuable tool for software development, there are still some situations where manual testing is necessary. By considering the specific needs and circumstances of the project, teams can determine when manual testing is required, and can use it effectively to improve the quality and functionality of the software.


Do you know how to Toggle?

Toggles, also known as feature flags or feature switches, can help agile teams in several ways. First, they allow teams to quickly and easily enable or disable specific features or functionality without having to do a full deployment. This can be useful for testing new features or for rolling back changes that cause problems.

Second, toggles can help teams experiment and test different variations of a feature to see which one performs best. This can be done through A/B testing, where different versions of a feature are shown to different users, and the team can then analyze the results to determine which version is most effective.

Third, toggles can help teams manage the deployment of complex features that may take a long time to develop and test. By using toggles, teams can gradually roll out the feature to a small group of users, monitor its performance, and then gradually expand its use to more users. This can help teams avoid the risks associated with deploying a complex feature to all users at once.

Toggles can help agile teams be more flexible and responsive to changing needs, and can make it easier to test and deploy new features and functionality.


Coping with change control in an agile environment

Control boards and change approval boards are processes that are used to review and approve changes to a project or product. In an agile environment, these processes can slow down the development and deployment of new features and functionality because they add an additional layer of review and approval that must be completed before a change can be made.

To address this, teams can take a number of steps to streamline control boards and change approval boards without sacrificing the benefits of having a review and approval process in place. For example, teams can:

  • Set clear criteria for what types of changes require review and approval, and which ones can be made without going through the control board or change approval board.

  • Use automated tools to help manage the review and approval process, which can speed up the flow of information and reduce the need for face-to-face meetings.

  • Establish clear roles and responsibilities for members of the control board or change approval board, and ensure that they have the necessary training and support to do their jobs effectively.

  • Regularly review and evaluate the effectiveness of the control board or change approval board, and make changes as needed to improve their efficiency and effectiveness.

It is important for teams to strike a balance between the need for review and approval processes and the need for agility and speed in an agile environment. By taking a proactive and thoughtful approach to managing control boards and change approval boards, teams can minimize their impact on agile development without sacrificing the benefits they provide.


6 Easy steps to replace your monolith incrementally

Here are some tips for replacing your monolith incrementally:

  1. Start by identifying the parts of your monolith that can be replaced first. This could be a standalone component or a group of related components that can be extracted and replaced without disrupting the rest of the monolith.

  2. Create a plan for how you will extract and replace the selected components. This should include details about the technologies and approaches you will use, as well as any dependencies or challenges you may encounter.

  3. Communicate your plan to the rest of your organization and get buy-in from key stakeholders. This will help ensure that everyone is on board and understands the implications of the changes you’re making.

  4. Begin extracting and replacing the selected components according to your plan. This should be done carefully and incrementally, to minimize disruption and ensure that the monolith continues to function properly during the transition.

  5. Monitor and test the extracted components to ensure they are functioning properly and meeting the organization’s needs. This will help you identify any issues or challenges that need to be addressed before proceeding with the next phase of the replacement.

  6. Continue extracting and replacing components until the entire monolith has been replaced. This may take some time, depending on the size and complexity of your monolith, but the end result will be a more modular, scalable, and maintainable system.

By following these steps, you can replace your monolith incrementally and minimize the disruption and risk associated with such a major change. This will help ensure a successful transition and enable your organization to reap the benefits of a more modular, agile architecture.


Have you implemented continuous testing?

In the Agile software development approach, continuous testing is the practice of integrating testing activities into the development process in a way that allows teams to identify and fix defects as early as possible in the development lifecycle. This approach helps teams to deliver high-quality software faster and with fewer defects, as testing is integrated into the development process rather than being treated as a separate phase.

Continuous testing typically involves the use of automated testing tools and techniques, such as unit tests, integration tests, and functional tests, to ensure that the software is working as intended at all times. This can include running tests continuously in the background as code is being developed, as well as running tests before and after code is deployed to production.

One key benefit of continuous testing is that it helps teams to catch defects early in the development process, when they are easier and less expensive to fix. This can significantly reduce the time and effort required to fix defects, and it can also help to improve the overall quality of the software. Additionally, by integrating testing into the development process, teams can get faster feedback on the quality of their software, which can help them to identify and address issues more quickly.


Heat Mapping – where is your software system fragile?

Heat mapping is a technique that can be used to visually represent the distribution and intensity of defects in a software system. This is typically done by creating a heat map that represents different parts of the system using different colors, with warmer colors indicating a higher concentration of defects.

Heat mapping engineering defects can help in a number of ways. First, it can provide a visual representation of the distribution and intensity of defects in the system, which can help teams to identify areas of the system that may be more prone to defects. This can be particularly useful for identifying patterns or trends that may not be immediately apparent from looking at individual defects.

Second, heat mapping can help teams to prioritize their efforts by identifying areas of the system that are most in need of attention. For example, if a particular component of the system has a high concentration of defects, it may be a good candidate for further investigation or refactoring.

Finally, heat mapping can help teams to track the progress of their efforts to reduce defects over time. By comparing heat maps from different points in time, teams can see if their efforts are having the desired impact and make adjustments as needed.


Addressing Software Fragility

In software development, “fragility” refers to the susceptibility of a system to break or malfunction when changes are made to it. A fragile system is one that is prone to unexpected errors or failures when modifications are made, even if those changes are minor or unrelated to the parts of the system that are breaking.

Fragility can be caused by a variety of factors, including poor design, a lack of testing, and a lack of separation between different components of the system. It can also be caused by a lack of modularity, where changes to one part of the system have unintended consequences on other parts of the system.

To address fragility in software, it is important to design systems with modularity and separation of concerns in mind, and to thoroughly test the system to ensure that it is robust and can withstand changes. It is also important to continuously monitor and maintain the system to identify and fix any potential issues that may arise.


Long-term application supportability

There are several reasons why software systems can become difficult to support over time. Some common reasons include:

Lack of documentation:

If the software system was not well-documented, it can be difficult for support staff to understand how the system works and how to troubleshoot problems.

Complexity:

Complex software systems can be more difficult to support because they may have many different components and integrations, making it harder to identify and fix issues.

Outdated technology:

As technology advances, software systems that rely on older technologies may become more difficult to support because the necessary skills and resources may no longer be readily available.

Customization:

Customized software systems can be more difficult to support because they may be unique and not well-understood by support staff.

Poor quality:

Poorly-designed or implemented software systems can be more difficult to support because they may be prone to errors and glitches, making it harder to identify and fix issues.

It’s important for organizations to carefully consider the long-term supportability of software systems when choosing and implementing them, in order to minimize the difficulties and costs associated with supporting them over time.


Get specific about NFRs

Non-functional requirements (NFRs) are software requirements that specify how a system should behave, rather than what it should do. They describe the system’s quality attributes, such as reliability, performance, security, and usability. Here are some examples of non-functional requirements for software:

1. Performance

This includes requirements related to the speed, efficiency, and scalability of the system. Examples might include response time goals for specific actions, the maximum number of users the system can handle, and the ability to scale up or down as needed.

2. Security

These are requirements related to protecting the system and its data from unauthorized access or tampering. Examples might include requirements for encryption, authentication, and access control.

3. Usability

These are requirements related to the ease of use and understandability of the system. Examples might include requirements for user-friendly interfaces, clear error messages, and the ability to easily navigate the system.

4. Reliability

These are requirements related to the stability and dependability of the system. Examples might include requirements for uptime, the ability to recover from errors or failures, and the ability to handle unexpected input or conditions.

5. Maintainability

These are requirements related to the ease of maintaining and updating the system over time. Examples might include requirements for clear documentation, modular design, and the ability to easily test and deploy changes.

Non-functional requirements are important because they ensure that the system meets the quality standards that are necessary for it to be effective and usable.


DevOps is the Backbone of Agile

DevOps is a set of practices that aims to improve collaboration and communication between software development and operations teams, with the goal of delivering software more frequently and reliably. It is often considered the backbone of agile because it supports and enables the principles and practices of agile development.

One of the key benefits of DevOps is the ability to deliver software quickly and frequently, which is a key aspect of agile development. By automating many of the processes involved in software delivery, DevOps enables teams to iterate and deploy code faster, which allows for faster feedback and the ability to respond to changing business needs.

In addition, DevOps promotes a culture of collaboration and continuous improvement, which is essential for agile teams. By bringing development and operations teams together and fostering a culture of continuous learning, DevOps helps teams to identify and eliminate bottlenecks, improve efficiency, and deliver value to customers more quickly.

DevOps is a key aspect of agile development because it enables teams to deliver software faster, more reliably, and with higher quality, which is essential for organizations that are looking to respond to changing business needs in a flexible and efficient manner.


Help your application support team establish classes of service

An application support team could use classes of service to prioritize and manage the work that they do. By establishing different classes of service, the team can ensure that they are focusing their efforts on the most important and urgent tasks first, while still addressing lower-priority tasks as time allows.

To use classes of service, the application support team would need to define the criteria for each class of service, such as the severity of the issue, the impact on users, or the urgency of the request. They could then use these criteria to assign incoming requests to the appropriate class of service.

For example, the team might define a “critical” class of service for issues that are preventing users from accessing the application, a “high” class of service for issues that are impacting a large number of users or have a significant impact on business operations, and a “low” class of service for issues that are minor or have a limited impact on users.

The team could use different visual indicators, such as different colors or shapes of cards or stickers, to represent the different classes of service and help them prioritize their work. They might also use a kanban board or other tool to visualize and manage the work in their workflow.

Using classes of service can help the application support team to be more efficient and effective in their work, by ensuring that they are addressing the most important issues first and providing a clear understanding of the priority of each task.

Read More

Topics: Agile Technical Practices

ICON Agility Services named a 2022 Top Workplace

Posted by Sawyer Conrady on January 12, 2023

July 8, 2022

ICON Agility Services was awarded a 2022 Top Workplaces honor by The St. Louis Post Dispatch and STLtoday. All winners were featured in a special section on Sunday, June 26, and online at STLtoday.com. The list is based solely on employee feedback gathered through a third-party survey that measures 15 culture drivers critical to the success of any organization. This award comes authentically from our team, they were given a voice to be heard, and we are honored and proud of the results.

We sat down and chatted with our recruitment department to share insight into our culture and recruitment process. In this brief interview, we learn what they look for when recruiting a new coach or team member, the steps to the hiring process, their opinions on why we made the Top Workplaces list, and why they love recruiting top talent for ICON.

Ed Barber

I have been with ICON for 23 years. There are many reasons for this, but the main reason, I think, is the people I get to work with. From the people in the home office that keep the company running and, most importantly, working with clients to identify my next opportunity to the awesome consultants they bring together for each client engagement. They treat me like a family member, not just a “resource.”

Question: Agile Transformation Coaches, on average, stay with ICON for 10+ years. Why do you think that is?

MB: Easy! We don’t view them as resources but as what they are. Talented human beings with unique skillsets! When I’m on the phone with someone, I know they just got it when they give me an “I remember this one time…” So if anybody hits me with that, I listen! I’ll start to notice if the story matches one of our client’s Transformation needs, and when I can begin to create a match, it’s a win-win situation for all parties involved! It’s not about the hours and how many days – it’s about elevating someone and helping them find something they love so they never have to work.

BL: When you work at ICON, you are more than a number. We see you as an individual with endless potential and want to help you succeed! When ICON demonstrates this people-oriented mentality, coaches don’t want to leave. We offer lasting relationships.

Question: What qualities do you look for when searching for a new Coach?

MB: I look for empathetic, optimistic, and enthusiastic people every time I take a call. We all have to play the game and be professional, but on the flip side, everyone needs a chance to be themselves. These characteristics are crucial for Transformation efforts. It creates a rich working culture and successful relationships.

BL: We look for outgoing, passionate, and people-oriented individuals.

Question: What is ICON’s Typical Recruitment Process?

Because we are a senior-level SAFe/Agile coaching firm, our team thoroughly assesses background, seniority, and experience. In addition, we complete several interviews to determine culture fit and past experiences that might fit within an ICON client’s transformational journey.

2022 Top Workplaces

  1. Contact for an initial conversation with our recruitment team begins with a submitted resume. Submissions come directly from the website, referrals from current ICON Coaches, or LinkedIn outreaches. Once the resume has been reviewed for relevant experience (typical ICON Transformation Coaches have 10+ years), a recruitment team member will reach out and initiate the first conversation. Applicants should expect a more “laid back” type of conversation – Mike and Blake want to learn about them and their passions and make sure they find the right fit for our client and the candidate.
  2. After the initial conversation, a vetting process and the first technical interview with an experienced ICON Coach will begin. The first technical interview will dive deeply into the candidate’s past roles and responsibilities. In addition, this interview is an opportunity for potential candidates to network with current ICON experts.
  3. The third interview will occur with the ICON client’s Lead Transformation Coach. When connected for this second round, the ICON Lead will share information based on the overall project, how mature in SAFe the client is, and the expectations for the role. In addition, they will get a sense of the candidate’s ability to adapt to the current climate.
  4. The final conversation will be between the account lead and the potential candidate (recruitment will continue to stay as active as possible). Through this discussion, we will establish the final Terms of Agreement.
  5. With the candidate’s approval, ICON will submit them to the client. Once submitted, the candidate will follow the procedures and policies of our client’s interview processes. ICON Agility will continue to act as the candidate’s advocate the entire step of the way!

Question: What brought you to ICON?

MB: My professional journey began as a school teacher, where I was passionate about creating communities of learners and good humans. In 2018, I interviewed with ICON Agility Services and became the recruitment lead. My passion as a teacher helps me present the best possible candidates for ICON’s clients.

BL: I have a passion for helping individuals grow. ICON is a leader in the world of Scaled Agile, but also in building relationships. I love building relationships and assisting individuals in growing their career paths. ICON allows me to help individuals grow as we grow together!

Question: What do you love the most about your job as an ICON recruiter?

MB: Recruiting at ICON has been nothing short of rewarding! Each day I meet people worldwide who bring unique skills to the table. ICON encourages me to empathize with each person and emphasize the importance of finding the perfect career path to fit their specific skill set. Finding the approach that works best for our coaches is essential to ICON. We have open discussions with each individual to ensure we meet their expectations. Through these conversations, we can determine how to work with one another, allowing all parties involved to align in the best ways possible for everyone to benefit! Open communication has significantly reduced our candidates’ stress levels. They feel they can take control of their life and know they will be able to make massive impacts on all of ICON’s clients. The team is always pleased to meet people where they are and be an advocate for them. This approach has grown our success and allows us to draw in top talent!

BL: I love meeting so many people worldwide, all with different stories, journeys, and paths. It’s such a blessing every day to get to know all the people I talk to and help them grow in their careers!


ICON Agility Services would like to thank our coaches and team members for making us a Top Workplace of 2022.

If you are interested in learning more about ICON Agility Services and joining our worldwide team of Agile Leaders, email Mike Bellinger or Blake Lawson at recruiting@iconagility.com for more information about our open opportunities.

In management science, there is a concept referred to as “conditioning your audience,” meaning that people tend to behave to the level of your expectations. As you send subtle, subconscious messages, your audience can become “trained” in a certain behavior. For example, if you treat someone like a child, then this person will likely begin acting like one. Without respectful but assertive dialog, you wind up “training” your leadership to walk all over you. They will keep asking you to do things, because you tend to say “Yes.” The better option is to engage and provide context. The results will surprise you.

Read More

Free ICON Maturity Assessment Tool for your SAFe® Transformation

Posted by Sawyer Conrady on January 12, 2023

Apr 15, 2019

Let’s consider a common request from Agile Transformation teams and PMO offices: Have you assessed the Agile maturity of your teams?

This seems like a reasonable ask—after all, the teams are the ones responsible for creating the shippable software every two weeks. But do team-based metrics tell the whole story?

Now consider this: Is it possible for teams (even high performing teams) to be limited by the Agility of their executives, stakeholders, managers, and shared services?
The answer is a resounding yes. The software development teams might be Agile, but if the business is still in project mentality with expectations of Big Bang delivery and no measurable outcomes for the value of their ideas…then, realistically, how far can a SAFe® transformation get?

Well, we’ve got good news: ICON has a tool that not only allows the teams to assess their own Agile maturity, but also the maturity of their SAFe ecosystem. With the right assessment at your disposal, you can easily evaluate the teams, the ART, and the SAFe transformation—all without complicated tools or expensive subscriptions.

Download ICON’s free Excel assessment, and we’ll walk through how to use it right now in this very blog post (although the assessment also includes an instructions tab). When we’re done, you’ll know exactly how to conduct an assessment that shows the maturity of both the team practices and the SAFe transformation. Ready? Let’s dive in.

***Keep in mind that this should be a lightweight tool, used to inform on the maturity of the SAFe transformation; not to compare team performance.

 

Step 1: Identify participants, including the Lean Portfolio Management Team and System Team

When you identify teams to participate, think beyond software development teams. Include the Lean Portfolio Management team, Program Team, System Team, and shared services teams.

Agile Release Train

Also decide if the transformation coaches will be asked to assess the teams. There is a separate column in the spreadsheet for the coach of each team.

Step 2: Determine how to gather Assessment Responses

Will you survey individuals or have facilitated team discussions? Read on to learn the benefits and best practices for each choice.

Team Discussion Facilitated by Scrum Master or Release Train Engineer

One of the benefits of team discussion is that people may discover things they were previously unaware of, and this newfound knowledge may inform their assessment.

If you choose a team discussion, set aside 1-2 hours of uninterrupted time in a location where the team members can speak freely. The Scrum Master, Release Train Engineer, or another team member may facilitate the discussion.

Don’t go down rat holes; keep the conversation moving to reach a consensus and make it a point to hear everyone’s voice. You may capture backlog items for improvement or risks to be escalated, but the primary purpose of the assessment is to take the temperature, not diagnose the problems.

Agile for All has an excellent description of how to use Fist-of-five voting to reach consensus.

Fist-of-Five Voting

If the team is distributed, use an online tool so that everyone can vote and then discuss and settle on a number. PointingPoker.com can be customized for numbers 1,2,3,4, and 5, and usually everyone can access it from a smartphone or computer.

Many online meeting tools such as WebExZoom and Skype also have polling features that can be setup in advance with the choices 1, 2, 3, 4, and 5.

Individual Survey Responses

If you decide to survey individuals, you will still aggregate their answers into one team response for each question on the assessment, so it is important to identify which team the respondent belongs to.

Tools like Google Forms or Survey Monkey may be used to send out the assessment, or you may copy A1:E26 from Health Check tab into a separate spreadsheet, and email it to your participants.

 

Step 3: Get everyone onboard with a SAFe® Maturity Assessment

Communicate the purpose of the assessment with the participants in advance so they can understand why it is important for them to participate.

Here is an example message that can be sent out in advance. Be sure to customize it for your organization and situation:

In an effort to understand the progress of our SAFe® transformation, we are asking several teams to participate in a short assessment. Some teams will complete the assessment as a group; others may do individual surveys and collate them into a team response.

We are on a transformation journey; we are stopping for a moment to check our compass and landmarks, to see where we are along the way, so we know how far we have com and how far we still need to travel. This will allow us to make any necessary course corrections.

The Agile Transformation Team wants to understand the reality of the transformation so we can provide practical and useful coaching to address our needs. We will be sharing the results with the teams who participate and <names of people who will get results>.

If you have questions, please contact <name of person to contact>.

Thank you in advance for your participation.

Step 4: Capture the Results

If the assessment is a facilitated discussion, the results can be entered into the team column of the Health Check tab of the spreadsheet.

If individuals are surveyed, the results of each team should be collated and the average response for each item should be recorded in the team column of the Health Check tab of the spreadsheet.The radar charts for the team tabs will automatically be updated as the numbers are filled in on the Health Check tab.

Health Check

 

The SAFe Transformation Coach for each team should put their responses in the Coach column of the Health Check tab of the spreadsheet.

Coaches tab

The Combined tab puts all of the team results on a single radar, and averages the coach’s responses into one response line.

Combined

 

Step 5: Review the Results for the Entire Agile Release Train

The results should be reviewed with the teams who participated and with the stakeholders who were previously identified. Below is an example of what the results might look like.

 

ICON Assessment tool for SAFe Transformation

 

The combined view may show that some teams are farther along on their transformation journey, or they may be quite similar. Results may depend on when the teams started, how much training and coaching they have received, whether they are co-located or distributed. The results show opportunities for growth and successes to be emulated to other parts of the organization.

Early in SAFe transformation journey, teams tend to think they are much farther along than their coaches think they are. Agile transformation is not unlike growing up—when we are young children, we know we have a lot to learn; when we are in our teens and 20s, we know everything; in our 30s and 40s, we realize we still have more to learn.

 

Step 6: Use Newfound Insights to Create Strategies for the Coaching Backlog

This assessment is not about how well your teams execute Scrum or Kanban, but a way to measure the maturity of the SAFe transformation. The assessment results should stimulate conversations about how to mature weak areas and ensure that strong areas continue to thrive and become part of the culture. These insights will become part of the coaching backlog.

Assessments without follow-on coaching produce little value; signing up for a SAFe Transformation is like joining a gym without a trainer to show you how to use the equipment. You can guess, but you’re probably not performing the exercises well enough to obtain the maximum value—or you might even hurt yourself. ICON’s experienced coaches can help you accelerate change and realize the promises of Agile and SAFe.

 

Other SAFe® Assessment Tools

This tool has been developed by our coaches through years of experience working with clients on SAFe transformations. We also customize assessments for our clients. Of course, there are other tools available which may also serve your needs. We also recommend SAFe® Metrics, which are freely available; and AgilityHealth® Radars are a paid option that ICON coaches are certified to facilitate.

If you are unsure about which tool is right for you, don’t hesitate to contact us. ICON specializes in meeting you where you are, gathering the full picture of your situation before offering guidance.

Written by Susan K. Strain

 

Susan is an Agile Transformation Coach who works with clients implementing Agile practices that span the enterprise. She coaches and trains Agile principles and methodologies, including Enterprise Business Agility Strategy, Scrum, Kanban, and the Scaled Agile Framework (SAFe). She has experience with clients in a wide variety of industries including banking, financial, government, hospitality, insurance, investments, manufacturing, military, publishing, and retail.

 

Read More

SAFe® Benefits

Posted by Sawyer Conrady on January 12, 2023

Need help with Agile or SAFe? CLICK HERE to speak to an expert today!


SAFe Agile Improves Time to Market

There are several ways that organizations can accelerate their time to market. Some of these include:

  • Adopting agile methodologies, which can help teams to quickly and efficiently deliver high-quality products or services.

  • Investing in automation and other technologies that can help teams to work more efficiently and reduce the amount of time required to complete key tasks.

  • Collaborating with customers and other stakeholders to ensure that the team has a clear understanding of their needs and priorities, and can focus on delivering the most valuable features and functionality first.

  • Prioritizing speed and agility over perfection, and being willing to iterate and improve products and services over time.

  • Breaking large projects down into smaller, more manageable pieces and delivering them incrementally, which can help teams to stay focused and avoid getting bogged down in complex and time-consuming tasks.

  • Investing in training and development for team members, to ensure that they have the skills and knowledge they need to work efficiently and effectively.

Organizations that are looking to accelerate their time to market should focus on adopting agile methodologies, investing in technology and automation, and fostering collaboration and continuous improvement within their teams. By taking these steps, organizations can improve their speed and agility, and better meet the needs of their customers and stakeholders.


SAFe Agile Transformations improves NPS

Net Promoter Score (NPS) is a customer satisfaction measurement tool that is used to gauge the likelihood that a customer will recommend a company’s products or services to others. NPS is based on a simple question: “On a scale of 0 to 10, how likely are you to recommend our company to a friend or colleague?” Customers who respond with a score of 9 or 10 are considered “promoters,” while those who respond with a score of 0 to 6 are considered “detractors,” and those who respond with a score of 7 or 8 are considered “passives.” The NPS is calculated by subtracting the percentage of detractors from the percentage of promoters.

Agile companies can use NPS to measure customer satisfaction and identify areas for improvement. By regularly collecting and analyzing NPS data, agile companies can get a sense of how their customers feel about their products and services and where they may need to make adjustments. For example, if a company’s NPS is low, it may indicate that there are issues with the product or service that are causing dissatisfaction among customers. The company can then use this information to identify and address these issues, potentially through iterative changes and improvements to the product or service.

In addition, agile companies can use NPS data to help prioritize and guide their product development efforts. By understanding which aspects of their products or services are most important to their customers and receiving regular feedback on their performance, agile companies can make informed decisions about which features or capabilities to focus on in order to drive customer satisfaction.

NPS can be a valuable tool for agile companies looking to measure and improve customer satisfaction, and can help guide product development efforts and inform decision-making.


SAFe Agile eliminates 5 kinds of Waste

Agile methods can help to eliminate several common types of waste in companies. Some examples include:

1. Overproduction

This refers to the production of more products or services than are needed, which can result in excess inventory and higher storage costs. Agile methods, which focus on delivering small increments of value frequently, can help to reduce overproduction by only producing what is needed when it is needed.

2. Waiting

This refers to delays in the production process, such as waiting for approvals or for materials to be delivered. Agile methods, which prioritize continuous flow and quick delivery, can help to minimize waiting times and increase efficiency.

3. Defects

This refers to errors or defects in products or services that need to be corrected, which can be costly and time-consuming. Agile methods, which emphasize continuous improvement and the use of feedback loops, can help to identify and address defects more quickly and efficiently.

4. Overprocessing

This refers to the unnecessary use of resources or steps in the production process, which can increase costs and lead to inefficiencies. Agile methods, which focus on simplicity and value, can help to eliminate unnecessary steps and streamline the production process.

5. Underutilized talent

This refers to the failure to fully utilize the skills and expertise of employees, which can result in a lack of engagement and productivity. Agile methods, which prioritize teamwork and collaboration, can help to ensure that the skills and expertise of all team members are utilized and valued.


Eliminating these categories of waste increases productivity

By adopting agile, organizations can reduce or eliminate various forms of waste that can hinder their ability to deliver value and achieve their goals. Some examples of waste that agile can help solve include:

  • Overproduction.

    Agile helps teams focus on delivering small, incremental changes frequently, rather than trying to produce large amounts of work upfront. This can help teams avoid overproducing work that may not be needed or used, which can save time and resources and reduce waste.

  • Waiting.

    Agile emphasizes collaboration and communication, which can help teams avoid waiting for other teams or stakeholders to provide input or feedback. This can help teams move faster and avoid delays, which can reduce waste and improve efficiency.

  • Defects and rework.

    Agile encourages teams to iterate and improve their work continuously, which can help teams identify and fix defects or problems more quickly and efficiently. This can reduce the need for rework and help teams avoid wasting time and resources on fixing problems that could have been avoided.

  • Overprocessing.

    Agile encourages teams to focus on delivering value to the customer, rather than producing unnecessary or excessive documentation or paperwork. This can help teams avoid overprocessing and unnecessary bureaucracy, which can save time and reduce waste.

  • Wrong work.

      Teams can frequently be directed to work on someone’s pet project, fix a concern for an upset customer, slip in some bug fixes.  Without proper prioritization of work based on value, precious capacity can be applied to work that should have been lower priority.


4 Ways SAFe Agile increases revenue generation

There are several ways in which agile software development can potentially increase revenue generation:

1. Faster time-to-market

Agile development emphasizes rapid prototyping and iterative delivery, which can help organizations bring products and features to market faster than traditional development approaches. This can be particularly valuable in industries where there is strong competition and a need to quickly respond to changing customer needs and market conditions.

2. Improved customer satisfaction

Agile development emphasizes regular feedback and collaboration with customers, which can help organizations build products that better meet the needs and preferences of their target audience. This can lead to increased customer satisfaction and loyalty, which can translate into increased revenue.

3. Increased efficiency

Agile development can help organizations identify and address bottlenecks and inefficiencies in their development processes, which can lead to cost savings and increased productivity. This can ultimately contribute to increased revenue by enabling organizations to deliver more value to their customers in a shorter period of time.

4. Greater agility

Agile development enables organizations to be more responsive to changing market conditions and customer needs. This can help organizations better adapt to new opportunities and threats, and ultimately lead to increased revenue.


SAFe Agile Methods increase Accountability

Agile methods, such as Scrum and Lean, can increase accountability in several ways:

  • Regular check-ins and progress reviews:

    Agile methods typically include regular check-ins and progress reviews, such as daily stand-ups, sprint planning meetings, and retrospectives. These meetings provide an opportunity for team members to report on their progress and to identify any issues or challenges that may be impacting their ability to meet their goals. This can help to increase accountability by ensuring that team members are regularly communicating and tracking their progress.

  • Emphasis on individual and team ownership:

    Agile methods also place a strong emphasis on individual and team ownership of the work being completed. Team members are encouraged to take responsibility for the success of the project, and to identify and address any issues or challenges that may arise. This can help to increase accountability by ensuring that team members are actively engaged in the work and are committed to delivering high-quality results.

  • Use of metrics and data:

    Agile methods often make use of metrics and data to track progress and identify areas for improvement. This can help to increase accountability by providing a clear and objective measure of performance, and by enabling team members to track their progress and identify areas where they may need to focus their efforts.

Agile methods, like those shown in this section, can increase accountability by providing regular opportunities for team members to report on their progress, emphasizing individual and team ownership of the work, and using metrics and data to track performance and identify areas for improvement.


5 Ways implementing SAFe Agile leads to cost reduction?

Scaled agile frameworks, such as the Scaled Agile Framework (SAFe), can help organizations bring costs down in a number of ways. Some of these include:

1. Reducing waste and inefficiency

By adopting an agile approach, organizations can eliminate waste and inefficiency in their processes, which can help reduce costs.

2. Improving predictability and visibility

Scaled agile frameworks provide a clear framework for planning, executing, and tracking work, which can help organizations better predict costs and manage their budgets.

3. Reducing risk and uncertainty

Agile methods help organizations better manage risk and uncertainty, which can help reduce the costs associated with unexpected events.

4. Accelerating time-to-market

Scaled agile frameworks can help organizations bring products and services to market faster, which can help reduce costs by allowing them to generate revenue sooner.

5. Improving quality and customer satisfaction

Agile methods help organizations deliver high-quality products and services that meet customer needs, which can help reduce costs by reducing the need for rework and improving customer satisfaction.


The Best Agile Companies achieve these things…

Agile companies often report a number of benefits and successful outcomes as a result of using agile methods and practices. Some examples of these benefits include:

  • Increased customer satisfaction: Agile companies tend to be more responsive to customer needs, which can lead to higher levels of customer satisfaction.

  • Faster time to market: Agile approaches prioritize the delivery of working software, which can help organizations bring products and services to market more quickly.

  • Improved quality: Agile methods often emphasize continuous testing and feedback, which can help identify and fix defects early in the development process, leading to higher quality products.

  • Increased collaboration and transparency: Agile approaches encourage collaboration and open communication, which can improve team cohesion and increase transparency within an organization.

  • Greater adaptability and flexibility: Agile methods allow organizations to be more responsive to change, which can be beneficial in rapidly changing markets or environments.

  • Higher team morale and motivation: Agile approaches often focus on empowering teams and giving them autonomy, which can lead to higher levels of job satisfaction and motivation among team members.

  • Improved predictability and visibility: Agile methods can provide better visibility into the development process, helping organizations to better predict when certain features or capabilities will be delivered.


Leverage SAFe Agile to accelerate decision making

Agile development is a method of software development that emphasizes rapid prototyping and iterative delivery, and it can help accelerate decision making in a few different ways:

  • Regular feedback and collaboration:

    Agile emphasizes regular communication and collaboration with stakeholders, including customers and team members. This can help ensure that decisions are based on current information and insights, and that any changes or adjustments are made quickly.

  • Emphasis on experimentation:

    Agile encourages teams to embrace a culture of experimentation and rapid prototyping, which can help organizations quickly test and validate ideas and hypotheses. This can help teams make more informed decisions faster.

  • Flexibility:

    Agile approaches are designed to be flexible and adaptable, which can help teams quickly respond to changes in customer needs or market conditions. This can enable teams to make decisions more quickly and effectively in the face of uncertainty.

  • Smaller, incremental steps:

    Agile approaches encourage teams to break down large projects into smaller chunks, or “sprints,” which can help teams make progress and make decisions more quickly.

The key to accelerating decision making with agile is to embrace a culture of rapid prototyping, experimentation, and collaboration, and to be flexible and adaptable in the face of changing circumstances.


5 Indicators of a successful SAFe Agile transformation

Agile transformation is a process that requires a lot of hard work, dedication, and commitment. It is a process of changing the way your organization works and operates, moving away from traditional methods of working and towards new and innovative ways of working. This can be a daunting and challenging process, but it can also be incredibly rewarding. When it comes to knowing whether or not your agile transformation is successful, there are a few key indicators that you should look out for. 

Here are some of the ways that you can tell if your agile transformation is successful: 

1. Increased Productivity

One of the main goals of an agile transformation is to increase productivity. If you are seeing increased productivity levels in your organization, this is an indicator that your transformation is being successful.

2. Improved Collaboration

Improved collaboration is another key indicator of a successful agile transformation. If you are seeing an increase in cross-team collaboration, this is a good sign that your transformation is working. 

3. Increased Employee Engagement

An agile transformation should also lead to an increase in employee engagement. If you are seeing an increase in employee engagement, this means that your employees are enjoying the new way of working and are actively engaged in the process.

4. Reduced Costs

An agile transformation should also lead to reduced costs. If you are seeing a decrease in costs associated with your organization’s operations, this is an indicator that your agile transformation is successful. 

5. Increased Customer Satisfaction

Finally, an agile transformation should also lead to an increase in customer satisfaction. If you are seeing an increase in customer satisfaction, this means that your customers are happy with the new way of working and are more likely to continue using your services.

These are just a few of the ways that you can tell if your agile transformation is successful. Keep an eye out for these indicators and make sure you are taking the necessary steps to ensure that your transformation is successful.


8 Companies who’ve successfully implemented SAFe

As organizations move towards larger, more complex projects, they need to find ways to scale up their existing Agile process. Scaled Agile Framework (SAFe) is one of the most popular frameworks used to scale Agile across large organizations. It enables teams to collaborate and share resources more effectively, while also improving visibility and control over releases. 

In this section, we’ll look at 8 companies who have successfully implemented SAFe. 

1. Microsoft

Microsoft is one of the biggest names in technology, and they’ve been using SAFe since 2013. Microsoft uses SAFe to manage their teams and projects, and they have seen significant improvements in their release velocity, quality, and visibility. 

2. Target

Target is one of the largest retailers in the US, and they’ve been using SAFe since 2017. Target has seen a 30% increase in productivity and a 20% reduction in cycle time since implementing SAFe. 

3. Amazon

Amazon is one of the world’s largest ecommerce companies, and they’ve been using SAFe since 2016. Amazon has seen a 70% increase in team productivity and a 30% reduction in cycle time since implementing SAFe. 

4. Apple

Apple is one of the world’s most innovative companies, and they’ve been using SAFe since 2017. Apple has seen a 50% increase in release velocity and a 40% reduction in cycle time since implementing SAFe. 

5. Yahoo

Yahoo is one of the world’s largest internet companies, and they’ve been using SAFe since 2015. Yahoo has seen a 40% increase in team productivity and a 20% reduction in cycle time since implementing SAFe. 

6. Lockheed Martin

Lockheed Martin is one of the world’s largest defense contractors, and they’ve been using SAFe since 2016. Lockheed Martin has seen a 30% increase in team productivity and a 25% reduction in cycle time since implementing SAFe.

 7. SAP

SAP is one of the world’s largest software companies, and they’ve been using SAFe since 2013. SAP has seen a 40% increase in release velocity and a 30% reduction in cycle time since implementing SAFe. 

8. Oracle

Oracle is one of the world’s largest database companies, and they’ve been using SAFe since 2016. Oracle has seen a 50% increase in team productivity and a 35% reduction in cycle time since implementing SAFe

These 8 companies are just a few examples of companies who have successfully implemented SAFe. SAFe is a powerful framework that can help organizations scale their Agile process, and it has proven to be successful for many different types of organizations. If you’re looking for a way to scale your Agile process, SAFe is definitely worth considering.


A success story for SAFe Agile at Scale – John Deere

John Deere credits its success with agile in part to its implementation of the Scaled Agile Framework (SAFe). SAFe is a framework for scaling agile practices to large organizations and is designed to help organizations achieve agility at scale.

By implementing SAFe, John Deere has been able to apply agile principles and practices across its organization and achieve agility at scale. This has helped the company to improve efficiency, reduce lead times, and increase customer satisfaction.

In addition, John Deere has used SAFe to foster collaboration and teamwork across its organization and to improve communication and coordination. This has helped the company to align its efforts towards common goals and to deliver value to customers more efficiently and effectively.

John Deere’s implementation of SAFe has played a significant role in its success with agile and has helped the company to achieve agility at scale.


Companies who’ve failed to implement Business Agility with SAFe

Business agility refers to an organization’s ability to adapt and respond quickly and effectively to changing circumstances in order to deliver value to customers and stakeholders. There are many examples of companies that have struggled to achieve business agility, either due to organizational culture, rigid processes, or other factors. Here are a few examples:

  • Blockbuster:

    Blockbuster was once a dominant player in the video rental industry, but it struggled to adapt to the rise of streaming and online video services, and ultimately went bankrupt in 2013.

  • Kodak:

    Kodak was a leader in the film photography industry, but it struggled to adapt to the rise of digital photography and eventually filed for bankruptcy in 2012.

  • Blackberry:

    Blackberry was once a dominant player in the smartphone market, but it struggled to adapt to the rise of smartphones with touch screens and was eventually overtaken by competitors such as Apple and Samsung.

  • Sears:

    Sears was once a dominant retailer, but it struggled to adapt to the rise of online shopping and changes in consumer preferences, and filed for bankruptcy in 2018.

The examples above demonstrate the importance of business agility in an increasingly competitive and fast-changing business environment. Companies that are unable to adapt and respond quickly and effectively to changing circumstances are at risk of being overtaken by competitors.


How Does SAFe Agile Propel Digital Transformation?

Digital transformation is the process of leveraging digital technologies to create new, or modify existing, business processes and customer experiences. It is a fundamental shift in how organizations use technology to compete in the digital economy. To achieve digital transformation, organizations must be agile and continuously innovate. This means rethinking their organizational structures and business models, their products and services, and their customer and employee experiences. 

The Scaled Agile Framework (SAFe) is an organizational framework that enables organizations to achieve agility, speed, and innovation. It is a set of principles, practices, and tools that help organizations deliver value faster and more efficiently in the digital economy. With SAFe, organizations can scale agile practices, align teams, and apply lean principles across the entire organization.

SAFe is designed to help organizations achieve digital transformation by increasing agility and speed, while minimizing risk. It enables organizations to rapidly respond to customer needs and market changes, and provides a platform for continuous innovation. By providing a common language, structure, and process, SAFe helps organizations achieve a common understanding of the organization’s goals and objectives. This in turn enables teams to work together in a more cohesive manner, to better coordinate across divisions, and to deliver value faster. 

SAFe also helps organizations identify and prioritize initiatives that can help them reach their goals. It provides guidance on how to break down large projects into smaller chunks, enabling teams to focus on the highest-value tasks first. This helps teams deliver value more quickly, and reduces the risk of failing to deliver the full value of a project. 

Finally, SAFe can help organizations maximize the value of their existing technology investments. It provides guidance on how to integrate existing systems with new technologies and services, and how to use data to inform decision-making and drive innovation. 

By leveraging the principles of SAFe, organizations can accelerate their digital transformation. SAFe provides organizations with a framework for coordinating teams, managing projects, and delivering value faster. It helps organizations identify and prioritize initiatives that will help them reach their goals, and provides guidance on how to maximize the value of their existing technology investments. With SAFe, organizations can achieve agility, speed, and innovation, and propel their digital transformation forward.


6 reasons agile is becoming popular for business teams

Agile has been a popular software development methodology for years, but it’s now gaining traction in the business world as well. Agile is becoming popular for business teams because it offers a number of advantages that can help them work better together. Here are six reasons why agile is becoming popular for business teams.

1. Flexibility

Agile allows teams to adapt quickly to changes in their environment, which can be particularly useful when dealing with volatile markets or customer needs. It also encourages teams to think outside the box and come up with creative solutions to business problems. 

2. Improved Communication

Agile promotes close collaboration between team members and encourages them to share their ideas. This helps teams stay on the same page, which is essential for successful business operations. 

3. Visibility

Agile provides teams with greater visibility into their progress, which helps them stay on track. The team can easily see how far along they are in achieving their goals and make adjustments to their strategy if necessary. 

4. Efficiency

Agile is designed to maximize efficiency by eliminating unnecessary steps and focusing on the most important tasks first. This helps teams get more done in less time. 

5. Focus

Agile encourages teams to focus on the most valuable tasks and avoid getting sidetracked by less important tasks. This helps teams stay on track and reach their goals faster. 

6. Quality

Agile emphasizes quality over quantity, which helps teams deliver better results. By focusing on quality, teams can ensure that their work is up to the highest standards. These are just a few of the reasons why agile is becoming popular for business teams. Agile provides teams with the tools they need to collaborate effectively, stay on track and deliver results. By embracing agile, business teams can improve their performance and achieve greater success.


SAFe® Agile Success in the Utilities Industry

There are several examples of agile success in the utilities industry:

  • National Grid:

    National Grid, a utility company in the UK, implemented agile practices in its operations and maintenance team in order to improve efficiency and effectiveness. By adopting agile principles and practices, the team was able to reduce downtime, improve communication and collaboration, and deliver value to customers more quickly.

  • PG&E:

    PG&E, a utility company in California, implemented agile practices in its customer care and billing department in order to improve efficiency and customer satisfaction. By adopting agile principles and practices, the department was able to reduce cycle times, improve quality, and increase customer satisfaction.

  • DTE Energy:

    DTE Energy, a utility company in Michigan, implemented agile practices in its IT department in order to improve efficiency and deliver value to customers more quickly. By adopting agile principles and practices, the IT department was able to reduce lead times, improve quality, and increase customer satisfaction.


SAFe® Agile Success in Government

There are several examples of agile success in government:

  • United States Digital Service (USDS):

    The USDS is a government agency that uses agile principles and practices to improve the delivery of government services. By adopting agile, the USDS has been able to improve the efficiency and effectiveness of its projects and deliver value to citizens more quickly.

  • UK Government Digital Service (GDS):

    The GDS is a government agency in the UK that uses agile principles and practices to improve the delivery of government services. By adopting agile, the GDS has been able to reduce lead times, improve quality, and increase customer satisfaction.

  • Australian Government Digital Transformation Agency (DTA):

    The DTA is a government agency in Australia that uses agile principles and practices to improve the delivery of government services. By adopting agile, the DTA has been able to reduce lead times, improve quality, and increase customer satisfaction.

These examples demonstrate how agile can be successfully applied in government to improve the efficiency and effectiveness of projects and deliver value to citizens more quickly.


SAFe® Agile Success in Retail

There are several examples of agile success in the retail industry:

  • Zara:

    Zara, a fashion retailer, has used agile principles and practices to improve its supply chain and enable faster delivery of new products to customers. By adopting agile, Zara has been able to reduce lead times, improve quality, and increase customer satisfaction.

  • Target:

    Target, a retail chain in the US, has used agile principles and practices to improve its online shopping experience. By adopting agile, Target has been able to improve the efficiency and effectiveness of its online operations and deliver a better shopping experience to customers.

  • Amazon:

    Amazon, an e-commerce retailer, has used agile principles and practices to improve its operations and deliver value to customers more quickly. By adopting agile, Amazon has been able to reduce lead times, improve quality, and increase customer satisfaction.

These examples demonstrate how agile can be successfully applied in the retail industry to improve efficiency, reduce lead times, and increase customer satisfaction.


SAFe Agile is influencing the future of Agriculture

Agile concepts are being applied to the agriculture industry in a number of ways:

  • Agile farming:

    Agile farming is an approach that uses agile principles and practices to improve the efficiency and effectiveness of farming operations. This may involve adopting agile practices such as continuous delivery and continuous improvement to optimize crop production and reduce waste.

  • Agile supply chain management:

    Agile principles and practices can be applied to supply chain management in the agriculture industry to improve the efficiency and effectiveness of the supply chain. This may involve adopting agile practices such as customer collaboration and continuous delivery to optimize the flow of materials and reduce lead times.

  • Agile product development:

    Agile principles and practices can be applied to product development in the agriculture industry to improve the efficiency and effectiveness of the product development process. This may involve adopting agile practices such as iteration and continuous improvement to quickly develop and test new products and meet changing customer needs.

Agile concepts are being applied to the agriculture industry in a variety of ways to improve the efficiency and effectiveness of farming operations, supply chain management, and product development.


SAFe® Agile resonates with Millennials

Agile resonates with millennials for a variety of reasons. Some of the main factors that may contribute to agile’s appeal to millennials include:

  • Focus on customer needs:

    Agile emphasizes the importance of delivering value to customers and meeting their needs, which aligns with millennials’ values and priorities.

  • Collaborative and inclusive approach:

    Agile promotes collaboration and inclusivity, which may be particularly appealing to millennials who value diversity and teamwork.

  • Emphasis on continuous learning:

    Agile emphasizes continuous learning and improvement, which aligns with millennials’ desire for personal and professional growth.

  • Flexibility:

    Agile provides flexibility and autonomy, which may be particularly appealing to millennials who value work-life balance and the ability to work in different locations and on different projects.

Agile’s focus on customer needs, collaborative and inclusive approach, emphasis on continuous learning, and flexibility may all contribute to its appeal to millennials.


Why SAFe is the leading agile framework

SAFe has gained popularity in recent years because it provides a structured and flexible approach for coordinating and aligning the work of multiple Agile teams.

There are a number of factors that have contributed to SAFe’s emergence as a leader in the field of Agile development. One factor is that SAFe provides a comprehensive framework for implementing Agile at scale, which includes guidance on key areas such as team organization, program execution, portfolio management and Lean-Agile leadership. Additionally, SAFe has a strong focus on continuous improvement and has a well-defined process for incorporating feedback and learning into its practices.

SAFe has a strong community of practitioners and a robust ecosystem of tools, training, and support resources, which has helped to make it a widely recognized and respected approach to scaling Agile. These factors, along with the growing demand for effective approaches to scaling Agile development in large organizations, have contributed to SAFe’s emergence as the leader in this field.


How you know your SAFe Transformation is Working

As Agile continues to evolve and grow, the need for more robust and advanced frameworks to support it has become increasingly clear. One such framework, SAFe (Scaled Agile Framework), has become one of the most popular and widely adopted frameworks for managing and scaling Agile. The SAFe framework can help organizations more effectively manage and scale their Agile projects, but how can you know when your SAFe transformation is working? The first indicator of success when implementing a SAFe transformation is an overall improvement in the organization’s ability to deliver value to its customers. SAFe’s focus on cross-functional collaboration and small, often autonomous teams helps to ensure that projects are completed in a timely and effective manner. When teams are working together effectively, there should be a noticeable increase in the speed of delivery for customer-facing projects. Another important indicator of success is the increased visibility of the Agile process throughout the organization. With the introduction of SAFe, teams now work together to complete their work in an integrated fashion, creating an environment of collaboration and shared accountability. As a result, it should be easier to track progress, identify issues, and make decisions that affect the entire organization. Finally, a successful SAFe transformation should also be reflected in the organization’s financials. By streamlining and improving the delivery of value to customers, SAFe can help to reduce costs and improve revenue. Additionally, the increased visibility of the Agile process throughout the organization should lead to increased customer satisfaction, resulting in more loyal customers and higher customer retention rates. When a SAFe transformation is effective, it should result in a noticeable improvement in the organization’s ability to deliver value to its customers, increased visibility of the Agile process throughout the organization, and improved financial performance. If you’ve implemented SAFe in your organization and are seeing these results, then you’re likely on the right track to successful Agile transformation.


What does SAFe offer that other frameworks miss?

The Scaled Agile Framework (SAFe) is a framework for scaling agile practices and principles to support the development of complex systems. It offers several benefits and features that distinguish it from other agile frameworks:

  • Holistic approach:

    SAFe takes a holistic approach to scaling agile, addressing the needs of the enterprise, portfolio, and team levels. This allows it to address the challenges of scaling agile in a comprehensive way, rather than focusing on a specific aspect of the process.

  • Customization:

    SAFe is designed to be customizable and adaptable to the specific needs of an organization. It provides a set of tools and practices that can be tailored to fit the organization’s culture and goals.

  • Support for multiple teams:

    SAFe is designed to support the coordination and collaboration of multiple teams working on a single project or product. It provides tools and practices for managing work across teams and aligning efforts towards a common goal.

  • Integration with other frameworks: SAFe is designed to be compatible with other agile frameworks, such as Scrum, Lean, and Kanban. This allows organizations to leverage the strengths of multiple frameworks to create a customized approach that meets their specific needs.

  • Enterprise focus:

    SAFe is specifically designed to address the challenges of scaling agile at the enterprise level. It provides guidance on how to align development efforts with the overall goals and strategy of the organization.

Read More

7 Ways to Overcome the Obstacles of Adopting SAFe®

Posted by Sawyer Conrady on January 3, 2023

Dec 13, 2022

The best way to overcome obstacles of adopting the Scaled Agile Framework (SAFe) is to approach the adoption process in a systematic and disciplined manner. This typically involves the following steps:

  1. Identify the key stakeholders and decision makers who need to be involved in the adoption process, and make sure that they are on board with the decision to adopt SAFe.
  2. Create a clear and compelling vision for how SAFe will benefit the organization, and communicate this vision to all stakeholders in a way that resonates with their needs and concerns.
  3. Develop a detailed plan for implementing SAFe, including a timeline, a budget, and a list of specific tasks and activities that need to be completed.
  4. Identify any potential obstacles or challenges that may arise during the adoption process, and develop strategies for addressing and overcoming these challenges.
  5. Provide training and support to help individuals and teams adopt SAFe and become proficient in using its principles and practices.
  6. Monitor progress closely, and make adjustments to the implementation plan as needed to ensure that the adoption of SAFe remains on track.
  7. Integrate experienced SAFe coaches into your team to quickly identify and correct any gaps in skills and efficiently guide teams and organizations through the process of implementing SAFe, providing expertise and support to ensure that the framework is properly applied and that the desired outcomes are achieved.

Overall, the key to overcoming obstacles to adopting SAFe is to approach the process with a sense of purpose, commitment, and collaboration, and to be willing to adapt and adjust as needed to ensure success.

Written by Katie Snelson , Director of Sales and Recruiting

ICON partners with clients in their Business and IT Transformations to produce collaborative outcomes that have proven vital in many industries. Since 1992, our highly experienced coaches and practitioners have been collaborating with companies to solve their most complex challenges using SAFe® methodology, Business Agility best practices, advanced OKRs, DevSecOps at the team level, and the Lean-Agile mindset

Read More

Agile Recruiters Look For These Key Things In Resumes

Posted by Sawyer Conrady on January 3, 2023

Nov 21, 2022

Making a resume can be stressful! You may ask yourself “What should I show? What are important objectives and critical results that a company recruiter wants to see?” There are certainly things that I look for in resumes and like to see emphasized. Always remember, resumes aren’t everything, but they are a way to open a recruiter’s eyes and get the ball rolling with a potential partner. So, here are some of the key things to highlight that can lead to the creation of a strong resume.

Showcase Qualified Knowledge and Experience

First off, when you are making a resume, make sure that you have qualified knowledge and experience in the role that you are applying for. With the majority of experience, agile recruiters do not want to see you reiterate the job description of a role – we want to see you talk about your unique experiences and how your experiences have led to strong contributions to your impact at an engagement.

When making a professional resume, make sure that it is written in the third person and uses the proper tenses based on the elaboration of an engagement. For example, if you are writing about a role you did from 2010 to 2013, this is going to be written in the past tense about the impact you made in that opportunity. Also, when writing about the impact you made on an opportunity, do not write about what the organization did – directly get to the point of what impact you made.

If you are a technical coach or a consultant, showing your hands-on experience with your skills set is paramount. Your specific skill set and knowledge of agile tools is one of the most important ways to show impactful assets that would drive and help in a new organizational transformation.

Tailor Versions of your Resume for Each Agile Role

Applying for more than one agile role can take more time and organization. You might ask yourself “How do I show all my experience and knowledge if I can play many roles in an Agile & SAFe® environment?” A simple way to highlight all of your roles and experiences is to have different versions of your resume. Consider dedicating time to dividing your experience to better develop your opportunities. For example: if you are a SAFe Team Coach and you have the skills and enjoyment of being a Senior Scrum Master, you should have one resume that represents your “Senior Scrum Master” skills and experience and another version of your resume that represents “SAFe Team Coach” skills and experience. Swiss Army Knife Coaches need to be able to show that they have “been there, done that” within different versions of their resume.

Send Your Resume to ICON

I hope that these tricks and rule of thumbs that I have provided can help you get a better grasp on what highlights your resume. Like I said earlier, resumes aren’t everything, but they are a great representation of you and should reflect the first impression you wish to convey.

If you have what it takes to be an ICON Coach, please send your resume to Blake Lawson at Blake.Lawson@iconagility.com and I would be more than happy to talk with you about your resume!

Written by Blake Lawson , Recruiter

ICON partners with clients in their Business and IT Transformations to produce collaborative outcomes that have proven vital in many industries. Since 1992, our highly experienced coaches and practitioners have been collaborating with companies to solve their most complex challenges using SAFe® methodology, Business Agility best practices, advanced OKRs, DevSecOps at the team level, and the Lean-Agile mindset

Read More

Answer the client’s primary question: What value am I receiving in return for my check?

Posted by Sawyer Conrady on January 3, 2023

Nov 18, 2022

During every engagement someone on the client’s side wants to know “what are we getting for all this money we are paying?” The question is a legitimate one. The money paid is crystal clear. There is a desire to measure the value delivered from this investment. Let me also note that there are several aspects to the answer. In this article I will just address one aspect – the business value delivered by the agile teams.

Let’s define value

I would like to start by defining “value.” The dictionary defines value as “the regard that something is held to deserve; the importance, worth, or usefulness of something.” So, value inherently involves the perception of a person or persons. Some companies put an emphasis on revenue while others like non-profits place an emphasis on charitable action for the cause. As agile coaches, we have the potential to work with both kinds of clients. The value definition belongs to the client. If a client doesn’t have a clear definition of value, they are often left unable to see the value they are receiving based on what we are helping them accomplish. In this case, it’s important that we help clients define value at the very beginning of our partnership.

Measuring value

SAFe® addresses this problem in a straightforward way – it says there are two primary outputs to a successful PI Planning event. The first is a program board and the second is committed PI objectives. The PI objectives are what provide us with what we need to drive the business to a clear understanding of what is valuable to them. In brief, the features prioritized in a PI Planning session are submitted to the agile teams and the teams determine what portion of them can be accomplished during the PI. As the teams are working through that process, they create PI objectives which provide a feedback loop to the business to confirm the agile teams have a common understanding of what is being requested through the features. As the business reviews the PI objectives, they designate the value (between one and ten) that those PI objectives represent in terms of business value. At the end of the PI, the PI objectives are reviewed and the business grades the actual business values obtained through the work completed during the PI by the teams.

Delivering value “predictably”

From PI to PI, this business value delivered is tracked through the mechanism of predictability metric. The overall result is to provide visibility of enterprise values and volume of value being delivered to everyone. The business can now see both sides of the equation – what they are paying and what value is being delivered.

Written by Jim Camden

 

Jim has over 35 years of helping large and small companies solve painful problems in technical and organizational areas. His early career was in software for large and complex mission-critical systems. He was a developer, designer, architect, and business analyst. Jim has been intrigued by the human side of technology success for the last 20 years, which led him to Agile and SAFe. He is motivated by observing successful SAFe Transformations in organizations that benefit in tangible ways from their efforts. As a coach, he has seen the organizations he works with gain clarity on what matters and what doesn’t, and then concentrate on the former. These principles are so powerful that they work when adopted in any organization—in every sub-group, in any industry, at every level, whether co-located or distributed—despite the current level of Agile maturity within the organization and regardless of the current structure. The key is to have a coach that can make them real to you and your people.

 

Read More

Why Companies Invest in a Scaled Agile Transformation

Posted by Sawyer Conrady on January 3, 2023

Nov 11, 2022

Read More

5 Qualifications Recruiters Look For In Agile Talent

Posted by Sawyer Conrady on January 3, 2023

Nov 4, 2022

Have you ever gone into an interview over-analyzing your strengths and weaknesses? The feeling that makes you ask yourself “What do I need to showcase to set myself apart from other agile talent?”

Typically, interviews can be nerve racking. They are full of rapid fire questions, including the old school burning question “where do you see yourself in 5 years?” As a recruiter, I firmly dislike cliche interview questions like this because they do not lead to answers that tell me more about my candidate. I want to get to know my candidates. I want to get to know you.

I came to ICON Agility Services because it is a people-focused culture. We help each other succeed and we value having each other’s back. In kind, I’d like to help you prepare for your next Agile interview. To help get you on the road to success, I will help you make a game plan from my own experience. Recruiters look for many different factors that set you above other Agile Talent. I’ve always been told that recruiters are the gate-keepers to a company, so I thought it would be helpful to provide you with a cheatsheet of the qualities I look for in my candidates.

Top 5 qualifications recruiters
look for when hiring Agile Talent

1. Experience

First things first, you need to show that you are actually qualified for the role you are interested in. When a recruiter asks you “Tell me about your background and your prior work experiences” emphasize any instance or situation where you have hands-on experience with the role you would like to get.

For example: If I am looking for Release Train Engineer (RTE) opportunities, agile professionals that emphasize how many ARTs and PI Plannings they have been a part of will go a long way.

OR: If there are Scrum Master opportunities that need to be filled, those who demonstrate their experience bringing teams together, impediments overcome, and ways you’ve influenced the team’s agile mindset will automatically position themselves for qualification. With this in mind, show the recruiter that you have practical hands on experience that would make you a strong candidate.

2. Presentability

Bottom line: being presentable is such an important factor when going into an interview. You’d be wrong for thinking that being presentable is a given. Speak clearly, confidently, and directly when being asked questions. Keep away from providing long winded answers that might lose the attention of the interviewer. Additionally, show that you are flexible and a “go-getter” that likes to make a true impact. Most importantly, on any video calls get on camera and wear something nice!

3. Consultative

In the agile world, it’s critical to be a consultative influencer. Most companies do not want a role player, they want an impact maker. Consultative is the ability to demonstrate your skills/strengths while coaching others to create real results. Interviewers will look for this unique skill, so demonstrate your ability and your consultative nature within your allotted interview time. Any company could use agile talent who can provide that kind of support for agile transformation.

4. Coachability

You might be thinking “What? A coach being coached?” Accepting feedback from others, even as a coach, promotes the mindset of continuous improvement – even a component of the SAFe® mindset. Make sure your “attitude” or “ego” does not prevent you from continuously growing as an agile professional. Being able to work with others and listen to feedback makes you a better teammate and aligns with what Agile encourages.

5. Ambitiousness

Many recruiters are looking for mentors and continuous learners. Show that you can be “a rockstar!” Set yourself apart from the rest unapologetically. You are someone that goes above and beyond to drive an organization’s transformation forward. So, tell them that! Don’t be afraid to be a disruptor. An organization’s digital transformation relies on employees who want to be a difference maker.

Want to work with us?  Apply here!

ICON combines industry best practices and processes with real world experience to deliver pragmatic customer solutions in a rapidly changing marketplace. But we can’t do it alone.

I’m excited to learn more about what you are looking for as the next step in your career (just make sure to use the 5 Qualifiers I just told you about). Apply at the above link, learn more about opportunities to further your professional agile career, or reach out to me directly at Blake.Lawson@iconagility.com.

Written by Blake Lawson , Recruiter

ICON partners with clients in their Business and IT Transformations to produce collaborative outcomes that have proven vital in many industries. Since 1992, our highly experienced coaches and practitioners have been collaborating with companies to solve their most complex challenges using SAFe® methodology, Business Agility best practices, advanced OKRs, DevSecOps at the team level, and the Lean-Agile mindset

Read More