Digital Visual Management https://validator.w3.org/feed/docs/rss2.html Blog Planning Sprints Around Federal Holidays, PTO, and Training Days (2) Crashing vs Fast-Tracking: Measure the Gap Before You Compress the Schedule Velocity vs. Capacity: What Government Agile Teams Get Wrong (Part 2) Scrum of Scrums: Make the Cross-Team Dependency Meeting Count Student Syndrome & Parkinson’s Law: The Two Habits That Eat Your Schedule Buffer How to Calculate Team Capacity When Half Your Team Is Part-Time or Detailed Elsewhere (2) The Bus Factor: When One Person’s Absence Moves a Committed Release Date Sprint Spillover: How Carryover Quietly Erodes a Committed Release Date Aligning Sprint Planning with Capacity Planning: A Practical Guide for Public-Sector Teams (2) Brooks’s Law: Why Adding People Makes a Late Release Later Jira Apps for the Atlassian Collections Why Sprint Capacity Planning Matters More in Government Than Anywhere Else A Day in the Life: Sprint Planning With Capacity on One Screen The SAFe Program Board Is a Snapshot. Your Dependencies Aren’t. Bringing Visibility to Who’s Working on What Across Sprints Padding Estimates: The Hidden Buffer Your Release Can’t See How to Create a Sprint in Jira: Create, Start, and Close It the Right Way How Many Sprints in a Release? A Velocity-Based Answer Do You Need a Sprint Goal? What the LinkedIn Scrum Debate Reveals How to Plan Capacity Around Contract and Fiscal-Year Boundaries Making the Business Case for Better Sprint Planning Tools to Procurement The Cone of Uncertainty Doesn’t Narrow on Its Own Capacity-Aware Backlog Refinement for Government Teams Watermelon Reporting: Why a Release Stays Green Right Up Until It Slips Sprint Planning Anti-Patterns in Public-Sector Agile (and Fixes) Schedule Slippage: What Actually Moves a Committed Release Date The Real Cost of an Over-Allocated Government Developer No Estimates vs Story Points: What the Debate Misses About Sprint Planning Your Say-Do Ratio Is a Great Post-Mortem. It’s a Terrible Early Warning. Forecasting the Next Quarter Using Past Velocity Your Go/No-Go Meeting Shouldn’t Be Where You Find Out How to Run Sprint Planning When Requirements Change Mid-Cycle Your Code Freeze Can’t Give You the Days Back Your Release Burndown Says You’re On Track. Your Committed Date Disagrees. Reducing Context-Switching: Planning Capacity in One Tool Your Release Forecast Is Only as Honest as the Throughput Behind It What a Healthy Sprint Looks Like: Metrics Government PMOs Should Track The Sprint Estimation Confidence Gap: Feeling Sure and Still Missing Stop Promising a Release Date. Promise a Release Window. Sprint Rollover: Why 8 in 10 Teams Carry Work Over Every Sprint Capacity Planning for Hybrid and Distributed Government Teams You Committed to the Date, But at What Confidence? Your Release Date Reads “85% Confident.” Here’s How to Read It Capacity Risk: The Third Thing That Erodes a Committed Release Date Story Points or Hours? Choosing an Estimation Model for Public-Sector Teams How Days-Off Planning Prevents Sprint Failure Your Fist of Five Was Right on Day One. Is It Still Right on Day Thirty? The Compliance Case for Documented Sprint Capacity Decisions Scope Creep Doesn’t Wait for Your Next PI Planning