Agile has pretty much taken over as the industry standard for software teams. But how many software teams have a good understanding of how this idea of agile software emerged? How many software teams have actually read the Agile Manifesto? And what does this manifesto actually say?
In this episode, Derek and Jeremy review the history of the Agile Manifesto, give it a read, analyze it, and compare it to some real-world scenarios.
Topics:
• 03:23 – What’s the deal with this waterfall?
• 07:01 – Back to 2001
• 16:21 – What’s in this manifesto anyway?
• 19:40 – Where’s the fun in planning everything?
• 26:50 – Why do we make this so complicated?
• 28:00 – Let’s talk with the people on our teams
• 29:50 – Are our budgeting processes to blame?
• 30:59 – Dereks’ big idea
• 35:55 – The words’ meanings have changed since they’ve been published
• 41:47 – Derek finally sticks it.
Helpful Links:
– History of the Agile Manifesto
—–
Thanks for listening! We hope you enjoyed today’s episode. If you liked what you heard, be sure to like and subscribe wherever you get your podcasts! If you enjoyed today’s episode, please leave a comment and a five-star review. It helps us out a ton.
If you haven’t already, sign up for our email list. We won’t spam you. Pinky swear.
• Check out our website
• Follow us on twitter
• Find us on Facebook
• Subscribe on Google Podcasts
• Subscribe on Apple Podcasts
• Subscribe on Spotify
• Subscribe on Stitcher