LeadingAgile is Now LiminalArc. Read the Full Announcement

Move beyond isolated AI experiments to build scalable, domain-driven systems with AI-ready architectures.

Enhance valuation and accelerate ROI through due diligence, tech migrations, and strategic restructuring.

Control cloud costs, streamline data, and focus investments on high-value, scalable solutions.

Streamline operations and improve decision-making by aligning your ERP systems with how your business actually works.

Reduce risk and increase resilience by closing the security gaps hiding in your architecture and workflows.

Optimize operations, restructure teams, and modernize technology to maximize the value of digital investments.

Deliver mission-critical software in production-ready increments that create measurable value early.

Reduce risk and complexity with every cycle, turning legacy systems into platforms that can evolve.

The belief that shaped us — and how it evolved into LiminalArc, the natural next step in our journey.

Our team of over 100 experts spans the nation, from consultants and technical architects to product specialists.

We are looking to hire mature, pragmatic consultants who are deeply passionate about meaningful change.

Unless these three things exist, your organization will always struggle to adopt agile.

Tim Zack Chief Marketing Officer
Reading: Unless these three things exist, your organization will always struggle to adopt agile.

Backlogs, Teams, and Working Tested Software are the fundamental preconditions that must exist for an organization to be able to do agile well. In agile these three things have very specific meanings. Compromising on the quality of the backlog, the completeness of the team or the definition of working tested software always decreases agility.

Backlogs

Most organizations underestimate the amount of time and energy it takes to create backlogs with the needed level of granularity.

  • User stories written in a consistent format
  • 1-3 days in size
  • Agreement on method of collaboration

Teams

Teams that don’t stay together and aren’t able to get to a definition of done stop believing they can and will never stabilize velocity.

  • 6-8 People
  • Work together side by side
  • Swarm to develop solutions
  • Has the ability to produce what is in the backlog.

Working Tested Software

  • Have to know what done looks like
  • Need to be able to get to done by the end of the sprint.
Next Who's Afraid of Emergent Design?

Comments (2)

  1. Evan
    Reply

    I mostly agree with this list. However, our team is struggling due to executive leadership and a Scrum Master​ who is unable to control their influence. Goes back to the Scrum Master but his fear to push back is impeding our success.

    Reply
  2. Conrad
    Reply

    Also agree here – the central idea of the team becoming more confident when it is responsible for the right “externalites” .
    Since defects are an inflow competing for backlog time, any real-world facing team that deals with the externality of a customer raised “urgent requirement-change” has to have the power to plan that kind of work without having to go into bug-fix mode. So bugs don’t get tracked as velocity, but still impacts it. The team needs to thus communicate very well. Very well.

    Reply

Leave a comment

Your email address will not be published. Required fields are marked *

×