00:00:00
it doesn't matter what kind of
00:00:01
environment you work in agile scrum
00:00:04
waterfall here are six D wasters that
00:00:07
managers are currently doing right now
00:00:11
pushing developers out of your
00:00:13
organization if you're a developer
00:00:14
watching this it's really important that
00:00:16
you are aware of these Dam wases so that
00:00:19
you can try preventing your manager or
00:00:21
direct supervisor from wasting your time
00:00:24
and if you're a manager stop these right
00:00:26
now so first let's set the context when
00:00:29
I say manager I'm talking about the
00:00:31
direct supervisor of a developer or a
00:00:34
group of developers or someone at the
00:00:37
same level as this manager time waster
00:00:41
number one telling developers how to do
00:00:44
something if you want motivated
00:00:46
developers efficient effective
00:00:48
productive developers you need
00:00:49
developers working in a self-organized
00:00:52
self-managed environment gone of a days
00:00:55
where you should be telling developers
00:00:56
what to do micromanaging developers as a
00:00:59
manager or a direct supervisor give them
00:01:02
the power to decide how to do something
00:01:06
yes you can tell them the why yes you
00:01:08
can talk about the what to do work on
00:01:10
the priorities but concerning the how I
00:01:13
don't care that you were developer
00:01:15
previously I don't care that you are an
00:01:17
architect a tech lead engineering lead I
00:01:19
don't care how much knowledge you have
00:01:22
in this domain that's not your role now
00:01:24
you're a manager now let the developers
00:01:27
people who are actually doing the work
00:01:30
decide together how to do the work they
00:01:32
actually doing the work let them decide
00:01:34
how to do the work stop telling them how
00:01:36
to do something you believe you're
00:01:38
helping you believe you have the
00:01:39
knowledge to do it you're in a different
00:01:41
role now your role is to support them
00:01:44
motivate them and the number one way to
00:01:46
do that is to give them the power
00:01:49
decision making power focus on the why
00:01:51
focus on the what time was number two ah
00:01:54
this is a big one stop committing on
00:01:57
behalf of developers at a high level it
00:02:00
doesn't seem that it's wasting time of
00:02:02
developers when you're doing that when
00:02:04
you're going to a steering committee or
00:02:06
other meetings with top management and
00:02:08
directors telling them okay we can do
00:02:11
that we can do that we'll be able to
00:02:13
deliver that in two months it doesn't
00:02:15
seem that you're wasting developers time
00:02:17
while doing that but you are how do you
00:02:20
come up with dates how do you come up
00:02:21
with delivery dates you get a
00:02:23
requirement first you try to estimate
00:02:25
based on the information that you have
00:02:27
and you build a plan so you bypass all
00:02:29
all this and committed on behalf of
00:02:32
developers believing that you're doing a
00:02:34
good thing obviously not you're directly
00:02:37
wasting the D of developers and the
00:02:39
organization because of you all the plan
00:02:42
of the developers will be completely
00:02:45
messed up because you made a commitment
00:02:47
on something that you shouldn't have
00:02:49
made a commitment on again in a
00:02:51
self-organized self-managed environment
00:02:54
developers should have control on how to
00:02:56
do something and by when they can
00:02:58
deliver this thing I'm doing the work
00:03:00
how can you tell me when I should be
00:03:02
delivering the work I'm doing the work I
00:03:04
know how to do the work how can you tell
00:03:06
me how to do the work or I went to
00:03:08
deliver work you can tell me that this
00:03:10
work needs to be delivered in one month
00:03:13
basically you're giving me data with
00:03:14
regards to the priority of this piece of
00:03:16
work but I have control on plan and how
00:03:21
to deliver this thing number three
00:03:24
challenging developers yeah I know you
00:03:26
were a developer previously you have a
00:03:28
technical B backround previously that's
00:03:31
why maybe you're a direct supervisor or
00:03:33
a manager now but stop challenging the
00:03:36
estimations over the work of the
00:03:38
developers you can ask questions yeah
00:03:40
remember the goal your goal here is to
00:03:42
ensure that the developers are effective
00:03:45
that we are efficient but we are
00:03:47
productive helping them Reach This we're
00:03:50
going in the same direction we want
00:03:52
Effectiveness doesn't matter what kind
00:03:54
of environment you work in you want
00:03:56
Effectiveness so as previously mentioned
00:03:59
self organ ization self-management this
00:04:01
improves Effectiveness second
00:04:04
psychologically safe environment where
00:04:06
the developers know that they can speak
00:04:08
out speak their mind without being
00:04:11
punished or shamed or have any negative
00:04:15
consequences Your Role is to create this
00:04:17
kind of environment an environment of
00:04:19
fairness also and when you have this
00:04:22
environment then you can ask questions
00:04:24
start asking questions there's nothing
00:04:25
wrong with asking challenging questions
00:04:28
to ensure that they indeed need of
00:04:30
providing a fair estimate and a fair
00:04:32
plan on how to do the job and by when
00:04:34
they can deliver but when someone tells
00:04:37
you that it's going to take five days to
00:04:38
do it I know because I do the work and
00:04:41
you start telling me no it's just going
00:04:43
to take five days because in my day I
00:04:45
used to do it in two days we have a
00:04:47
problem with that and you force for
00:04:48
developers to do it in two days we have
00:04:50
a problem with that you're not creating
00:04:52
an environment where people will want to
00:04:54
work for your organization number four n
00:04:57
shielding developers but Developers
00:04:59
working in a self-organized self-managed
00:05:02
environment right so what's your role as
00:05:04
a manager you need to create this
00:05:06
environment help them have this positive
00:05:09
working environment psychological safety
00:05:11
and shielding developers they have a
00:05:14
list of priorities right to meet these
00:05:17
priorities maybe the days fact you
00:05:18
committed on investering committee we
00:05:20
need Focus we have a plan we need to
00:05:22
focus on that plan you gave a list of
00:05:24
priorities you talked about the what you
00:05:26
talked about the why now you need to
00:05:27
protect these developers they can't be a
00:05:30
situation where stakeholders managers
00:05:32
everyone is calling the developers every
00:05:33
single day every 30 minutes they need to
00:05:36
stop work because they got a call from
00:05:38
someone with another priority it doesn't
00:05:41
make sense as a manager you need to
00:05:43
Shield these developers because if
00:05:44
you're not shielding the developers
00:05:45
you're wasting the time of developers
00:05:47
because they are constantly context
00:05:48
switching multitasking and they won't be
00:05:51
able to deliver the priorities of your
00:05:53
organization if you are stakeholders or
00:05:55
anyone in the organization constantly
00:05:57
calling the developers there's some
00:05:59
something wrong with the way you do
00:06:01
priority fix that first build a system
00:06:04
so that all the requests all the calls
00:06:07
of stakeholders can be added to a basket
00:06:10
which will be prioritized instead of
00:06:12
someone calling the developer and this
00:06:14
developer needs to stop their priority
00:06:16
work and do something else doesn't make
00:06:17
any sense fix this first number five
00:06:20
piling work on the
00:06:23
developers this is very common we have a
00:06:25
date we are about to deliver on this
00:06:29
date
00:06:30
everyone committed on that it was a fair
00:06:32
estimation a fair plan and you as a
00:06:35
manager now you start to increase the
00:06:38
scope of a project or a feature being
00:06:41
built stop builing things new work New
00:06:44
pieces of work or other stakeholders are
00:06:46
doing that and you're not preventing the
00:06:48
other stakeholders from doing that and
00:06:50
to make matters worse you expect the
00:06:53
developers to deliver the build the
00:06:56
feature at the same date so you're
00:06:58
adding work and you expect the
00:07:00
developers to work over time or find a
00:07:02
solution in order to meet the same date
00:07:05
but with more work you messing up the
00:07:08
whole system by doing that you believe
00:07:11
maybe you're making the developers not
00:07:12
waste time being more productive a
00:07:14
little bit of pressure is good but
00:07:16
you're robbing the developers from being
00:07:18
self-managed you're creating an
00:07:20
environment where the estimations no
00:07:22
longer make sense or their planning no
00:07:24
longer makes sense because why estimate
00:07:26
in the first place why plan in the first
00:07:27
place why commit on something and then
00:07:29
you come back and you start forcing
00:07:31
developers to bypass this estimation
00:07:34
bypass this plan and do something else
00:07:36
so all your future estimations and plan
00:07:39
now they already know that but it no
00:07:40
longer makes sense but it's a waste of
00:07:43
time but they do that because someone
00:07:45
else in the organization will just come
00:07:47
and put something else all your priority
00:07:50
you have a list of priorities that
00:07:51
doesn't mean anything now the way to do
00:07:53
it the correct way to do it if you want
00:07:55
something in the build if you want
00:07:57
something to be developed that's fine
00:07:59
you remove something else you work on
00:08:01
your priority what's your role as a
00:08:02
manager not tell people how to do it or
00:08:04
by when to do it but at least for what
00:08:06
and why time waster number six I believe
00:08:09
that's the worst time waster it doesn't
00:08:11
look like a Time waster it's when you
00:08:14
take credit on behalf of
00:08:17
developers basically you're saying all
00:08:20
the work that the developers are put
00:08:22
into releasing this feature waste of
00:08:25
time for them because you're taking
00:08:27
credit for that always give the credit
00:08:30
to the developers to the people actually
00:08:33
doing the work without them this project
00:08:37
couldn't have been a success without
00:08:39
them this feature couldn't have been a
00:08:42
success if you want to create this
00:08:44
self-managed self-organized environment
00:08:47
where developers are motivated to come
00:08:50
to work every single day which will
00:08:52
result in productivity efficiency
00:08:55
effectiveness of the minimum is to give
00:08:58
them credit when when credit is due
00:09:01
again your role as a manager
00:09:03
psychological safety environment
00:09:06
self-managed Environ man let them do the
00:09:09
work trust them Shield them be a servant
00:09:13
leader if you want more tips insights on
00:09:16
Angel scrum personal CR pick on the
00:09:17
video that stands out the most on the
00:09:19
screen right now and I'll see you in a
00:09:21
few seconds
![3 logiciels d’Intelligence Artificielle pour investir en Bourse [+1 Bonus].](https://ruhnrawpgxrzdrgaohnf.supabase.co/storage/v1/object/public/images/video/7Fim1AVE5Ks/thumbnail.jpg)