top of page

Welcome to Mountain State

  • Alex
  • Aug 11
  • 1 min read

After 20+ years navigating different corners of the tech industry, including government contracts, oil & gas, aerospace, and more legacy systems than I care to count, I’ve seen what works. I've also seen what breaks teams, burns people out, and sends developers running off screaming into the night.


A lot of that time has been spent leading (or fixing) Agile delivery efforts, helping software teams get unstuck, and untangling the mess that happens when process takes priority over outcomes. I’ve coached teams, guided transformations, and survived more than a few "we do Agile now" rollouts that always overlook that pesky Delivering Working Software part.


This space is where I’ll share the lessons, missteps, patterns, thoughts, bad habits, hopes, dreams, and gripes I’ve picked up along the way. And maybe some I made up just for the engagement.


Expect practical takes, real talk, and the occasional jab at Agile theater. Most of what I’ll share will be short, focused, and slightly rough around the edges. All of it will be based on real-world experience and hard lessons.


If you’ve ever spent more time in meetings (sorry, ceremonies) than doing actual development, or been critiqued more on process adherence than customer satisfaction, you’ll probably feel right at home.


So sit back, strap in, and if you need help turning meetings into momentum, I’m here to help.

Recent Posts

See All
Agility in a World Full of Mandates

In this 2-part series, I'll be covering an issue I've seen several Agile teams face firsthand: how to stay Agile when developing mandated, compliance-based features. In Part 1  I'll look at ways to ap

 
 
Eight 1-Hour Naps ≠ Good Sleep

You wouldn’t tell someone they got a full night’s rest by taking eight one-hour naps at random times throughout the day. So why do we do something similar to our developers?

 
 
bottom of page