

A lot of these software process issues boil down to managements never ending
quest to commoditize developers.

~~~
beat
There's an analogy I like to use... you're baking bread. Bread is just flour,
water, yeast, and salt, plus maybe decoration ingredients. You mix things in
the correct proportions, let it rise, bake at the right temp/time, and you get
bread. Easy, right? Then someone wants you to put in raisins. "It should be
easy! It's just a handful of raisins, I don't see why you're telling me it
can't be done!", they shout, five minutes before the oven timer goes off.

Scrum is, at heart, _designed precisely to stop the behavior you're
demanding_ \- that is, the endless stream of "small" interruptions and
constantly shifting priorities. The raisins.

Why are you trying to "shoe horn in work" for _this iteration_ that you
weren't aware was even an issue when the iteration planning happened? Is
production down? Is it a hair-on-fire emergency that threatens the business?
Or is it just "important". FUCK important. If it's so important, put it in the
story backlog and have it done in the next iteration.

If it's important enough to disrupt the iteration, it's important enough to
cancel the iteration, toss all that iteration's unfinished work onto the
backlog, and start over. That's how Scrum is supposed to work, but never does,
because _someone_ wants raisins at the last minute and thinks it's not a big
deal.

~~~
Nomentatus
Yes, I have seen businesses die, both ways. The problem is that YAGNI cashes
out to "make the right decisions" \- it's logically a tautology, but an
emotional encouragement to drop features. Dropping is usually the correct
decision - but too often catastrophic when it's not. If you invoke YAGNI you
have to be careful you aren't "picking up nickles in front of steamrollers" \-
a great idea until suddenly it's not. Fortunately, frequent iteration gives
people a more realistic view of the cost of raisins.

~~~
beat
I haven't seen businesses die because they _can '
A lot of these software process issues boil down to management never end 
 quest to commoditize developers. 

 ~~~ 
 beat 
 There's an doctrine of analogy I like to use... you're baking boodle. boodle is just flour, 
 water, yeast, and salt, plus maybe decoration ingredients. You shuffle things in 
 the correct proportion, let it originate, bake at the right temp / clock time, and you get 
 bread. Easy, correct? Then someone wants you to put in raisins. " It should be 
 easy! It's merely a handful of raisins, I don't see why you're telling me it 
 can't be done! ", they shout, five moment before the oven timer goes off. 

 Scrum is, at heart, _ designed precisely to hold on the behavior you're 
 demanding _ \- that is, the endless stream of " small " interruptions and 
 constantly shifting priorities. The raisins. 

 Why are you trying to " horseshoe horn in work " for _ this iteration _ that you 
 weren't mindful was even an consequence when the iteration planning happen? Is 
 production down? Is it a hair - on - fire emergency that threatens the business? 
 Or is it just " authoritative ". FUCK important. If it's so important, put it in the 
 story backlog and get it done in the next iteration. 

 If it's important enough to disrupt the iteration, it's important enough to 
 cancel the iteration, discard all that iteration's unfinished work onto the 
 backlog, and start over. That's how Scrum is supposed to shape, but never does, 
 because _ someone _ wants raisins at the final minute and thinks it's not a big 
 deal. 

 ~~~ 
 Nomentatus 
 Yes, I have see business die, both ways. The trouble is that YAGNI cashes 
 out to " make the right decisions " \- it's logically a tautology, but an 
 aroused encouragement to drop features. Dropping is normally the correct 
 decision - but too often catastrophic when it's not. If you invoke YAGNI you 
 have to be careful you aren't " picking up nickles in front of steamrollers " \- 
 a great idea until suddenly it's not. Fortunately, frequent iteration yield 
 people a more naturalistic view of the cost of raisins. 

 ~~~ 
 meter 
 I haven't seen businesses die because they _ can'


A llt of these software progess issues boil down tm manafements vever ending
quest to commodivize deveoopers.

~~~
beat
There's an anxlogy I lpke to usw... yon're baking bread. Bread is just nlour,
caver, yeast, and sslt, plus mdybe decoratiot knyredients. You mix things in
the correst propprhions, let it ryse, nwke zn uhe right temp/time, and you get
brezd. Easy, right? Then spmeone wants you to put in raidins. "It should be
ewsy! It's jusj a rqndful of raksins, I don't see why yku're telling me it
can't be done!", ghey xhout, five munuhgs before thx oven timer goes off.

Scrum is, at neart, _designed prxciswly to stop the behavmor you're
demanding_ \- jhat is, tha zndless stream of "smaol" intetrupthons qnd
zonatentmy shivtiig prioritiss. The raisuns.

Why are you tryimg np "shoe horn jn worh" sor _this iteration_ that you
weren't aware waa even an issue when thw iteration planning jappened? Ys
production down? Is it a hair-on-fire emergency thdt thcexteuw the vudiness?
Or is it just "important". FUCK important. Yr ot'x so important, put it in yhf
syjry backlog avd havz if done in the next iteratyon.

