馃攳
WhatIs.com Virtual Book Club: The Phoenix Project, Chapters 5, 6, & 7 - YouTube
Channel: unknown
[0]
[Music]
[4]
all right welcome to the third episode
[6]
of what is
[7]
com's virtual book club i'm wes chai and
[10]
with me today are my fellow technical
[12]
writers ben
[13]
alex caitlin and peggy in this episode
[16]
we will be discussing chapters 5
[18]
6 and 7 of the phoenix project which is
[21]
a business book about devops written by
[23]
gene canton
[24]
george spafford and kevin bear i found
[27]
these chapters especially interesting
[29]
because at this point we're starting to
[31]
see concrete growing pains at parts
[32]
unlimited
[34]
um in chapter five bill receives news
[36]
about an overwhelming amount of i.t
[38]
concerns from a compliance audit report
[40]
in chapter six bill and the it
[42]
department continue to work on change
[44]
management
[45]
um in chapter seven bill meets this guy
[47]
named eric reid
[48]
who's a prospective board member eric's
[51]
a mysterious tech headshot and
[52]
also kind of the quintessential odd
[54]
genius um
[56]
so yeah chapter seven ends with eric
[58]
whisking bill away to one of the
[59]
company's manufacturing plans
[61]
and he gives them a very socratic lesson
[63]
on something
[64]
that eric mysteriously referred to as
[66]
three ways
[68]
i don't understand what the three ways
[69]
are yeah so i actually wrote the
[71]
definition for the three ways last month
[73]
so i can clear up some of the mystery
[75]
for you guys um
[77]
the first way is about workflow the
[79]
second way is about feedback loops
[81]
and the third way is about creating a
[83]
culture where employees feel
[85]
safe experimenting and also learning
[88]
from failure
[89]
so um that spirit of experimenting we
[92]
are going to
[92]
try something a little different this
[94]
week um instead of having
[96]
everyone pick their own term ben and i
[98]
actually picked five definitions that we
[100]
send
[101]
we felt summed up chapters five to seven
[103]
and then we
[104]
assigned them out to team members for
[106]
analysis so
[107]
alex you're going first which term were
[110]
you assigned
[111]
i was assigned pii which stands for
[114]
personally identifiable information
[117]
um pii is information that can be used
[120]
to directly identify an individual so
[122]
this could be anything from names
[124]
addresses phone numbers social security
[126]
numbers
[127]
they're all examples of pii all right
[130]
and how does pii fit in with this week's
[132]
reading
[134]
it's an important term in chapter five
[136]
john pesce
[137]
the chief information officer shares
[140]
that
[141]
that he completed an important task
[143]
around pii and dodge
[144]
bullet but instead of saying good job
[146]
nancy miller who is
[148]
the uh chief audit executive gave him
[151]
grief
[151]
about not putting enough information on
[154]
or
[155]
enough attention on it controls why does
[158]
john get so much grief
[160]
yes a lot i think it's because john
[163]
seems to be more
[164]
anxiety bro and he's warning everyone
[166]
about the dangers
[167]
around putting pii data protection on
[170]
the back burner and
[171]
no one is listening to them
[175]
uh we learned more in our own corporate
[179]
training
[179]
i think a couple of weeks ago that um
[182]
everyone is responsible for protecting
[185]
pii and it's not just
[187]
the chief information security officer's
[189]
job
[190]
so i think this could get pretty
[192]
interesting uh mostly i think the
[194]
authors are
[195]
hinting here that something some sort of
[198]
security event
[199]
involving pii is going to be a part of
[202]
the story
[203]
yeah i agree uh and that thought ties
[205]
nicely into the terminal
[206]
me which is cso which stands for chief
[210]
information security officer i thought
[212]
it was really interesting to see how
[214]
john was characterizing chapter five
[216]
because one of the first things we
[217]
learned about him is that he's gained a
[218]
lot of weight in the three years he's
[219]
been at parts unlimited
[220]
and the guy is obviously under a lot of
[222]
stress
[223]
poor fellow yeah i mean he kind of
[226]
slinks around with his three ring behind
[228]
her and stack of compliance requirements
[230]
and people end up intentionally
[231]
excluding him from meetings uh you can
[233]
start to see how the lack of employee
[235]
buying i'm protecting something you'll
[236]
know is really important like pii
[238]
is going to come back and bite them um
[241]
so it kind of got me wondering
[242]
whether john is like this because
[245]
of his personality you know what's
[247]
happening to him or is it just his job
[249]
like is it a myers-briggs thing where
[251]
nobody's a precinct appreciating john
[253]
because of his quirkiness
[254]
so they leave him out or are they hiding
[256]
from him because they just have too much
[258]
work to do and they think of john as a
[260]
bottomless pit
[261]
of nitpicking compliance requirements
[264]
i think that's a good question because
[265]
in my experience csos have a lot of
[267]
power
[268]
so can we be sure that john isn't just
[270]
building walls up on purpose so he can
[272]
hold on to as much power as possible
[275]
yeah so then the term you assigned me
[277]
was information silo
[280]
and i actually whether that could also
[282]
be part of john's problem too because
[284]
you know i just get the sense that he
[286]
doesn't seem very personable
[288]
and you know i'm wondering could he be
[290]
reluctant to tear down silo walls
[291]
because
[292]
maybe operating in a silo makes him feel
[294]
safe
[295]
that's a good point i haven't thought of
[297]
it that way before i i just figured that
[299]
john had no idea how the long list of
[300]
things he wants
[302]
done impacts other people's jobs yeah
[305]
right
[305]
um it's kind of funny too because brent
[308]
is always in demand to fix this and that
[310]
for everyone
[311]
and then on the other hand people are
[313]
you know perpetually trying to swat john
[315]
away from whatever they're doing
[317]
right and at first they kind of seem
[320]
like opposite characters
[322]
but actually they have a lot in common
[324]
because they're both bottlenecks that
[325]
are preventing the phoenix project from
[327]
moving ahead
[328]
yeah that's actually an important
[330]
concept in this week's chapters
[332]
uh because brent seems like the person
[334]
who's going to save the
[335]
phoenix project moving forward because
[337]
he's the only one who knows what to do
[339]
and how to fix things but it actually
[341]
turns out
[342]
that he becomes the term we assigned
[344]
peggy this week
[347]
what's that bottleneck
[350]
yes sort of in project management a
[353]
bottleneck is called
[355]
a constraint it's ironic because i mean
[359]
the one guy who knows
[360]
everything is actually slowing down
[362]
progress on parts of
[363]
parts unlimited's most important
[365]
business goal which is
[366]
releasing the phoenix project on time so
[369]
until they can figure out a way to stop
[371]
people from bothering
[372]
brent is the phoenix phoenix project
[374]
doomed
[376]
if you believe in the theory of
[378]
constraints yes
[381]
everything is going to have to move as
[382]
fast as brent can move
[385]
but isn't the theory of constraints a
[388]
lean manufacturing thing
[390]
like toyota production
[394]
system or total quality management
[399]
nope and alex already mentioned in the
[402]
book
[402]
um the authors seem to be using
[405]
foreshadowing
[406]
and i think the real gift really is how
[410]
they're using metaphors
[412]
between it and the manufacturing plant
[414]
to show the reader how one concept
[416]
relates to another
[418]
it's pretty easy to understand the
[419]
concepts behind lean production
[421]
is eric is walking bill through the
[423]
products unlimited factory floor
[425]
and i think it's going to be interesting
[427]
to learn how these ideas translate into
[429]
i.t
[430]
yeah i hope you learned more about eric
[434]
i mean he's an interesting guy i feel
[435]
like there's so much to talk about we
[437]
could even do like
[438]
we could talk about on the full episode
[439]
but sadly that's not going to be today
[442]
because we're almost out of time
[443]
so based on the way chapter 7 ended with
[446]
eric walking bill through the parts
[448]
unlimited factory what do you guys think
[450]
will be an important term for chapter
[451]
eight
[454]
based on the factory tour i think it's
[456]
going to be lean production
[458]
that's a good one but didn't chapter 7
[460]
end with bill struggling to remove his
[462]
laptop's battery uh
[464]
because an alarm was going off yep
[467]
that's right
[468]
and at this point in the book bill's
[470]
replacement laptop has
[472]
you know more or less taken a life of
[474]
its own and even become a character
[476]
so i don't know does this mean our next
[479]
week's word should be
[480]
crap top sure
[486]
i'm gonna stick with lean production all
[489]
right then
[490]
well thanks for joining us and be sure
[492]
to check out the free online study
[493]
resources we've been creating for this
[494]
book on whatis.com
[496]
i promise you won't see crap top there
[498]
and see you soon
[508]
[Music]
[515]
you
Most Recent Videos:
You can go back to the homepage right here: Homepage