Kanban in SAFe: Visualizing ART Workflow

Within the Scaled Agile Framework (SAFe), Agile Release Trains (ARTs) represent long-lived, self-organizing teams optimized to deliver value continuously. Kanban boards, a core component of Lean management, offer a mechanism to visualize and manage the flow of work across these ARTs; Atlassian Jira, a popular tool for agile project management, can be configured to support these Kanban implementations. One specific query addresses what is one way Kanban boards are used in SAFe: they provide transparency by making workflow visible, enabling teams to identify bottlenecks and improve efficiency in alignment with the principles championed by individuals like Dean Leffingwell, the creator of SAFe.

Unlocking Agility at Scale with Kanban in SAFe

The Scaled Agile Framework (SAFe) provides a structured approach for scaling agile practices across large organizations. When integrated effectively, Kanban principles can significantly enhance agility and workflow efficiency within SAFe implementations. This integration allows organizations to visualize work, limit work in progress, and optimize flow at scale, leading to faster delivery and improved business outcomes.

Kanban: A Primer

Kanban, at its core, is a method for visualizing and managing workflow. It emphasizes continuous improvement by focusing on flow and limiting work in progress (WIP).

The fundamental principles of Kanban include:

• Visualizing the Workflow: Making the process transparent and easily understood by all stakeholders.
• Limiting Work In Progress (WIP): Constraining the amount of work in each stage to reduce bottlenecks and improve focus.
• Managing Flow: Continuously monitoring and optimizing the flow of work to ensure smooth and efficient delivery.
• Making Policies Explicit: Clearly defining the rules and guidelines governing the workflow.
• Implementing Feedback Loops: Regularly reviewing and adjusting the process based on feedback and data.
• Collaborative Improvement: Fostering a culture of continuous improvement through teamwork and shared learning.

The Synergy Between Kanban and SAFe

Kanban’s emphasis on flow and continuous improvement complements SAFe’s structured approach to scaling agile. Within SAFe, Kanban provides a mechanism for teams and Agile Release Trains (ARTs) to visualize their work, manage dependencies, and continuously improve their processes. This is especially beneficial in large, complex organizations where coordination and alignment are critical for success.

Blog Post Roadmap

This post explores how Kanban principles can be applied within the SAFe framework to enhance agility and flow at scale. We will delve into the core Kanban practices, how they integrate with the ART Kanban, and how they contribute to overall organizational agility.

Understanding Kanban: A Foundation for Agile Scaling

Unlocking Agility at Scale with Kanban in SAFe The Scaled Agile Framework (SAFe) provides a structured approach for scaling agile practices across large organizations. When integrated effectively, Kanban principles can significantly enhance agility and workflow efficiency within SAFe implementations. This integration allows organizations to visualize workflows, limit work in progress, manage flow, and foster continuous improvement at scale. Before exploring how Kanban integrates with SAFe, it's crucial to understand the Kanban method itself.

Kanban, at its core, is a method for managing workflow that emphasizes visualizing the process, limiting work in progress (WIP), and continuously improving flow. It's not a software development lifecycle methodology, but rather a method to manage a process, applicable to various knowledge work domains, including software development. Understanding its principles and history is essential for effectively applying it within SAFe.

Core Principles of Kanban

Kanban operates on a set of core principles that guide its implementation and ensure its effectiveness. These principles are not rigid rules but rather guiding philosophies that should be adapted to the specific context of the organization and its work. The primary objective is to optimize flow and deliver value efficiently.

• Visualize the Workflow: This involves creating a visual representation of the workflow, typically using a Kanban board. The board depicts the different stages of the process. This visualization makes it easier to identify bottlenecks and areas for improvement.

• Limit Work In Progress (WIP): Limiting WIP is crucial for improving flow and reducing cycle times. By restricting the amount of work in each stage of the workflow, teams can focus on completing tasks. This prevents bottlenecks and reduces the lead time for delivering value.

• Manage Flow: Kanban emphasizes the importance of managing the flow of work through the system. This involves monitoring metrics such as lead time, cycle time, and throughput. By understanding how work flows through the system, teams can identify and address impediments to flow.

• Make Policies Explicit: Explicit policies are essential for creating clarity and alignment within the team. This involves defining clear rules and guidelines for how work is managed and how decisions are made. Explicit policies reduce ambiguity and ensure that everyone is on the same page.

