News for hackers. Stuff that matters.
Re:Gitlab's Guide to All-Remote by adolfoabegg on Thursday March 12, 2020 @08:49AM (#22556233)
From the manifesto: The results of work over the hours put in.

How do you adapt that to the scrum process which has a burndown chart based in the time spent on tickets.

Re:Gitlab's Guide to All-Remote by joeconway on Thursday March 12, 2020 @09:40AM (#22556680)
Scrum burndowns should not be related to time spent at all. That’s not an actual agile technique, that’s your company not trusting you and not understanding how software works. Story points that are meant to represent unknowns and complexity, not hours, used for estimation and burndowns are one solution to this
Re:Gitlab's Guide to All-Remote by sytse on Thursday March 12, 2020 @09:20AM (#22556489)
At Gitlab we try to reduce the scope of tickets so that they all ship in the same sprint.

We measure efficiency by measuring the MR rate, the number of merge requests in a month devided by the number of engineers. To game the number you have to split work up in smaller Parts which helps cycle time, coordination, predictability, and quality, for example smaller changes are easier to review.

Re:Gitlab's Guide to All-Remote by roneesh on Thursday March 12, 2020 @09:46AM (#22556744)
That isn't agile. Tickets should be based on relative effort, not hours, and certainly not more hours being better.
Re:Gitlab's Guide to All-Remote by xtat on Saturday March 14, 2020 @12:17AM (#22573145)
when are we going to burndown agile