Technical Products SUCK

Send us a text

They SUCK because they mean teams do not get to know their customer, solve problems for their users and appreciate how they are contributing to increased happiness and revenue.

And by "Technical Products", I mean Components and by Components I mean pieces of something that as a whole is valuable that has many components all working in unison, but no one component has value on its own.

This makes me sad; this is why I think "technical products" SUCK. 

Why do people end up in this dire situation? In part, it is because of the gap between what is taught is taught in many basic Scrum courses and what the essence of Scrum was.

Things to watch and read I mentioned in this episode: 

1. Dreams of Feature Teams
2. Who are the most important people when scaling agile?
3. How to Identify Copy & Paste (Aka) Fake Scrum

Host Bio

Ben is a seasoned expert in product agility coaching, unleashing the potential of people and products. With over a decade of experience, his focus now is product-led growth & agility in organisations of all sizes.

Stay up-to-date with us on our social media📱!

Ben Maynard

🔗 https://www.linkedin.com/in/benmaynard-sheev/

🐦 https://x.com/BenWMaynard

💻 https://sheev.co.uk/

Product Agility Podcast

🔗 https://www.linkedin.com/company/productagilitypod/

💻 https://productagilitypod.co.uk/

🖇️ https://linktr.ee/productagility

Listen & Share On Spotify & iTunes

• Spotify - https://open.spotify.com/show/0lkwAYJzVSuk5zfJ1vIDZq?si=4c691fb12f124a56
• iTunes - https://apple.co/3YvTX8p

Want to come on the podcast?

Want to be a guest or have a guest request? Let us know here https://bit.ly/49osN80