• Implement Feedback Loops: Feedback loops are crucial for continuous improvement. This involves regularly reviewing the Kanban system. Teams need to assess performance, and identify areas for improvement. Regular feedback allows the team to adapt and optimize the system over time.

• Improve Collaboratively, Evolve Experimentally (using models & the scientific method): Kanban promotes a culture of continuous improvement and encourages teams to collaborate and experiment with new ideas. By using data and feedback to guide their decisions, teams can evolve their Kanban system over time. This ensures that it remains effective and aligned with the changing needs of the organization.

A Brief History and Evolution of Kanban

The origins of Kanban can be traced back to the Toyota Production System (TPS), developed in the late 1940s. Toyota used a "pull" system to manage inventory and production, using visual signals (Kanban cards) to trigger the replenishment of materials. This system helped Toyota reduce waste and improve efficiency.

In the early 2000s, David J. Anderson applied the principles of Kanban to knowledge work, creating the Kanban Method as it is known today. Anderson's work focused on visualizing workflow, limiting WIP, and managing flow in software development and other knowledge-based industries. He formalized the Kanban Method with practices, values, and principles, drawing from lean manufacturing, queuing theory, and systems thinking.

Anderson's contributions were pivotal in shaping Kanban into a widely adopted approach for managing workflow in various industries. His work emphasized the importance of continuous improvement, collaboration, and customer focus.

Benefits of Kanban

Implementing Kanban offers numerous benefits for organizations seeking to improve their agility and efficiency. These benefits extend beyond just software development. Kanban can be used to improve any process that involves managing workflow.

• Improved Flow: By visualizing the workflow and limiting WIP, Kanban helps to optimize the flow of work through the system. This results in faster cycle times and increased throughput.

• Reduced Bottlenecks: Kanban helps to identify and address bottlenecks in the workflow. By visualizing the flow of work, teams can quickly identify areas where work is getting stuck. This allows them to take corrective action and improve the overall flow of the system.

• Increased Predictability: Kanban provides greater visibility into the workflow. Teams can better predict when work will be completed. This increased predictability helps to improve planning and coordination.

• Enhanced Continuous Improvement: Kanban fosters a culture of continuous improvement. Teams are encouraged to regularly review their Kanban system, identify areas for improvement, and experiment with new ideas. This continuous feedback loop helps to ensure that the system remains effective and aligned with the changing needs of the organization.

• Reduced Waste: By limiting WIP and focusing on completing tasks, Kanban helps to reduce waste in the system. This includes reducing the amount of time spent on multitasking, waiting for dependencies, and fixing defects.

• Increased Team Focus: Limiting WIP encourages team members to focus on completing the tasks at hand before starting new work. This increases productivity and improves the quality of work.

Understanding these core principles, historical context, and the potential benefits of Kanban is vital for understanding its application within SAFe. This understanding sets the stage for exploring how Kanban practices can be integrated into Agile Release Trains (ARTs) to optimize flow at scale.

The Agile Release Train (ART): The Heartbeat of SAFe

The Scaled Agile Framework (SAFe) provides a structured approach for scaling agile practices across large organizations. When integrated effectively, Kanban principles can significantly enhance agility and workflow efficiency within SAFe implementations. To understand where and how Kanban brings this value, it’s essential to first grasp the fundamental concept of the Agile Release Train, or ART, which serves as the primary value delivery construct within SAFe.

Understanding the Agile Release Train

The Agile Release Train (ART) is defined as a self-organizing, cross-functional team-of-teams that plans, commits, and executes together in a synchronized cadence. Think of it as a virtual organization of 50 to 125 people that operates like a single, cohesive unit. This unit is dedicated to a specific development value stream, focusing on delivering a continuous flow of value to the end customer.

Unlike traditional hierarchical structures, the ART empowers teams to collaborate seamlessly, break down silos, and respond quickly to changing market demands. It's the engine that drives value delivery within SAFe, providing a consistent rhythm for development and release.

Structure and Purpose of the ART

The ART follows a fixed schedule, typically every two weeks, known as an Iteration (or Sprint in Scrum terminology). These Iterations are aggregated into Program Increments (PIs), usually spanning 8-12 weeks, providing a larger planning horizon and a mechanism for integrating and delivering significant increments of value.

