Requirements Management
Exploring the Principle of Transparency in Lean and Agile
Transparency in Agile: Strategies for Scrum, Kanban, and SAFe Teams What Is 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…
Queuing Theory in Product Development: Managing Queues and Wait Times
Queuing Theory in Product Development: Managing Queues and Wait Times Discover how effective queue management can dramatically increase profits by minimizing inactivity and optimizing cycle times in product development. Learn why mastering queueing theory is essential. Why Manage Queues? Effective…
Batch Size in Product Development: Economics and Optimization
Batch Size in Product Development: Economics and Optimization
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.
by Morne Wiggins
Optimizing Flow with Work in Progress (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…
Explore the Principle of Visibility in Lean and Agile
Visibility in Agile: Making Work Visible Across Distributed Teams 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…
Case Study: Using Agile to Improve Productivity by 240%
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…
SAFe Agile Product Delivery Assessment and Implementation Guide
SAFe Agile Product Delivery Assessment and Implementation Guide This comprehensive guide explores Agile Product Delivery in the context of the Scaled Agile Framework (SAFe). What is SAFe Agile Product Delivery? SAFe Agile Product Delivery is a customer-centric approach to defining, building and…
Mastering Team and Technical Agility with SAFe
Mastering Team and Technical Agility with SAFe Dive into this comprehensive exploration of Team and Technical Agility - a crucial element in contemporary organizations. What is SAFe Team and Technical Agility? Team and Technical Agility refers to the ability of development teams to adapt rapidly to…
Implementing SAFe: Requirements Model (v6)
Implementing SAFe: Requirements Model (v6) Software development is a complex and often challenging process. As development teams grow in size, managing requirements becomes increasingly difficult. What is the SAFe Requirements Model? The SAFe Requirements Model is a hierarchical structure that…
The Ultimate Guide to User Research: Mastering Usability, Discovery, and User Studies
The Ultimate Guide to User Research: Mastering Usability, Discovery, and User Studies Discover the power of user research, usability testing, and discovery to create successful products. Learn how to conduct user studies, analyze results, and apply findings for continuous improvement. Introduction…
The Design Thinking Mindset
The Design Thinking Mindset What Is 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.…
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…
Agile Requirements Management in Multi-team Agile Environments
Agile Requirements Management in Multi-team Agile Environments Requirements management are crucial for planning in multi-team agile environments. What Is Introduction? Effective requirements management is critical for identifying and managing dependencies in multi-team agile environments. Breaking…
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…
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 (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. What Is LeSS requirements…