Artwork

Content provided by Jayme Edwards and Tech Career Strategist. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Jayme Edwards and Tech Career Strategist or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Scrum Is The “Motor” Of Your Project, But Who’s Steering?

8:58
 
Share
 

Manage episode 207636976 series 1756036
Content provided by Jayme Edwards and Tech Career Strategist. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Jayme Edwards and Tech Career Strategist or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.

When talking about the differences between scrum (or kanban) and agile development, the motor and steering wheel of a car can be a useful analogy.

When your team is working to write requirements, write code, test, and deploy releases of your software – they probably follow a development process like scrum or kanban to get work done.

This work can be thought of as the motor of the car that propels the software product forward, changing or adding new features to it.

However software companies sell products in a changing market – competitors can force us to change, customers can force us to change, and our own team members can discover information that forces us to change.

This is when the leadership of a software team especially need to trust their other team members to make changes.

Each time the team makes one of these changes to respond to unplanned events, they are being agile.

Being agile in software development is like using the steering wheel of the car.

When things change, the direction of the features needs to be turned so the “power” of the engine is focused on something different.

In software development, we steer the car by putting new product backlog items (or kanban tickets) at a high priority to make satisfying our customer paramount.

Customers won’t buy a software product when we’ve built everything WE think they want – but only what THEY accept.

In this episode, I share some thoughts around this analogy and how you might use it to ask this question next time you’re making a software development process decision:

Is this practice going to help, or hurt our team’s ability to ‘steer’ the car that is our software product’s queue of work to be done?

Join my Patreon: https://thrivingtechnologist.com/patreon

Learn about one-on-one career coaching with me: https://thrivingtechnologist.com/coaching

TechRolepedia, a wiki about the top 25 roles in tech: https://thrivingtechnologist.com/techroles

The Thriving Technologist career guide: https://thrivingtechnologist.com/guide

You can also watch this episode on YouTube.

Visit me at thrivingtechnologist.com

  continue reading

178 episodes

Artwork
iconShare
 
Manage episode 207636976 series 1756036
Content provided by Jayme Edwards and Tech Career Strategist. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Jayme Edwards and Tech Career Strategist or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.

When talking about the differences between scrum (or kanban) and agile development, the motor and steering wheel of a car can be a useful analogy.

When your team is working to write requirements, write code, test, and deploy releases of your software – they probably follow a development process like scrum or kanban to get work done.

This work can be thought of as the motor of the car that propels the software product forward, changing or adding new features to it.

However software companies sell products in a changing market – competitors can force us to change, customers can force us to change, and our own team members can discover information that forces us to change.

This is when the leadership of a software team especially need to trust their other team members to make changes.

Each time the team makes one of these changes to respond to unplanned events, they are being agile.

Being agile in software development is like using the steering wheel of the car.

When things change, the direction of the features needs to be turned so the “power” of the engine is focused on something different.

In software development, we steer the car by putting new product backlog items (or kanban tickets) at a high priority to make satisfying our customer paramount.

Customers won’t buy a software product when we’ve built everything WE think they want – but only what THEY accept.

In this episode, I share some thoughts around this analogy and how you might use it to ask this question next time you’re making a software development process decision:

Is this practice going to help, or hurt our team’s ability to ‘steer’ the car that is our software product’s queue of work to be done?

Join my Patreon: https://thrivingtechnologist.com/patreon

Learn about one-on-one career coaching with me: https://thrivingtechnologist.com/coaching

TechRolepedia, a wiki about the top 25 roles in tech: https://thrivingtechnologist.com/techroles

The Thriving Technologist career guide: https://thrivingtechnologist.com/guide

You can also watch this episode on YouTube.

Visit me at thrivingtechnologist.com

  continue reading

178 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide

Copyright 2025 | Privacy Policy | Terms of Service | | Copyright
Listen to this show while you explore
Play