The primary purpose of the ART is to align multiple agile teams around a shared mission, vision, and roadmap. During PI Planning, all members of the ART come together to collaboratively define objectives, identify dependencies, and create a plan for the upcoming Program Increment.

This shared understanding and commitment are crucial for ensuring that everyone is working towards the same goals and that potential roadblocks are identified and addressed early on. The ART enables the autonomous execution of the plan in a decentralized manner by removing management bottlenecks.

Key Roles within the ART

Several key roles are essential for the smooth functioning of the ART:

• Release Train Engineer (RTE): The RTE serves as the servant leader and coach for the ART, facilitating PI Planning, removing impediments, and helping the ART improve its processes.

• Product Management: Product Management is responsible for defining and prioritizing the ART backlog, ensuring that it aligns with the overall business strategy and customer needs.

• System Architect/Engineer: The System Architect/Engineer provides architectural guidance and technical leadership to the ART, ensuring that the system evolves in a sustainable and scalable manner.

• Business Owners: Business Owners are key stakeholders who provide guidance and support to the ART, ensuring that it delivers value that aligns with business objectives.

Benefits of Using an ART within SAFe

Implementing an ART within SAFe offers several significant benefits:

• Improved Alignment and Collaboration: The ART fosters a shared understanding and commitment among all teams, leading to better alignment and collaboration.

  You also like

  What Makes a Person Cool? The Science of Cool

• Faster Time-to-Market: The consistent cadence and synchronized planning of the ART enable faster delivery of value to the market.

• Increased Quality: The focus on built-in quality practices and continuous integration within the ART leads to higher-quality products and services.

• Enhanced Adaptability: The ART's ability to respond quickly to changing market demands allows organizations to be more adaptable and competitive.

• Reduced Risk: Regular integration and testing within the ART help to identify and mitigate risks early in the development process.

  You also like

  What Did the Daughters of Liberty Do?

The Agile Release Train forms the backbone of value delivery within SAFe. Its structure, purpose, and key roles are designed to enable alignment, collaboration, and continuous improvement at scale. By understanding the ART, organizations can lay the foundation for successfully implementing Kanban and realizing its full potential within the SAFe framework.

The ART Kanban System: Visualizing and Managing Flow Across Teams

The Scaled Agile Framework (SAFe) provides a structured approach for scaling agile practices across large organizations. When integrated effectively, Kanban principles can significantly enhance agility and workflow efficiency within SAFe implementations. To understand where and how Kanban brings the most impact, it's important to understand the ART Kanban.

The ART Kanban system serves as a vital tool for visualizing and managing the flow of value across the entire Agile Release Train (ART). It provides a holistic view of the work being undertaken, enabling better decision-making, improved collaboration, and continuous improvement at scale.

Purpose of the ART Kanban

The primary purpose of the ART Kanban is to provide a centralized, visual representation of the work flowing through the ART. This visualization enables stakeholders to understand the current status of initiatives, identify bottlenecks, and make informed decisions regarding prioritization and resource allocation.

By visualizing the workflow, the ART Kanban fosters transparency and alignment among the various teams and individuals involved in the ART. It provides a shared understanding of the overall progress and helps to identify potential risks or dependencies early on.

Ultimately, the ART Kanban aims to optimize the flow of value delivery by promoting continuous improvement and reducing waste.

Key Elements of the ART Kanban

The ART Kanban consists of several key elements that work together to provide a comprehensive view of the workflow.

These elements include columns representing workflow stages, Features and Enablers as work items, and explicit policies governing the movement of work items across the board.

Columns Representing Workflow Stages

The columns on the ART Kanban represent the different stages of the workflow, from initial idea to delivery. Common stages may include:

• Funnel
• Analyzing
• Portfolio Backlog
• Program Backlog
• Implementation
• Testing
• Deployment
• Releasing

These stages provide a clear understanding of where each work item is in the overall process.

The specific stages included in the ART Kanban should be tailored to reflect the unique workflow of the ART.

Features and Enablers as Work Items

The ART Kanban primarily tracks Features and Enablers as work items. Features represent increments of value that can be delivered independently to the end-user, while Enablers support the delivery of Features by addressing technical debt, infrastructure improvements, or exploration activities.

By visualizing both Features and Enablers on the same board, the ART Kanban enables stakeholders to understand the relationship between them and to prioritize work accordingly.

