News for hackers. Stuff that matters.
Re:I don’t believe in sprints by gbro3n on Wednesday October 05, 2022 @07:57AM (#33094233)
Kanban is the best middle ground IMO. I agree sprints are a distraction. The planning and ceremonies alone sap time. Sprints are really just a form of pressure. In my experience the stories estimating is not accurate enough to set up a predictable sprint, and the inevitable deviation from the plan just creates additional work to audit and adjust, along with a sense of failure around what has often been a productive 2 weeks.
Re:I don’t believe in sprints by stingraycharles on Wednesday October 05, 2022 @08:05AM (#33094318)
Sprints and planning are useful for organizations that attach a lot of value to planning and deadlines. It creates a lot of additional work and pressure, as you say, but I can also imagine that for certain types of organizations that may be worth it (eg when doing client work on a fixed budget with strict deadlines).

Other than that, I fully agree that Kanban is a great middle ground, as it’s low overhead and focuses on prioritization and flexibility rather than planning and burndown charts and whatnot.

Re:I don’t believe in sprints by elboru on Wednesday October 05, 2022 @09:15AM (#33095144)
> Sprints are really just a form of pressure

I’ve felt the opposite. My team switched from “Scrum” to “Kamban”. Then after a few months the sensation of having an endless pile of cards, without a time frame, felt overwhelming.

In the other hand, having a short lived cycle used to help me manage my time. If for any reason one day I was not able to accomplish much, I knew I still had a few more days to compensate. The same was true for the opposite, I could be really productive a few days and then I could relax for the rest of the sprint.

That workflow really worked for me. With Kanaban I feel the pressure to always be “productive”, because I don’t have a clear reference on how “relaxed” I’m (or not), during the week or month.

Maybe I just need to find a different reference. I guess my point is that sprints don’t necessarily mean pressure for everyone.

Re:I don’t believe in sprints by throwaway4aday on Wednesday October 05, 2022 @08:31AM (#33094600)
You can value planning and deadlines and still not do sprints. The key is that whoever is managing the project, whether it's a dedicated PM or just the lead dev, needs to be fully engaged with the team and understand the work that is being done. Cards (beyond a basic todo list and record of who's doing what), points, sprints, standups, backlogs all of these are symptoms of bad communication and a lack of an overall understanding of the project. Unfortunately, or fortunately if you can put it in to practice, this means that the person leading/managing the team needs to understand software development as well as the current tech and tools being used. There is a place for non-technical managers but it is outside of the software development team where they act as an interface between dev and the other departments or interests in the company.
Re:I don’t believe in sprints by bluGill on Wednesday October 05, 2022 @09:04AM (#33095026)
Kanban is still better than sprints. You organize things that are most important at top, and what is done by the deadline is done and ships; what isn't done doesn't ship. Deadlines may mean you branch so can make the release stable, while feature work that clearly won't be done one time can continue if the team working on it isn't involved in the release.

It doesn't matter if you have sprints of kanban, if there is a deadline is project managers need to do the same work to verify things are progressing fast enough for the release. This work is estimating how much time remains, and if there isn't plenty take action. The plenty part is where most management goes wrong: they want everything done on time, but the only way to get that is have everything done early. That in turns means you need to have at least 20% (the higher the better) of the things planned for your deadline things that you are willing do allow to slip to the next release. Of course working against that is the human tendency to polish things until the last minute, but that shouldn't be managed by the deadline (even though it often is)

I'm against the web release early and often model - don't make your users your beta testers. I'm in favor of spending several months of test after the branch to ensure everything is stable even though this is a lot more expensive. I do agree with the web have automated tests for everything model, I just don't think automated tests alone are enough quality control - automated tests ensure that everything you can think of didn't go wrong, manual testing is about noticing things you didn't think of. (you will note I work in an area where my code can kill people)

Re:I don’t believe in sprints by pnut on Wednesday October 05, 2022 @09:17AM (#33095171)
Funny how whenever I've done kanban, top tech debt items always are eternally pushed down to #5 or 6 in the backlog, never to see the light of day.

I have my criticisms for sure, but sprints give more discretion to the teams to carve out space for multiple types of priorities held in balance, and lock that ratio in for a period of time.

Re:I don’t believe in sprints by jacobyoder on Wednesday October 05, 2022 @10:01AM (#33095697)
> sprints give more discretion to the teams

when they do. i was part of an 'agile' team in 2019 (6 mo contract). I wasn't there long enough to have strong views on work items or priorities, but did watch the interactions between others. It was a decently organized team inside a (fast) growing org - lots of challenges there. But overall, there was a decent balance.

Worked on another smaller team longer - 2 years. As the company grew, it got far more process heavy. The 'sprint' stuff was "as tech lead, you get 5 points to use however you want per sprint!" (yay?). that got taken over by the CTO getting involved and using those '5 points' for constant infrastructure stuff. I was reviewing code I delivered, and it was full of cut corners to continually hit deadlines. I begged on a few occasions for more 'cleanup' time. It was always denied (except for 3 days over xmas, because... literally no one else was working, so they couldn't say no).

The project transformed in to "here's our strategic goals for 2022" with every quarter mapped and filled to the brim with work. 0 time for anything but bare minimum MVP. The thinking was "well... you've been able to work at that pace before, and we added someone new, so we can increase that". In 2019, it was MVP - test the idea. Speed to market makes some sense. In 2022, millions of dollars and hundreds of lives affected each month... we need to take a bit more time to clean up existing code, retire legacy code, adopt a slower pace to focus on clarity, testability, even performance concerns etc. This seemed to fall on deaf ears.

"discretion to the teams" tends to ring hollow to me based on recent experiences, and ideally I'll work with another group in the future with a healthier balance.

Re:I don’t believe in sprints by david422 on Wednesday October 05, 2022 @10:20AM (#33095907)
I think the answer here is to point your current tickets higher. When someone asks for estimates on time, or points, you give a higher estimate so as to not leave as much tech debt behind. In theory or course, may not work in practice.
Re:I don’t believe in sprints by jacobyoder on Wednesday October 05, 2022 @10:30AM (#33096035)
Potentially, some, yes. However, when goals have already been decided, and 'missing' those goals is a 'bad thing', there's only so much you can do. We'd gone from collaborative to 'command and control'. And... FWIW, we got a lot more done under 'collaborative', but it was mostly just 'me' on the dev side and one other person on the product side.

At some point though, many of the original assumptions about problems are understood to have been fundamentally wrong/misaligned, and need some revisiting. You need to touch old code, whether to delete it, or to have it align with new standards or new ... whatever. Touching anything that didn't relate to an explicit 'agreed on' jira ticket was seen as wrong/bad. I ended up bundling in 'fixes' of unrelated stuff when working on 'new' stuff because... it had to get done, but was ignored or rejected during any sort of planning.

I've heard it said that "to go fast, do it alone. to go far, you need a team". I can get on board with that, but you need a team in agreement and competent. I have a colleague working on a small team and... they're mostly just completely inexperience and bad, but there's no self-awareness. Taking direction from the guy who was in high school last year, while ignoring the person who's lead multiple teams and has delivered high value software for 20 years... that's a bizarre imbalance that can't be fixed with 'sprints' or process alone.

Re:I don’t believe in sprints by bluGill on Thursday October 06, 2022 @09:10AM (#33107761)
On a 6 month contract you haven't been around the code long enough to know what is tech debt and what is a good solution for a complex solution.

Though your point is correct - you rarely are given time to fix tech debt. If you switch to a long term employee, then you should intentionally slow your velocity a little to fix tech debt. By the time management catches on you will have fixed enough that an improvement is visible and so you have proven yourself, and thus will be allowed to do more of it.

Also note that a story isn't done until refactoring is done. Sure it works, but if the code is a mess your story isn't done and you don't move onto the next one. Many developers fail to force this, but as a professional this should be part of your code of conduct and thus not optional no matter what the deadline.

In any case the point is you will never be officially given those 5 points - but you can take them by force.

Re:I don’t believe in sprints by benrow on Wednesday October 05, 2022 @10:33AM (#33096076)
Agreed.

As an aside, one thing just came to mind. Even if you're bringing tech debt tickets into each sprint, there's a possibility they'll get picked up last - fine, unless they keep getting pushed back!

Part of me thinks this could be mitigated by reducing the velocity expectation. But there tends to be an overarching sprint goal relating to product work, and this often invites extra scope due to unforeseen impediments. So 'background' work like tech debt is easily pushed back.

I don't know of a better way. Perhaps it comes down to human factors such as limited focus.

Re:I don’t believe in sprints by bluGill on Thursday October 06, 2022 @09:12AM (#33107782)
There are two ways management can handle getting things done on time: commit to taking only 80% of the teams capacity, thus ensuring there is plenty of buffer; or commit to the full thing, and accept that some things won't get done. If (as most do despite Agile warnings about it being wrong) your management wants you to get done 100% of what you commit to, then as a team you need to hide 20% of your capacity from management.
Re:I don’t believe in sprints by marcosdumay on Wednesday October 05, 2022 @12:14PM (#33097419)
Do not let formal debt and improvements compete on the same ranking.

Either do 2 of this, 1 of that, or have separated time slots, or whatever. But separate them.

Re:I don’t believe in sprints by robertlagrant on Wednesday October 05, 2022 @12:50PM (#33098002)
Yep. We used to dedicate 20% of story points to tech debt, when we had quite a lot of it.
Re:I don’t believe in sprints by patrickserrano on Wednesday October 05, 2022 @09:53AM (#33095599)
At a past job for a while we did Kanban with the sprint as a time box and it worked really well for the constraints we were working in. When we had work with deadlines, we'd flag that work as needing to be done in the sprint time box and put it on the top of the pile. Otherwise the team just kept picking up the next item, and we'd do a single review meeting at the end of the sprint to check in and see how everyone felt and what was accomplished. It was less of a retro and more of a temperature check.

It worked really well for a team that served a lot of different stakeholders and also had to field requests from customers since the priority of the work was always changing even if the deadlines for the work didn't.

Re:I don’t believe in sprints by closeparen on Wednesday October 05, 2022 @08:33AM (#33094617)
If you place a lot of value on planning and deadlines, you should probably embrace that wholeheartedly, and not try to pretend to be “agile.”
Re:I don’t believe in sprints by LtWorf on Wednesday October 05, 2022 @08:01AM (#33094287)
In a job a long time ago there was a brogrammer in the team, always estimating absurdly short times because he was so good and fast (he wasn't bad, but he was 2-3x slower than he himself estimated). So I had picked up the habit of estimating 5x longer on tasks, to balance him out.

Also all the sprint planning and retrospective took basically 30% of our time.

Re:I don’t believe in sprints by gbro3n on Wednesday October 05, 2022 @08:07AM (#33094332)
Agreed. The differences of opinion during estimating are another form of pressure. Programmers work differently. I might estimate a task longer than a colleague, but I might be the type of programmer who tidies up and refactors along the way, or who spends more time communicating with the team on strategy and architecture. These are hard to quantify behaviors that Jira can't effectively track, unless you're going to spend half your day _in_ Jira writing down every action every day. Don't event get me started on the effect of context switching.

Managers are pushed to produce reports to prove they're managing. Reports require metrics, and that's a lot of where all this rubbish starts. The solution in my experience is to keep teams small enough that you don't need those sorts of layers of management (though the opposite is inevitable in larger companies).

Re:I don’t believe in sprints by pwinnski on Wednesday October 05, 2022 @09:43AM (#33095480)
How does something like this take 30% of your time? On my calendar it's two hours out of 80, or 2.5%. One hour per sprint for planning, one hour for retro, why would it be longer?

My team lead spends more time prepping tasks with the PM prior to sprint planning, but even then it's about 5%.

My last company, we had one-week sprints, but we didn't do official retros, so it was still 2.5%, one hour of planning for 40 hours of work.

Re:I don’t believe in sprints by pwinnski on Wednesday October 05, 2022 @04:58PM (#33101186)
Sprint planning today took 26 minutes.

The Retro yesterday was 30. So that's less than 1.25% of my time spent.

Re:I don’t believe in sprints by pevey on Wednesday October 05, 2022 @08:26AM (#33094543)
I find it challenging to estimate my own time in tasks. Part of every task is figuring out how to actually do the thing you are wanting to do, and sometimes that takes 5 minutes and sometimes much longer. So I am terrible at estimating my own time, and even worse at estimating someone else’s. It doesn’t add pressure to a person if you give them a time goal they know is basically arbitrary.
Re:I don’t believe in sprints by nobodyandproud on Wednesday October 05, 2022 @09:40AM (#33095452)
Software estimation is very hard.

This is what scrum (done well) helps with. Unless the software was horribly written, it’s usually easy to estimate effort for very modest, well-defined changes.

Take a large enhancement or overhaul, however, and estimates will be wildly off and it’s because of the iceberg effect of unknowns.

What scrum forces the inexperienced teams to do is start breaking down, plan and incrementally chip away at a ill-defined, large request by turning it into many smaller and better understood deliverables.

It’s what very good teams do, though they do it without the need for formality.

Re:I don’t believe in sprints by LtWorf on Wednesday October 05, 2022 @09:16AM (#33095163)
That means the task is underspecified. You should schedule a "figure this out" instead, and once the task is well defined it can be done.
Re:I don’t believe in sprints by pevey on Wednesday October 05, 2022 @11:47AM (#33097072)
You never know if you have really completed the "figure it out" task until the "get it done" task is completed.
Re:I don’t believe in sprints by yucky on Wednesday October 05, 2022 @08:04PM (#33102772)
A meeting to plan for the meeting. Instead of turtles, it's meetings all the way down.
Re:I don’t believe in sprints by LtWorf on Friday October 07, 2022 @01:43AM (#33117835)
I never said a meeting. That says a lot about you :p
Re:I don’t believe in sprints by haasted on Wednesday October 05, 2022 @08:06AM (#33094325)
Shouldn't that lead to a team discussion about why the estimates differ so drastically? In most circumstances, the reasons would be inaccurate assessment of scope or complexity. Clearing up misconceptions like that can be a great boost for productivity.

"Oh, you can do it like THAT?! I was not aware. I'll take a shot at implementing the feature using that approach."

Re:I don’t believe in sprints by throwaway284243 on Wednesday October 05, 2022 @08:51AM (#33094845)
> "Oh, you can do it like THAT?! I was not aware. I'll take a shot at implementing the feature using that approach."

Next performance review, your manager goes: It seems like you're not really aware of a lot of techniques of how to solve problems efficiently. Maybe you should do more pairing with the other seemingly much better developers to strengthen your skills. And now you've cornered yourself as a junior for the next 2 years, who was "hired on the wrong level".

All of this is assuming that the team members will prioritise the performance of the team higher than their own performance, of which there are no incentives. The incentives is to make yourself look as good as possible (don't admit your idea is inferior), and skew the playing field to your advantage (insist on using the tools you know best) etc.

People simply don't spontaneously cooperate and simply don't "just get along" in a situation like this.

Even in hippie communities where everything is voluntary and there is no personal gain to be had, it still falls apart because some people just don't cooperate.

So how do you expect that to happen in a situation with money involved, and competition between people?

Why do the software industry and scrum think they have spontaneously discovered how people always just get along, inside a basic weekly planning schedule? That would literally be a nobel peace prize right there.

Re:I don’t believe in sprints by acdha on Wednesday October 05, 2022 @08:27AM (#33094554)
Theoretically, yes, but if you’re spending half of your time on process overhead there isn’t much left to do that well and most of the time there’ll be enough differences from sprint to sprint that it’s plausible that this time was late for other reasons, until you have a sufficiently long data set to show that it’s a trend.
Re:I don’t believe in sprints by LtWorf on Wednesday October 05, 2022 @08:23AM (#33094499)
It did. I said I would not stop doing it until he'd stop. So we just continued this way.
Re:I don’t believe in sprints by steveBK123 on Wednesday October 05, 2022 @08:25AM (#33094529)
It inevitably does and then everyone slowly starts estimating everything at the middle point size in the agreed spectrum, with only 2-3 outliers
Re:I don’t believe in sprints by denton-scratch on Wednesday October 05, 2022 @08:25AM (#33094525)
Estimates should be made in abstract units (e.g. 'function points'), then converted to man-days or dollars or whatever using a scaling factor specific to the estimator. That way, the actual value of the estimate is moot; it's the consistency of the estimates that counts.
Re:I don’t believe in sprints by polotics on Wednesday October 05, 2022 @08:15AM (#33094415)
KANBAN is good at ensuring you do not have too many themes on your plate at the same time.

Producing effort estimates is one of the many approaches to start talking about a task, and not doing it may mean that somebody else's better idea on how to tackle it gets ignored.

Having sprints is a good way to coax people in fully finishing things, it is often needed as many developers tend to jump to the next shiny.

If any of these three things gets used by a bad manager to get fake importance, to put pressure, push people down instead of pulling them up... then get rid of that manager.

Re:I don’t believe in sprints by ozim on Wednesday October 05, 2022 @09:17AM (#33095174)
From my experience sprints ensure that stuff is "good enough" and pushed out the door. Like QA having idea that some icon is not aligned - but yeah it is end of the sprint close it and fix in next iteration and get to work on other thing that has priority now - not aligning some unimportant details.

So sprints are also good way to coax people into cutting scope instead of working till it is "perfect". Then pushing back on management to have breathing space and accepting changes only after sprint ends and not when they have a brilliant idea.

Sprints and ceremonies create touch points for business people to interact with dev team instead of constantly breathing on their neck or coming up with ideas. Business using JIRA and writing stories/tickets should make sure there is enough context in these so your tickets are living documentation "who,why,where".

Re:I don’t believe in sprints by 29athrowaway on Wednesday October 05, 2022 @09:19AM (#33095193)
Don't capitalize words that are not acronyms.

It's just a 5 letter word, it's not that difficult.

Re:I don’t believe in sprints by quesera on Wednesday October 05, 2022 @10:48AM (#33096254)
> It's just a 5 letter word, it's not that difficult.

Beware the careless pedant!

Re:I don’t believe in sprints by 29athrowaway on Wednesday October 05, 2022 @01:42PM (#33098767)
Instant karma. Thank you, phone keyboard.

I rate my comment a perfect 7/5.

Re:I don’t believe in sprints by polotics on Wednesday October 05, 2022 @01:33PM (#33098621)
カンバン then!
Re:I don’t believe in sprints by steveBK123 on Wednesday October 05, 2022 @08:35AM (#33094641)
Yup, that was the overall vibe at my last place. Sprints are too micro and lead to tunnel vision. Got a lot of stuff done, but the hard tickets were always underestimated & dragged across sprints. And was it the "right stuff" to be working on to start with? Everyone felt like we were failing even as we got a lot of stuff done.

Additionally, despite the attempt at predictability, wider project management was lacking, which lead to cross-team long running projects running over by 100-200%.

Often this was failure to capture actual requirements, making generous assumptions that a vendor would provide a magic bullet, allocating little to know time for integration / cross team work, etc.

Each team worked on the tickets in their sprint, from their backlog, according to what product management wanted. The fact that none of it tied together at the end was not devs fault if you want to institute such a tunnel vision process on them.

Re:I don’t believe in sprints by xxs on Wednesday October 05, 2022 @08:37AM (#33094669)
> tickets were always underestimated

Teach the developers who estimate them to treat the process as the circle circumvent instead of the diameter and multiple by Pi. There you go - done.

Re:I don’t believe in sprints by steveBK123 on Wednesday October 05, 2022 @09:08AM (#33095064)
Many tickets were also overestimated! They just don't stick out as a problem since they close early and make the sprint look good. Naturally, the ones that don't close are the ones that are underestimated!

If you overestimate everything then you end up idle at end of sprint & picking backlog items to bring in, so then product wants to put more points/stories into next sprint.

The system is seemingly designed to produce this outcome.

Re:I don’t believe in sprints by StevePerkins on Wednesday October 05, 2022 @09:46AM (#33095518)
This folds in with the mantra of "Do NOT think about blockers and interruptions when estimating your story points, only think about the task in a vacuum"... and then not looking at blockers and interruptions when judging your velocity and results, either.

The system is to teach everyone how to lie and juke the system. It feels awful working in most sprint-based environments. Because even when you're highly productive it still feels like you failed in multiple places, and it always feels like you're being dishonest and have no real choice about it.

Re:I don’t believe in sprints by steveBK123 on Wednesday October 05, 2022 @01:10PM (#33098300)
Yup the other stupid thing that kept happening was sizing the work to fit the model. Medium sized tickets were least controversial in 3 hour backlog refinement meetings. Therefore every ticket began to ranked at that level. Which then beget us chopping up anything larger into these medium sized tickets, and avoiding creating any too-small tickets.

So instead of "ticket: make pasta for dinner" it was like "ticket 1: purchase prego & pasta from instacart" , "ticket 2: boil water & get out the jar opener", "ticket 3: cook the pasta and sauce", "ticket 4: place the meal and serve".

Zero chance all 4 finished in the sprint, in fact they were rarely even all planned for same sprint.

It became impossible to express to users what they were getting at the end of each sprint. "OK, so you've.. purchased ingredients, when do I get to eat?"

This happened with multiple product managers, agile coaches and tech leads so it wasn't just a single person forcing stupidity on the process..

Re:I don’t believe in sprints by RamblingCTO on Wednesday October 05, 2022 @11:50AM (#33097111)
If you do scrum properly you shouldn't have a lot of meetings for "planning and ceremonies". We follow "scrum and xp from the trenches" quite closely. We have four meetings: - scrum planning (max 1h/week of the sprint)* - dailies (max 15 minutes per meeting)* - demo (we like to call it sprint review, because it's interactive, not one-sided). takes about 30 minutes - retro (takes an hour)

*most of the times we use a lot less

So we have 2h of meetings in the first weeks, 2.5h of meetings in the second week if you do a two-week sprint as we do. the rest of the meetings is rather "working together" than having "meetings". If you have much more hours in meetings than this (which can be attributed to scrum) you're simply doing it wrong.

Re:I don’t believe in sprints by twic on Wednesday October 05, 2022 @09:56AM (#33095632)
Every competent agile team i've ever been on ended up with vestigial sprints / iterations. There might be a weekly rhythm to meetings, but there is a continuous flow of stories, commits, and releases. Why on earth would you do it any other way?
Re:I don’t believe in sprints by kixxauth on Wednesday October 05, 2022 @08:21AM (#33094480)
I think the point of the OP is missed here. Productive teams don’t need any of this garbage; least of all a religious war about methodologies.

Productive teams are primarily hackers solving larger problems. This stuff gets in the way, causing the team to morph into developers instead.

Re:I don’t believe in sprints by sillyquiet on Wednesday October 05, 2022 @08:25AM (#33094521)
So... developers aren't productive?

This is a weird take.

Re:I don’t believe in sprints by kixxauth on Wednesday October 05, 2022 @08:29AM (#33094577)
Yeah, good point. If productivity equates to value creation then hackers are more productive. If productivity equates to what software management can measure, then developers are more productive.

I’m making a pithy statement about the difference hackers and developers

Re:I don’t believe in sprints by sillyquiet on Wednesday October 05, 2022 @08:47AM (#33094786)
I gotta say that your distinction between 'hackers' and 'developers' is pretty ill-informed - just out of curiosity, have you primarily worked in start-ups?
Re:I don’t believe in sprints by drstewart on Wednesday October 05, 2022 @09:20AM (#33095205)
This has a real "no TRUE Scotsman" vibe
Re:I don’t believe in sprints by brightball on Wednesday October 05, 2022 @09:32AM (#33095348)
Wrote extensively about this a few years back and it generated a great discussion here.

https://news.ycombinator.com/item?id=17154355

Re:I don’t believe in sprints by pjmlp on Wednesday October 05, 2022 @09:25AM (#33095255)
On my experience Kanban only works for IT kind of tasks, where each ticket is an isolated action, instead of a small step to a bigger goal.
Re:I don’t believe in sprints by pelasaco on Wednesday October 05, 2022 @08:52AM (#33094855)
After working with many methodologies, I think the most important thing is: regardless of which methodology you team is using, stick to the rules and deviate as less a possible from that, otherwise after some years, nobody understands the methodology in place, and people have real issues to follow it.