Requirements Management

Transparency in Agile uai

Exploring the Principle of Transparency in Lean and Agile

Transparency in Agile What is Transparency in Agile? Transparency in Agile teams is the open sharing of all project-related information among team members and stakeholders, including progress, challenges, and processes. In Agile teams, transparency is foundational for effective collaboration and…


Queuing Theory Blog post header image

Managing Queues in Product Development

Why Manage Queues? Effective queue management reduces cycle time and increases profits by minimizing inactivity in product development processes. Optimizing cycle time within product development is crucial because it directly influences economic outcomes. The main issue with extended product…


Optimizing Batch Sizes header image - puzzle pieces.

Optimize Batch Sizes

What are "Batches" in Product Development? Batch size refers to the quantity or volume of tasks, items, or units grouped for processing, development, or transmission at one time.


Kanban Board with WIP limits

Optimizing Flow with Work in Progress (WIP) Limits

What are WIP Limits? WIP limits are a deliberate constraint placed on the amount of work in progress within a process, which is pivotal in enhancing the workflow's focus, efficiency, and overall effectiveness. Work In Progress (WIP) limits define the maximum quantity of work in each stage of a…


Implementing Built in Quality

What is "Built-in Quality" in SAFe? "Built-in Quality" in SAFe is a core practice ensuring quality standards are met throughout the Agile team's process of creating customer value.


Visibility in Agile

Explore the Principle of Visibility in Lean and Agile

What is the Principle of Visibility in Agile? The Principle of Visibility in Agile emphasizes making all aspects of the Agile process visible to improve decision-making, accountability, and progress tracking. The Principle of Visibility in Agile is about making work visible and creating an…


Portfolio Kanban board with various tasks and progress indicators

Implementing SAFe: Portfolio Kanban

The SAFe Portfolio Kanban SAFe Portfolio Kanban is a method for visualizing and managing the flow of portfolio Epics, aligning strategy and execution in SAFe. In SAFe, Portfolio Kanban is a crucial tool for managing the flow of portfolio Epics, guiding them from ideation to analysis,…


Agility at scale case study 1 - Engagement Process

Case Study: Using Agile to Improve Productivity by 240%

Introduction This is a case study of a two-year project with an actual client. Over the period, we iterated through numerous improvement evolutions, experimenting with various concepts and processes. At the two-year mark, we measured the following improvements:Productivity increase of 240% Reduce…


SAFe Planning Process Illustration

Mastering SAFe PI Planning

What is SAFe PI Planning? PI Planning (Program Increment Planning), a regular event in SAFe, orchestrates Agile teams to envision shared objectives, devise strategic roadmaps, manage dependencies, and strengthen collaboration, aligning team efforts with overarching business goals. PI Planning…


Agile Product Delivery

Mastering Agile Product Delivery with SAFe

What is SAFe Agile Product Delivery? SAFe Agile Product Delivery is a customer-centric approach to defining, building and releasing a continuous flow of valuable products and services. SAFe Agile Product Delivery (ADP) reflects a profound shift from project-based to product-based delivery, hinged…


70-20-10 Learning Model for Agile Training Coaching Facilitation and Leadership Development

Mastering Lean Portfolio Management with SAFe

What is SAFe Lean Portfolio Management? SAFe Lean Portfolio Management (LPM) is a strategy execution framework for aligning strategy and execution in organizations. In the context of SAFe, LPM becomes a critical instrument that helps businesses connect strategy with execution, ensuring the work…


Mastering Team and Technical Agility with SAFe

What is SAFe Team and Technical Agility? Team and Technical Agility refers to the ability of development teams to adapt rapidly to changing customer needs, business goals, or technology while maintaining a high standard of work and technical excellence. Originating from the Agile Manifesto (Kent…


Software Development

Implementing SAFe: Requirements Model (v6)

What is the SAFe Requirements Model? The SAFe Requirements Model is a hierarchical structure that manages and organizes requirements in large-scale Agile projects. The SAFe Requirements Model helps organizations align their business objectives with their development efforts, ensuring that teams…


User Research

The Ultimate Guide to User Research: Mastering Usability, Discovery, and User Studies

Introduction In today's competitive market, understanding user needs and providing exceptional experiences are critical for product success. Mastering the art of user research, usability testing, and discovery can save time and money and ensure your product's success. In this comprehensive guide,…


Design Thinking

The Design Thinking Mindset

Introduction to Design Thinking "Why isn’t technology working better for humans?" This is the question that is at the center of technology design. People have responded to this question in various ways, shaping our approaches, habits, and mindsets. Our preferences and our biases. All the ways we…


value and customer needs

Understanding "Customer Value" and "Customer Needs" in Lean and Agile

What is the definition of Customer Value in Lean and Agile? In Agile, "customer value" refers to prioritizing delivering products that meet customer needs and provide tangible benefits. In Agile methodologies, "customer value" emphasizes creating and delivering products that satisfy customer needs…


business marketing strategy target management illustration free vector1 uai

SAFe Requirements Model (v6) - Program Level

What is the Scaled Agile (SAFe) Program Level? The SAFe Program Level is where Agile teams and stakeholders collaborate to deliver fully integrated, potentially shippable increments of a system or product. The Scaled Agile Framework (SAFe) Program Level is the second level of the SAFe model, where…


people planning task schedule with calendar scaled uai

Agile Requirements Management in Multi-team Agile Environments

Introduction Effective requirements management is critical for identifying and managing dependencies in multi-team agile environments. Breaking down large-scale initiatives into manageable work units, aligning them with business needs, and prioritizing and managing dependencies between teams…


people analyzing growth charts 23 21488668431

SAFe Requirements Model (v6) - Portfolio Level

What is the Scaled Agile Portfolio Level? The Scaled Agile Portfolio Level is the highest level of concern in the Scaled Agile Framework (SAFe), providing strategic direction and funding to value streams. The Scaled Agile Portfolio Level is the highest in the Scaled Agile Framework, where the…


business team brainstorm idea lightbulb from jigsaw working team collaboration enterprise cooperation colleagues mutual assistance concept pinkish coral bluevector isolated illustrat1

SAFe Requirements Model (v6) - Team Level

Why the Focus on Scaled Agile Teams? As we dive into the realm of software requirements, one might question the need to commence with a thorough examination of the organization, roles, and responsibilities within a Scaled Agile team. The essence of Agile diverges so drastically from traditional…


LeSS Requirements Model

LeSS (Large Scale Scrum) Requirements Management

LeSS Requirements Model LeSS (Large-Scale Scrum) is a framework for scaling agile development to large, complex projects involving multiple teams. LeSS provides a set of principles, rules, and practices for scaling agile development beyond the limits of a single team. LeSS requirements model…