It also helps to ensure that Enablers are given sufficient attention and are not overlooked in favor of more immediate Feature delivery.

Facilitating Alignment and Transparency

The ART Kanban plays a crucial role in facilitating alignment and transparency among the teams within the ART. By providing a shared visual representation of the workflow, it enables everyone to understand the overall progress and to identify potential bottlenecks or dependencies.

Regular reviews of the ART Kanban, such as during the Program Increment (PI) Planning and Inspect & Adapt events, provide opportunities for teams to collaborate and coordinate their work. These reviews also help to identify areas for improvement and to adjust priorities as needed.

Furthermore, the ART Kanban promotes transparency by making explicit the policies and processes governing the flow of work. This helps to ensure that everyone is on the same page and that decisions are made based on clear and consistent criteria.

Core Kanban Practices within the ART: Mastering Flow and Limiting WIP

The Scaled Agile Framework (SAFe) provides a structured approach for scaling agile practices across large organizations. When integrated effectively, Kanban principles can significantly enhance agility and workflow efficiency within SAFe implementations. To understand where and how Kanban becomes useful, this section details the core Kanban practices crucial for a successful ART Kanban, including workflow visualization, WIP limits, and flow management.

Visualizing Workflow on the ART Kanban

Visualizing the workflow is the foundational step in applying Kanban within an ART. The ART Kanban should accurately reflect the stages a Feature or Enabler progresses through, from initial concept to delivery. This typically involves mapping out the key steps in the value stream.

This may include stages such as:

• Funnel/Ideas: Where new Features and Enablers are initially proposed.
• Analysis/Refinement: Where items are analyzed and refined for feasibility and value.
• Ready: Items that are fully defined and ready for implementation.
• Development: Work is actively being developed.
• Testing/Validation: Completed development work undergoes testing and validation.
• Deployment: Items are deployed to production.
• Done: The Feature or Enabler is successfully delivered and providing value.

The specific stages will vary based on the context of the ART, but the key is to ensure that all significant steps are represented on the Kanban board. A well-defined workflow provides a clear understanding of the overall process, enabling better identification of bottlenecks and areas for improvement.

Limiting Work In Progress (WIP): Focus and Efficiency

Limiting Work In Progress (WIP) is a core principle of Kanban, and its implementation within the ART Kanban is critical for maximizing efficiency. WIP limits define the maximum number of items that can be in a particular stage of the workflow at any given time.

Setting and Enforcing WIP Limits

Establishing effective WIP limits requires careful consideration. Start by analyzing the capacity and capabilities of the teams involved in each stage.

Consider the following guidelines:

• Start small: Begin with relatively low WIP limits and gradually adjust based on observed performance.
• Consider dependencies: Take into account any dependencies between teams or stages when setting limits.
• Monitor and adjust: Continuously monitor the impact of WIP limits and make adjustments as needed to optimize flow.

Enforcing WIP limits is essential to realize their benefits. When a stage reaches its WIP limit, the team must focus on completing existing work before starting anything new.

This can be challenging, but it forces prioritization and collaboration, leading to more efficient throughput.

Benefits of Limiting WIP

The benefits of limiting WIP are multifaceted:

• Increased Focus: By limiting the amount of work in progress, teams can focus their attention on completing tasks more quickly and efficiently.
• Faster Cycle Times: Reducing the number of items in the system leads to faster cycle times, as items move through the workflow more quickly.
• Improved Quality: With less multitasking and more focused attention, teams can produce higher-quality work with fewer defects.

Furthermore, limiting WIP exposes bottlenecks and inefficiencies in the system. This provides valuable insights for continuous improvement efforts.

Managing Flow: Metrics and Impediment Removal

Effective flow management is the ultimate goal of implementing Kanban within the ART. This involves continuously monitoring the flow of work through the system and identifying and addressing any impediments that arise.

Measuring Performance: Lead Time, Cycle Time, and Throughput

Key metrics for managing flow include:

• Lead Time: The time it takes for a Feature or Enabler to move from the initial idea to delivery.
• Cycle Time: The time it takes for a Feature or Enabler to move from the "Ready" state to delivery.
• Throughput: The number of Features or Enablers delivered within a specific time period.

Regularly tracking these metrics provides valuable insights into the performance of the ART and helps identify areas for improvement.

