Commitment vs. Forecast: A Subtle But Important Change to Scrum (2011) • Hacker News Board

Re: Commitment vs. Forecast: A Subtle But Important Change to Scrum (2011)

#11

Post by make3 » Fri, Jan 19, 2018, 2:37 PM UTC

saas_co_de wrote: post #2

http://programming-motherfucker.com/

do people really pair program in real life? I've never actually seen it

Re: Commitment vs. Forecast: A Subtle But Important Change to Scrum (2011)

#12

Post by qznc » Fri, Jan 19, 2018, 2:38 PM UTC

Now I would suggest to deprecate "sprint". It is not healthy to sprint continuously. Sane software development is much more like a marathon.

Re: Commitment vs. Forecast: A Subtle But Important Change to Scrum (2011)

#13

Post by romanovcode » Fri, Jan 19, 2018, 2:39 PM UTC

Can we deprecate scrum in 2018?

Re: Commitment vs. Forecast: A Subtle But Important Change to Scrum (2011)

#14

Post by subway » Fri, Jan 19, 2018, 2:41 PM UTC

lwkl wrote: post #6

saas_co_de wrote: post #2

http://programming-motherfucker.com/

That's probably exactly why you are told that you are socially awkward. Edit: I don't know the creator is there a story to this I don't know?

https://en.m.wikipedia.org/wiki/Zed_Shaw

Re: Commitment vs. Forecast: A Subtle But Important Change to Scrum (2011)

#15

Post by taherchhabra » Fri, Jan 19, 2018, 2:45 PM UTC

throwanem wrote: post #5

saas_co_de wrote: post #2

http://programming-motherfucker.com/

Zed Shaw is a treasure. I'm not sure he's all that much of a role model.

https://learnpythonthehardway.org/book/advice.html

Re: Commitment vs. Forecast: A Subtle But Important Change to Scrum (2011)

#16

Post by dudul » Fri, Jan 19, 2018, 2:48 PM UTC

qznc wrote: post #12

Now I would suggest to deprecate "sprint". It is not healthy to sprint continuously. Sane software development is much more like a marathon.

I don't know if this is meant to be facetious, but I actually fully agree. "Sprint" is a terrible analogy because in reality it is impossible to be sprinting all the time. I usually just say "iteration".

Re: Commitment vs. Forecast: A Subtle But Important Change to Scrum (2011)

#17

Post by dudul » Fri, Jan 19, 2018, 2:49 PM UTC

make3 wrote: post #11

saas_co_de wrote: post #2

http://programming-motherfucker.com/

do people really pair program in real life? I've never actually seen it

Yes.

Re: Commitment vs. Forecast: A Subtle But Important Change to Scrum (2011)

#18

Post by crdoconnor » Fri, Jan 19, 2018, 2:50 PM UTC

taeric wrote: post #7

Funny to see this. I thought getting commitment was one of the soft mechanisms of scrum. An annoying one, because power dynamics are always at play. Still a mechanism, though. I think I'm supportive of the idea on removing it. Seems the goal is ultimately to find ways in rhetoric and action to align the teams in working to the end goal. Which, often, might require tradeoffs to reach a timely delivery. And timing is a…

It probably made more sense to put it in in the beginning when the process was still being sold to senior managers. Now that scrum is much more embedded, taking out for the reasons given makes more sense.

Re: Commitment vs. Forecast: A Subtle But Important Change to Scrum (2011)

#19

Post by spinningarrow » Fri, Jan 19, 2018, 2:52 PM UTC

make3 wrote: post #11

saas_co_de wrote: post #2

http://programming-motherfucker.com/

do people really pair program in real life? I've never actually seen it

Yes, and I highly recommend it!

source: used to think pair programming was odd until I gave it a proper go.

Re: Commitment vs. Forecast: A Subtle But Important Change to Scrum (2011)

#20

Post by DoubleGlazing » Fri, Jan 19, 2018, 2:55 PM UTC

saas_co_de wrote: post #2

http://programming-motherfucker.com/

Oh yes, this rings true with me.

I once worked at a company where the powers that be decided to go all Scrum. They hired a PM to convert all project, inc ongoing ones, to Scrum. It turned an enjoyable job in to a miserable one.