Dual Track Agile. What Is It? Why UX Professionals And Startups Love It?
Everything that you need to know about this massively ignored Agile strategy.
👋 Hello, I’m Vibhor, and welcome to the 🔒 subscriber-only edition 🔒 of my weekly Training Series powered by Winning Strategy. Every week, I answer one reader question about Agile Products, Role-Based Skills, and anything else that you need answered about your Career Growth. You can send me your questions here.
Note: If you enjoy reading this post, please show your support by clicking the little gray heart below the title above. It would really mean a lot and help spread the word about this growing newsletter. 😍
Let’s get started.
Why am I writing about “Dual Track Agile”?
This topic surfaced as I was going through my year-end notes.
About 9 years ago, at the food court of my workplace building, I overheard a group of UI/UX professionals talking about project challenges they were facing.
What caught my attention was when they mentioned 'Dual Track Agile'.
I'd never heard of it, but it sounded like it could solve a lot of common Product Trio issues in software development.
So, I did some digging. Turned out, Dual Track Agile was this neat approach that splits the “software development” process into two parts:
Discovery and
Delivery.
It was about understanding what users need before jumping into building it and then making sure what's built is spot-on.
At that time, I was mind blown. It was solving the age-old conflict between Agile and UI/UX folks.
I figured this could be super useful for many of us, so I've put together this newsletter. We'll explore what Dual Track Agile is, how it works, why it might be a game-changer for many projects and where it doesn’t make sense.
So stay tuned for some practical insights and tips!