สำเนาบทสนทนา 🔗
WEBVTT
00:00:01.530 --> 00:00:10.949
welcome to the Arguing Agile Podcast, where Enterprise Business Agility Coach Om Patel and Product Manager Brian Orlando argue about product management, leadership, and business agility, so you don't have to.
00:00:11.926 --> 00:00:13.086
Welcome back to arguing agile.
00:00:13.147 --> 00:00:14.037
I was on the team once.
00:00:14.237 --> 00:00:18.437
And the director of the department, for all the teams, would go up to individual developers.
00:00:18.667 --> 00:00:24.376
And he would always know that he's about to introduce a work item that he wants done under the radar.
00:00:24.667 --> 00:00:29.376
Because he would walk up and he would say, Hey, buddy! The old, Hey buddy.
00:00:29.527 --> 00:00:30.667
That doesn't happen much though.
00:00:30.667 --> 00:00:31.056
Right?
00:00:31.207 --> 00:00:33.597
It happens all the time in product management.
00:00:33.597 --> 00:00:40.036
We call this thing, the shadow backlog the shadow backlog is real and it will haunt you.
00:00:40.307 --> 00:00:41.347
So this is your podcast.
00:00:41.396 --> 00:00:42.837
you're going to learn a lot today, hopefully.
00:00:42.987 --> 00:00:47.947
the first thing we want to talk about was this informal request is this old Pat on the back.
00:00:47.996 --> 00:00:51.116
Hey buddy, you're such a great, you use this example on other podcasts.
00:00:51.116 --> 00:00:52.616
So you're like, you're such a great developer.
00:00:52.616 --> 00:00:54.417
You can knock this out in five minutes.
00:00:54.476 --> 00:00:57.947
Or whatever your estimate is I'll just say real high, and then cut it in half.
00:00:57.996 --> 00:01:01.237
So I have referenced this before, I think, at least a couple of times.
00:01:01.487 --> 00:01:03.716
This is what I call ego stroking, basically, right?
00:01:03.746 --> 00:01:06.826
Somebody's gonna come to you and say, you're awesome, you can do this, you got this.
00:01:07.126 --> 00:01:08.206
And it won't take you long.
00:01:08.527 --> 00:01:12.257
And before you know it, days go by and you're still in the middle of this mess.
00:01:12.406 --> 00:01:22.337
definitely that is one way to spot what is coming at you In your shadow backlog because it's not defined up front in your actual backlog, and you're working on this stuff, right?
00:01:22.356 --> 00:01:26.466
Somebody told you to, or asked you to sometimes it's a bit more formal.
00:01:26.606 --> 00:01:38.796
The CEO or COO, somebody fairly high up, CXO, they'll come to you and say, I got to ask you to do this for me because we're going to show this at a conference that's taken place and it's important for the company, right?
00:01:39.087 --> 00:01:43.177
So you do it because you know, well, their management, that's another way.
00:01:43.227 --> 00:01:47.516
It's like, Hey buddy, but it's more like with a, a tone of, you want to do this?
00:01:47.576 --> 00:01:48.686
Hey buddy, or else.
00:01:48.727 --> 00:01:49.343
Yeah, Exactly.
00:01:49.343 --> 00:01:56.865
So
Load full transcript
that's another way of spotting uh, the source of uh, items that are coming into your shadow backlog.
00:01:56.915 --> 00:02:06.835
I've seen managers, direct managers in matrix organizations where the product management people and the developers are, owned by different people, different hiring managers in the organization.
00:02:06.986 --> 00:02:09.485
And then the hiring manager says, well, this is my person.
00:02:09.545 --> 00:02:14.506
They're just going to knock out this thing real quick and then there'll be available for but they haven't told anyone Right.
00:02:14.586 --> 00:02:16.286
it's taking time out of their day.
00:02:16.466 --> 00:02:16.795
Yeah.
00:02:16.936 --> 00:02:19.795
And they don't talk to product people because of that reason you mentioned, right.
00:02:19.795 --> 00:02:21.116
They're completely separate.
00:02:21.265 --> 00:02:26.955
You said, they have their people, their resources as they call them often that are seconded to the project.
00:02:27.105 --> 00:02:28.945
So yeah, they'll pull their favors.
00:02:28.945 --> 00:02:32.006
And yeah, that's another way to see shadow backlog.
00:02:32.056 --> 00:02:33.276
You don't actually see it though.
00:02:33.276 --> 00:02:34.135
Ironically, right?
00:02:34.415 --> 00:02:53.756
It's, they're kind of lurking and it's taking bandwidth away from The other, the other part of this, the, informal requests at ad hoc system of interrupting people basically that I've seen is I told this story on a podcast once a million years ago, We were integrating a vendor product into our mobile product.
00:02:53.756 --> 00:03:04.626
at the vendor company we were using, they had a development team that was producing our product and somebody thought it would be a good idea to have a shared Slack channel, our development team and their development team together.
00:03:04.776 --> 00:03:16.705
But I believe it ended up being managers and project people and whatever, what would end up happening is multiple times throughout the day, somebody would ping our developers in that channel and say, Hey, this thing.
00:03:16.855 --> 00:03:18.825
You know, this API request is coming back with this.
00:03:18.825 --> 00:03:23.545
Can you change it so it's like this or this this mobile transaction is passing these variables.
00:03:23.545 --> 00:03:24.566
We want to add another one.
00:03:24.566 --> 00:03:26.656
Can you make sure that you're accepting it on your side?
00:03:26.656 --> 00:03:28.376
I can't remember what it was like, little things like that.
00:03:28.376 --> 00:03:31.686
They would, and then our developers would go in and start making changes.
00:03:31.836 --> 00:03:34.895
And then you would say like, Hey, why are you still working on that?
00:03:34.936 --> 00:03:36.895
Like we are, I thought we were releasing that.
00:03:36.936 --> 00:03:37.265
Oh no.
00:03:37.265 --> 00:03:40.455
the vendor team asked me to add one little change.
00:03:40.626 --> 00:03:44.026
Without discussion with the product people, none of that, right.
00:03:44.036 --> 00:03:44.596
Without discussion.
00:03:44.746 --> 00:03:46.575
And that is very prevalent.
00:03:46.616 --> 00:03:51.336
I mean, anytime you have a channel that's open like that, it really needs to be very carefully curated.
00:03:51.485 --> 00:03:57.415
Otherwise you are going to run this risk, especially if stakeholders are involved because that's their conduit into the team.
00:03:57.415 --> 00:03:57.645
Yeah.
00:03:57.915 --> 00:03:58.286
Right.
00:03:58.436 --> 00:03:59.316
They're like water.
00:03:59.336 --> 00:04:10.056
They're taking the path of release resistance because they are perceiving going through the quote, normal backlog channel as you know, overly burdensome.
00:04:10.265 --> 00:04:16.045
Prohibitive sometimes you're overly bureaucratic I got to have an hour long meeting with your product manager.
00:04:16.045 --> 00:04:16.836
I don't want to do that.
00:04:16.846 --> 00:04:20.406
Or they just don't know what the correct process.
00:04:20.555 --> 00:04:20.865
Right.
00:04:20.935 --> 00:04:21.175
Yeah.
00:04:21.175 --> 00:04:21.925
That's very likely.
00:04:21.925 --> 00:04:25.755
They don't know, but just like water, I mean, it will fill up the space that's there.
00:04:25.906 --> 00:04:29.206
let's just briefly talk about ad hoc, right?
00:04:29.245 --> 00:04:31.906
So ad hoc, it's fine to have ad hoc, right?
00:04:31.925 --> 00:04:36.716
You solicit feedback from your customers and they can, they don't have to be cadenced or anything like that.
00:04:36.735 --> 00:04:40.346
they can give you the feedback at any point, but it needs to be triaged properly.
00:04:40.495 --> 00:04:40.795
Right.
00:04:40.836 --> 00:04:44.165
It needs to be carefully incorporated into the main backlog.
00:04:44.165 --> 00:04:48.396
So it doesn't end up just being worked on out of sight, out of mind in a shadow backlog.
00:04:48.545 --> 00:04:51.956
So I, I don't want us to kind of say clamp down on that.
00:04:51.956 --> 00:04:53.425
Oh, that's not what we're saying here.
00:04:53.475 --> 00:04:53.766
Right.
00:04:53.815 --> 00:04:55.605
We're just saying there's the right way to do things.
00:04:55.656 --> 00:04:57.716
So yeah, I forgot what we were going on.
00:04:57.716 --> 00:05:01.956
I was going to say we, we were just about to say, oh, it sounds like you're not a team player.
00:05:01.956 --> 00:05:04.076
When your boss comes to you and says, I need you to do this one thing.
00:05:04.076 --> 00:05:06.336
And then you say, have you talked to my product manager?
00:05:06.336 --> 00:05:15.755
Like he's he would be interested to know what when it comes yearly review time you know, same, same thing could happen if you say, well I request you to go talk to my scrum master, same thing.
00:05:15.906 --> 00:05:16.136
Yeah.
00:05:16.136 --> 00:05:18.545
Except same thing, except we can fire the scrum master.
00:05:18.696 --> 00:05:19.675
Because they work for a development.
00:05:19.675 --> 00:05:20.185
Right.
00:05:20.386 --> 00:05:21.096
That's true.
00:05:21.396 --> 00:05:25.615
So there is that, there is that real possibility that you're, you're not seen as a team player.
00:05:25.615 --> 00:05:27.766
You're not doing what someone's asking you for.
00:05:27.766 --> 00:05:29.115
You're not a true collaborator.
00:05:29.206 --> 00:05:29.586
That's right.
00:05:29.605 --> 00:05:31.446
Whereas the reality is you should really be.
00:05:31.596 --> 00:05:32.865
Not doing that.
00:05:33.014 --> 00:05:34.725
Listen, Ohm we got to move fast.
00:05:34.725 --> 00:05:36.345
We can always be talking about process.
00:05:36.384 --> 00:05:38.665
This process that that's the other way I've heard.
00:05:38.785 --> 00:05:42.564
Yeah, it's, I mean, it's very gaslighting, but speed is everything.
00:05:42.564 --> 00:05:52.024
Yeah, that's how I've heard people justify this, this, what we're talking about now, this informal request system of you, you, you, you scratch my back and I don't fire you.
00:05:52.175 --> 00:05:53.225
There's no benefit in it.
00:05:53.225 --> 00:05:57.735
I mean, it's just it actually is making your day worse because now you're failing on everything else you committed to, Right.
00:05:57.754 --> 00:05:58.014
Yeah.
00:05:58.014 --> 00:05:59.805
There's really nothing good that can come out of it.
00:06:00.144 --> 00:06:08.365
If I'm going to be a little more like the informal request network, altering the products and whatever, I'll be harsh on that one because rightfully so like I should be.
00:06:08.514 --> 00:06:13.985
Workarounds and quick fixes or hot fixes or, you know break fixes.
00:06:13.985 --> 00:06:18.454
basically something breaks in production and we now have to have the fire drill to put it out.
00:06:18.605 --> 00:06:33.185
this is one of the categories where like of course We should stop what we're doing and fix that You know the only I feel nobody gets into trouble with prioritization with this one I feel where people get into troubles when they have systems where this stuff happens all the time Now you can't be a your commitments because you you have no control of this.
00:06:33.334 --> 00:06:38.845
Well that speaks to Volumes to the quality or lack of it of the process as well as the product.
00:06:38.884 --> 00:06:39.685
Maybe so.
00:06:39.865 --> 00:06:41.194
But there is something else there, right?
00:06:41.204 --> 00:06:42.935
If you're fixing things in production.
00:06:43.084 --> 00:06:49.254
Okay, you have to fix things, so fine, do it, but at the same time, don't neglect documenting things, right?
00:06:49.435 --> 00:06:53.654
Don't neglect reflecting back and figuring out why is it, could we have avoided it?
00:06:53.675 --> 00:06:55.714
How can we not repeat that again?
00:06:55.865 --> 00:07:01.894
So all of those things have to follow and typically you find that because you're at the tyranny of time, right?
00:07:01.915 --> 00:07:05.154
They don't follow because you're just break fixing after break fixing.
00:07:05.485 --> 00:07:08.904
Well, that's the thing about quick fixes is they're done quickly.
00:07:09.055 --> 00:07:13.555
Who's to say that like that ever makes it back to the permanent code.
00:07:13.654 --> 00:07:16.795
Like I have seen quick fixes that are applied in production.
00:07:16.944 --> 00:07:23.685
And then the next time a release rolls out into production, the thing gets broken again because it was never really fixed.
00:07:23.735 --> 00:07:24.345
yeah, exactly.
00:07:24.495 --> 00:07:24.764
Yeah.
00:07:24.764 --> 00:07:25.975
I've seen that for sure.
00:07:25.975 --> 00:07:27.735
Especially in products where.
00:07:28.084 --> 00:07:33.384
You can do that through scripting or some other means or manipulating SQL or whatever it is, right?
00:07:33.535 --> 00:07:36.365
So that's really masking the symptom, right?
00:07:36.365 --> 00:07:37.814
It's not fixing the root cause.
00:07:37.964 --> 00:07:40.814
But again, it comes down to sound engineering principles there, right?
00:07:40.814 --> 00:07:46.654
If you're going to fix it, fix it, but then do a proper fix, put it into the code, test it and all of that.
00:07:46.675 --> 00:07:46.915
Right.
00:07:46.944 --> 00:07:51.545
Unless it's pressure tested before it releases again, you're going to find that it's never really fixed.
00:07:51.685 --> 00:07:54.144
But allow me to make the situation way worse.
00:07:54.154 --> 00:08:00.545
So now our team that does feature development, we say, well, we want to unburden them just to be purely feature development.
00:08:00.654 --> 00:08:05.754
So we're going to hire this other team that they're just going to do break fixes in production because it's become such a problem.
00:08:05.975 --> 00:08:07.824
So now this other team that is constantly.
00:08:07.975 --> 00:08:15.694
In the code, this new team, doing break fixes, maybe an offshore team, it's doing break fixes and responding to support issues.
00:08:15.845 --> 00:08:22.704
They're in the code base, fixing issues that come up while the other team is introducing new features into the code at the same time.
00:08:22.704 --> 00:08:25.375
So both those teams are working at the same time and now.
00:08:25.524 --> 00:08:30.084
You see where the, like the, you're on the Titanic at this point and like knowing what's about to happen, right?
00:08:30.235 --> 00:08:31.834
Yeah, that's a better analogy.
00:08:31.834 --> 00:08:36.745
I was thinking, well, you're trying to change the tires on a car while it's being driven on the highway at 60 miles an hour.
00:08:36.754 --> 00:08:38.514
You're trying to change tires on the Titanic.
00:08:38.664 --> 00:08:39.375
Yeah, that's right.
00:08:39.524 --> 00:08:40.625
While it's still.
00:08:40.774 --> 00:08:41.904
Halfway in the water.
00:08:42.054 --> 00:08:48.264
No, it's, it's pandemonium at that point because people aren't talking to one another, especially if you have dedicated teams.
00:08:48.264 --> 00:08:51.345
So how do you, how do you
survive in that long term?
00:08:51.404 --> 00:08:56.065
I just can't wait for the person that's going to comment on this and be like, Brian, that scenario is ludicrous.
00:08:56.065 --> 00:08:56.934
No one would ever do that.
00:08:57.115 --> 00:09:00.225
Like I only bring that up because I lived through that exact experience.
00:09:00.375 --> 00:09:01.644
I like to talk to that person.
00:09:01.644 --> 00:09:02.664
Cause it happens all the time.
00:09:02.794 --> 00:09:03.465
Oh boy.
00:09:03.485 --> 00:09:12.024
We have so much, we have so, it's so unstable, like quality is so bad that we have to get another team that their job is just to do like quality improvements.
00:09:12.144 --> 00:09:20.245
But basically bug fixes, they'll wrap it is quality improvement I've seen Not, they don't have entire teams to do it, but I have seen them dedicate one developer.
00:09:20.245 --> 00:09:22.115
Well, that's the on call developer this week.
00:09:22.134 --> 00:09:33.914
Their job is just to catch all the bugs and garbage that blows up So in the former where we have a separate team or even a developer, it leads to this behavior from your development team that let's just, Scaffold it up.
00:09:33.914 --> 00:09:35.034
If it breaks, they'll fix it.
00:09:35.184 --> 00:09:35.605
Right?
00:09:35.894 --> 00:09:36.924
And that's terrible.
00:09:37.134 --> 00:09:40.434
Because you're releasing code that's not of quality to begin with.
00:09:40.585 --> 00:09:42.375
I'm a big fan of you build it, you run it.
00:09:42.524 --> 00:09:45.245
Oh, you're not a big fan of we, we Throw it over the wall?
00:09:45.245 --> 00:09:46.684
We'll fix it and document it later?
00:09:46.686 --> 00:09:49.245
Because later never comes.
00:09:49.394 --> 00:09:51.715
Oh man, somehow this needs to be a separate podcast.
00:09:51.764 --> 00:09:56.955
I want to let my feature team just develop features and put all the maintenance and refactoring off this other team.
00:09:57.284 --> 00:09:59.154
Like whoever thought that was a good idea.
00:09:59.154 --> 00:10:00.804
Like it needs its own podcast.
00:10:00.865 --> 00:10:01.914
I don't know what it would be called.
00:10:01.914 --> 00:10:03.245
Doing a whole podcast on that.
00:10:03.254 --> 00:10:04.424
Cause there's so much there.
00:10:04.434 --> 00:10:06.134
It's not just people that fix your stuff.
00:10:06.134 --> 00:10:11.134
It's also potentially people that are putting your code into production of your team is not right.
00:10:11.284 --> 00:10:14.315
these teams will go fix things quickly because well.
00:10:14.465 --> 00:10:17.004
They're the ones in charge of putting things into production.
00:10:17.004 --> 00:10:18.264
And if he breaks, it looks bad on them.
00:10:18.264 --> 00:10:22.465
So they fix it up, but he never gets back to the dev team and doesn't get back to the main branch.
00:10:22.615 --> 00:10:23.465
And that's the problem.
00:10:23.495 --> 00:10:27.945
Learnings don't get back, nor does the skill get back, which
leaves you with a whole nother problem.
00:10:28.095 --> 00:10:28.615
Correct.
00:10:28.764 --> 00:10:38.394
And so potentially you could have not a shadow backlog, but multiple shadow backlog, we're already very, very, very close to be talking about technical debt right now.
00:10:38.394 --> 00:10:40.085
So let's just launch straight into.
00:10:40.235 --> 00:10:50.455
The technical debt backlog, at more than one place so I'm not trying to call anyone out, but more than one place, the developers some places the developers will revolt and say like, we must fix this.
00:10:50.455 --> 00:10:51.445
We can't wait anymore.
00:10:51.595 --> 00:11:03.164
Sometimes they'll try to be proactive overly cautiously proactive to say like, Oh, we've got to have a, a completely separate roadmap to, of how we're going to fix technical debt and improve the systems and bring them up to date.
00:11:03.475 --> 00:11:05.445
Whatever SPAC or current version, whatever it is.
00:11:05.445 --> 00:11:20.365
So they'll try to have their own parallel backlog because usually the people that lead engineering at a high level in organization, they're pretty much charged with like, Hey, how can we have all these systems that are falling over they get pointed out to say you're doing a bad job because they're the ones looking at quality dashboards and things.
00:11:20.384 --> 00:11:25.455
I mean, in reality, it's a partnership between engineering and product management that resolves the technical debt.
00:11:25.455 --> 00:11:36.715
So it's not, it's kind of not fair just to point at the engineering leadership to say you're not doing a good job cause you could have, you could have product people that completely don't understand what it takes to keep the system moving.
00:11:36.865 --> 00:11:40.375
They're completely disconnected from what's happening with the technology under hood.
00:11:40.654 --> 00:11:44.865
And they just I was gonna say go to lunch all day, but also they just asked for features.
00:11:45.014 --> 00:11:47.144
They don't want to do any technical under hood stuff.
00:11:47.144 --> 00:11:47.945
They don't understand it.
00:11:47.945 --> 00:11:48.914
They don't want to talk about it.
00:11:49.065 --> 00:11:52.355
I've been in a room with executives actually that are like this.
00:11:52.504 --> 00:11:53.605
They only want features.
00:11:53.804 --> 00:11:55.985
They don't want to talk about the systems under hood.
00:11:56.134 --> 00:11:57.144
They don't want to pay for things.
00:11:57.144 --> 00:11:58.585
They don't want to spend any development time on it.
00:11:58.625 --> 00:12:04.975
and honestly, like if you start talking about anything like this, sometimes you go into the weeds to talk about how a feature would be solutioned.
00:12:05.105 --> 00:12:05.315
Yeah.
00:12:05.654 --> 00:12:06.794
Like people do, right?
00:12:07.105 --> 00:12:07.794
They'll zone out.
00:12:07.794 --> 00:12:10.875
Like I had a guy once who would get up and practice his golf swing.
00:12:11.144 --> 00:12:12.615
He would do shadow golf swings.
00:12:12.674 --> 00:12:13.634
in a conference room.
00:12:13.784 --> 00:12:17.174
When the developers would start talking I don't know if I'm going to keep this story in the podcast.
00:12:17.375 --> 00:12:18.034
It's so good.
00:12:18.034 --> 00:12:19.894
I can't, I can't stop myself from telling it though.
00:12:19.965 --> 00:12:21.674
So he's an executive, right?
00:12:21.705 --> 00:12:27.355
They brought him in I think 'cause he had like deep ties with a particular customer we were trying to sell anyway, and they're like, we don't know what to do with you.
00:12:27.355 --> 00:12:28.855
You're gonna run development department.
00:12:28.860 --> 00:12:30.475
So he became in charge of the development department.
00:12:30.475 --> 00:12:31.585
This C the c-level exec.
00:12:31.585 --> 00:12:32.514
I don't remember what his title was.
00:12:32.845 --> 00:12:36.955
Anyway, this guy comes in, he could not care about technology at all.
00:12:36.955 --> 00:12:38.784
He, when we would, he would practice his golf.
00:12:38.845 --> 00:12:39.115
I see.
00:12:39.355 --> 00:12:40.284
I still remember him.
00:12:40.534 --> 00:12:41.924
Practicing his golf swing.
00:12:43.095 --> 00:12:44.605
I still remember him practicing.
00:12:44.654 --> 00:12:46.595
Well that just tells you what the company thought.
00:12:46.615 --> 00:12:47.164
Yeah of course.
00:12:47.315 --> 00:12:57.945
But I still remember him practicing his golf swing while we were talking about something highly technical that needed to be solved before we could launch some feature or scale the system or do something basically.
00:12:58.095 --> 00:13:01.034
And He could care less playing golf in a corner.
00:13:01.365 --> 00:13:02.865
He didn't last surprisingly.
00:13:02.875 --> 00:13:09.054
I remember talking to somebody years later after that guy had left who was like a senior developer who worked their way up in that company.
00:13:09.205 --> 00:13:10.735
And I was like, man, that guy.
00:13:10.934 --> 00:13:12.235
What a piece of work that guy.
00:13:12.235 --> 00:13:15.595
And then I remember the person who is developer was like, actually, it wasn't that bad.
00:13:15.745 --> 00:13:17.514
I'm like, what are you talking about?
00:13:17.815 --> 00:13:20.105
What were you on a different planet than I am?
00:13:20.254 --> 00:13:21.394
Actually, it wasn't that bad.
00:13:21.544 --> 00:13:27.934
I think wasn't that bad means I can do whatever technical debt I want and he'll, he won't challenge it because he has no idea.
00:13:28.034 --> 00:13:29.384
I think that's what it meant.
00:13:29.384 --> 00:13:34.065
He would either ignore what I'm doing and implicitly just approve it or he'll rubber stamp it.
00:13:34.065 --> 00:13:35.534
He'll just say, yeah, that's fine.
00:13:35.684 --> 00:13:36.375
It sounds good.
00:13:36.404 --> 00:13:42.004
I think that's what he meant by he wasn't that bad is that he didn't get into details or challenge
you about details because he couldn't.
00:13:42.065 --> 00:13:42.565
Right.
00:13:42.664 --> 00:13:44.975
But again, that guy had no business in business at all.
00:13:45.144 --> 00:13:47.965
That's that was my opinion on him and I still feel that way.
00:13:48.654 --> 00:13:49.945
He's probably out there winning the U.
00:13:49.945 --> 00:13:50.085
S.
00:13:50.085 --> 00:13:50.735
Open right now.
00:13:50.784 --> 00:13:53.134
we may or may not be returning from a Segway right now.
00:13:53.284 --> 00:13:54.485
About golf.
00:13:54.634 --> 00:14:01.534
But yeah, the refactoring in order to solve technical debt, everyone can pretty much understand, like developers, like they, they see it happen.
00:14:01.544 --> 00:14:07.485
They, if you're, you're not going to give them the space to do it and it's painful enough, they're just going to go do it themselves, completely understand that.
00:14:07.565 --> 00:14:08.215
No problem.
00:14:08.365 --> 00:14:12.715
But the optimum is the underhood optimization that you could basically spend forever on.
00:14:12.865 --> 00:14:15.784
Like that, that is the other place that I've seen this goodness.
00:14:15.784 --> 00:14:15.975
Yeah.
00:14:16.184 --> 00:14:18.134
So tuning, right.
00:14:18.184 --> 00:14:21.705
Tuning and then forever refining and polishing.
00:14:21.715 --> 00:14:21.995
Right.
00:14:22.235 --> 00:14:22.605
Right.
00:14:22.634 --> 00:14:23.485
Gilding the lily.
00:14:23.514 --> 00:14:23.725
Right.
00:14:23.975 --> 00:14:25.465
So yeah, definitely have seen that.
00:14:25.615 --> 00:14:28.134
Especially, so there's two sides to this though, right?
00:14:28.184 --> 00:14:33.174
I have seen some developers that are so passionate about their work that they just want to keep improving.
00:14:33.495 --> 00:14:34.245
It can be better.
00:14:34.345 --> 00:14:36.294
I can make it 2 percent faster.
00:14:36.445 --> 00:14:37.794
I can optimize the queries.
00:14:37.945 --> 00:14:39.745
Nobody really is complaining about it.
00:14:39.894 --> 00:14:40.254
Right?
00:14:40.595 --> 00:14:41.524
But they're into it.
00:14:41.794 --> 00:14:42.654
There's that side of it.
00:14:42.705 --> 00:14:47.304
The other side of it is Save that one, because that one, when we talk about personal tasks, Oh yeah, yeah, yeah.
00:14:47.585 --> 00:14:48.684
That's definitely in that category.
00:14:48.735 --> 00:14:51.225
Is you guys are not taking this feature seriously enough.
00:14:51.375 --> 00:14:53.504
I'm going to go show you how good it could be.
00:14:53.504 --> 00:14:56.375
I've seen people spend nights and weekends doing that for sure.
00:14:56.375 --> 00:14:57.565
You're not going to get time in the backlog.
00:14:57.575 --> 00:14:58.495
We've talked about it.
00:14:58.625 --> 00:15:01.375
That ship has sailed and they go do an anyway on nights and weekends.
00:15:01.375 --> 00:15:02.514
And now they're burning themselves out.
00:15:02.664 --> 00:15:03.705
Is burning them out.
00:15:03.705 --> 00:15:03.975
Right.
00:15:04.004 --> 00:15:08.235
But I've seen people do it during their work days and they're not doing the committed features.
00:15:08.284 --> 00:15:08.644
Right.
00:15:08.965 --> 00:15:10.475
So there's two sides to it.
00:15:10.684 --> 00:15:11.904
Just briefly go back to.
00:15:12.059 --> 00:15:21.340
This idea of having the break fixes under like one leader manager and net new features functionality under different one, maybe product, right?
00:15:21.490 --> 00:15:25.330
Of course, they're going to protect their turf, they're not going to talk to one another.
00:15:25.480 --> 00:15:27.799
The person who has all these fixes to do.
00:15:27.950 --> 00:15:30.909
They're not going to go back to the product and say, can we just fix it?
00:15:30.909 --> 00:15:32.840
So that our processes and so forth.
00:15:33.090 --> 00:15:36.159
So we don't have as much to fix because well, they're employed.
00:15:36.309 --> 00:15:38.679
So it's their vested interest that they're protecting.
00:15:38.679 --> 00:15:41.679
I think it goes back to that whole org design thing again.
00:15:41.779 --> 00:15:42.019
Yeah.
00:15:42.029 --> 00:15:44.730
You know, how you organized in your company, right?
00:15:44.980 --> 00:15:47.240
I like the, there's so much to talk about here.
00:15:47.279 --> 00:15:49.070
I want to have a whole podcast on technical debt.
00:15:49.100 --> 00:15:51.210
there's so much here that I want to talk about.
00:15:51.210 --> 00:15:53.945
we have yet to even talk about the.
00:15:54.095 --> 00:16:05.245
Maintenance of legacy systems and, estimates on legacy systems when the people giving the estimates are not the people that built the legacy system, you bring on people to maintain a legacy system where you have new developers and the old developers are gone.
00:16:05.245 --> 00:16:06.945
Like your estimates are all garbage.
00:16:07.095 --> 00:16:12.335
You know, it always takes a long time to do something and you resist doing stuff to that other system or.
00:16:12.654 --> 00:16:18.174
Migrating it or touching it or spending any time that involves the the cost quality that you hadn't noted before.
00:16:18.174 --> 00:16:21.345
Like there's so many things I want to talk about in this, in this tech debt category.
00:16:21.495 --> 00:16:26.394
I think on that legacy one, oftentimes because legacy, I mean, it's old technology, right?
00:16:26.445 --> 00:16:32.034
And people that are well versed with the latest technologies have this Dunning Kruger effect that they're thinking.
00:16:32.184 --> 00:16:32.975
I can do that.
00:16:33.125 --> 00:16:34.654
I mean, that's not, that's old tech.
00:16:34.745 --> 00:16:35.605
I can do that.
00:16:35.654 --> 00:16:35.934
Yeah.
00:16:36.014 --> 00:16:36.264
Right.
00:16:36.304 --> 00:16:44.434
I can read COBOL if I have four hours to read the code, it's not that hard, but that's where they're wrong because they don't have documentation or worse yet.
00:16:44.445 --> 00:16:46.095
They don't have the domain
knowledge.
00:16:46.095 --> 00:16:49.735
To fix things in whatever the old, the old languages were.
00:16:49.764 --> 00:16:50.485
It's not old tech.
00:16:50.495 --> 00:16:51.394
It's lost tech.
00:16:51.394 --> 00:16:52.215
It's lost tech.
00:16:52.274 --> 00:16:53.164
The long lost tech.
00:16:53.384 --> 00:16:54.534
What program am I thinking of?
00:16:54.534 --> 00:16:57.674
the technology is so advanced that the human beings forgot.
00:16:57.904 --> 00:17:02.884
I don't know if it's like Wally or one of the, basically the P the people are living, is it twilight zone?
00:17:02.904 --> 00:17:10.674
I don't remember what it was like the people are living on the ship, but the people that are living on the ship are like far removed descendants from the people that built the ship and they lost the ability.
00:17:10.825 --> 00:17:15.065
To work on the ship and you know, that's real that is real when you're working on legacy.
00:17:15.214 --> 00:17:15.775
That's this.
00:17:15.775 --> 00:17:21.174
Yeah, that's exactly this So their estimates though coming back to that right their estimates are very ambitious.
00:17:21.515 --> 00:17:28.045
I could fix that in a day Yeah, and 15 days later, they're still into it, right not their fault necessarily, but that's reality.
00:17:28.095 --> 00:17:36.424
It happens all the time Yeah, yeah going down a rabbit hole, trying to figure out That like that exploratory work as like I work with many, many developers who do that.
00:17:36.454 --> 00:17:37.994
and you know what to be honest, I do that.
00:17:38.095 --> 00:17:40.355
I spent two hours on something that wasn't working.
00:17:40.505 --> 00:17:57.954
Normally, I won't spend that much time on two hours is an immense amount of time for me in one Pomodoro like one go for me, like two hours back to back straight uninterrupted sitting at my computer, like two hours is amazing that I can pound out a bunch of stuff that's super helpful to me in two hours.
00:17:58.105 --> 00:18:03.494
But I had this two hours I spent trying to figure out why an API response wasn't coming back properly.
00:18:03.644 --> 00:18:04.394
Total waste of time.
00:18:04.545 --> 00:18:09.424
And even when I'm doing it, I know I'm spending way more time, but it's like the next, the next hit is going to work.
00:18:09.575 --> 00:18:10.654
The next hit is going to work.
00:18:10.884 --> 00:18:13.434
You know, the next thing is the gambler syndrome, right?
00:18:13.454 --> 00:18:18.005
You're really is the next spin is going to land the ball exactly on the number I'm gambling on.
00:18:18.045 --> 00:18:19.065
It really is.
00:18:19.095 --> 00:18:29.474
But the idea that you need to keep this stuff in a separate roadmap and lobby and do whatever and have a big bang or, Oh, we have to have a big project to do this stuff or introduce a new database or cut over to a database or whatever.
00:18:29.625 --> 00:18:35.204
No, if you can't do it as a normal part of your normal stream work, it's highly likely that you can't do it.
00:18:35.355 --> 00:18:35.664
Right.
00:18:35.815 --> 00:18:37.904
Technical debt is why I think it should be a different podcast.
00:18:38.055 --> 00:18:38.664
We will do one.
00:18:38.674 --> 00:18:43.025
It worries me as a product manager who used to be on development teams.
00:18:43.174 --> 00:18:48.704
It worries me because is a product manager who's empowered with prioritization, like that's their role.
00:18:48.855 --> 00:18:50.085
Do they really understand?
00:18:50.234 --> 00:19:04.805
what being versions behind or what being on this old technology or what being on several versions behind on the technology or not migrating to the latest technology that's purposely built for this or being on this old version of the language, do they really understand what that means?
00:19:04.954 --> 00:19:16.285
And do they re and can they illustrate in front of management when management is playing golf, that golf swing guy who doesn't know anything about technology, couldn't care less running a tech company.
00:19:16.609 --> 00:19:20.839
Couldn't care less about technology when they're dealing with that flippant attitude.
00:19:20.990 --> 00:19:22.500
Can they make it matter?
00:19:22.670 --> 00:19:28.990
The product manager, can they take all the concerns of the dev team and understanding of technology and make it matter to that person?
00:19:28.990 --> 00:19:31.059
Can they weave that story and make it matter to that person?
00:19:31.210 --> 00:19:38.450
I'm super worried when I, again, like most of the product managers, the advice that you'll see online is partner with your engineering lead.
00:19:38.795 --> 00:19:40.174
Have them help you do it.
00:19:40.214 --> 00:19:43.805
Believe your dreams, get lunch all day, beefcake, that's not good enough.
00:19:44.125 --> 00:19:48.424
Listen, you're describing a unicorn of a product manager who can actually do that, right?
00:19:48.454 --> 00:19:52.845
I found, I mean, there are very few that are technical enough to understand these things.
00:19:52.884 --> 00:19:53.214
Right.
00:19:53.365 --> 00:19:56.585
So yeah, we were talking before the podcast about teams wanting to.
00:19:56.734 --> 00:19:59.444
Upgrade To a new library or something like that.
00:19:59.595 --> 00:20:03.644
The product people aren't necessarily aware of the reasons why that should be done or not done.
00:20:03.644 --> 00:20:05.325
Visualization libraries is what we're talking about.
00:20:05.375 --> 00:20:07.234
But it could be, it could be anything though, right?
00:20:07.525 --> 00:20:10.474
visualization libraries are a really good example because they're in your face.
00:20:10.515 --> 00:20:11.174
six months.
00:20:11.174 --> 00:20:11.724
They're outdated.
00:20:11.765 --> 00:20:13.244
They move so fast.
00:20:13.355 --> 00:20:13.724
exactly.
00:20:13.724 --> 00:20:15.255
So I think it's a tall order.
00:20:15.394 --> 00:20:17.424
How do you partner with the engineering lead?
00:20:17.424 -->
00:20:19.765
If they the type of people that you're describing, right?
00:20:19.775 --> 00:20:20.424
It's hard.
00:20:20.664 --> 00:20:21.125
It is hard.
00:20:21.125 --> 00:20:34.095
the only other thing about technical debt, kind of, that's wrapped up in the legacy systems and technical debt to bring up here is, and it's only tangentially part of the shadow backlog is sometimes you will run into these hero developers.
00:20:34.095 --> 00:20:43.934
these wolf developers who have found themselves Outside of a team Also the other moniker that is relevant to these people is the Paris Hilton developer.
00:20:44.079 --> 00:20:45.049
Let, I haven't heard that one.
00:20:45.085 --> 00:20:46.315
Let explain, let me explain.
00:20:46.464 --> 00:20:49.644
I'm glad, I'm glad I can be the first one to lay this on you in this podcast.
00:20:49.644 --> 00:20:50.065
Yeah, I haven't heard that.
00:20:50.065 --> 00:20:51.920
you know the Wolf developer, you know that?
00:20:51.924 --> 00:20:51.925
Yeah.
00:20:51.984 --> 00:20:52.765
They work alone.
00:20:52.769 --> 00:20:54.265
They're only working on the latest fire.
00:20:54.265 --> 00:20:55.164
They're seen as a hero.
00:20:55.194 --> 00:20:56.365
'cause they go from fire to fire.
00:20:56.365 --> 00:20:58.255
they're the people that can do, do things.
00:20:58.305 --> 00:20:59.964
The Paris Hilton developer is like that.
00:21:00.035 --> 00:21:02.184
they're famous for being famous.
00:21:02.335 --> 00:21:18.694
They're at all the parties, they're at all the release events, they're at all the launches, you gotta get them in the room to have them in the room, but they're not really part of any team, they don't work on anything significant that you can remember, they just happen to be there whenever significant things happen, they're a developer that's really good at being there.
00:21:18.845 --> 00:21:20.605
When significant things are happening.
00:21:20.904 --> 00:21:24.384
So it's interesting because I actually have come across this.
00:21:24.575 --> 00:21:25.634
This should be a podcast.
00:21:25.785 --> 00:21:28.285
Our podcast should have been the Paris Hilton developer.
00:21:28.285 --> 00:21:29.355
That's a good title.
00:21:29.664 --> 00:21:32.244
I've come across architects that fall in this category.
00:21:32.555 --> 00:21:33.384
They go around.
00:21:33.424 --> 00:21:35.944
I don't know if architects can exist in any other category.
00:21:36.095 --> 00:21:36.525
Fair point.
00:21:36.525 --> 00:21:38.265
They go around with their little dog in their purse.
00:21:38.295 --> 00:21:40.365
Yeah, they go around looking all important.
00:21:40.414 --> 00:21:42.765
You know, they go ask the teams that they're working on.
00:21:42.825 --> 00:21:43.914
Offer their two cents.
00:21:43.954 --> 00:21:45.865
No, don't pick up the glass that way.
00:21:45.865 --> 00:21:46.795
Pick it up this way.
00:21:46.944 --> 00:21:49.265
Not that it matters, but you know, yeah, yeah.
00:21:49.265 --> 00:21:50.974
Pick it up and then that's it.
00:21:50.974 --> 00:21:51.934
They just hover around.
00:21:52.220 --> 00:21:54.130
They butterfly in and they butterfly out.
00:21:54.390 --> 00:21:56.180
So yeah, I've come across those guys.
00:21:56.190 --> 00:21:57.039
Oh, I know.
00:21:57.049 --> 00:21:59.539
Like when I, when you say it out loud, you're like, actually.
00:21:59.690 --> 00:22:01.299
I do know a few of those people.
00:22:01.450 --> 00:22:04.839
But you know what they do is they're really good at sticking around for a long time.
00:22:04.940 --> 00:22:14.299
staying in the media, What things is Paris Hilton good at staying in the, staying in the public eye, staying in the public eye, being seen.
00:22:14.359 --> 00:22:18.000
Right, but also knowing where to be at a certain time.
00:22:18.150 --> 00:22:22.509
You can't do that unless you're hoarding all that knowledge that someone might eventually need.
00:22:22.509 --> 00:22:23.250
Great point, yes.
00:22:23.400 --> 00:22:31.809
so again, the Paris Hilton developer is what I, my example of someone who's hoarding knowledge for their own benefit, not necessarily for anyone else's benefit.
00:22:31.950 --> 00:22:40.539
the quiet, Developer that kind of just goes from team to team and mentors the new people, walks them through the code, does code reviews for other people.
00:22:40.539 --> 00:22:44.210
Like those people don't get any of the glitz and the cameras that the Paris Hilton developer gets.
00:22:44.250 --> 00:22:46.279
they don't get to rescue the situation, right?
00:22:46.480 --> 00:22:48.980
This person does by hoarding knowledge.
00:22:48.990 --> 00:22:54.609
They do rescue the situation, but when they do it, they attribute it to the team and they don't take it personally on their own.
00:22:54.759 --> 00:22:55.519
Actual team player.
00:22:55.720 --> 00:22:58.980
But Paris Hilton is looking to be in front of the camera Exactly.
00:22:59.309 --> 00:22:59.460
Yeah.
00:22:59.460 --> 00:23:01.690
Don't be a Paris Hilton developer is what we're saying right now.
00:23:01.710 --> 00:23:02.359
Exactly.
00:23:02.369 --> 00:23:04.000
Just carry your lapdog in your purse.
00:23:04.029 --> 00:23:05.539
Not, not all that knowledge.
00:23:05.690 --> 00:23:09.549
Well, This is going to be a hard one to segue from, but I'm going to try.
00:23:09.809 --> 00:23:12.799
We said we would save personal tasks until it's own category.
00:23:12.799 --> 00:23:14.740
Do you remember why we said we would save personal tasks?
00:23:14.740 --> 00:23:16.490
Oh, no, it was, I had a solution.
00:23:16.640 --> 00:23:18.369
And then we chose not to implement that solution.
00:23:18.369 --> 00:23:20.180
So I'm going to do it on nights and weekends.
00:23:20.279 --> 00:23:20.630
That's right.
00:23:20.630 --> 00:23:26.420
Yeah, that was, so those kinds of personal tasks where the product manager says, I'm not going to do this.
00:23:26.759 --> 00:23:28.019
I don't want to spend time on it.
00:23:28.029 --> 00:23:33.480
Like
it's outside of the sprint goal and it's outside of any of our goals for the quarter or whatever, right?
00:23:33.529 --> 00:23:36.559
And like, it doesn't line up with any of our goals, so I don't want to spend any time on it.
00:23:36.779 --> 00:23:37.680
And developer says.
00:23:38.000 --> 00:23:39.130
Well, I think it's important.
00:23:39.200 --> 00:23:40.269
I'm going to do it anyway.
00:23:40.299 --> 00:23:43.730
I'm going to do it on nights a week I'm going to show you that people like listen.
00:23:43.730 --> 00:23:47.740
I'm conflicted on this one and I'll tell you why because I do this.
00:23:47.890 --> 00:23:49.079
That's my confession.
00:23:49.220 --> 00:24:01.240
I do this I don't do as I do I do nights and weekends development To say, I'm going to go figure out how to query this database to go get the exact right data to use in this thing.
00:24:01.240 --> 00:24:03.940
And then tell the development team Hey, I can get this query.
00:24:03.940 --> 00:24:05.789
This is not exactly what we're talking about, what I'm doing.
00:24:05.940 --> 00:24:15.019
Is implementing like a feature or, or basically anything else like a, an NFR, a technical debt thing, something that I think that we're falling behind on.
00:24:15.019 --> 00:24:16.410
So I'm going to go do it.
00:24:16.559 --> 00:24:25.349
Like I, again, I, I have where I do things like this is I'll say, Hey, we don't have a, we don't have a program to query something from this database.
00:24:25.500 --> 00:24:34.269
And query something from this database and then put those two things together and send out a report and so that we can make this other decision and I could ask my development team to do it.
00:24:34.319 --> 00:24:38.509
It is development work, but it doesn't line up with any of our quarterly goals.
00:24:38.849 --> 00:24:40.710
It really doesn't take that long to get the data.
00:24:40.859 --> 00:24:55.230
The only pain is it's a manual one time thing when I want to go get the data So it takes me 30 minutes or whatever But if I can spend an hour and a half in the middle of the night and automate the process Number one I can make life easier on everybody that's looking for that data Number two, I don't have to ask the development team to do it.
00:24:55.230 --> 00:24:55.650
Number three.
00:24:55.650 --> 00:25:03.835
I don't have to lobby To make it a quarterly goal to do internal automation, to make whatever X, Y, Z, easier, whatever process I'm trying to do.
00:25:03.894 --> 00:25:04.174
You know what I mean?
00:25:04.174 --> 00:25:08.914
So like I do this all the time, so it's tough for me to talk about this one because I certainly do.
00:25:09.115 --> 00:25:14.204
if you're doing it, this doesn't matter if you're doing it or developers doing it, there's an opportunity cause you're doing something.
00:25:14.555 --> 00:25:18.934
If you're doing it out in your own time, evenings and weekends, you're still burning yourself out.
00:25:18.984 --> 00:25:19.974
A hundred percent agree.
00:25:20.194 --> 00:25:23.664
So I mean, I'm a little conflicted on it for a different reason.
00:25:23.674 --> 00:25:30.295
Are we really constraining the innovation that people can bring to the table by not allowing this to happen, right?
00:25:30.595 --> 00:25:37.815
So maybe, Maybe one thing to consider is reserve a bit of time every so often and have a hackathon.
00:25:37.825 --> 00:25:40.474
Let, let teams come up with basically what Google does, right?
00:25:40.775 --> 00:25:43.454
Let the teams come up with some innovation in that way.
00:25:43.765 --> 00:25:45.904
So that's their channel at the same time.
00:25:45.904 --> 00:25:50.789
You can protect the main backlog and make sure that people aren't distributed across seeing an unseen work.
00:25:50.789 --> 00:25:51.555
If you will.
00:25:51.615 --> 00:25:53.224
I wonder, I don't see this going away.
00:25:53.375 --> 00:25:54.075
This is what I'm saying.
00:25:54.224 --> 00:25:55.785
As long as people are there, they won't go.
00:25:55.785 --> 00:25:55.994
Right.
00:25:56.025 --> 00:25:56.654
That's what I'm saying.
00:25:56.654 --> 00:25:59.954
I don't see this going away, but I wonder 20 years from now.
00:26:00.105 --> 00:26:08.105
If the broad view of product development I wonder what the number of loading your developers down per week would be.
00:26:08.414 --> 00:26:09.734
So like what you just said.
00:26:09.744 --> 00:26:13.484
it sparked an idea in my head, which is like, maybe I don't want to load my developers.
00:26:13.484 --> 00:26:16.545
Like in America, 40 hour workweek, like that's the standard.
00:26:16.605 --> 00:26:19.825
some people will say 45, they're trying to squeeze a little more out of you, whatever.
00:26:19.825 --> 00:26:19.890
Right.
00:26:20.039 --> 00:26:27.900
I want to think like, what if the work week in the future is like 25 hours and we're reserving another 10 hours ish, right?
00:26:28.049 --> 00:26:34.019
Cause some of those hours that are spent at work are spent on purely administrative stuff that's not, it doesn't advance your work at all.
00:26:34.049 --> 00:26:35.440
So there are some hours to do that.
00:26:35.440 --> 00:26:40.609
Let's say we're only going to load developers down to 25 hours a week, and then we're reserving that other 10 hours.
00:26:40.759 --> 00:26:42.009
Whatever, eight hours, six hours.
00:26:42.009 --> 00:26:54.119
We can negotiate on a number, but we're reserving a number of hours per week on just things that the developer sees that need to be corrected, that they can just jump on because again, they're the people closest to the problems.
00:26:54.400 --> 00:27:07.640
So it does make sense to reserve some of their time for this category, this personal task category to reserve some of their time to counter what I'm saying, which is I do this, I can't expect my developers to not do this because if I'm doing it.
00:27:07.954 --> 00:27:09.055
And I'm leading the team.
00:27:09.404 --> 00:27:13.664
I'm basically
setting the example that people are going to see, and they're going to follow my example.
00:27:13.974 --> 00:27:17.255
So I guess what I'm saying is I am leading and propagating this.
00:27:17.505 --> 00:27:19.795
So can I alter the system?
00:27:19.944 --> 00:27:21.234
Cause I can't alter my behavior.
00:27:21.565 --> 00:27:22.615
My behavior is set in stone.
00:27:22.664 --> 00:27:25.234
Like the real, that's the real fix here is Brian.
00:27:25.244 --> 00:27:25.775
Don't do that.
00:27:25.805 --> 00:27:27.194
Or if you do it, just shut up.
00:27:27.305 --> 00:27:28.974
Like don't, don't tell anybody.
00:27:29.115 --> 00:27:30.214
I almost cursed the bucket.
00:27:30.505 --> 00:27:33.964
Don't tell anybody that you do it because then other people see you doing it.
00:27:34.295 --> 00:27:39.625
You know, this is the same thing as like, if, if, if I work for a boss who never takes vacation, now I can't take vacation.
00:27:39.775 --> 00:27:41.394
That's the same thing that we're talking about here.
00:27:41.454 --> 00:27:42.345
It's the same effect.
00:27:42.494 --> 00:27:53.275
But the personal test one, if you know that you have this problem, if you have a problem, where's Mike Miller when I need him this personal testing, like maybe you can reserve some capacity, just like you would reserve capacity to deal with technical debt.
00:27:53.474 --> 00:27:53.795
Okay.
00:27:53.795 --> 00:27:55.184
We're going to reserve 20 percent of our.
00:27:55.335 --> 00:28:02.444
points in the sprint or whatever to know that technical debt stuff's going to need to be worked on, let engineering choose what that's going to be, and we'll drop it in.
00:28:02.444 --> 00:28:06.464
If we don't have something up in the roadmap, maybe this is the same thing we were going to reserve some time.
00:28:06.615 --> 00:28:11.005
if you don't need to do any of this stuff, then you just work on normal backlog items and everything's fine.
00:28:11.075 --> 00:28:16.505
I like the idea of reserving time because one of the other things you can add in that mix is skills development.
00:28:16.515 --> 00:28:19.184
So reserve whatever hours you mentioned, right?
00:28:19.234 --> 00:28:20.305
It doesn't matter what the hours are.
00:28:20.315 --> 00:28:20.644
It doesn't matter.
00:28:20.664 --> 00:28:21.605
You figure out the number.
00:28:21.605 --> 00:28:24.115
for personal tasks as well as skills development, right?
00:28:24.134 --> 00:28:25.714
Obscure yourself, learn something new.
00:28:25.775 --> 00:28:26.275
I like that.
00:28:26.275 --> 00:28:26.454
Yeah.
00:28:26.605 --> 00:28:31.125
I like that too, but it doesn't because really there's no room for that in day to day.
00:28:31.285 --> 00:28:39.585
You think about what teams work on, they're always working on either the actual backlog or some other version of it, which is what we're calling the shadow backlog.
00:28:39.595 --> 00:28:41.255
We probably could think about this number off the top of our head.
00:28:41.255 --> 00:28:43.555
Like every additional team that you're on, you add 20%.
00:28:43.585 --> 00:28:45.755
So, right away, you cut your utilization.
00:28:45.904 --> 00:28:50.875
if we're going to talk about the dirty four letter word that's called utilization, we're going to talk about that for a second.
00:28:51.025 --> 00:28:56.765
let's break out like, okay, you're a developer on one team what is your utilization to that team?
00:28:56.805 --> 00:28:57.664
Just off the start.
00:28:57.664 --> 00:29:03.464
Are we just going to say like 15 percent of your time is just pure overhead, like just on one team meetings and stuff like that.
00:29:03.535 --> 00:29:04.634
let's call one team 20%.
00:29:04.785 --> 00:29:07.644
Being on one team, 20 percent of your time is already gone.
00:29:07.924 --> 00:29:12.204
So, that's 80 percent potentially dedicated to development work that you do.
00:29:12.234 --> 00:29:15.505
Now, let's say, we're gonna do this personal task slash learning thing.
00:29:15.734 --> 00:29:18.424
So, let's take 30 percent of your time and dedicate it to these things.
00:29:18.434 --> 00:29:20.815
So, either personal tasks you have to do or learning and development.
00:29:21.015 --> 00:29:22.055
So, now we're down to 50%.
00:29:23.085 --> 00:29:25.325
Of your time dedicated to actually servicing the backlog.
00:29:25.325 --> 00:29:26.974
So now we're at 20 hours a week, basically.
00:29:27.125 --> 00:29:28.015
I think that's fair.
00:29:28.065 --> 00:29:29.355
We're going to take care of your L and D.
00:29:29.515 --> 00:29:32.315
We're going to take care of your time to work on the stuff that you're super passionate about.
00:29:32.484 --> 00:29:40.634
We're going to take care of the time to work on things that you would like to, to workshop and prove concept that the hackathon type of stuff, building into your schedule.
00:29:40.809 --> 00:29:41.720
I love this idea.
00:29:41.720 --> 00:29:44.680
You're basically exposing the skunkworks at that point, right?
00:29:44.680 --> 00:29:47.109
You say, well, don't hide things under the table.
00:29:47.119 --> 00:29:50.200
We're giving you the time and you can make it fun.
00:29:50.210 --> 00:29:51.789
You could make it rewarding for them.
00:29:51.940 --> 00:29:54.400
You know, if they come up, we said that's basically the google thing.
00:29:54.660 --> 00:29:59.609
Google have been doing this for a while, you know that on fridays the developers do this sort of thing, right?
00:29:59.759 --> 00:30:00.869
But I like the idea.
00:30:00.920 --> 00:30:04.289
Well, the point of all this is I want it all Transparent.
00:30:04.380 --> 00:30:05.380
I want it all clear.
00:30:05.500 --> 00:30:21.339
So like maybe I'll carve some time out in our sprint review for you to bring this work forward that you're working on and if the sprint review is not the appropriate place because maybe the audience is not the appropriate place, then maybe the engineering team itself has like the hackathon review, like
maybe every month or every two weeks or something like that.
00:30:21.349 --> 00:30:24.869
Maybe the engineering team just the engineers in the matrix of engineering.
00:30:24.930 --> 00:30:28.359
Maybe just the engineers go to a across team engineering.
00:30:28.509 --> 00:30:31.930
Session where they share what they've been doing for this type of stuff.
00:30:32.109 --> 00:30:35.930
I would keep it separate from the sprint review because you possibly have stakeholders in the room.
00:30:35.930 --> 00:30:37.130
Well, it depends on how big your company is.
00:30:37.170 --> 00:30:37.930
But yeah, sure.
00:30:37.990 --> 00:30:39.180
If you're small enough.
00:30:39.180 --> 00:30:40.269
I mean, obviously if you have.
00:30:40.565 --> 00:30:43.095
60 plus developers in your program okay, like that.
00:30:43.244 --> 00:30:46.184
Yeah, yeah, I would agree with you yeah, let's do that separately.
00:30:46.244 --> 00:30:54.305
I, as a product manager Will become the person who goes to that optionally like I'm on the optional invite to see what cool new things It's for them by them.
00:30:54.305 --> 00:31:05.535
So yeah, it makes sense But they're also As part of personal tasks, that's their time to pitch things So sort of like it could be Part demo part pitch meeting at that point anyway, I think so too.
00:31:05.555 --> 00:31:05.835
Yeah.
00:31:05.835 --> 00:31:06.515
I think this is good.
00:31:06.634 --> 00:31:09.565
maybe I can try exploring some of that to the extent possible.
00:31:09.714 --> 00:31:09.924
Yeah.
00:31:09.944 --> 00:31:12.644
Even if it's theoretical now, just treat that as an experiment.
00:31:12.654 --> 00:31:13.115
Try it out.
00:31:13.174 --> 00:31:13.924
in personal tasks.
00:31:13.924 --> 00:31:16.625
We kind of talked about developers trying out new things.
00:31:16.904 --> 00:31:26.494
Talking about personal tasks is developers researching new technologies, or we talked a little bit about new libraries for charting and stuff like that, like new ways of querying, you know what I mean?
00:31:26.494 --> 00:31:31.785
New technologies, that exploratory work of like, Oh you know, we know that this thing is upcoming in the backlog.
00:31:31.785 --> 00:31:32.964
They're going to ask us to implement.
00:31:33.244 --> 00:31:36.144
And in advance of that, we have to try some different ways.
00:31:36.440 --> 00:31:46.119
developers can go down a rabbit hole on that exploratory work proof of concept work like real, like things that are not directly in our product now, but maybe in the future, again, people listen to the podcast.
00:31:46.150 --> 00:31:49.380
know, I have a label in my ALM system.
00:31:49.690 --> 00:31:51.579
You can put a label on whatever system you're using.
00:31:51.769 --> 00:31:55.200
I use Jira, but it could be any system that you're using.
00:31:55.259 --> 00:32:00.319
I put a label in there for capabilities, which means my team is doing exploratory work.
00:32:00.500 --> 00:32:01.720
this is not feature development.
00:32:01.720 --> 00:32:03.450
This is not CapEx development.
00:32:03.450 --> 00:32:04.799
This is OpEx.
00:32:04.950 --> 00:32:06.420
The team is exploring something new.
00:32:06.470 --> 00:32:07.750
It may turn into nothing.
00:32:08.009 --> 00:32:10.559
It may turn into capitalizable features.
00:32:10.710 --> 00:32:11.430
I don't know yet.
00:32:11.650 --> 00:32:16.150
I have a tag for that because I want my developers coming to me and saying, we need to do this.
00:32:16.474 --> 00:32:18.444
And put some time into it and lobby for it.
00:32:18.484 --> 00:32:21.644
And then I'll put it in the backlog and we'll order it and it'll pop up.
00:32:21.795 --> 00:32:28.144
But not a lot of product managers can have that discussion and understand the need and understand the pitch.
00:32:28.375 --> 00:32:32.954
And again, like you said, be able to pitch it back to the business because they're paying for it.
00:32:32.954 --> 00:32:53.974
So the reason why exploratory work goes under the radar is because Any break in anything I just explained your, your ability of developer to explain to me, the product manager, me, the product manager's ability to prioritize it in line with the rest of the stuff that we have me, the product manager's ability to sell it to the people above me, like any, any breakdown in any of those things.
00:32:54.125 --> 00:32:56.265
I mean, assuming you didn't have a product manager, right.
00:32:56.414 --> 00:32:56.845
Right.
00:32:56.994 --> 00:32:57.305
Yeah.
00:32:57.454 --> 00:33:02.424
So yeah, you're right that developers have a tendency to go down the rabbit hole, especially tool selection.
00:33:02.434 --> 00:33:03.565
Let's use that as an example.
00:33:03.565 --> 00:33:04.244
That's a good example.
00:33:04.244 --> 00:33:05.595
New tools coming up, right?
00:33:05.684 --> 00:33:11.555
Well, let's try this new fine, shiny tool because that's the latest thing and I hear other people are using it.
00:33:11.704 --> 00:33:13.825
Maybe there's some value in that if they try it out.
00:33:14.035 --> 00:33:18.204
So put my guard rails around it if you want, but put it in the main backlog, right?
00:33:18.355 --> 00:33:22.894
And yeah, you got to be able to stand up and say, we're doing this because you can't do that.
00:33:23.045 --> 00:33:23.964
That's, that's the guard.
00:33:23.974 --> 00:33:26.565
The guardrails are, it's in the backlog.
00:33:26.815 --> 00:33:27.734
It's been prioritized.
00:33:27.775 --> 00:33:28.515
We're working on it.
00:33:28.515 --> 00:33:30.884
And then every day you're working on it, you're.
00:33:31.035 --> 00:33:34.095
Kind of giving your feedback about Hey, this is what we found.
00:33:34.434 --> 00:33:46.585
Maybe not every day that we're working on, but I mean, every couple of the regularly, yeah, regularly in the background, what I find is like a developer wants to be left alone with a new tool to just spend like, again, me in the middle of the night spending two consecutive
hours.
00:33:46.734 --> 00:33:48.335
Working on this API.
00:33:48.335 --> 00:33:57.765
I mean, how long, like two hours again, for me at my level of where I'm at is extreme amount of time to spend on one task.
00:33:57.914 --> 00:33:59.525
I don't know about different people's levels.
00:33:59.525 --> 00:34:02.775
Two weeks might not be extreme for somebody else.
00:34:02.775 --> 00:34:08.224
I don't know what that time is, but if I'm doing scrum and I'm in sprints and you've spent two weeks.
00:34:08.375 --> 00:34:12.594
Exploring something, man, you better be a top to bottom expert.
00:34:12.605 --> 00:34:21.445
Wiz have several proof of concepts like coded and working like the, my problem with this exploratory work, not being in the backlog is the developers.
00:34:21.594 --> 00:34:27.105
Desire to just be left alone with a piece of tech for an extended period of time to really learn it inside out.
00:34:27.255 --> 00:34:28.704
And that is where we get into trouble.
00:34:28.704 --> 00:34:38.594
It's I can't have like, I, as a product manager, I cannot have you disappearing down a rabbit hole for the whole sprint unless that expectation has been set when we pulled the item up, So I agree, first of all, right.
00:34:38.594 --> 00:34:43.105
If you let it go, this is your analogy of water applies here again, because people are just going to keep.
00:34:43.210 --> 00:34:44.599
Playing with the new shiny tool.
00:34:44.750 --> 00:34:55.210
The other thing I've seen that kind of really odd is I've seen developers take leads, let's say, or even architects say, We need to do an exploration or a spike sprint.
00:34:55.360 --> 00:34:56.769
We need to do a spike sprint.
00:34:56.929 --> 00:34:59.179
How am I going to sell that to leadership?
00:34:59.420 --> 00:35:02.280
A whole sprint, 10 days, let's say, times six people.
00:35:02.309 --> 00:35:05.199
Well, we're going to do all of that just for exploration.
00:35:05.349 --> 00:35:08.440
Maybe we need to think through this and say, what's our opportunity cost?
00:35:08.489 --> 00:35:09.730
What are we not working on?
00:35:09.980 --> 00:35:12.369
That's really bringing value to the business.
00:35:12.690 --> 00:35:14.260
So again, it's not black and white.
00:35:14.320 --> 00:35:16.190
Not saying no, just saying, well.
00:35:16.340 --> 00:35:21.960
You know what gives right and having that discussion with those people above you leadership.
00:35:21.980 --> 00:35:23.639
And so can we take a little bit of time?
00:35:23.670 --> 00:35:23.849
Yeah.
00:35:24.000 --> 00:35:28.480
So it's a negotiation with your teams, plus with your peers and your superiors, right?
00:35:28.630 --> 00:35:30.610
Have you seen the Jeff Sutherland tweets?
00:35:30.760 --> 00:35:33.519
About you should estimate spikes.
00:35:33.670 --> 00:35:34.690
I think I have.
00:35:34.730 --> 00:35:36.159
Yes, I have seen that.
00:35:36.309 --> 00:35:45.590
The reason I was looking for the post from Jeff Sutherland about spike work, sizing
spike work is because I think spike work needs to be just time box and that's it.
00:35:45.739 --> 00:35:48.219
You can find out what you can find out in the time allotted.
00:35:48.369 --> 00:35:55.170
And then if you decide that you need to extend the time box or create another time box or whatever, then you create another time box of the same length.
00:35:55.320 --> 00:35:59.099
And then you can get around dealing with the size of spike.
00:35:59.150 --> 00:36:02.050
I guess you can get around that also by just saying all spikes are the same size.
00:36:02.199 --> 00:36:04.719
Spike should be able to be dealt with in a day or two, right?
00:36:04.840 --> 00:36:11.110
But that, I was looking for that post because I was going to say Spikes, the topic, all alone, separate podcast.
00:36:11.150 --> 00:36:12.139
That's what I was going to pitch.
00:36:12.179 --> 00:36:12.769
Oh, yeah, yeah.
00:36:12.809 --> 00:36:16.210
That's why I was going down that road because I, and I would open up with that.
00:36:16.280 --> 00:36:22.179
I'd open up with that tweet, basically, to say, Jeff Sutherland says, Hey, you can't estimate it if it doesn't have an estimate.
00:36:22.329 --> 00:36:23.750
So everything needs to have an estimate.
00:36:23.760 --> 00:36:27.780
That's the policy here at Brian and Ohm's HR company.
00:36:27.929 --> 00:36:39.010
Whatever happened to the software company who said we need to have an estimate the category here was exploratory work, basically blowing up and becoming part of the shadow backlog because you never give you developers time to do exploratory work.
00:36:39.159 --> 00:36:43.469
I wonder about teams where exploratory work is a big part of the shadow backlog.
00:36:43.619 --> 00:36:56.829
I wonder how those teams do their refinements because a lot of times in refinement, we're pulling up systems and we're calling in experts and we're getting their opinion on basically a lot of the answers for exploratory work.
00:36:56.840 --> 00:37:00.820
we're making room for them during that time to come in and give us answers.
00:37:00.969 --> 00:37:06.250
That we otherwise would have to dedicate a person to, and that person would have to go chase down these things and whatnot.
00:37:06.400 --> 00:37:09.989
So, I do this stuff in refinements, which is different than sprint plannings.
00:37:10.139 --> 00:37:12.760
Where sprint planning assumes we already have these details.
00:37:12.909 --> 00:37:15.489
So I would assume you're not doing a lot of that kind of stuff.
00:37:15.639 --> 00:37:18.750
You know what else in exploratory work that can blow up is proof of concepts.
00:37:18.900 --> 00:37:23.190
Oh yeah, definitely proof of concepts, especially if there's no scope bounding.
00:37:23.250 --> 00:37:23.579
Right.
00:37:23.590 --> 00:37:24.969
And people will just keep working on it.
00:37:24.969 --> 00:37:26.449
Often there isn't in a POC.
00:37:26.449 --> 00:37:27.369
It's very ambiguous.
00:37:27.519 --> 00:37:31.469
So that needs to come with, how do we know when we're done with the POC?
00:37:31.530 --> 00:37:33.199
I mean, some sort of DOD, right?
00:37:33.210 --> 00:37:35.340
Some sort of definition of done on the POC.
00:37:35.360 --> 00:37:40.030
Plus having those frequent reviews of the POC and asking, is this enough?
00:37:40.260 --> 00:37:41.110
Or do we keep going?
00:37:41.260 --> 00:37:41.510
Right.
00:37:41.559 --> 00:37:43.119
I think you just nailed it right there.
00:37:43.119 --> 00:37:44.269
that's how we know we're done.
00:37:44.280 --> 00:37:50.559
we demo it on a regular basis, Honestly, more frequent than the sprint release, like the normal sprint and cadence.
00:37:50.559 --> 00:37:51.570
I think it should be more than that.
00:37:51.909 --> 00:37:54.130
And then we ask, here's the work that was done.
00:37:54.210 --> 00:37:54.829
Are we done?
00:37:54.980 --> 00:37:56.119
So on the cadence, right?
00:37:56.269 --> 00:37:57.260
We don't even need a cadence.
00:37:57.369 --> 00:38:00.380
As soon as you put a piece of functionality in there, get feedback.
00:38:00.400 --> 00:38:02.219
You say, well, here, we just added this.
00:38:02.420 --> 00:38:04.409
And at some point ask what else was missing.
00:38:04.559 --> 00:38:10.519
I like the world that you're living in because some other developers live in the world of, I'm just going to keep throwing stuff.
00:38:10.639 --> 00:38:12.300
and throwing stuff in the release pipeline.
00:38:12.329 --> 00:38:20.960
well they may see that as their actual work and the actual releasing to production, the pipeline, like executing the pipeline and having it roll out to the environments.
00:38:21.289 --> 00:38:24.969
They might see that as additional overhead or somebody else's job.
00:38:24.980 --> 00:38:28.280
If they can ship it to another team, like a DevOps release team or something like that.
00:38:28.429 --> 00:38:33.239
So you have a development team that just keeps throwing stuff into the pipeline and never actually running a release.
00:38:33.389 --> 00:38:45.230
So then when they finally go to run a release, you got all these merge conflicts and stuff that's got to be figured out it's a big disaster because they're not releasing I only call that out because I did live in that world in a previous part of my career.
00:38:45.420 --> 00:38:48.369
I don't live in that world anymore, so I don't talk about it anymore.
00:38:48.389 --> 00:38:48.659
Right.
00:38:48.664 --> 00:38:49.860
But it's, well, that world is real.
00:38:49.860 --> 00:38:50.820
It's very real.
00:38:51.119 --> 00:38:51.900
Yeah, it's real.
00:38:51.900 --> 00:38:55.230
And a lot of people live in that world, so just be mindful of that.
00:38:55.309 --> 00:39:02.000
I think that people listening to this should not walk away by kind of taking just one thing that we say, right.
00:39:02.050 --> 00:39:03.280
that exploratory work.
00:39:03.309 --> 00:39:03.579
Okay.
00:39:03.579 --> 00:39:04.780
Well, gotta be careful.
00:39:05.019 -->
00:39:06.130
No, we're not saying that.
00:39:06.130 --> 00:39:07.090
What we're saying is.
00:39:07.239 --> 00:39:09.210
It's on a case by case basis, right?
00:39:09.219 --> 00:39:11.730
How quickly do you need to do that POC?
00:39:11.780 --> 00:39:12.699
What do you need to learn?
00:39:12.710 --> 00:39:13.449
How fast?
00:39:13.599 --> 00:39:16.340
And size work that way, but put it in the main backlog.
00:39:16.500 --> 00:39:17.550
Yeah, that's what we're saying.
00:39:17.559 --> 00:39:18.130
Yes.
00:39:18.250 --> 00:39:23.090
if your policy is, we don't pull anything into the sprint to get done unless it has points.
00:39:23.320 --> 00:39:26.380
So now we have to have this big heartache about.
00:39:26.699 --> 00:39:29.389
Do we point our spikes or not point our spikes?
00:39:29.389 --> 00:39:38.869
Well, I don't know like You don't need any of that like pick a number throw it in there Or don't pick a number don't pick it up Don't pick a number and just time box it and you're done with it Like you don't need to be complicated about this.
00:39:38.920 --> 00:39:45.059
No, that's exactly right Yeah, and if you time box it or if you don't land it, well fine extend it, right?
00:39:45.150 --> 00:39:46.619
Okay Based on feedback.
00:39:46.929 --> 00:39:47.710
That's all I mean.
00:39:47.750 --> 00:39:55.630
Yeah Enough said like I don't Again, there's a reason I could have a whole podcast about that specific topic Cause people get ridiculous.
00:39:55.639 --> 00:39:56.570
Like ridiculous?
00:39:56.570 --> 00:39:57.090
Who cares?
00:39:57.239 --> 00:40:00.130
So dogma, the point of the spike is I need the learning.
00:40:00.329 --> 00:40:03.090
I need to know I need that ambiguity knocked down.
00:40:03.369 --> 00:40:13.230
So I'm basically willing to pay any costs to have it get knocked down until you tell me until it gets too expensive, like until it becomes so expensive that I'm not willing to pay it anymore.
00:40:13.239 --> 00:40:13.579
Right.
00:40:13.880 --> 00:40:14.090
Right.
00:40:14.099 --> 00:40:16.139
So how can we control that?
00:40:16.289 --> 00:40:17.579
Oh, I know how we can control it.
00:40:17.619 --> 00:40:20.860
We can just time box it and say, have we learned enough in the time allotted?
00:40:20.889 --> 00:40:21.320
No.
00:40:21.429 --> 00:40:21.860
Okay.
00:40:21.989 --> 00:40:23.780
Let me give you another time segment.
00:40:23.929 --> 00:40:31.059
I also think there's another element to it, which is just, just describe up front, what is it that we hope to learn so we know when we're done.
00:40:31.170 --> 00:40:34.110
Otherwise we just keep learning and the developers will keep going.
00:40:34.309 --> 00:40:34.829
With the team.
00:40:35.070 --> 00:40:42.289
I mean, that is the old arguing agile of the side of this, the other side of this is let me the developer figure out what I'm done and just go away leave me alone.
00:40:42.289 --> 00:40:45.599
why do I have to keep coming to you asking permission to have more time?
00:40:45.750 --> 00:40:47.269
We like, you like getting paid, right?
00:40:47.420 --> 00:40:49.889
We, we get money when customers buy real product.
00:40:50.190 --> 00:40:50.679
Yeah.
00:40:50.679 --> 00:40:58.690
I mean, I understand, but also like you have empathy for their position, which is like, it takes a lot of time to really understand the new technologies and understand all the business cases through it.
00:40:58.739 --> 00:41:20.800
the point that you're raising, which also is my point is nobody can go off on their own and burn a bunch of company money on their own, like without checking in with anybody, nobody in the business, product managers, executives, nobody works like that in the, even the C level, even CEO executives, you can't just burn an infinite amount of money and time and expect to not have to report that to somebody.
00:41:20.949 --> 00:41:24.170
Yeah, expensive to be accountable for that to somebody.
00:41:24.320 --> 00:41:31.119
Exactly, I had two other quick things that I think are quick, we'll see which is parallel teams slash tracks of work.
00:41:31.130 --> 00:41:35.099
What I mean by that is multiple products being serviced by one team.
00:41:35.405 --> 00:41:35.965
Team.
00:41:36.114 --> 00:41:43.824
if you have multiple products, usually what happens is as the team members are moving fast and transitioning between products, there's that switching costs.
00:41:44.155 --> 00:41:48.804
Part of paying that switching costs is they'll just do something real quick over here and then come back to the main thing they're working on.
00:41:48.804 --> 00:41:50.494
So they're incurring debt the whole time.
00:41:50.494 --> 00:41:51.224
They just don't know it.
00:41:51.315 --> 00:41:51.735
Right.
00:41:51.775 --> 00:41:52.034
Yeah.
00:41:52.045 --> 00:41:56.635
that's part of the shadow backlog is like, you don't really realize that they've come off of the main thing.
00:41:56.684 --> 00:42:00.655
To go do one, two little quick fixes on this other thing, and then they're popping back off.
00:42:00.704 --> 00:42:03.614
You don't notice it until they're gone two days and like, wait a minute, what's going on?
00:42:03.795 --> 00:42:04.074
Yeah.
00:42:04.114 --> 00:42:07.724
And that's made even worse by who's judging them?
00:42:07.724 --> 00:42:09.824
Like who's actually measuring what they're working on.
00:42:09.974 --> 00:42:16.445
So if they're being measured on this main work that they're doing and they kind of just go away somewhere and come back.
00:42:16.594 --> 00:42:18.715
Then they're going to want to rush things over there.
00:42:18.764 --> 00:42:21.085
So then come back to this cause all eyes are on this.
00:42:21.135 --> 00:42:21.375
Right.
00:42:21.375 --> 00:42:21.445
Right.
00:42:21.594 --> 00:42:22.804
It's just bad practice.
00:42:23.014 --> 00:42:26.034
It's just too many, two balls in the air is one ball too many.
00:42:26.315 --> 00:42:26.795
Probably.
00:42:26.945 --> 00:42:27.724
Parallel teams.
00:42:27.875 --> 00:42:29.844
I wanted to combine this with another category.
00:42:30.045 --> 00:42:32.394
it was either like non transparent.
00:42:32.405 --> 00:42:38.235
Don't understand the, like maybe one of these parallel tracks that's happening is a very, very old legacy product.
00:42:38.235 --> 00:42:38.275
Right.
00:42:38.425 --> 00:42:39.684
That maybe they don't like this.
00:42:39.724 --> 00:42:42.514
The company doesn't want to staff product managers for right.
00:42:42.545 --> 00:42:46.414
So it's unclear about who sets the priority for an end.
00:42:46.425 --> 00:42:49.175
Also unclear about when things get worked on.
00:42:49.224 --> 00:42:53.795
it doesn't have a clearly defined roadmap that's transparent and it's not clear when they're making releases.
00:42:53.844 --> 00:42:56.474
the customers are still using it and are happy when they get new releases.
00:42:56.625 --> 00:43:02.775
They can't be guaranteed that they're going to get a new release every week or whatever, like that cadence has changed because the business is no longer funding.
00:43:02.775 --> 00:43:10.655
the business may well be wanting customers to get off of the old legacy, And jump onto one of their newer versions Yes This is a very passive aggressive category.
00:43:10.844 --> 00:43:11.244
Yes, indeed.
00:43:11.244 --> 00:43:15.375
This multiple products, one team like, dude, this is a problem.
00:43:15.525 --> 00:43:17.085
I guess if it's multiple products.
00:43:17.235 --> 00:43:21.485
With one team and one product manager who is also over all the products.
00:43:21.635 --> 00:43:30.815
Then I guess it's a little easier because it's one team working out of multiple backlogs and then they have one sprint, but that one sprint is composed of different products.
00:43:30.864 --> 00:43:54.315
Yeah, but I mean, I guess the point of that category though as far as the shadow backlog goes, is like, I've also been on teams where as programs are dissolved, or as teams are dissolved, or whatever, like the people that are left join another team, and then the maintenance of that product that's in sunset mode is also added to this other team's responsibilities or sometimes it's not added to the other team's responsibilities.
00:43:54.454 --> 00:43:57.135
I was once with a program that was completely spun down.
00:43:57.135 --> 00:44:00.135
They only kept two developers and they added those two developers.
00:44:00.135 --> 00:44:07.885
They added one to one team and one to the other, but those two developers were the ones that got calls from the project managers when the project managers of that organization own the customers.
00:44:07.885 --> 00:44:09.264
Don't ask me how I didn't set this up.
00:44:09.414 --> 00:44:14.855
The project managers own the customer relationships and the customers would say, Hey, we had this problem with the software.
00:44:15.005 --> 00:44:16.505
We found a bug, we need to fix.
00:44:16.534 --> 00:44:25.224
And the project managers would
go to the product managers who own those developers to say, we need this developer for a certain amount of time to do these fixes or whatever.
00:44:25.224 --> 00:44:26.375
And they would interrupt their.
00:44:26.525 --> 00:44:27.764
Sprints that are in progress.
00:44:27.764 --> 00:44:31.614
they're committed work that was in progress because this stuff would come up as like support work.
00:44:31.625 --> 00:44:36.304
in that instance, we like the project managers and the product managers had good working relationships.
00:44:36.454 --> 00:44:42.195
But it very easily could have been the project managers go directly to the developer to say, Hey, we need you to fix this.
00:44:42.445 --> 00:44:44.695
And now there's a stream of work in the shadow backlog.
00:44:44.844 --> 00:44:45.545
So, yeah.
00:44:45.545 --> 00:44:49.425
And it's, it's really not all that pleasant for the poor developer who's caught in this thing.
00:44:49.425 --> 00:44:49.684
Right.
00:44:49.835 --> 00:44:51.844
I mean, they have multiple masters.
00:44:51.974 --> 00:44:56.885
Oh, I was, Well, one of the, one of the two left cause they didn't want to work in that environment.
00:44:56.905 --> 00:45:03.514
And then we had one developer that did all the maintenance for that sunset product line that still brought in a significant amount of revenue for the company.
00:45:03.784 --> 00:45:05.565
So that's your like million dollar developer.
00:45:05.565 --> 00:45:11.454
So basically like that developer could have, they were not the kind of person who would ask for like, Hey, 20%.
00:45:11.605 --> 00:45:16.034
50 percent or whatever I'm going to leave, but they very well could have, they could win the lottery.
00:45:16.034 --> 00:45:17.425
And now the company's in deep trouble.
00:45:17.445 --> 00:45:22.085
The only other category that we have left is dealing with NFRs, which is usability.
00:45:22.315 --> 00:45:25.885
Like I want to go make this change to the UI, like a UI front end developer.
00:45:25.914 --> 00:45:26.605
We'll do this.
00:45:26.635 --> 00:45:30.135
I've, I've seen them do this often Hey, I, I need to add.
00:45:30.445 --> 00:45:34.184
This new toggle to the map or this I want to add a dark mode to the map.
00:45:34.244 --> 00:45:40.465
Nobody says, everyone else has got dark modes and we don't have dark modes and I feel real strongly that we should have a dark mode.
00:45:40.465 --> 00:45:41.605
Cause I'm I, I'm a developer.
00:45:41.605 --> 00:45:44.125
I like only working on everything is dark mode all the time.
00:45:44.275 --> 00:45:45.594
Live my life on dark mode.
00:45:45.744 --> 00:45:46.514
Yeah, definitely.
00:45:46.514 --> 00:45:48.715
Everything you just said starts with the letter I.
00:45:48.875 --> 00:45:55.244
So yeah, these are solo people that just basically have their own opinions on what should be in the product and they go work on it.
00:45:55.264 --> 00:46:01.994
Maybe, maybe, maybe because scalability and performance, I've seen developers get lost down the rabbit hole of scalability and performance.
00:46:02.235 --> 00:46:13.494
But performance of, hey, I need to Go and pull all the SQL queries in our system and optimize every single query Performance is one of those things that the more you work on it, the more you can work on it.
00:46:13.605 --> 00:46:15.304
It keeps going on and on and on.
00:46:15.304 --> 00:46:15.574
Right.
00:46:15.744 --> 00:46:16.034
Yeah.
00:46:16.175 --> 00:46:16.795
absolutely.
00:46:16.985 --> 00:46:20.644
I've seen people like that, that are very passionate about their work.
00:46:20.795 --> 00:46:23.574
And they're like, no, I know I can improve this two more percent.
00:46:23.809 --> 00:46:24.150
Right?
00:46:24.300 --> 00:46:26.300
It's like, oh, just go work on something else.
00:46:26.300 --> 00:46:27.690
Nobody cares about that.
00:46:27.829 --> 00:46:29.230
It's already fast enough.
00:46:29.260 --> 00:46:29.719
They care.
00:46:29.900 --> 00:46:30.619
You know, they care.
00:46:30.659 --> 00:46:31.469
They themselves do.
00:46:31.599 --> 00:46:32.610
Yeah, this is very close.
00:46:32.610 --> 00:46:37.050
The NFR thing is very close to the personal task list that we were talking about scalability, for example.
00:46:37.114 --> 00:46:40.414
Where do you stop at scalability?
00:46:40.565 --> 00:46:43.394
You know, the system needs to handle a hundred concurrent users.
00:46:43.625 --> 00:46:45.764
The system needs to handle a thousand concurrent users.
00:46:45.945 --> 00:46:50.965
do you stop at a hundred times what our current normal traffic is?
00:46:50.974 --> 00:46:52.625
So rule of thumb is 10, isn't it?
00:46:52.804 --> 00:46:55.844
So stop at 10 and then build in auto scaling.
00:46:55.885 --> 00:46:56.125
Yeah.
00:46:56.164 --> 00:47:08.940
I think this category is the personal task list because the more that someone is concerned and digs into a category and keeps working on it as their kind of like pet project of I think about network engineers, this way is like, oh, I got a, Optimize the network.
00:47:08.940 --> 00:47:11.429
And I got to make sure we got bandwidth for this and redundancy.
00:47:11.480 --> 00:47:12.920
failover, basically failover.
00:47:13.070 --> 00:47:14.510
Especially with cloud tech now.
00:47:14.539 --> 00:47:22.949
But I remember those days too and then you add on top of that, all the nuances you fail over, but you can't have data from Germany, outside of Germany, right.
00:47:23.099 --> 00:47:25.539
All of those little nuances layer on top of that.
00:47:25.690 --> 00:47:32.550
Yeah, a lot of this, a lot of that in the four categories the personal task list, now that I'm now that I'm thinking about it a little bit deeper, so.
00:47:32.699 --> 00:47:40.340
I think, I think you can go a long way towards you know, eliminating quite a bit of that by defining the attributes that you need up front.
00:47:40.360 --> 00:47:40.559
Yeah.
00:47:40.820 --> 00:47:43.269
And putting guardrails there, right?
00:47:43.360 --> 00:47:47.889
If it scales to a hundred times, Is that better than 50 times?
00:47:48.039 --> 00:47:49.969
Cause we've never had that before, you know?
00:47:49.969 --> 00:47:55.750
So maybe stop and just monitor their times, probably better spent putting in some application monitoring.
00:47:55.750 --> 00:47:58.570
So it reports out the peaks and valleys, right.
00:47:58.719 --> 00:48:00.179
During the day or whatever.
00:48:00.230 --> 00:48:01.460
Monitoring is a great one too.
00:48:01.500 --> 00:48:05.989
Cause like there's always one additional detail, monitor anything, one additional detail.
00:48:06.000 --> 00:48:07.179
You just gotta have, it'll be perfect.
00:48:07.179 --> 00:48:09.840
If I have one additional detail, that's another great one.
00:48:09.989 --> 00:48:10.380
Yeah.
00:48:10.530 --> 00:48:11.190
That's true.
00:48:11.340 --> 00:48:17.789
Well, that's the podcast today of you know, , a shadow backlog, the hey buddy backlog, anybody backlog.
00:48:17.880 --> 00:48:18.500
I like that.
00:48:18.579 --> 00:48:19.010
Yeah.
00:48:19.030 --> 00:48:23.750
if you're looking at a backlog, that might be your Robin, if you're Batman, or it could just be a shadow Batman.
00:48:23.900 --> 00:48:26.380
I don't think it's, I think it's your Joker, if you're Batman.
00:48:26.380 --> 00:48:27.849
I think it's your worst enemy.
00:48:27.849 --> 00:48:28.889
Standing over your shoulder.
00:48:28.949 --> 00:48:31.329
we only kind of talked about all the different types.
00:48:31.480 --> 00:48:33.760
Of things that can contribute to the shadow backlog.
00:48:33.760 --> 00:48:37.280
We didn't really talk about what to do with them, how to resolve them or whatever.
00:48:37.280 --> 00:48:41.349
Maybe that's a part two, maybe it's a second part, completely separate podcast.
00:48:41.500 --> 00:48:49.929
I don't know if you have good backlog management, if you're doing backlog refinements, if you're involving your team, if you're getting the right stakeholders in there, you can do a lot to mitigate this.
00:48:49.929 --> 00:48:54.940
So I think when we talked about how you manage the backlog is not clear, it's not transparent.
00:48:55.000 --> 00:48:56.710
Like that is the.
00:48:56.860 --> 00:49:09.269
Kind of the crux of why this is a big problem is people don't understand your backlog management Maybe they're not invited to it and they should be maybe you're not casting a wide enough net to bring people into your refinements, you know Yeah, absolutely agree with that.
00:49:09.449 --> 00:49:12.400
Let's do a second part on what to do about these things.
00:49:12.550 --> 00:49:13.730
Yeah, I think that would be a good one.
00:49:13.739 --> 00:49:14.940
It may not be as long as this.
00:49:14.980 --> 00:49:15.440
I don't know.
00:49:15.630 --> 00:49:21.239
Yeah, maybe not, but I don't, I don't know what the title of that one is like killing the, killing the shadow backlog.
00:49:21.389 --> 00:49:23.829
It's a shining a light on the illuminate.
00:49:23.829 --> 00:49:24.329
Yeah.
00:49:24.480 --> 00:49:27.190
Well, if you have an idea for what part two would be Hit us up in the comments.
00:49:27.199 --> 00:49:28.539
Yeah, we'd love to hear from you.
00:49:28.690 --> 00:49:30.300
And don't forget to like and subscribe.