Sign up to save your podcasts
Or
Share The Role of Product Management on Truly Agile Development Teams (with Allen Holub, Software Architect, Consultant & Outspoken Twitter Agilist)
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
The Role of Product Management on Truly Agile Development Teams (with Allen Holub, Software Architect, Consultant & Outspoken Twitter Agilist)
Allen Holub is a software development and agile consultant who wants to help you build better software and build software better. He's also not shy when it comes to telling the world what he thinks about product development via Twitter.
Here are some of Allen's spicy takes:
Making true organisational change requires C-level buy-in
It's easy to get hired by the engineering team to help them learn how to make sausages better but the better goal is to work out if you want to make sausages, and you need top-level buy in for this
There are too many people walking on eggshells on Twitter
You should be able to share your version of the truth in an open, direct way. If people don't like it, they can listen to someone else! Context is important, but it's not ivory tower thinking to try to change a system.
Empowering people to be agile doesn't mean leaving them to it
Removing organisational blockers and waterfall thinking is important, but you can't just leave them to it and not support them. They need support to become a learning organisation.
Scrum is, at best, mostly harmless, but only in good teams
You don't need backlogs, you don't need scrum masters, you don't need Sprints. You don't need any of it. Scrum was just a way to make agile acceptable to bureaucratic micromanagers. But all frameworks fly against agile thinking.
Product managers do essential work that developers won't do if left to their own devices, but..
It's important that they're part of the development team, that they're not a silo, they aren't the boss or decision maker for the team & they aren't a replacement for the customer
JIRA is actively contributing to poor development behaviours
We don't need big long complicated specs, we don't need backlogs, estimates, story points or velocity charts. We'd be better off with index cards stuck to a wall (or Miro!)
Listen to the episode for this and more!
Follow the progress of Allen's book:
Allen is writing a book! Check out the progress of the book here.
Go to Allen's User Story workshop
If you want to go to Allen's upcoming class on User Stories, check out the details here.
Contact Allen
You can reach out to Allen on Twitter, or book a chat with him.
View all episodes
By One Knight in Product
4.7
1414 ratings
Allen Holub is a software development and agile consultant who wants to help you build better software and build software better. He's also not shy when it comes to telling the world what he thinks about product development via Twitter.
Here are some of Allen's spicy takes:
Making true organisational change requires C-level buy-in
It's easy to get hired by the engineering team to help them learn how to make sausages better but the better goal is to work out if you want to make sausages, and you need top-level buy in for this
There are too many people walking on eggshells on Twitter
You should be able to share your version of the truth in an open, direct way. If people don't like it, they can listen to someone else! Context is important, but it's not ivory tower thinking to try to change a system.
Empowering people to be agile doesn't mean leaving them to it
Removing organisational blockers and waterfall thinking is important, but you can't just leave them to it and not support them. They need support to become a learning organisation.
Scrum is, at best, mostly harmless, but only in good teams
You don't need backlogs, you don't need scrum masters, you don't need Sprints. You don't need any of it. Scrum was just a way to make agile acceptable to bureaucratic micromanagers. But all frameworks fly against agile thinking.
Product managers do essential work that developers won't do if left to their own devices, but..
It's important that they're part of the development team, that they're not a silo, they aren't the boss or decision maker for the team & they aren't a replacement for the customer
JIRA is actively contributing to poor development behaviours
We don't need big long complicated specs, we don't need backlogs, estimates, story points or velocity charts. We'd be better off with index cards stuck to a wall (or Miro!)
Listen to the episode for this and more!
Follow the progress of Allen's book:
Allen is writing a book! Check out the progress of the book here.
Go to Allen's User Story workshop
If you want to go to Allen's upcoming class on User Stories, check out the details here.
Contact Allen
You can reach out to Allen on Twitter, or book a chat with him.
More shows like One Knight in Product
View all
a16z Podcast
1,001 Listeners
The Tim Ferriss Show
16,084 Listeners
The Twenty Minute VC (20VC): Venture Capital | Startup Funding | The Pitch
510 Listeners
Decoder with Nilay Patel
3,125 Listeners
How I Built This with Guy Raz
30,242 Listeners
The Product Podcast
166 Listeners
Masters of Scale
3,967 Listeners
All-In with Chamath, Jason, Sacks & Friedberg
8,773 Listeners
The Memo by Howard Marks
407 Listeners
Hard Fork
5,361 Listeners
Product Thinking
144 Listeners
Sharp Tech with Ben Thompson
90 Listeners
The AI Daily Brief (Formerly The AI Breakdown): Artificial Intelligence News and Analysis
421 Listeners
BG2Pod with Brad Gerstner and Bill Gurley
433 Listeners
AI + a16z
33 Listeners