Identifying and Addressing Impediments to Flow

Analyzing the data collected from these metrics enables the identification of bottlenecks and other impediments to flow. This might include:

• Blocked Items: Identify items that are stuck in a particular stage of the workflow.
• Resource Constraints: Identify any shortages of resources that are hindering progress.
• Process Inefficiencies: Identify any bottlenecks or inefficiencies in the workflow.

Once identified, these impediments should be addressed promptly. This may involve:

• Re-prioritizing Work: Adjusting the order of work to focus on unblocking critical items.
• Allocating Resources: Shifting resources to address constraints.
• Improving Processes: Streamlining the workflow to eliminate bottlenecks and inefficiencies.

Continuous monitoring and improvement are essential for maximizing the flow of value through the ART Kanban.

By mastering these core Kanban practices, organizations can unlock the full potential of SAFe, achieving greater agility, predictability, and continuous improvement at scale.

Managing Features and Enablers on the ART Kanban: Prioritization and Progress

The Scaled Agile Framework (SAFe) provides a structured approach for scaling agile practices across large organizations. When integrated effectively, Kanban principles can significantly enhance agility and workflow efficiency within SAFe implementations. To understand where and how to utilize Kanban effectively in SAFe, it is crucial to clarify how Features and Enablers can be visualized on the ART Kanban to manage prioritization and progress.

This section explores the definitions of Features and Enablers, demonstrates methods for visualizing their progress through the ART Kanban system, and provides guidance for prioritizing these essential work items.

Defining Features within the ART Kanban

In the context of the Agile Release Train (ART), a Feature represents a service that fulfills a stakeholder need. This is usually written in the "Benefit Hypothesis" format and is sized to be delivered within a single Program Increment (PI).

Features are designed as stand-alone increments of value. They should directly contribute to the overall solution being developed by the ART. Consider Features as marketable, demonstrable functionalities providing tangible value to the end-user or customer.

Tracking Feature Progress on the ART Kanban

The ART Kanban serves as the visual hub for managing the flow of Features.

Each Feature moves through different stages. These stages represent the steps required for its development and deployment. Mapping these stages onto the Kanban board provides transparency into the Feature's current status and progression.

Common stages include:

• Funnel/Idea Backlog: Initial repository for new Feature proposals.
• Analyzing: Feature is analyzed and refined.
• Portfolio Kanban: A separate Kanban to determine whether the feature moves on with investment.
• Program Backlog: Features are prioritized and readied for implementation.
• Implementation: Teams are actively working to develop and test the Feature.
• Validation: The Feature is tested.
• Deployment: The Feature is deployed.

The movement of Features across the ART Kanban provides a real-time view of the ART's progress, enabling stakeholders to quickly assess the status of various Features and identify potential bottlenecks or delays.

Defining Enablers within the ART Kanban

Unlike Features, Enablers are technical activities that support the delivery of Features. They often do not directly deliver end-user value but are crucial for building the architectural runway necessary for future Features.

Enablers can include activities such as:

• Research and prototyping.
• Infrastructure improvements.
• Refactoring existing code.
• Developing testing frameworks.

Enablers are essential for ensuring the long-term sustainability and scalability of the solution. They facilitate the smooth and efficient delivery of Features over time.

Prioritizing and Managing Enablers Alongside Features

Effectively managing Enablers requires careful prioritization alongside Features. Failing to do so can result in technical debt, architectural limitations, and ultimately slower Feature delivery.

There are a few key things to keep in mind when prioritizing:

• Balance: Strive for a balance between Feature and Enabler work. A healthy balance ensures that the ART can deliver value while maintaining a solid technical foundation.
• Visibility: Make Enablers visible on the ART Kanban. This helps ensure that they receive the attention and resources they require.
• Collaboration: Encourage collaboration between teams to identify and prioritize Enablers that benefit multiple teams or the entire ART.

Prioritization Techniques

Several techniques can be employed to prioritize Enablers:

• Weighted Shortest Job First (WSJF): Apply WSJF to prioritize both Features and Enablers, considering the cost of delay, job size, and user-business value.
• Capacity Allocation: Allocate a specific percentage of the ART's capacity to Enabler work during each PI.
• Dependency Mapping: Identify dependencies between Features and Enablers, prioritizing Enablers that are critical for unlocking multiple Features.