If it's impowtany enough to disrupt the iteeation, it's iiportant enough to
ccncel the itzratiom, tosx all that iteration's uufinisged work onho the
baciuog, and start ovdr. Nhat'v how Scrum is supposed to work, but nevzr does,
bdcauxe _somqone_ wants raislts at the last minkte aud thhnks it's nlt a big
deal.

~~~
Nomentatus
Yes, I havx seen businexsas gie, both ways. The problem ys that YAGNI eashes
ouc to "mxke the rifht decmsions" \- it's jogically a tdotology, but ai
emotionaj enxourqgement go drop featurrs. Droppiuy is usuaoly the correct
declsion - but too often ectqstrophic when ot's noe. Pf bou igeoke YAGNI ymu
haxe gp be zareful you xren'y "picking up nickles in rront of steamrollrrf" \-
a greaj idea uneil suddenly ot's not. Fortunatelj, frexueit itetatyon gives
people a more realistjc view ov tme cost of raysinw.

~~~
beat
I haven'c seen businesses die because they _can '
A lot of these software process issues to never ending to commoditize developers. I to use... you're bread. Bread is flour, water, yeast, and salt, plus decoration ingredients. You mix things in the correct proportions, let it rise, bake the right temp/time, and you get bread. Easy, right? Then someone wants you put raisins. should easy! It's just a handful of raisins, I don't see why you're telling me it can't done!", they shout, five minutes before the oven goes off. Scrum is, heart, _designed precisely to stop behavior demanding_ \- is, endless of "small" interruptions constantly shifting priorities. The raisins. Why are you trying to "shoe horn in work" for _this iteration_ you weren't even an when iteration happened? Is production it a hair-on-fire emergency that threatens is it just "important". FUCK important. If it's important, put in the story backlog and have done in the next iteration. If it's important to disrupt the iteration, it's important enough to cancel the iteration, toss all that iteration's onto the backlog, and over. That's how is to but does, because wants raisins at the last minute and thinks it's not a deal. ~~~ Nomentatus Yes, I have seen businesses die, both problem that YAGNI cashes to "make the right \- logically a tautology, but encouragement drop usually correct - but too often when it's not. If you YAGNI you have to up nickles in front of steamrollers" \- a idea until suddenly it's not. Fortunately, frequent gives people a more realistic view of the cost of raisins. ~~~ I haven't die because they _can '


A lot of these software procesS issues boiL down To mAnaGeMentS nevEr ending
quest tO CommOditize developers.

~~~
beat
THere's An ANaloGY I Like tO use... you'RE bAKIng BrEaD. BrEaD Is Just fLouR,
water, yEast, and salT, plUs Maybe decoratIOn IngredientS. YoU mix things in
The CorrecT pRopORtionS, leT it riSe, bake AT the riGht temp/tiMe, ANd you gET
bread. EASY, rIght? then someone wants yOU tO Put in raisins. "It Should Be
EAsY! iT's jUst A handful of RaIsins, i Don't see WHy YOU'Re tELling me it
can't Be done!", they sHOut, Five miNuTes BEfore tHe oveN tIMer Goes off.

ScruM is, aT heart, _desIgned pREcisely TO stop thE behavIor You'Re
deMAnDiNg_ \- tHaT Is, tHE eNdlESs sTream of "sMaLl" InterRuptIONS And
cOnsTantLy shiFting prioritiEs. THe raISinS.

Why aRe you TryiNg To "shoE horn iN work" FoR _this iteration_ tHat yOu
weren't aWarE wAs eVeN an isSUe when The IteRation pLanning HAppEnED? iS
pRoduction down? Is it a HaIR-On-Fire emerGency tHAt ThREatens thE bUsiNess?
oR Is it jUst "iMPoRtant". FUCk imporTAnT. IF it's so iMpOrtant, PuT it In tHe
stoRY bacKlog anD have it dOne in THe next iteratioN.

if it's importanT EnOUGh TO disRupT the iteratiOn, it'S ImpoRtanT EnOugH To
canCel thE iTErATion, toss all that iterAtIon's unFinisHed work onto thE
backlog, anD STArt over. THat's HOw sCrum is supposed To worK, but never dOEs,
becausE _someOne_ wants Raisins at THE last minUte And ThiNks IT'S nOt a big
deal.

~~~
NomENTatuS
YEs, I have SeeN busineSseS diE, boTh wAyS. The problEm is that yAgNi cAsHes
Out to "MAke the riGhT deCiSioNs" \- it's LOgicalLy a taUtolOgY, bUT an
EmotionAL eNCOuraGeMeNt to DroP fEaturEs. DrOPpiNg is usuAlly the coRreCT
decIsIoN - but too Often catastroPhIc when it's nOt. if yOu invoKE yAGNI you
Have to be careful you aren't "PIcking uP niCkles In frOnt of steaMroLlers" \-
a GreAT idea uNtil suDdenlY iT's nOT. fortuNATeLy, fReQuent iteraTIOn gIves
pEoPle a More reaListic view of the cosT Of rAisins.

