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.

It Starts with Cross-Functional Teams

Mike Cottmeyer Chief Executive Officer
Reading: It Starts with Cross-Functional Teams

Mike Cottmeyer describes the core challenges with transformations begins with setting up cross-functional teams.

Learn more by watching the Base Patterns of Business Agility on-demand webinar series here

Transcript

How do I take this functionally siloed organization and turn it into the kind of organization that we can actually deliver the way we want to deliver? So that’s the core challenge of transformation. But this pattern, and I want to anchor back on the pattern is, it is inevitable at some level of scale that we are going to have to have a combination of shared services. We are going to have a set of teams that consume the services. There’s going to be something that I’ll say plans and integrates the services. And there’s something that governs the services. Now you think about like what safe is, right? What safe is is really interesting, right? So safe is designed basically this idea that we’re going to encapsulate value streams and then we’re going to put release trains and planning increments and all that kind of stuff around the value streams. But again, what I believe that safe has done is that it’s largely codifide like a way of dealing with multiple teams independencies at scale. But what we’re experiencing in some of these super large organizations that we’re working in, is that the value streams aren’t even decoupled from each other. So I guess just point being, just maybe kind of put a little bit of a bow on this, is that what we’ve got to figure out how to do, is start off with, how are we going to form teams? How are we going to group teams? How are we going to govern teams? And then ultimately, how are we going to measure and control teams? And then the big question is, what are we going to do with dependencies and how are we going to manage dependencies when they exist? So what we want to be able to do is, we want to be able to look into the organization and at the lowest level try to figure out how we can create complete cross functional teams.

Next Getting the Outcomes You Want From Technical Spikes

Leave a comment

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

×