Understanding Team and Technical Agility in SAFe

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at enterprise scale. A key aspect of SAFe is enabling business agility, which requires both team agility and technical agility. In this blog post, we’ll take a closer look at the three dimensions of team and technical agility in SAFe: Team and Workspace, Agile Product Delivery, and DevOps and Release on Demand. By focusing on these areas, organizations can build the foundational competencies needed for agile teams to efficiently build, test, and release high-quality software in a fast, sustainable way.

Dimension 1: Team and Workspace 

The Team and Workspace dimension is a critical aspect of SAFe that focuses on creating an environment conducive to high-performing, cross-functional agile teams. It emphasizes the importance of a shared workspace that supports focus, collaboration, and pair work. Let’s dive deeper into the key elements of this dimension.

Collocated, Dedicated, Cross-Functional Teams:

In SAFe, it is highly recommended that agile teams be collocated in the same workspace. This physical proximity enables high-bandwidth communication, face-to-face interactions, and seamless collaboration among team members. Collocation eliminates the barriers and delays often associated with distributed teams, allowing for quick problem-solving and decision-making.

Moreover, agile teams in SAFe should be dedicated and cross-functional. A dedicated team is one that is fully committed to a single Agile Release Train (ART) and is not frequently shuffled between different projects or initiatives. This dedication allows the team to maintain focus, build momentum, and deliver value consistently. Cross-functionality means that the team possesses all the necessary skills and expertise to define, build, test, and deliver an increment of value. This includes roles such as product owner, scrum master, developers, testers, and other specialists as needed. Having a cross-functional team reduces dependencies on external resources and enables the team to deliver end-to-end value.

Self-Organization and Self-Management:

SAFe empowers agile teams to self-organize and self-manage their work. The team is given the autonomy to determine how they can best achieve their goals and deliver value. They collaboratively plan their own work, manage their own processes, and make their own technical decisions. This autonomy fosters a sense of ownership and accountability within the team.

However, self-organization does not mean lack of leadership. SAFe promotes the concept of servant leadership, where leaders focus on enabling and supporting the team rather than controlling them. Servant leaders remove impediments, provide guidance, and create an environment that allows the team to thrive. They trust the team’s expertise and decision-making abilities while providing the necessary resources and support.

Shared Workspace:

The physical workspace plays a crucial role in fostering team collaboration and enabling agile practices. SAFe recommends creating an open and collaborative workspace that supports teamwork, knowledge sharing, and pair work. The workspace should be designed to promote transparency, facilitate communication, and enable quick feedback loops.

Information radiators, such as physical boards or digital dashboards, should be prominently displayed in the workspace. These radiators provide visibility into the team’s progress, sprint goals, backlog items, and other relevant information. They serve as a central point of reference for the team and stakeholders, promoting transparency and alignment.

The workspace should also support pair work, where two team members collaborate together in real-time on a single task. Pair work helps improve code quality, share knowledge, and catch defects early. The workspace should provide adequate space and equipment to facilitate pair programming, such as dual monitors, comfortable seating, and whiteboards for design discussions.

Additionally, the workspace should minimize distractions and enable focus. This can be achieved through techniques such as designated quiet areas, noise-canceling headphones, and agreeing on team norms for interruptions and communication.

Dimension 2: Agile Product Delivery

The Agile Product Delivery dimension in SAFe focuses on the technical practices and processes that enable teams to efficiently build and deliver high-quality solutions. It encompasses the entire lifecycle of product development, from continuous exploration and backlog refinement to iteration execution and quality assurance. Let’s explore each aspect in more detail.

Continuous Exploration:

Agile teams in SAFe continuously explore market needs, customer feedback, and emerging technologies to identify opportunities for innovation and value delivery. They maintain a shared understanding of the product vision and roadmap, which guides their work and aligns them with business goals.

Teams employ design thinking techniques to gain a deep understanding of customer problems and define the most valuable features and solutions. They collaborate with customers, stakeholders, and subject matter experts to gather insights, validate assumptions, and refine their understanding of requirements.

Backlog Refinement:

Product and solution backlogs are the primary artifacts that drive agile product delivery. SAFe emphasizes the importance of continuously refining and decomposing these backlogs into small, well-defined user stories. User stories capture the desired functionality from the user’s perspective and provide a clear understanding of the value being delivered.

During backlog refinement sessions, the team collaborates with the Product Owner to clarify requirements, identify dependencies, and estimate the effort required for each story. They define acceptance criteria to establish a shared understanding of what “done” means for each story. This ongoing refinement process helps maintain a healthy backlog and ensures that the team has a clear understanding of the work ahead.

Agile Estimation and Planning:

SAFe teams use agile estimation and planning techniques to forecast and manage their work. They plan their work for each iteration, typically a two-week timebox, and make visible commitments to what they will deliver.

Estimation is done using relative measures such as story points or ideal days, rather than absolute hours or days. Story points capture the relative complexity, effort, and uncertainty of each user story. The team collaboratively estimates the stories, leveraging their collective knowledge and experience.

Velocity, which is the average number of story points completed per iteration, is used to guide planning and improve forecasting. By tracking velocity over time, teams can predict their capacity and make reliable commitments.

Iteration Execution:

During each iteration, the team focuses on delivering a high-quality, tested increment of value. They break down user stories into smaller, actionable tasks and collaborate to complete them. The team holds a daily stand-up meeting to synchronize their efforts, share progress, and identify any impediments.

