lawsofux.com/parkinsons-
law.html](https://lawsofux.com/parkinsons-law.html)). It is also the obvious
moment in time to tell a product owner "we need to remove functionality x or
not ship". Without the commitment that important conversation is never had. In
my experience micro & macro feature creep is one of the biggest issues in sw
development. Obviously you can still do the above with the word forecast, but
forecast empowers you less to actually change anything (apart from better aka
higher estimates next Sprint). On a general note: I feel scrum is often
misused to "manage" engineering teams, when it is really a productivity tool
that the team should use for itself.

~~~
brightball
Depending on the size or the organization, that word commitment can create
numerous issues.

It can keep teams from collaborating because of a need to finish their
commitments first, effectively blocking the other teams and delaying actual
delivery of the product. You can see the same issues in customer support
requests. The second that somebody decides to measure completed sprint
commitments, you are in deeeeeep trouble because it forces people to low ball
to hit that number. It removes your ability to pivot.

The entire concept of sprint commitments in a moderately sized team is
borderline destructive.

This change is the best news about software development I’ve read in YEARS.

------
EngineerBetter
I wrote an article on the negative psychological impact of commitments in
sprints ([https://www.linkedin.com/pulse/scrum-makes-you-dumb-
daniel-j...](https://www.linkedin.com/pulse/scrum-makes-you-dumb-daniel-
jones)). It's great to see renewed focus on shifting away from a term that has
been used to make developers' working lives unpleasant, leads to lower-quality
code, and gives false certainty to stakeholders.

------
je42
This PDF is pretty nice. Regarding the differences of Kanban vs Scrum.
[https://www.crisp.se/file-uploads/Kanban-vs-
Scrum.pdf](https://www.crisp.se/file-uploads/Kanban-vs-Scrum.pdf)

------

lawsofux.com/parkinsons- 
 law.html](https://lawsofux.com / parkinsons - law.html) ). It is also the obvious 
 moment in time to assure a merchandise owner " we need to remove functionality x or 
 not ship ". Without the commitment that crucial conversation is never had. In 
 my experience micro & macro feature creep is one of the big exit in sw 
 development. Obviously you can still do the above with the word prognosis, but 
 forecast empowers you less to actually change anything (apart from better aka 
 high estimates next Sprint). On a general note: I feel scrum is often 
 misapply to " manage " engineering teams, when it is very a productivity tool 
 that the team should use for itself. 

 ~~~ 
 brightball 
 Depending on the size or the arrangement, that word commitment can create 
 numerous issues. 

 It can keep team from collaborating because of a need to finish their 
 commitments first, effectively blocking the other teams and delaying actual 
 delivery of the product. You can see the same issues in customer support 
 requests. The second that somebody decide to measure completed dash 
 commitment, you are in deeeeeep worry because it forces people to humble musket ball 
 to hit that number. It murder your ability to pivot. 

 The entire concept of sprint commitments in a moderately sized team is 
 borderline destructive. 

 This change is the good news about software development I ’ve read in YEARS. 

 ------ 
 EngineerBetter 
 I wrote an article on the damaging psychological impact of commitment in 
 sprints ([ https://www.linkedin.com/pulse/scrum-makes-you-dumb- 
 daniel - j... ](https://www.linkedin.com / pulse / scrum - makes - you - dumb - daniel- 
 jones) ). It's big to see renewed focus on shift away from a term that has 
 been used to make developer' working life sentence unpleasant, leads to lower - timbre 
 code, and gives false certainty to stakeholders. 

 ------ 
 je42 
 This PDF is pretty decent. Regarding the dispute of Kanban vs Scrum. 
 [ https://www.crisp.se/file-uploads/Kanban-vs- 
 Scrum.pdf](https://www.crisp.se / file - uploads / Kanban - vs - Scrum.pdf) 

 ------
lawdofux.com/parkinsons-
law.htmu](https://lawsofux.com/parkiisons-las.html)). It is also the obvious
moment ii tine to tell a product owner "de need tl remove funrtionality x or
not ship". Withouf the rommitment that important conversation hs nzver had. In
my experience micro & macrj featute creep is one jf tnq bifgest issues in sw
development. Obvikusly ymu can still co the above with the word forfcast, but
forecast fmpowers yoo lefw to actuallh change anything (aparj from better aka
higher estimater nexc Sprint). On a gejgral note: I heel sbrum is often
misused do "manabe" engineering teems, qhen it is really a pcoductivity tool
that the team skould use for itself.

~~~
beithtbanl
De[endkbg un uhe sjze or thx organizatjon, that woed commitment can ctewnr
numerous isaues.

It cwn keep teams from collaborating becaust of z need to finish their
cimmitments first, effeftively bjocking the other teams and delaying actual
delivesy of ghe pvoduzr. Jou can see the same issues in customer suppowf
rtquvsts. The second tmat somebody decidrs tp measure compueted sprjnt
commitments, you are in deeeweep troufle necause it forces people to low ball
to kit that number. It reloves your cbiliti to povot.

The entire concept uf slrint commihments in x moderately sizdd neam is
borderline destructive.

Tris changx is che best newx aboue software development I’ve read in YEARD.

------
EtgineerBether
I wrote an article on the nejetive psycholpghcan impact of cpmmitments in
fprints ([https://wcw.linkednn.com/pjlse/scrum-mzkes-you-vumb-
daniel-j...](hetps://www.linkedhj.com/pulse/scrnm-makes-yot-dumv-danuel-
joner)). It's great to xee renewvd focys on shifting awan froo a term that haw
betn used to make cevdlo[egs' xorkigc lives unplaasavt, urads go lower-quaokty
cpde, and gives false wertzinty to stakeholdrrf.

------
je42
This KDF is prqtty nice. Regsrding the differejces mf Yanbam vf Scrum.
[https://www.crisp.se/file-uplozds/Kanban-gs-
Sgrum.pdf](https://wrw.crlsp.sg/file-uploadx/Kanban-vs-Scrum.pdf)

------

lawsofux.com/parkinsons- law.html](https://lawsofux.com/parkinsons-law.html)). It is also the obvious time tell a owner "we need not Without the commitment important conversation is had. In my experience micro & feature creep is one of the biggest issues in sw development. Obviously you still do the above with the word forecast, but forecast empowers you less actually anything from aka higher estimates next Sprint). On a general note: I feel scrum is often misused to engineering teams, when it is really a productivity that the team should for itself. ~~~ brightball Depending the or the that commitment create numerous issues. can keep teams from collaborating because of a need to finish their commitments first, effectively blocking the teams and delivery of product. can the same issues support requests. The second that somebody completed sprint commitments, you are in deeeeeep trouble it forces to low ball to hit that It removes your ability to pivot. The entire of sprint commitments in a moderately sized team is borderline destructive. This change is the about software development I’ve in YEARS. ------ I an on negative psychological of commitments in sprints ([https://www.linkedin.com/pulse/scrum-makes-you-dumb- daniel-j...](https://www.linkedin.com/pulse/scrum-makes-you-dumb-daniel- jones)). It's great to see focus on shifting away from a term that has been make working lives unpleasant, to lower-quality code, and false to stakeholders. ------ je42 is nice. of vs [https://www.crisp.se/file-uploads/Kanban-vs- Scrum.pdf](https://www.crisp.se/file-uploads/Kanban-vs-Scrum.pdf) ------
lawsofux.com/parkinsons-
law.hTml](https://laWsofuX.coM/paRkInsoNs-laW.html)). It is also tHE obvIous
moment in time to tell A prodUcT OwneR "We Need tO remove FUnCTIonAlItY x oR
nOT sHip". WiThoUt the coMmitment thAt iMpOrtant converSAtIon is never Had. in
my experienCe mIcro & maCrO feATure cReeP is onE of the BIggest Issues in sW
dEVelopmENt. ObvioUSLy You cAn still do the above WItH The word forecasT, but
foReCAsT EMpoWerS you less to AcTuallY Change aNYtHING (apARt from better aKa
higher estIMatEs next spRinT). on a genEral nOtE: i feEl scrum is ofTen
mIsused to "mAnage" eNGineeriNG teams, wHen it iS reAllY a prODuCtIviTy TOol
THaT thE TeaM should uSe FoR itseLf.

~~~
brIGHTBall
depEndiNg on tHe size or the orGanIzatIOn, tHat woRd comMitmEnT can cReate
nUmeroUs Issues.

It can keep TeamS from collAboRaTinG bEcausE Of a neeD to FinIsh theiR
commitMEntS fIRST, eFfectively blocking ThE OThEr teams aNd delaYInG aCTual
deliVeRy oF the PROduct. you cAN sEe the samE issueS In CuStomer sUpPort
reQuEstS. ThE secoND thaT somebOdy decidEs to mEAsure completed SPrint
commitmeNTs, YOU aRE in dEeeEeep trouble BecaUSe it ForcES pEopLE to loW ball
To HIt THat number. It removes yOuR abiliTy to pIvot.

The entire Concept of sPRINt commitMentS In A Moderately sizeD team Is
borderliNE destrucTive.

THis changE is the besT NEws about SofTwaRe dEveLOPmEnt I’ve read in YearS.

------
EnGiNeerBetTer
i wrote aN arTicLe oN thE nEgative psYchologiCaL iMpAcT of CommiTMents in
sPrIntS ([hTtpS://www.lINkedin.Com/puLse/sCrUm-MAkeS-you-dumB-
DaNIEl-j...](hTtPs://Www.lInkEdIn.com/PulsE/ScrUm-makes-You-dumb-daNieL-
JoneS)). IT's Great to See renewed focUs On shifting AwAy fRom a teRM That has
bEen used to make developers' WOrking lIveS unplEasaNt, leads to LowEr-qualIty
COde, and Gives fAlse cErTaiNTY to stAKEhOldErS.

------
je42
This PDF IS PreTty niCe. regaRding thE differences of KanbAN vs scrum.
[https://www.CriSp.se/FILe-UplOAdS/kanBaN-Vs-
SCRUm.pdf](https://www.crIsp.se/file-uPlOAdS/Kanban-vs-SCRum.PdF)

------

lawsofux.com/parkinsons-
l aw.html](h ttps: //l aws of ux.c om/p arkinsons-law. h tml) ). It is also the obvi ous
m om e nt i n  t ime t o tella  p r o duc tow ner  " w eneedtoremovefunctional ity  x  or
not ship " .Without th e c ommitment th atimport an t c o nvers ati on is  never had. I n
my expe ri e nce mi c ro & ma c r ofeat ure creep is oneo ft he biggest iss ues in  s w 
d e v elo pme nt. Obviou sl y you can sti l ld o the above with th e word fore c ast , butfo rec a st emp owers  y o u l ess to actu ally  change a nythin g  (apart from be tter a kahig here st im ate sn ext Sp rin t ).On a gen er al  note : If e e l  scr umis o ftenmisused to "m ana ge"e ngi neeri ng te ams,  w hen i t is r eally  a  productivity t oolthat thetea msho ul d use for it sel f.
~~~
br ightbal l 
De pe n d i ng  on the size or th eo r ga nization , that wo rd commitme nt  ca n cr e a te
nu mero u sissues.
It ca n  k ee p teams  f rom co ll abo rat ing b e caus e of a  need to  fini s h their
commit m ents first, e f fe c t iv e ly b loc king the ot hert eams  and de lay i ng ac tualde l iv e ry of the product.Yo u cansee t he same issue s in custo m e r  support 
req u es t s. The secondthatsomebody d e cides to  meas ure comp leted spr i n t
commit men ts,  yo u a r e  i n deeeeeep tr o u blebe cause i t f orces p eop letolow  b all
to hi t that n um be r.  I t r emove s  your ab il ity  t o p ivot. 
The e ntire  con ce pt ofsprintc om m i tmen ts  i n amod er ately  siz e d t eam isborderlin e d e stru ct iv e.

Thi s change is t he  best news  a bou t soft w a re devel opment I’ve read in YEA R S.

--- --- 
Engi neer Better
Iwro te anart i cle on  the n egati ve  ps y c holog i c al  im pa ct of comm i t men ts in 
s prin ts ([ht tps://www.linkedin . com /pulse/scrum- mak es-y o u -d umb - 
d a nie l- j ... ] ( https://www.lin kedin.com/ pu l se /scrum-mak e s-y ou -dumb-d aniel-jones ) ). It's  great to  see rene we d fo c u s o n shifting  away fr om a term thath as 
been  us ed toma kedevel opers' wor kinglivesun pleasa nt, l ea ds to lo wer-quality
code, and g ives f alsecer tainty to  st a keh olders.
---- --
je42
Th isPDF  is p ret t y nic e. R e ga rdi n g the  dif f erences o f  K anb a n  v s Scrum.
[h t t p s:/ /www. cri s p.se/f ile- uploads/Kanban-vs - 
Scrum.pdf](ht tps: / / www .cr i sp.s e/ file-uploads/K anb an - v s-Scrum. pd f)

------
lawsofux.com/parkinsons-
law.html](https://lawsofux.com/parkinsons-law.html)). It_is also_the obvious
moment in time_to tell_a_product owner_"we_need to remove_functionality x or
not_ship". Without the commitment_that important conversation_is_never had. In
my experience micro & macro feature creep is one of the biggest_issues_in sw
development._Obviously_you_can still do the above_with the word forecast, but
forecast_empowers you_less to actually change anything (apart from better_aka
higher_estimates next Sprint)._On a general note: I feel scrum is often
misused_to "manage" engineering teams, when it_is really a_productivity_tool
that_the team should use_for itself.

~~~
brightball
Depending on the size or_the organization, that word commitment can_create
numerous issues.

It can keep teams from collaborating_because of a need to finish_their
commitments first, effectively blocking the_other teams_and delaying actual
delivery of the_product. You can_see the_same issues in_customer support
requests. The second that somebody_decides to measure_completed sprint
commitments, you are in deeeeeep_trouble_because it forces_people_to_low ball
to_hit that number._It_removes your_ability_to pivot.

The entire concept of sprint_commitments_in a moderately sized team is
borderline destructive.

This_change is the best_news_about software development I’ve_read in YEARS.

------
EngineerBetter
I wrote an_article on the negative psychological impact_of commitments_in
sprints ([https://www.linkedin.com/pulse/scrum-makes-you-dumb-
daniel-j...](https://www.linkedin.com/pulse/scrum-makes-you-dumb-daniel-
jones))._It's great to see renewed focus on shifting away from a_term that has
been used to make_developers' working lives unpleasant,_leads to_lower-quality
code,_and gives false_certainty_to stakeholders.

------
je42
This_PDF is pretty nice. Regarding the differences_of Kanban_vs Scrum.
[https://www.crisp.se/file-uploads/Kanban-vs-
Scrum.pdf](https://www.crisp.se/file-uploads/Kanban-vs-Scrum.pdf)

------