By integrating Enablers into the ART Kanban and prioritizing them alongside Features, organizations can ensure that they are investing in the technical foundation necessary for sustained agile delivery at scale.

Integrating Team Kanban with the ART Kanban: A Unified Approach

The Scaled Agile Framework (SAFe) provides a structured approach for scaling agile practices across large organizations. When integrated effectively, Kanban principles can significantly enhance agility and workflow efficiency within SAFe implementations. To understand where Team Kanban practices and the ART Kanban intersect, we will now explore how these two distinct yet complementary systems integrate to create a unified approach to managing work at both the team and ART levels.

The Symbiotic Relationship Between Team Kanban and the ART Kanban

The Team Kanban and the ART Kanban systems are not mutually exclusive; rather, they are designed to work in tandem. Each serves a specific purpose while contributing to the overall agility and efficiency of the SAFe framework.

The Team Kanban focuses on the day-to-day work of individual teams. It provides a visual representation of their workflow, enabling them to manage their tasks, limit Work In Progress (WIP), and continuously improve their processes.

The ART Kanban, on the other hand, operates at a higher level. It provides a broader view of the Feature and Enabler flow across all teams within the Agile Release Train (ART). It allows stakeholders to track the progress of strategic initiatives, identify bottlenecks, and make informed decisions about prioritization and resource allocation.

How Individual Teams Utilize Team Kanban

Within the SAFe framework, individual teams are empowered to adopt and customize their own Kanban systems to suit their specific needs and workflows.

This autonomy allows teams to optimize their processes, manage their backlogs effectively, and ensure that they are delivering value consistently.

Teams use their Kanban boards to visualize their workflow, typically representing stages such as "To Do," "In Progress," "Testing," and "Done."

They also implement WIP limits to prevent overload and ensure that team members are focused on completing tasks efficiently.

Furthermore, Team Kanban boards facilitate daily stand-up meetings, where team members can discuss their progress, identify impediments, and coordinate their efforts.

ART Kanban: Aggregating and Visualizing Team Output

The ART Kanban acts as a central hub for visualizing the progress of Features and Enablers across multiple teams.

It aggregates the work of individual teams, providing stakeholders with a comprehensive overview of the ART's overall performance.

By visualizing the flow of Features and Enablers through the ART Kanban stages, stakeholders can quickly identify potential bottlenecks or delays. This visibility enables them to make proactive decisions to mitigate risks and ensure that the ART stays on track.

The ART Kanban also facilitates alignment among teams by providing a shared understanding of the ART's priorities and goals.

Ensuring Alignment and Coordination

To ensure that Team Kanban systems and the ART Kanban are effectively integrated, it is crucial to establish clear communication channels and synchronization mechanisms.

This requires a concerted effort to foster collaboration and transparency among teams and stakeholders.

Establishing Clear Communication Channels

Effective communication is the cornerstone of a successful integration between Team Kanban and the ART Kanban. Regular communication channels should be established between teams and the ART to ensure that information flows freely and transparently.

This can be achieved through various means, such as:

• Daily stand-up meetings: Teams should participate in daily stand-up meetings to discuss their progress and identify any dependencies or impediments that may impact other teams.

• Regular ART Sync meetings: Representatives from each team should participate in regular ART Sync meetings to share updates, coordinate their efforts, and resolve any conflicts.

• Shared communication platforms: Teams and the ART should utilize shared communication platforms, such as Slack or Microsoft Teams, to facilitate real-time communication and collaboration.

Synchronizing Work and Dependencies

In addition to establishing clear communication channels, it is also essential to synchronize work and dependencies across teams.

This can be achieved through various techniques, such as:

• Dependency mapping: Teams should map out their dependencies on other teams to identify potential bottlenecks and ensure that work is coordinated effectively.

• Cross-team collaboration: Teams should collaborate closely on tasks that require input from multiple teams to ensure that work is completed efficiently and effectively.

• Regular integration points: The ART should establish regular integration points to ensure that the work of individual teams is integrated seamlessly.

So, there you have it! Hopefully, this gave you a clearer picture of how Kanban principles and SAFe can work together. Remember, SAFe uses kanban boards as a visualization tool for ART workflow, helping teams track progress, identify bottlenecks, and continuously improve. Give it a try, experiment, and see what works best for your Agile Release Train! Good luck!