Search a title or topic

Over 20 million podcasts, powered by 

Player FM logo
Artwork

Content provided by Jamison Dance and Dave Smith, Jamison Dance, and Dave Smith. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Jamison Dance and Dave Smith, Jamison Dance, and Dave Smith 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://podcastplayer.com/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Episode 437: My company canceled all one-on-ones and moving to a single backlog

30:29
 
Share
 

Manage episode 453255979 series 133571
Content provided by Jamison Dance and Dave Smith, Jamison Dance, and Dave Smith. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Jamison Dance and Dave Smith, Jamison Dance, and Dave Smith 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://podcastplayer.com/legal.

In this episode, Dave and Jamison answer these questions:

  1. My company recently eliminated 1:1 meetings between managers and their direct reports. Previously, most people had these meetings every other week, and they were an opportunity to talk about career growth among other engineering things besides current work. They’re claiming the recurring meetings can be replaced with quick, more spontaneous calls when necessary. Although wiping meetings from the calendar does clear up more time to code, as a more junior team member, I’m concerned that this will negatively impact my career growth. It feels like career progression just got a little bit harder. What’s the read here? Is this a red flag? Should I start looking elsewhere? How can I navigate this changing environment and still make sure that I am able to progress my career?

  2. A listener named Matt says,

    I’d really like to move to a single team-dedicated backlog, where we use kanban and have work in progress limits, rather that the heavy release planning fixed-scope current model. I feel we would be more effective as a team that way (I’m one of many team leads in the company). Currently we operate in an agile-ish fashion but ultimately inside a waterfall process, driven from outside the technology team. Although I believe it would be a good thing, I’ve not actually worked in that way. Is it all it’s cracked up to be? Are there any issues of going to that model that I’m not seeing?

  continue reading

460 episodes

Artwork
iconShare
 
Manage episode 453255979 series 133571
Content provided by Jamison Dance and Dave Smith, Jamison Dance, and Dave Smith. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Jamison Dance and Dave Smith, Jamison Dance, and Dave Smith 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://podcastplayer.com/legal.

In this episode, Dave and Jamison answer these questions:

  1. My company recently eliminated 1:1 meetings between managers and their direct reports. Previously, most people had these meetings every other week, and they were an opportunity to talk about career growth among other engineering things besides current work. They’re claiming the recurring meetings can be replaced with quick, more spontaneous calls when necessary. Although wiping meetings from the calendar does clear up more time to code, as a more junior team member, I’m concerned that this will negatively impact my career growth. It feels like career progression just got a little bit harder. What’s the read here? Is this a red flag? Should I start looking elsewhere? How can I navigate this changing environment and still make sure that I am able to progress my career?

  2. A listener named Matt says,

    I’d really like to move to a single team-dedicated backlog, where we use kanban and have work in progress limits, rather that the heavy release planning fixed-scope current model. I feel we would be more effective as a team that way (I’m one of many team leads in the company). Currently we operate in an agile-ish fashion but ultimately inside a waterfall process, driven from outside the technology team. Although I believe it would be a good thing, I’ve not actually worked in that way. Is it all it’s cracked up to be? Are there any issues of going to that model that I’m not seeing?

  continue reading

460 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.

 

Listen to this show while you explore
Play