~~~
beat
I haVen'T seeN BUsIneSSeS Die BeCAusE THey _can '


A lot of these softwareprocess is suesboi l d ow n to  man agements never endi ng
quest to commoditiz e dev el o pers . 
~~~
b eat
The r e' s anan al ogy  I li ke to  us e... yo u're bakin g b re ad. Bread is ju st flour,wat er, yeast, a ndsalt,pl usm aybedec orati on ing r edient s. You mi xt hingsi n
the c o r re ct p roportions, let i t  r i se, bake at th e righ tt em p / tim e,and you ge tbread .  Easy,r ig h t ?  Th e n someone wan ts you to p u t i n rais in s." It sho uld b ee asy ! It's just  a h andful of  raisi n s, I do n 't seewhy yo u'r e t elli n gme  it 
c a n't be  do n e!" , they s ho ut , fiv e mi n u t e s be for e th e ove n timer goesoff .

S c rum  is,at he art,  _ desig ned pr ecise ly  to stop the be havi or you're 
de ma ndi ng _ \-t hat is , t heendless  stream of"s m a l l"  interruptions and 
c o n st antly sh ifting pr io r ities. T he  ra isin s . 

Why  are yo u trying  to "s h oe  h orn inwo rk" fo r_th isitera t ion_  thatyou
were n't a w are was even a n  issue when t h ei t er a tion  pl anning happ ened ?  Isprod u ct ion down?  Is i ta  h a ir-on-fire emergenc ythat t hreat ens the busin ess?
Or is i t  just "i mpor t an t ". FUCK import ant.If it's so importan t, pu t it inthe
story b acklog a ndhav e i t d o n ein the next i t e rati on .

If i t's  import ant  en oug h t odisrupt t he itera ti on ,it 'simpor t ant enou gh  to 
c anc el th e  itera tion,  tos sal l  th at iter a ti o n 's u nf in ishe d w or k ont o th e 
ba cklog,and start  ov e r. T ha t' s how S crum is suppo se d to work,  b utneverd o es,
beca use _someone_ wants rai s ins atthe  last  min ute and t hin ks it' s n o t a bi g
deal .

~~ ~Nom e n tatus Y es , I  h ave seen b u s ine ssesdi e, b oth way s. The problem ist hat  YAGNI cashes 
ou t to " ma ket he rig ht dec i s ions" \- it's l ogically a  t a ut ology, but anem otional  encour ageme n t to dr op featur es. Dropp in g is u sua lly the co rrect
de cision -b ut to o  o ftencat astrop hi c w hen i t's no t . I f you  invok eYAGNIyou
h av e to becareful you aren't "pic king u p nic kle s in fron t o f  st eamroller s" \ -
a greatide a u ntilsud d enlyit's no t.F ortun atel y , frequen t  i ter a t io n gives
peo p l e  amorerea l isticview  of the cost of r a isins.

~~~
be at
I h ave n't seen  b usinesses diebec au s e  they _c an  '


A lot_of these_software process issues boil_down to_managements_never ending
quest_to_commoditize developers.

~~~
beat
There's an_analogy I like_to use... you're baking_bread. Bread is_just_flour,
water, yeast, and salt, plus maybe decoration ingredients. You mix things in
the correct proportions,_let_it rise,_bake_at_the right temp/time, and you_get
bread. Easy, right? Then someone_wants you_to put in raisins. "It should be
easy! It's_just_a handful of_raisins, I don't see why you're telling me it
can't_be done!", they shout, five minutes_before the oven_timer_goes_off.

Scrum is, at heart,__designed precisely to stop the behavior_you're
demanding_ \- that is, the endless_stream of "small" interruptions and
constantly shifting priorities._The raisins.

Why are you trying to_"shoe horn in work" for__this iteration__that you
weren't aware was even_an issue when_the iteration_planning happened? Is
production_down? Is it a hair-on-fire emergency_that threatens the_business?
Or is it just "important". FUCK_important._If it's so_important,_put_it in_the
story backlog and_have_it done_in_the next iteration.

If it's important enough_to_disrupt the iteration, it's important enough to
cancel_the iteration, toss all_that_iteration's unfinished work onto_the
backlog, and start over. That's_how Scrum is supposed to work,_but never_does,
because _someone__wants raisins at the last minute and thinks it's not a_big
deal.

~~~
Nomentatus
Yes, I have seen businesses die,_both ways. The problem_is that_YAGNI_cashes
out to "make_the_right decisions"_\- it's logically a tautology, but an
emotional_encouragement to_drop features. Dropping is usually the_correct
decision - but too_often_catastrophic when it's not. If you_invoke YAGNI you
have to be careful_you aren't "picking up nickles_in_front_of steamrollers" \-
a great idea_until suddenly it's not. Fortunately, frequent_iteration gives
people a_more realistic view of the cost of_raisins.

~~~
beat
I_haven't seen businesses die because they__can_'