Throughout the iteration, the team integrates their work frequently and ensures that the software is always in a potentially shippable state. They employ test-driven development (TDD) practices, where tests are written before the code, to ensure that quality is built-in from the start.

At the end of each iteration, the team conducts a demo to showcase the completed work to stakeholders and gather feedback. They also hold a retrospective meeting to reflect on their process, identify improvements, and make necessary adjustments for the next iteration.

Pair Work:

SAFe encourages pair work, where two team members collaborate together in real-time on a single task. Pair programming, where two developers work together on the same code, is a common practice. Pair work helps improve code quality, catch defects early, and promote knowledge sharing among team members.

Pairing is not limited to programming; it can be applied to other activities such as design, testing, and documentation. Pairing fosters a collaborative culture, enables continuous learning, and reduces silos of knowledge within the team.

Built-in Quality:

SAFe emphasizes the importance of building quality into the product from the very beginning. Testing is not treated as a separate phase but is integrated throughout the development process. Teams employ practices such as test-driven development (TDD), acceptance test-driven development (ATDD), and behavior-driven development (BDD) to ensure that quality is baked into the product.

Automated testing, including unit tests, integration tests, and acceptance tests, is a key practice in SAFe. Teams strive for high test coverage and maintain a comprehensive suite of automated tests that are run frequently. Continuous integration and continuous testing practices ensure that any issues are identified and resolved quickly.

Teams also collaborate closely with Quality Assurance (QA) specialists to perform exploratory testing, usability testing, and other forms of manual testing. The goal is to identify and address defects early in the development process, reducing the overall cost and time required for fixing issues.

Dimension 3: DevOps and Release on Demand

The DevOps and Release on Demand dimension in SAFe focuses on the technical practices and automation capabilities that enable teams to continuously deliver value to end users. It emphasizes the importance of collaboration between development and operations teams, as well as the establishment of a robust and automated pipeline for building, testing, and deploying software. Let’s explore the key aspects of this dimension in more detail.

Continuous Integration:

Continuous Integration (CI) is a fundamental practice in SAFe that involves frequently integrating code changes into a shared repository. Developers work on small, incremental changes and integrate their code multiple times a day. Each integration triggers an automated build and testing process to provide rapid feedback on the quality and stability of the codebase.

CI helps detect and resolve integration issues early, reduces the risk of conflicting changes, and ensures that the software is always in a releasable state. Teams use CI tools to automate the build process, run unit tests, and perform static code analysis. This automation helps catch defects early and maintains the integrity of the codebase.

Continuous Deployment:

Continuous Deployment (CD) takes CI a step further by automating the entire process from code commit to deployment. The goal is to enable teams to release software to production or other environments with minimal manual intervention.

In a CD pipeline, after the code passes through the CI process, it automatically moves through various stages such as integration testing, performance testing, security testing, and user acceptance testing. Each stage verifies the quality and readiness of the software for deployment.

CD relies heavily on automation, including automated testing, infrastructure provisioning, and deployment scripting. Teams define deployment pipelines that automate the flow of software through these stages, ensuring consistency and reliability.

Infrastructure as Code:

Infrastructure as Code (IaC) is a practice where infrastructure is treated the same way as application code. Instead of manually provisioning and configuring servers, networks, and other infrastructure components, teams define infrastructure using code and configuration files.

IaC allows teams to version control their infrastructure, making it easier to track changes, collaborate, and maintain consistency across environments. Infrastructure code is stored in source code repositories, and changes go through the same review and testing processes as application code.

Teams use tools like configuration management systems (e.g., Puppet, Chef, Ansible) and infrastructure provisioning tools (e.g., Terraform, CloudFormation) to automate the provisioning and management of infrastructure. This automation enables teams to quickly spin up new environments, scale resources based on demand, and ensure consistency between development, testing, and production environments.

Continuous Monitoring:

Continuous Monitoring is the practice of continuously observing and analyzing the performance, health, and behavior of deployed software and infrastructure. It involves collecting metrics, logs, and events from various sources and using them to gain real-time visibility into the system.

Teams set up monitoring tools and dashboards to track key performance indicators (KPIs), such as response times, error rates, resource utilization, and user behavior. These tools alert teams when issues arise, enabling them to proactively identify and resolve problems before they impact end users.

Continuous monitoring also provides valuable feedback loops for both operational and business metrics. Teams can use this data to make informed decisions, optimize performance, and continuously improve the system.

Release on Demand:

Release on Demand is the ability to deliver value to end users whenever the business needs it. SAFe promotes the idea of decoupling features from releases, allowing teams to release software incrementally and frequently.

Teams use techniques like feature toggles (or feature flags) to decouple the deployment of code from the release of features. Feature toggles allow teams to deploy code to production but control the visibility and availability of specific features. This enables them to perform controlled rollouts, conduct A/B testing, and quickly roll back features if needed.

The release process itself is fully automated, with the ability to push a button and have the software deployed to the desired environment. This automation reduces the risk of manual errors, ensures consistency, and enables faster time-to-market.

Conclusion

By focusing on these three dimensions – Team and Workspace, Agile Product Delivery, and DevOps and Release on Demand – organizations can enable their agile teams to build, test, and release high-quality software faster and more predictably. These technical agility competencies, combined with cross-functional, collaborative teams, provide the foundation for business agility in SAFe.