News for hackers. Stuff that matters.
Re:Why I'm not a big fan of Scrum by cageface on Monday August 08, 2016 @07:19AM (#12246827)
I've been doing Scrum-driven development for a few years now after working much more independently for most of my career. I understand why managers like it because it at least lends some structure and predictability to what is an inherently unpredictable enterprise.

But the author's criticisms of the incentives of Scrum are on point I think. Because the stories are always articulated in terms of user facing features they encourage developers to hack things together in the most expedient way possible and completely fail to capture the need to address cross cutting concerns, serious consideration of architecture, and refactoring.

This is how you can get two years into a project and have managers and clients that think that things are going well when the actual code is an increasingly unmaintainable rats' nest. Good devs confronted with this kind of mess will eventually burn out on sticking their necks out defending necessary but opaque refactoring tasks and move on to greener pastures.

Re:Why I'm not a big fan of Scrum by draz on Monday August 08, 2016 @08:39AM (#12247226)
I am Product in a large corporation, and it's a certainly a fine balance. In a previous life, I was a developer, and I dealt with similar issues. I have a lot of respect and empathy for the the Tech team. Therefore, I asked my Tech team to inform me when things are getting out of hand -- that's the responsible Product thing to do. I instituted that technical debt is part of our KPIs. If it's not captured, it's not actionable. A few examples: - Documentation: required when method's cyclomatic complexity is high or method is just plain long (we defined what we consider "long"). Every customer facing method has a working usage example (%), etc. - Test Coverage: % unit tests (defined by modules) -- higher is not necessarily better, but it gives us a sense of where we stand. % of test automation: manual vs. automated. - Refactoring delays: # of TODO comments, # of compiler and static code analysis warnings (e.g., “this method is deprecated”) --> that is a sure sign that things will break in the future and an investment is needed.

There's some development work to be able to capture these things, but it gives visibility and power to Tech to inject some maintenance work into normal sprint development. I'd love to hear what other people are doing.

Re:Why I'm not a big fan of Scrum by superuser2 on Monday August 08, 2016 @01:28PM (#12249400)
> technical debt is part of our KPIs. If it's not captured, it's not actionable

This is where I suspect manager-types and developers have a vigorous divergence in values.

Professionals routinely encounter situations where something is wrong and needs to be "actioned" but its wrongness isn't effectively measured by any metric (other than the opinions of the experienced people looking at it).

There is a certain species of manager who has taken Taylorism a bit too far and says that anything not reflected in the KPIs is not real and not getting acted upon. I hope this isn't what you're expressing here, but oh man is that mindset frustrating.

Re:Why I'm not a big fan of Scrum by kpil on Monday August 08, 2016 @04:15PM (#12250570)
On the other hand, at the end of the road - or the rewrite - something should have been gained in terms of money, risk or time.

Being shitty is not reason enough, but it's almost always possible to reason and quantify and weigh the cost versus the benefits.

Re:Why I'm not a big fan of Scrum by timv on Monday August 08, 2016 @09:30PM (#12251961)
Senior staff in pretty much all organisations are given some latitude with respect to performing tasks that they believe will be beneficial without needing to produce a specified cost-benefit.

We have one-on-one catch-ups with staff, we have all-hands meetings, we visit clients, read books and articles, attend industry functions, issue press releases, meet with potential investors, etc.

There's value in all those things, but very rarely do we need to account for the fact that we spend time on them.

Senior engineering staff need that same freedom - it should be totally appropriate for them to make that call that "I'm accountable for the technical quality of this code, and I've decided that this needs to be done".

That requires some sense of business acumen - there needs to be an appropriate balance of technical investment to business investment - but that's part of the role of being a senior dev / tech lead / architect / whatever-your-organisation-calls-them.

Re:Why I'm not a big fan of Scrum by kpil on Tuesday August 09, 2016 @01:54AM (#12252859)
I agree.

I am not saying that you always need a detailed balance sheet, just that it's good to reason about the benefits.

It's especially hard to quantify risks - that's where you really need the expertise.

What I wanted to point out is that there seems to be quite many developers that actually do not have a sense of business acumen, and are willing to spend alot of money on low priority tasks, just for their own personal pleasure.

Re:Why I'm not a big fan of Scrum by superuser2 on Monday August 08, 2016 @05:07PM (#12250885)
Of course something should be gained, but that doesn't mean you can always tell how much would be or was.

There is no mature "actuarial science" of software development. The market can provide concrete pricing for new feature development; engineers can't tell you how many dollars of tech debt you're in or give three significant digits on the probability of a major outage tomorrow.

That doesn't make money/risk/time costs which are difficult to measure any less real and it doesn't make them smaller than the ones which are easy KPIs.

Nor can you necessarily look at the movement of measurable KPIs and say "man, that rewrite was a waste of money." Who's to say things wouldn't have been worse without it?

Re:Why I'm not a big fan of Scrum by dekimir on Monday August 08, 2016 @08:33PM (#12251771)
> it's almost always possible to reason and quantify and weigh the cost versus the benefits

I don't think so. As a pretty good analogy, can you quantify the benefit of replacing knob-and-tube wiring in an old house? Now consider that the house across the street keeps its old wiring for the next twenty years without anything bad happening.

Re:Why I'm not a big fan of Scrum by uklenny on Monday August 08, 2016 @09:22AM (#12247471)
The problem with raising issues with a framework like Scrum is that despite many share references, most people are in environments which apply Scrum in a slightly different way.

We talk about organisations applying Scrum but what we're really referring to are groups of people, and depending on those people, their mindset, their history and their current role requirements - they will use the Scrum model in their own idiosyncractic way.

Take the point about technical debt and running so fast with an Agile development workflow that you never get to refactor code or properly document etc.

Even if you just took that in reference to one specific company, the value of, cost of, and importance of these things could be different at different times.

When a startup is running to get MVP out to get customer feedback, it's usually much more efficient to set the basic expectation that the first version of your product will get thrown away once you've learned all the important aspects of what you need to deliver. With that in mind - startup development is a completely different beast than when your product is established and you have paying customers with expectations of up-to-date documentation etc.

Some managers are do not have good people skills and manage by just holding developers to account based on the expectations set in their Scrum planning day. Discussions about whether refactoring should be done yet or not may not even be something they want to know/talk about and they rely on engineers to factor that into their sprint estimates.

Depending on whether the company is being driven by sales/demo opportunities, or feature roll-out timescales etc. then the call about whether to do something 'quick' or 'right' may drop either way.

For developers it's important to understand the dynamics that are driving the business and what their role is (sometimes you have to 'JFDI'). If you have a good engineering team with a strong leader then these things shouldn't be that visible to anyone else. It's also important to be able to meet the expectations you set. If you keep delivering late then you'll also struggle to get people to let you do more than the minimum required at the time.

For the business as a whole it's all about the big picture and understanding the decisions you make and what their impact (short and medium term) is.

If you want quick releases and don't have the resources for that to allow for good documentation and/or scalable code, then you need to understand that technical debt is building up and at some point it will need to be paid.

Re:Why I'm not a big fan of Scrum by dekimir on Monday August 08, 2016 @08:28PM (#12251751)
> despite many share references, most people are in environments which apply Scrum in a slightly different way

Exactly. In fact, the linked text is a prime example: it professes to address the "standard Scrum as described in the official guide", and then goes on to condemn the notion of story points. Now, I happen to agree with those story-points criticisms, but guess what: that official guide says nothing about story points at all! :o

Re:Why I'm not a big fan of Scrum by maxxxxx on Monday August 08, 2016 @07:35AM (#12246896)
In my view the only way to handle this is to make constant refactoring part of the work without telling management. If you ask for permission for refactoring you will almost always get a "No".
Re:Why I'm not a big fan of Scrum by s_kilk on Monday August 08, 2016 @08:23AM (#12247131)
This is how we ended up with the "Shadow Sprint" at a previous workplace. A whole bunch of utterly essential engineering work was left out of the sprint process, so many of us would just go ahead and do what needed to be done anyway while working on whatever tickets we'd picked up frome the "real" sprint.

Utterly dysfunctional of course, but if it's do-or-die, I'd prefer to 'do'.

Re:Why I'm not a big fan of Scrum by bmj on Monday August 08, 2016 @09:32AM (#12247547)
How did you handle regression testing of the refactored functionality? That's our biggest hurdle. QC is swamped with "regular" sprint work, so there's no way they manage any additional load during the sprint.
Re:Why I'm not a big fan of Scrum by s_kilk on Monday August 08, 2016 @09:39AM (#12247614)
We had pretty good (but not amazing) unit and integration tests in many of those systems, and a willingness to manually test the systems where we didn't have tests.

If we had to lean on a QA department to get this stuff done, I'm not convinced we would have been able to actually deliver that project.

Re:Why I'm not a big fan of Scrum by ktRolster on Monday August 08, 2016 @01:38PM (#12249476)
Only refactor things in sections of code that you're changing anyway. That way QA already needs to test those sections of code, and gets no extra work.
Re:Why I'm not a big fan of Scrum by matthewmacleod on Monday August 08, 2016 @08:40AM (#12247234)
We tend to bundle that work up and include it in tickets with the full acknowledgement of the rest of the team.

"Oh, since we're adding new email features, we'll need to clean up some of the old email code. That will add additional complexity to this task, so we will estimate it higher."

It works, allows us to still track the impact on velocity, keeps everyone informed, and makes technical debt clear and trackable.

Re:Why I'm not a big fan of Scrum by xwkd on Monday August 08, 2016 @12:00PM (#12248762)
I believe this is the correct approach. You're not hiding the complexity of the work, and you're also not compromising on quality. This leaves only the task of saying "no" when asked if you, "for now, could just..."
Re:Why I'm not a big fan of Scrum by maxxxxx on Monday August 08, 2016 @01:42PM (#12249509)
This is how it should work in my view. You just need managers that are disciplined and don't tell you to not clean up old code because of deadline pressure.
Re:Why I'm not a big fan of Scrum by abritinthebay on Thursday August 11, 2016 @03:16PM (#12270897)
This is exactly what is supposed to happen in a Scrum system. If someone is not doing this they're not doing Scrum - just something they called Scrum to pacify people
Re:Why I'm not a big fan of Scrum by humanrebar on Monday August 08, 2016 @07:49AM (#12246961)
This is mentioned in the article as possible only for small changes. When the refactoring involves more systemic problems, it becomes impossible to make the change in the course of making other client-facing changes.

I'll add that some subsystems are a mess but stable. It's difficult to make refactorings with other changes when there aren't other changes to make. I see this in particular with old but stable subsystems that will need to be ported to new environments someday, but it's never a good day to lay the groundwork for that inevitable change.

Re:Why I'm not a big fan of Scrum by lmm on Monday August 08, 2016 @08:17AM (#12247099)
> I see this in particular with old but stable subsystems that will need to be ported to new environments someday, but it's never a good day to lay the groundwork for that inevitable change.

I think it's correct to defer that work until you need it. You may end up never porting that subsystem, in which case refactoring the currently-stable implementation is wasted effort. As and when porting becomes an actual business requirement it can be prioritized appropriately.

Re:Why I'm not a big fan of Scrum by humanrebar on Monday August 08, 2016 @08:38AM (#12247220)
> You may end up never porting that subsystem, in which case refactoring the currently-stable implementation is wasted effort.

I understand this approach, and it works many times. But when the porting is delayed until the last possible minute, it's more likely that hacks are put in because the requirement turned into a hard deadline. Instead of defining a sensible OS abstraction layer, the developers might find and replace "Windows XP" with "Windows 7".

Re:Why I'm not a big fan of Scrum by lmm on Monday August 08, 2016 @08:53AM (#12247314)
> I understand this approach, and it works many times. But when the porting is delayed until the last possible minute, it's more likely that hacks are put in because the requirement turned into a hard deadline. Instead of defining a sensible OS abstraction layer, the developers might find and replace "Windows XP" with "Windows 7".

Which may well be the right choice for the business at that point.

More generally, it's not like doing it now makes it faster than doing it later: you have to put the same amount of total work in either way. In fact you have to put more work in if you do it now, because you will have to ensure that any subsequent changes don't break the porting. If you have other tasks that are a higher priority than porting, you should do them first, almost by definition. Of course if the port is your highest priority then that is what you should be working on (again almost by definition). Porting should be left as late as possible, but no later.

Re:Why I'm not a big fan of Scrum by TeMPOraL on Monday August 08, 2016 @09:41AM (#12247630)
> Which may well be the right choice for the business at that point.

I think it may be imporant to raise a few points for consideration here:

- what may be a good choice for the business short-term can also be a very bad choice for the business long-term

- many - personally, I believe most - businesses don't care about products they make or services they give, they care about the money they can make via those products/services; ergo, the quality doesn't matter beyond the point the customer already paid what they were expected to pay

I don't bring it up as criticism, but only to point out that there are two completely different worldviews here competing. One, shared by many developers, is that the product is what that matters. The other, shared by the "business types", is that the profit generated by product matters.

I also feel that part of one becoming a professional developer is a shift from thinking about quality of work to thinking about its money-making potential. Which I personally consider a poison to the mind, and it makes me hate working in companies. But those are just my personal feelings.

Re:Why I'm not a big fan of Scrum by humanrebar on Monday August 08, 2016 @09:10AM (#12247408)
You misunderstand. If more than a small minority of your code cares what OS it's running on (beyond obvious excepted), you have a large amount of technical debt. Cleaning that up, either by refactoring or replacing the offending code, is in the business's best interest because it keeps costs down and keeps more options available to the business.

The 'business people' are not qualified by themselves to say that the cost-benefit analysis of the refactoring is worth the effort. Because while they may have a good idea of the customer benefits, they generally have little insight into what the future costs of technical debt are. You see this obviously demonstrated by 'business people' who are shocked that there is work to do on five-year-old code that has been working fine for years. Any reasonably experienced developer, any many junior developers besides, can tell you that code rots if it's not maintained properly.

Re:Why I'm not a big fan of Scrum by lmm on Monday August 08, 2016 @09:39AM (#12247612)
> Cleaning that up, either by refactoring or replacing the offending code, is in the business's best interest because it keeps costs down and keeps more options available to the business.

IME that's very rarely the highest-value thing you can be doing for the business. It's not worth paying for flexibility that you're never going to use, and it's not like it's going to take longer to refactor later than it would to do it now.

> The 'business people' are not qualified by themselves to say that the cost-benefit analysis of the refactoring is worth the effort.

Yes they are. Cost-benefit analysis is their job. It's your job to give them an accurate picture of the costs and the benefits.

> Because while they may have a good idea of the customer benefits, they generally have little insight into what the future costs of technical debt are. You see this obviously demonstrated by 'business people' who are shocked that there is work to do on five-year-old code that has been working fine for years. Any reasonably experienced developer, any many junior developers besides, can tell you that code rots if it's not maintained properly.

Yes and no. If you don't need to make changes to a given system then it's fine for it to "rot". Presumably there is a business reason they want to make changes, in which case bringing the code up to a point where you can make those changes is part of the cost of that business-level deliverable.

Re:Why I'm not a big fan of Scrum by st3v3r on Monday August 08, 2016 @02:06PM (#12249694)
"Yes and no. If you don't need to make changes to a given system then it's fine for it to "rot". Presumably there is a business reason they want to make changes, in which case bringing the code up to a point where you can make those changes is part of the cost of that business-level deliverable."

Except at that point, there's likely a hard (usually arbitrary) deadline, meaning you don't have the time. So you end up hacking stuff up again, and the tech debt doesn't get addressed. Your best people end up getting frustrated that they're not being listened to, and that they constantly have to explain this stuff to the business people, and eventually they leave.

Re:Why I'm not a big fan of Scrum by Fargren on Monday August 08, 2016 @11:25AM (#12248483)
> it's not like it's going to take longer to refactor later than it would to do it now.

It is so, when you have to build on top of something you will have to refactor later. I think the miscomunnication here is happening because the person you are replying to is assuming that case, and you are assuming the case where the code to be refactored is isolated form the rest of the system.

Re:Why I'm not a big fan of Scrum by st3v3r on Monday August 08, 2016 @02:02PM (#12249663)
"More generally, it's not like doing it now makes it faster than doing it later"

No, but "faster" isn't necessarily the point. Doing it correctly leads to it being "faster" because you don't have to constantly go back and fix bugs because you used ugly hacks to get stuff done in the short timeframe you had because the company decided to wait until the last minute.

Re:Why I'm not a big fan of Scrum by fsloth on Monday August 08, 2016 @08:45AM (#12247260)
In a non-broken organization technical leads (or equivalent) have same level of authority to guide development as feature driven personnel and the necessity of features vs. quality can be triaged in bright daylight.

If the organization is not sane, that's another thing of course (and often the case, sadly).

Re:Why I'm not a big fan of Scrum by maxxxxx on Monday August 08, 2016 @09:36AM (#12247586)
True, but don't forget that non-broken organizations are very rare :-)
Re:Why I'm not a big fan of Scrum by clifanatic on Monday August 08, 2016 @10:45AM (#12248175)
Do you know of one? I've been looking. For 25 years.
Re:Why I'm not a big fan of Scrum by engi_nerd on Monday August 08, 2016 @12:15PM (#12248874)
All organizations are broken, but some are more broken than others.
Re:Why I'm not a big fan of Scrum by fsloth on Monday August 08, 2016 @03:04PM (#12250100)
There are several in the Helsinki area (that I'm aware of - that have been at some point at least - sane in this regard. Many broken of course as well).
Re:Why I'm not a big fan of Scrum by Zigurd on Monday August 08, 2016 @01:15PM (#12249306)
This is a typical way that agile and related approaches become a barrier between implementers and management.

The fault is almost all on the management side because, ipso facto, they're the ones making the decisions that drive this outcome.

In the real world, there are outcomes that are much worse than this. But this does have the effect of neutralizing the value of scrum: Management gets what implementers decide they get, and scrum is just the way middle management is told the story that they pass up the chain.

Re:Why I'm not a big fan of Scrum by gedy on Monday August 08, 2016 @09:19AM (#12247453)
TBH this is what I've always assumed it should be from day one with Scrum, after training with Ken Schwaber etc. The backlog is not a Todo list.

It's the only way that seemed sane without twisting user stories into weird refactoring or architecture stories and keeping team from writing garbage code waiting for these "tech stories" to clean it up.

Re:Why I'm not a big fan of Scrum by blub on Monday August 08, 2016 @07:55AM (#12246992)
Why is management getting involved?

The PO should try to balance this with feature impementation and the team + SM should make it clear when it's needed. This seems to work fine in an environment based on collaboration between PO,SM and dev team, but will probably fail in an adversarial one.

Re:Why I'm not a big fan of Scrum by maxxxxx on Monday August 08, 2016 @09:35AM (#12247570)
I have rarely seen a PO as the single contact to the "business". Most of the time there are multiple project managers, product mangers and line managers who have a say and put pressure on the dev team.
Re:Why I'm not a big fan of Scrum by JustSomeNobody on Monday August 08, 2016 @08:22AM (#12247127)
Because managers have to report to other managers and they don't want to report that the devs are working on something that already has been implemented and "works".
Re:Why I'm not a big fan of Scrum by cel1ne on Monday August 08, 2016 @08:16AM (#12247095)
Indeed. That's sometimes the case with other stuff like playability too. I've added simple animations which delighted users from time to time.

If I had asked beforehand to invest time for this, the response would be "let's postpone this (forever)".

Re:Why I'm not a big fan of Scrum by JustSomeNobody on Monday August 08, 2016 @08:19AM (#12247114)
Can't do that for deep refactoring. You'll need QA involved and the boss will never sign off on that because, well, he's a boss not a proper manager.
Re:Why I'm not a big fan of Scrum by patothon on Monday August 08, 2016 @12:18PM (#12248896)
I don't like scrum myself, but let me try to defend it because I think the problem of most of the people who don't have a good experience with scrum is a misunderstanding of the underlying principles behind it.

Let's just remember that Scrum is just a tool that is trying to replicate some practices of the toyota production system (TPS), and an important principle of the TPS is continuous improvement, and Scrum has this through restrospectives. Another principle is quality built in.

Now, how to avoid having a rat's nest after 2 years?

First of all, you have to remove velocity as a goal for your team. It's easy to game, and it de-incentivizes finding a _predictable_ velocity, which is the goal of that tool.

The goal of velocity, is to know what's the "cost" of building an healthy system.

i.e.: Your team ships an arbitrarily 10 points per sprint by doing what they think is right. The same team could ship an arbitrarily 20 points per week. 10 is the _true_ cost of building a healthy system. There is not a lot more to do for good team, honestly, at that point. Management can't say anything, because you bring them predictability, and that's mainly what they want. They might think you're slow, but hey, all of this is relative.

Suddenly, what does that mean when your team only ships 5 arbitrary points? That they had to push extra. That there was an unexpected problem. That things were on fire and you had to stop working on features entirely.

Basically, that there is something to retro on, find the root cause and anticipate for next sprints, and use to go back to the healthy level of points.

I used this at several places. It demands trust, but it always pays off.

With some teams I worked with, we set up a technical prioritization planning meeting every week, where basically decided what was going to be prioritized for that week. Each team was picking 2/3 things to do on top of the features.

You don't tell anyone. You do it.

Re:Why I'm not a big fan of Scrum by ubernostrum on Monday August 08, 2016 @03:41PM (#12250350)
I think the problem of most of the people who don't have a good experience with scrum is a misunderstanding of the underlying principles behind it.

Unfortunately this has become a cliché whenever someone criticizes scrum, Agile in general, etc.: it's never the fault of the idea/process, it's the fault of the manager/team for not understanding it properly or not doing it right.

Even if these philosophies and processes are so amazingly great when properly understood and implemented, the fact that hardly anyone seems to be able to properly understand and implement them would be a fatal flaw.

Re:Why I'm not a big fan of Scrum by patothon on Monday August 08, 2016 @06:31PM (#12251281)
Agreed, that's why I specified I don't really like Scrum. Mainly because it's hard to actually implement without all the flaws if you don't try to understand the underlying principles. Unfortunately, Scrum books and coaches rarely go through these.
Re:Why I'm not a big fan of Scrum by dragonwriter on Thursday August 11, 2016 @03:29PM (#12270986)
> Mainly because it's hard to actually implement without all the flaws if you don't try to understand the underlying principles. Unfortunately, Scrum books and coaches rarely go through these.

If you are implementing Scrum, I don't see how you do it without the Scrum Guide (which defines Scrum), which is both quite short and does, in fact, go through the underlying principles.

Re:Why I'm not a big fan of Scrum by abritinthebay on Thursday August 11, 2016 @03:17PM (#12270904)
> it's never the fault of the idea/process, it's the fault of the manager/team for not understanding it properly or not doing it right.

Well, almost every time I see Scrum criticized the described process is not Scrum and merely cribs ideas from it without understand the purpose or how things inter-relate.

So it's a fair criticism.

Re:Why I'm not a big fan of Scrum by bighi on Monday August 08, 2016 @03:54PM (#12250436)
> Suddenly, what does that mean when your team only ships 5 arbitrary points?

In my experience, it means some developers failed to game the system that particular time.

But you can be sure there were many other problematic moments in previous sprints, but the developer could hack together an ugly mess of a code to avoid the shame of failing in front of everyone in a meeting, and dragging the team's points down.

Because the unwritten thing about points is that they are used to shame people. In public. Sometimes not explicitly, but the feeling is there. It's always there.

Re:Why I'm not a big fan of Scrum by patothon on Monday August 08, 2016 @06:35PM (#12251295)
Yes.

That's why, if you have to work with and/or manage a scrum team, making velocity not the focus of the sprint is step 1 for a sane process. We count points, but it's not a contract. We try to reach the points, but it's not a contract.

In my parent comment:

_First of all, you have to remove velocity as a goal for your team. It's easy to game, and it de-incentivizes finding a _predictable_ velocity, which is the goal of that tool._

Re:Why I'm not a big fan of Scrum by vibrato on Monday August 08, 2016 @06:26PM (#12251268)
Scrum really is shame driven development in my experience
Re:Why I'm not a big fan of Scrum by ktRolster on Monday August 08, 2016 @01:36PM (#12249465)
Your team ships an arbitrarily 10 points per sprint by doing what they think is right. The same team could ship an arbitrarily 20 points per week. 10 is the _true_ cost of building a healthy system. There is not a lot more to do for good team, honestly, at that point. Management can't say anything

This sort of thing is only useful for managers who don't understand what is going on. Since they are unable to look at code and understand it, 'points' give them a semi-opaque substitute.

If management trusts the team, it is not necessary.

Re:Why I'm not a big fan of Scrum by patothon on Monday August 08, 2016 @02:10PM (#12249720)
I guess if you understand what is going on as a manager, then you might prefer the 10 points team?

I know I do.

Re:Why I'm not a big fan of Scrum by ktRolster on Monday August 08, 2016 @02:15PM (#12249756)
If you understand what is going on, you will get rid of points altogether, and look at the git log from time to time.

If you are a leader, and not just a manager, you will help your programmers improve their skill, so over time you spend less and less time managing them. Your programmers will appreciate it because with greater self-management comes greater happiness and job satisfaction.

Re:Why I'm not a big fan of Scrum by DougWebb on Monday August 08, 2016 @03:05PM (#12250106)
The points are (also) an estimating mechanism. They let you estimate a new task in points (effort measurement) instead of hours (time measurement), and then use history to predict a likely timeframe based on your typical rate.

The extra layer of indirection helps to account for uncertainties in the task, imprecision in the estimate, and chaos (in the scientific sense) in how long individual tasks take relative to aggregated historical metrics.

Re:Why I'm not a big fan of Scrum by ktRolster on Monday August 08, 2016 @03:31PM (#12250293)
That's surely worth something, but it's easier to think of estimates as a 90% outer bound: "I am 90% sure that the task will be completed by date X." Uncertainty can be incorporated, and you don't need to learn a new conversion factor from time to points.
Re:Why I'm not a big fan of Scrum by DougWebb on Monday August 08, 2016 @04:21PM (#12250600)
That doesn't work when you can't predict what other tasks might interrupt you between now and date X. That's why estimating in units of effort is much more reliable than units of time.

The drawback to units of effort is that estimates eventually bubble up to non-technical people who don't discern the difference between effort and time, and for most projects there are going to be some time-based constraints on the schedule.

Re:Why I'm not a big fan of Scrum by ktRolster on Monday August 08, 2016 @08:17PM (#12251707)
That doesn't work when you can't predict what other tasks might interrupt you between now and date X

You can still take a probabilistic approach to tasks that might interrupt you.

Re:Why I'm not a big fan of Scrum by patothon on Monday August 08, 2016 @02:30PM (#12249855)
Totally. Some teams want the points though So I let them have it. But I just set the principles I explained above for the points to have an actual meaning.
Re:Why I'm not a big fan of Scrum by tomelders on Monday August 08, 2016 @07:39AM (#12246913)
I leave my current role in just under two weeks for the very reason you describe. I'm tired of being the "difficult dev" that everyone has grown to hate. Let them launch. Let it fail. Let's see who the arsehole is then.
Re:Why I'm not a big fan of Scrum by taneq on Monday August 08, 2016 @07:56AM (#12246999)
You, because the moment you leave you become that-guy-who-we-can-safely-blame.

Mostly joking but plenty of places do work like that.

Re:Why I'm not a big fan of Scrum by mgkimsal on Monday August 08, 2016 @08:12AM (#12247073)
Yes, they'll blame him. It won't make sense for the most part, but it'll still happen. Probably largely things like "it only tomelders had worked with us more instead of being 'difficult', we wouldn't be in this mess", even if the 'mess' is precisely what he was advocating people work on before he left...
Re:Why I'm not a big fan of Scrum by Ntrails on Monday August 08, 2016 @08:46AM (#12247266)
I will always blame whoever most recently left for everything. The rain, the chair being broken, the mouldy cream cheese in the fridge.

No jokes. It's Brads fault.

Re:Why I'm not a big fan of Scrum by JustSomeNobody on Monday August 08, 2016 @08:24AM (#12247137)
It will indeed be his fault. He set them up for failure and left, they'll say.
Re:Why I'm not a big fan of Scrum by Bartweiss on Monday August 08, 2016 @12:30PM (#12248969)
Isn't there a name for this pattern?

I swear I remember reading a piece on how having a team member leave can be good for cohesion and efficiency, because everyone is free to vent about old, bad decisions without targeting anyone still at the company. I think it was part of a story about a team clearing their technical debt by convincing a reluctant manager that they needed to undo the last guy's mistakes.

Re:Why I'm not a big fan of Scrum by jorge-fundido on Monday August 08, 2016 @01:32PM (#12249426)
"Blame Canada". PM: "We can't blame Canada for missing our targets 4 sprints in a row."
Re:Why I'm not a big fan of Scrum by xorblurb on Monday August 08, 2016 @01:40PM (#12249496)
And in a way it's saner than if you blamed over and over some people who still work 5m from you, even if they deserve it; and we all have stories about that kind of people.

You often needs to be more subtile with them (x) than blatantly calling on their bullshit every time...

(x): I mean to try to influence them so they progress so your life is better, not to shit on them

Re:Why I'm not a big fan of Scrum by thackerhacker on Monday August 08, 2016 @07:59AM (#12247011)
It's a long time since I've had to deal with "strict" Scrummers. But I do remember being utterly baffled as to the insistence on user features being ready by the end of a sprint, even for quite complex, technical components.

Why can't we make some sub-component this sprint then the UI bit the next?

I tried various ways of reframing it such that the developer of the UI be the "user" but it didn't wash.

Re:Why I'm not a big fan of Scrum by ozmbie on Monday August 08, 2016 @09:37AM (#12247594)
Because that two weeks you spent writing excellent code is mostly useless unless you have a way to get feedback on it. As a customer, you've given me no value.

What if you finally hook up UI to the sub-component and the customer/stakeholder decides they don't like any of it? You could have known about it earlier.

Re:Why I'm not a big fan of Scrum by redler on Monday August 08, 2016 @11:46AM (#12248649)
The problem with this is that it imposes a membrane on the process that is only permeable to work that contains a shippable piece of user-facing software. It presupposes that all work can be divided into such pieces. And since that's not true, it leads to contorted stories to squeeze necessary work through that membrane.
Re:Why I'm not a big fan of Scrum by ozmbie on Monday August 08, 2016 @06:20PM (#12251243)
I agree that sprint lengths can be arbitrary and counter-productive to developing good software.

I think it's important to understand that the sprint "membrane" is not designed to help developers. It's designed as a compromise between developers and their managers.

Developers want to work uninterrupted and perfect their work before releasing it, and managers want working software quickly and like to interrupt developers and change courses frequently. Sprints are an attempt to find a middle ground, but it's not always ideal.

Re:Why I'm not a big fan of Scrum by abritinthebay on Monday August 08, 2016 @02:30PM (#12249859)
> It presupposes that all work can be divided into such pieces.

No, it states the reasonable conclusion that all valuable features can be broken down into such (because otherwise if it adds no value to the product).

There are also Scrum tasks around Research, Tech Debt, etc that are perfectly fine to create and work on but they have an affect on your overall time to build new features and that's ok. Because it needs to be done, so they'll get prioritized accordingly.

Re:Why I'm not a big fan of Scrum by redler on Tuesday August 09, 2016 @12:06AM (#12252555)
You italicized "valuable features" and I understand why, but I think the trouble spot is actually the word "all"; your parenthetical about adding no value merely begs the question. I'd argue that, indeed, some valuable features can be organically broken down into two-week user-facing deliverables, but certainly not all and probably not even most. There's nothing magical about being able to partition a deliverable into a sprint's time frame that, by such distinction alone, makes it valuable versus valueless.

Systems like scrum try to wrangle into a manageable bolus a process that -- if we're to make good softare -- necessarily includes creativity, inspiration, and the traveling of paths yet unseen. It's like writing a novel and having two-week deliverables like "complete the arc of the Alice character", versus "write approximately 100 pages". It's not valueless to write 100 pages, despite not finishing the Alice section, and perhaps specifically because we discover that Alice's emerging story turns out to intersect perfectly with what we want to do with the Bob arc later on.

So there's writing and engineering and lines of code versus plotting and architecture and inspiration. We need all of it, right? Does everything that's not a "valuable feature" have to be shunted into the cul de sac of a research spike, doomed to be frowned upon by the management for whom the system otherwise provides the sheen of predictable velocity? Does the critical work of "dreaming" of what to do at both macro and micro levels become a casualty of the banal necessity of marching equal-sized boluses through the development tract?

I'm making a florid point, but to me this feels like the essential tension.

Re:Why I'm not a big fan of Scrum by abritinthebay on Thursday August 11, 2016 @03:02PM (#12270800)
> but certainly not all* and probably not even most.*

Yet to find any that can't. I've yet to hear of any either. Usually that's a problem with the people trying to break things down not being used to modeling things differently - not the process. It's pretty common.

I'd love to hear some examples tbh.

> There's nothing magical about being able to partition a deliverable into a sprint's time frame that, by such distinction alone, makes it valuable versus valueless.

Of course not! The point is not that the time-boxing makes it valuable, I hope I didn't imply that, it's that all features that have value should be specific enough to be able to be broken down. If something is too vague it's not a valuable feature because at that point is just pie in the sky spitballing. That's what requirements and grooming is for - to identify what needs to be broken down, expanded on, or specced out better by the Product Owner.

> It's like writing a novel and having two-week deliverables like "complete the arc of the Alice character", versus "write approximately 100 pages".

That would be awful Scrum process. Also the Product Owner is the Sprint Team in a novel but lets pretend they are two separate people for this: here's how that should work in a Scrum system...

- Story: "complete the arc of the Alice character"

- Feedback: Too vague. What IS the arc? What perspective should it be from? Lots of questions, needs to be broken down.

Next, after the product owner has worked out that we're going to hit these beats in a 3 act structure.

- Story: "complete Alice's arc for Act One, with exposition introducing her and the other characters, ending on the inciting incident for the main plot"

- Feedback: Better, but this is really 3 things - the introduction of Alice, the intro of the other characters, and the inciting incident. You should split those up.

Next, the PO has split this up into those three Stories and presents the first one...

- Story: "We need to introduce Alice so the audience can start to get to know her."

- Feedback: Great, this seems low complexity and simple. We have requirements for her backstory? Ok, great, lets work with that. Seems like a Complexity 2 Story.

Then, when Sprint Planning...

- Scrum Master (not PO): "Ok so we were planning on getting this Alice introduction done this sprint, we still ok with that?"

- Everyone: Yup!

- Scrum Master: Ok, lets break this down into tasks of things we want to cover then.."

And then that part of the story gets written. Obviously it's an odd metaphor, but that's kind of how many (not all, at all) professional authors break down a lot of their writing process anyhow. Some are more freeform of course, but many plan a lot too.

The point is - that just because you have a planning step doesn't remove the creative process, it helps you plan better for work. That's all.

Scrum doesn't magically change how you code or what you code, it's just a planning and change management tool that emphasizes incremental steps.

Re:Why I'm not a big fan of Scrum by TeMPOraL on Monday August 08, 2016 @09:44AM (#12247658)
That's why I sometimes say at my workplace that we should make our projects in Flash. Faster to make an interactive UI this way and get the approval of the management/customer, no time wasted on useless things like having the program actually work in an efficient, useful and secure way.
Re:Why I'm not a big fan of Scrum by protomyth on Monday August 08, 2016 @05:19PM (#12250946)
I knew some folks in the 90's that prototyped in Shockwave. They did UI and animated uses cases. I was impressed by how quick people got their blob-type people animated use cases that were basically little cartoons. Seemed like way too much work, but I guess it worked for them.
Re:Why I'm not a big fan of Scrum by TeMPOraL on Monday August 08, 2016 @07:50PM (#12251606)
I've learned the hard way just how effective such prototyping tools can be if you only care about... prototypes. Or the visual stuff. Seeing a designer whipping up a running example in 15 minutes in Construct2 that was equivalent to what me and two of my friends spent last 8 hours coding has taught me to respect those tools, at least in particular use cases.

And my point is, if we're focusing only on short-term client-recognizable value, we may as well just make shiny prototypes. Who cares about the pesky internals anyway.

Re:Why I'm not a big fan of Scrum by protomyth on Monday August 08, 2016 @11:20PM (#12252380)
To be fair to them, they were hella good C++ programmers and used Shockwave to prototype and lock down the business requirements. You can do an amazing amount of specification like that. It was basically CRC cards put to animation as people and things interacting.

They provided quite a bit of short and long term value by being better at giving clients an understanding of what they were actually getting. They cared about the internals and making sure their clients understood the logic the internals would use.

If I was skilled in some animation tool like they were I would do the same.

Re:Why I'm not a big fan of Scrum by marpstar on Monday August 08, 2016 @10:29AM (#12248025)
...Flash?
Re:Why I'm not a big fan of Scrum by TeMPOraL on Monday August 08, 2016 @10:38AM (#12248107)
Yeah, that thingie in which you draw stuff, sprinkle them with a script or two, and with a few click you get something that can be run or embedded in a webpage. The thing HTML 5 supposedly replaced.
Re:Why I'm not a big fan of Scrum by dozzie on Monday August 08, 2016 @10:03AM (#12247805)
> As a customer, you've given me no value.

Erm. But it's you who is the customer in this scenario, not him? Or am I missing something?

Re:Why I'm not a big fan of Scrum by thackerhacker on Monday August 08, 2016 @10:13AM (#12247889)
He's saying that eventually when your feature surfaces as a UI the customer may not like it.

To which I have 2 responses:

1. not all features need a UI to be useful

2. this also demonstrates the infantilising nature of scrum where no developers can be trusted to think deeply, talk to stakeholders and otherwise do the right thing in a fully-rounded way but must just follow the exact instructions expressed

Re:Why I'm not a big fan of Scrum by ozmbie on Monday August 08, 2016 @05:55PM (#12251141)
I mentioned UI because of the parent comment (about hooking UI up to a sub-component).

The core idea I was trying to get across is that until a feature is working and in front of a customer (or stakeholder), it's essentially in limbo because you don't know if you've built what they wanted. Maybe there was a miscommunication, maybe they find the feature confusing, maybe they've changed their mind. The goal is to get feedback as soon as reasonably possible.

eg: A stakeholder (or customer) requests feature X, and everyone agrees it's a good idea and we should to work on it right away. The dev team could spend 2-4 weeks writing excellent behind-the-scenes code that's not hooked up to anything, or you could spend 2-4 weeks on holiday. Either way, you've given stakeholder the same thing: No new feature.

If you're confident that you know exactly what it is you want to build then you don't need Agile, scrum or sprints. Scrum isn't supposed to be waterfall with arbitrary reviews every 2 weeks.

Re:Why I'm not a big fan of Scrum by dozzie on Monday August 08, 2016 @03:27PM (#12250279)
But he said:

> As a customer, you've given me no value.

Meaning:

> You, being a customer, have given me no value.

This is what I don't understand.

Re:Why I'm not a big fan of Scrum by jholman on Tuesday August 09, 2016 @07:03AM (#12253720)
He said

> As a customer, you've given me no value.

Meaning:

> [From my hypothetical perspective] as a customer, you've given me no value.

Or more concisely:

> [Speaking] as a customer...

Re:Why I'm not a big fan of Scrum by dozzie on Tuesday August 09, 2016 @08:41AM (#12254080)
I'm not sure this is how the grammar works...
Re:Why I'm not a big fan of Scrum by bmurphy1976 on Monday August 08, 2016 @10:37AM (#12248097)
Customer is a poor term. It should be stakeholders. Sometimes the stakeholders aren't "customers" per se, they could be other parts of the organisation for example. I'd consider my CTO a stakeholder and I'm pretty sure he's interested in the value of fixes for a security audit or working database backups even though those don't necessarily have a nice demonstrable UI.
Re:Why I'm not a big fan of Scrum by abritinthebay on Monday August 08, 2016 @02:26PM (#12249824)
> I tried various ways of reframing it such that the developer of the UI be the "user" but it didn't wash.

Are you surprised? The developer isn't the user of the UI, product wise, so no wonder it didn't get very far.

The trick in this case is to break the story down. So the original story isn't do-able in one sprint? Ok, so what is actually the MVP of that Story? What's the first block that builds the overall feature? Take a 5 point Story and make it three 2 point Stories or something. That's what the refinement step is for in Scrum.

Unless you're doing abnormally short sprints there should be some part of that Story that can be abstracted into a smaller Story that fits into a sprint.

Re:Why I'm not a big fan of Scrum by lmm on Monday August 08, 2016 @08:12AM (#12247076)
> Why can't we make some sub-component this sprint then the UI bit the next?

Because that's how you get bad UI. The user-facing design needs to drive the API interface, not the other way around.

Re:Why I'm not a big fan of Scrum by gmarx on Monday August 08, 2016 @12:44PM (#12249062)
I disagree. It varies from situation to situation but I would argue in my domain at least (healthcare) this is how you get bad data models
Re:Why I'm not a big fan of Scrum by fsloth on Monday August 08, 2016 @08:49AM (#12247286)
"The user-facing design needs to drive the API interface, not the other way around."

I don't see how this need would nullify the ability to modularize code.

Re:Why I'm not a big fan of Scrum by lmm on Monday August 08, 2016 @09:11AM (#12247415)
Modularize by functionality, not by layer. Start with a simple end-to-end path and grow outwards, rather than trying to go top-down or bottom-up, and don't split into distinct layers until you're actually deriving value from doing so. Writing code when you don't have the use case yet is always a bad idea.
Re:Why I'm not a big fan of Scrum by Udik on Monday August 08, 2016 @09:45AM (#12247672)
Yep. And then at the third sprint into this path you realize that the way the backend has been built during the first two sprints makes it impossible to deliver some essential or just very desirable feature that nobody took in consideration because it was outside the scope of the first two sprints. Seen it happen multiple times.
Re:Why I'm not a big fan of Scrum by lmm on Monday August 08, 2016 @11:21AM (#12248455)
That's the opposite of my experience. It's always the extra layer that was added for some planned feature that we never actually implemented in the end that gets in the way.
Re:Why I'm not a big fan of Scrum by goalieca on Monday August 08, 2016 @09:55AM (#12247744)
I disagree. This is how you end up with messy code that needs constant refactoring. Making time to come up with a composable design shouldn't be that difficult. It usually isn't.
Re:Why I'm not a big fan of Scrum by abritinthebay on Monday August 08, 2016 @02:27PM (#12249833)
All code should be constantly refactored. This way your code gets refactored as the design changes (which... it will) rather than having to shoehorn an architecture that worked great originally into a set or requirements that have moved on.
Re:Why I'm not a big fan of Scrum by tener on Monday August 08, 2016 @08:31AM (#12247176)
Not true. If you have design ready before the implementation starts (as you should unless it is very simple) then you are free to implementation things separately. Just have the interface well specified.
Re:Why I'm not a big fan of Scrum by beerwulf on Monday August 08, 2016 @08:50AM (#12247290)
Sounds like you've never worked in a shop where they think "agile" == "no need to plan ahead"
Re:Why I'm not a big fan of Scrum by tener on Monday August 08, 2016 @02:35PM (#12249897)
This is sad, but my point still holds. Perhaps being honest with oneself about real tasks that need to be done will help. Planning the architecture/feature, doing proof of concept etc. are all valid tasks even if they don't bring immediate business values. If you claim that you can only do business features without doing any exploratory work then you are effectively claiming to have an oracle giving you perfect solutions out of the blue. In which case you should stop whatever you are trying to do and start selling the services of your oracle.
Re:Why I'm not a big fan of Scrum by matthewmacleod on Monday August 08, 2016 @08:42AM (#12247240)
Speaking from a UI developer perspective, this never works :) But YMMV, I suppose…
Re:Why I'm not a big fan of Scrum by tener on Monday August 08, 2016 @02:41PM (#12249931)
We always do a brainstorming before implementing any serious feature / change. Once we have the initial design business gets involved (if we can get their attention...). The results usually works without needing any drastic changes, which is still better than no planning at all. It does require involvement from a number of parties though.
Re:Why I'm not a big fan of Scrum by lmm on Monday August 08, 2016 @08:55AM (#12247327)
Design is better when it's informed by implementation, IME. The only complete specification is working code; if you accept something lower-fidelity then it's very easy to miss ambiguities.
Re:Why I'm not a big fan of Scrum by tener on Monday August 08, 2016 @02:43PM (#12249956)
Even code have bugs so it's not perfect. Your design can incorporate high level algorithm to be implemented, ins/outs, or whatever else high level constraints are most applicable to your domain.
Re:Why I'm not a big fan of Scrum by st3v3r on Monday August 08, 2016 @02:11PM (#12249730)
But if you design things ahead of time, then you're not "agile"!
Re:Why I'm not a big fan of Scrum by tener on Monday August 08, 2016 @02:42PM (#12249939)
See my other comment regarding oracle: https://news.ycombinator.com/item?id=12249897
Re:Why I'm not a big fan of Scrum by xorblurb on Monday August 08, 2016 @01:43PM (#12249521)
In your church, maybe.

In a country where logic reigns, it depends.

Re:Why I'm not a big fan of Scrum by bighi on Monday August 08, 2016 @04:02PM (#12250498)
Imaginary countries don't count.

;)

Re:Why I'm not a big fan of Scrum by taneq on Monday August 08, 2016 @09:36PM (#12251985)
Depends what you're building. Which leads us to the worst (meta-)aspect of Agile/Scrum these days, which is that it's the industry's current favourite hammer and so it gets used to bash every single problem. Now, hammers are quite versatile, but you have to know when to bash, when to use the claw, when to lever or just nudge things instead of swinging.

The moment you start getting dogmatic about your process is the moment your decisions start being driven by something other than your actual needs at hand. And that's the moment when you start to produce a bad product.

Re:Why I'm not a big fan of Scrum by afroisalreadyin on Monday August 08, 2016 @08:13AM (#12247084)
Author of the post here, thanks for your comment. As you said, the fact that you have to stick out your neck and fight for code quality is very annoying, and after some time, one just stops doing it, and starts flowing with the "add the one more line of crap to get things working and collect the points".
Re:Why I'm not a big fan of Scrum by discreteevent on Monday August 08, 2016 @08:46AM (#12247264)
"Lean" is supposed to address quality and habitability more. 2 of the 7 tenets of lean focus on it:

Build Quality In

Optimize the Whole

I've never practiced it and my only exposure has been reading some of the book "Lean Architecture". But it certainly seems like an improvement over Scrum which seems blind to some of the most critical things in developing complex innovative systems. In fact I'm convinced that Scrum was designed to work with basic information systems where a feature consists of essentially adding a new data entry form or report for a database (e.g. a lot of web stuff)

Re:Why I'm not a big fan of Scrum by Spooky23 on Monday August 08, 2016 @09:35AM (#12247578)
Remember that "Lean" (SCRUM is really a subset of those practices) is at it's core a manufacturing process. Manufacturing isn't engineering. The author of the original post captured this very well:

> ...one can claim that this is not the job of Scrum, which is a software management methodology, and not a software engineering methodology, that it's only concerned with organizing the teams' time and workload

A manufacturing process can only drive quality if both the primitives and end system have gone through some sort of engineering process. Web developers love this stuff because they have components, frameworks and clients where the engineering details are taken care of in MANY scenarios.

Using a contrived scenario involving LEGO -- you cannot expect kids and parents to design new LEGO parts. The components are designed and engineered to work together in a completely different context. Carrying this further, if you want kids to assemble a consistent, specific artifact (Say a Star Wars X-Wing fighter), someone at LEGO needs to design that and produce documentation. Designing on the fly with sprints ("ok, kids, today figure out how to make a wing") isn't going to be a productive exercise.

Most SCRUM projects that I have personally seen fail are projects where "agile" is a codeword for "we didn't think this through, so we'll figure it out as we go". Then the "sprints" become a real joke as the team repeatedly runs into a wall.

Re:Why I'm not a big fan of Scrum by afroisalreadyin on Monday August 08, 2016 @09:44AM (#12247665)
That book appears to be very interesting, I'll definitely have a look. Thanks for the tip.
Re:Why I'm not a big fan of Scrum by shepbook on Monday August 08, 2016 @08:24AM (#12247136)
I feel much the same way as much of what you've said in this post. I'm curious what you think of things like the #NoEstimates camp that removes the ambiguity and "gut check" nature of things like points or even time estimates?
Re:Why I'm not a big fan of Scrum by afroisalreadyin on Monday August 08, 2016 @08:54AM (#12247319)
I read the first chapter of the no estimates book, and have to admit that I found it weak on arguments and poorly written. I think there is real value into doing software estimations if you take them seriously, even using story points, but there must be better ways of using those estimates. One really interesting way of doing this is the Monte Carlo estimate method I linked to in the blog post. Would love to try that sometime, and see how it works out.
Re:Why I'm not a big fan of Scrum by galleman on Tuesday August 09, 2016 @12:19PM (#12255657)
The notion that the business can make decision in the presence of uncertainty is the basis of No Estimates. As a participant in another accelerator our funding sources would find that laughable at best and toss us out the cohort at worst.
Re:Why I'm not a big fan of Scrum by deejbee on Monday August 08, 2016 @08:01AM (#12247018)
This sounds like more of an issue with technical debt management. I'm much more of a proponent of Kanban, whenever possible, so in this case if a user story requires a refactor or architectural change then that's just fine. Also regular code reviews to eliminate hacking and sanity checking automated tests shouldn't be made optional, they should be actively encouraged by the team leads and dev manager.
Re:Why I'm not a big fan of Scrum by Noseshine on Monday August 08, 2016 @08:54AM (#12247318)

    >  if a user story requires a refactor or architectural change then that's just fine
Those clear cases are not the problem since they are... clear. There is a lot of need for refactoring that arises only slowly and not through one feature. It's more like the boiling frog thing (which by the way is a bogus story but I still use it nevertheless because everybody understands the point). So a problem is you can never really justify the refactoring effort using one specific new feature. It's like partial vs. full cost accounting, sometimes you just have things you can't break down but it still needs to be done (paid). Which makes this a real problem for organizations who don't have the accounting set up for this. In my experience especially large firms may have teams that get their budget "per feature", so even the best manager can't solve that problem - the next (management) layer above doesn't care though because your little software team is too small to get them to laboriously change the accounting process and the SAP system.
Re:Why I'm not a big fan of Scrum by specialist on Monday August 08, 2016 @08:53AM (#12247315)
Kanban is the software development equivalent of the Concentration (Memory Match) card game.

https://en.wikipedia.org/wiki/Concentration_(game)

As though a useful, usable product design (architecture) could be divined thru piecemeal revelation.

Re:Why I'm not a big fan of Scrum by crdoconnor on Monday August 08, 2016 @08:07AM (#12247046)
One amendment I always wanted to make was to have a "technical debt dial". You could stick it on the wall next to the scrum board.

The debt dial should be from 0% (spend all the time refactoring) to 100% (spend zero time refactoring, get it out at all costs).

Management should have complete control over the dial. Developers should have control over what kind of refactoring they do (ideally the retro should have a question "what debt/tooling issues caused you the most pain this sprint? and a parallel track for debt/tooling stories").

Re:Why I'm not a big fan of Scrum by Udik on Monday August 08, 2016 @09:57AM (#12247755)
I often have the impression that the term "technical debt" is just an euphemism to avoid admitting that someone in the team has produced poorly thought and poorly written code.

I'm not sure I ever found myself in the position of writing bad code just for the sake of speed - I surely wrote tons of bad code because I didn't know how to do it better, or because I didn't have the requirements clear from the start, or because of bad design and planning. But to get a feature out quicker, no. If anything, it seems to me that writing bad code requires more time than writing clean and elegant code.

In the end, "technical debt" becomes a way to shift the blame from your own (the team's) inadequacy at planning, designing and developing, towards supposed time constraints that always lie outside of the team's responsibility.

Re:Why I'm not a big fan of Scrum by nilkn on Monday August 08, 2016 @10:32AM (#12248048)
I have to disagree with this comment. Technical debt is sometimes the result of just one lone cowboy coder, but even then there's some responsibility across the team because that means his or her code passed all reviews, i.e., nobody took ownership for the overall team's code quality and vetoed the bad code.

Time constraints can certainly be relevant too. It's not always an artificial shift of blame. For instance, time constraints could be why the code passed review to begin with.

And some programmers certainly do write worse code when they have to do it quickly. Typically, the code itself doesn't look all that bad in a vacuum, but it presents problems months down the line when a new feature needs to be added or an existing one changed in a non-trivial way. There was little forethought in its design.

Or, let's just look at the ways you said you might write bad code:

> I surely wrote tons of bad code because I didn't know how to do it better, or because I didn't have the requirements clear from the start, or because of bad design and planning

In other words, these things can cause you to write bad code:

1. You just didn't know better.

2. Unclear requirements at the start.

3. Bad design and planning.

In (1), you might realize after writing some code that you didn't quite know what you were doing and you should refactor it, but you're now under pressure from management to just get it out. Oops, no time to refactor. Now code that you know is bad is going into production, and it'll bite you in six months.

For (2), the reason the requirements weren't clear is because not enough time was spent by management/product owners/designers on clarifying said requirements.

For (3), it's the same thing -- bad planning is often the result of time constraints (notably, time constraints which may not be visible to you as a rank and file programmer).

Re:Why I'm not a big fan of Scrum by Udik on Monday August 08, 2016 @12:36PM (#12249001)
but it presents problems months down the line when a new feature needs to be added or an existing one changed in a non-trivial way.

I think I have yet to see any software to which this doesn't apply sooner or later. While the whole point of "technical debt" is that it is something you're supposed to knowingly acquire because of time constraints. You're basically saying "we knew it was wrong, but they forced us to do it that way". While to me, most of the times, the truth is that you really didn't know. Yes, you coded in a hurry, but there is always a time constraint of some kind so that's no excuse. Somebody else in the same time would have done a better job.

As for my points: if I realize I didn't know what I was doing, I always refactor the code. Committing code that you know to be conceptually wrong is just sloppy. And if I am under pressure by the management is because I spent time developing without understanding what I was doing; a better developer would have gotten it right at the first try, and there would be no technical debt.

If the managers/ product owners didn't produce clear requirements, it's not a technical debt, it's a sloppy job on their part.

If the planning was wrong, that's a sloppy job on the part of who had to do it. Responsibilities should be found and action should be taken. Saying "ah yes you know, we were under pressure so we (kind of naturally) accumulated this technical debt" is just a way to save everybody's face.

Re:Why I'm not a big fan of Scrum by nilkn on Monday August 08, 2016 @01:04PM (#12249215)
> And if I am under pressure by the management is because I spent time developing without understanding what I was doing; a better developer would have gotten it right at the first try, and there would be no technical debt.

While this reasoning is probably not technically wrong, I'm not sure if it's relevant to the real world.

You can always make an argument of form "there exists a developer who could have got this feature right on the first try, with very little time spent." This simply does not matter when you do not happen to have that developer on your team right at the moment. The nature of the work is that you will work on a variety of things, and you won't necessarily be the best in the world at every individual thing. You're inevitably going to encounter work that's challenging enough for you where you don't get it perfectly right on your first try.

> If the managers/ product owners didn't produce clear requirements, it's not a technical debt, it's a sloppy job on their part.

It's a sloppy job on their part, induced by time pressure, which produces technical debt. I feel like you're just playing with definitions here to avoid admitting that technical debt can come from poorly managed time pressure.

> if I realize I didn't know what I was doing, I always refactor the code.

All that tells me is that you've never been under a lot of time pressure. That's not a bad thing. It most likely means the management at your companies have been competent. But it doesn't mean that technical debt does not exist or cannot be induced from time pressure in other companies.

Re:Why I'm not a big fan of Scrum by Udik on Monday August 08, 2016 @01:51PM (#12249577)
I guess that what I'm trying to say - and that got clearer to me while replying to other comments in this thread- is that it feels we're using the term "technical debt" as a way to avoid talking about personal skills or lack thereof, and to avoid admitting our or other people's faults. If I say that we need one more week of work on something because of technical debt due to the exceptional circumstances is one thing; if I say that it is because one of my colleagues didn't do his or her job properly, it's different. Remember that the business might have no clue of how long or difficult some tasks are and judge them only by the amount of work required. So a series of bad design decisions and consequent technical debt can give the impression of a very hard task on which everybody is working skillfully, while in fact it's an easy task with somebody that doesn't know how to do his job.

As for your other points: maybe one of my team members produces consistently more technical debt than the others. Is it still technical debt? Manager or designers can be the source of time pressure for those down in the chain, because bad planning or decisions, made in absence of time pressure, can force others to work under pressure. Again, "technical debt" masks the real problem. I might not have worked in extremely high pressure environments - but I've surely worked in teams where we were leaving the office at ten or eleven pm every night for months on end just because demented design decisions had been made by the much respected solution architect.

Re:Why I'm not a big fan of Scrum by crdoconnor on Tuesday August 09, 2016 @06:42AM (#12253672)
>As for your other points: maybe one of my team members produces consistently more technical debt than the others. Is it still technical debt?

???

Why wouldn't it be?

Creating lots of extra technical debt, in fact, is a defining feature of poorer developers.

Re:Why I'm not a big fan of Scrum by Udik on Tuesday August 09, 2016 @09:32AM (#12254334)
>>I often have the impression that the term "technical debt" is just an euphemism to avoid admitting that someone in the team has produced poorly thought and poorly written code

>Creating lots of extra technical debt, in fact, is a defining feature of poorer developers.

I think we agree then. It's just that "technical debt" makes it sound- to me at least- inevitable and impersonal, while it is possible (at least for substantial amounts of it) to ascribe it to specific people and to avoid it by hiring better people.

Re:Why I'm not a big fan of Scrum by crdoconnor on Monday August 08, 2016 @01:27PM (#12249390)
>And if I am under pressure by the management is because I spent time developing without understanding what I was doing; a better developer would have gotten it right at the first try, and there would be no technical debt.

This is possibly the most wrongheaded comment you've made.

1) There is no such thing as "no technical debt". It asymptotically trends to zero but never, ever gets there. If you think that you oe anybody else is the kind of developer who magically creates debt-free code all the time then you're deluded.

2) The "right first try" argument is wrong. You shouldn't even try to get it right first try - that's the whole point of red/green/refactor. You're supposed to get it working and then clean it up because prematurely 'cleaning up code' is an inefficient way to work.

It's not called red/green/refactor-if-you're-too-shit-to-get-it-right-first-try.

Re:Why I'm not a big fan of Scrum by Udik on Monday August 08, 2016 @01:59PM (#12249631)
Ok for your first point - although I'd argue that technical debt is something that usually asks to be repayed within months. A two year old technical debt is just an improvable software - that is, it didn't yet show problems serious enough as to call for a refactor at unchanged requirements.

As for your second point, what should I do? Try to get it wrong? To get it working how? We're not talking of premature optimization here, we're talking about understanding the requirements, understanding the tools, understanding the big picture, understanding your time constraints, and pulling out the best job you can.

Re:Why I'm not a big fan of Scrum by andrewingram on Monday August 08, 2016 @03:19PM (#12250217)
Simplest kind of technical debt:

1. I use a particular technique/abstraction/whatever to solve the problem, it solves the problem well.

2. Over time we solve other problems elsewhere. As we go, the bigger picture becomes clearer and we pick more suitable techniques/abstractions/whatevers as we go.

3. Eventually we have to solve a problem that interacts with the original problem, the newer techniques/abstractions/whatevers don't work cleanly with the new ones. So we have to make a choice:

a) Hack something together that solves the current problem without us having to touch much of the older code.

b) Rewrite the old code to match the newer technique/abstractions/whatevers.

c) Put down tools and thoroughly evaluate whether there's an even better technique/abstraction/whatever that solves the old problems and the new ones.

We all know that C would give us the best code, but it's also likely to mean we never get anything done because every new problem means reevaluating everything. B happens more often, but in reality we usually end up doing A due to various pressures.

At no point has bad code been written, but there's technical debt nonetheless.

Over time we become better at adopting patterns an architectures that allow for clearly defined boundaries and reduced cost of making mistakes, you still get technical debt (because just about anything you want to change can be considered technical debt), but it doesn't tend to cripple your ability to get things done.

Re:Why I'm not a big fan of Scrum by crdoconnor on Tuesday August 09, 2016 @05:11AM (#12253395)
>Ok for your first point - although I'd argue that technical debt is something that usually asks to be repayed within months. A two year old technical debt is just an improvable software - that is, it didn't yet show problems serious enough as to call for a refactor at unchanged requirements.

I've worked on five year old technical debt. It meant that bugs were far more common and fixes/new features took 10-15x as much effort as they would have otherwise.

It wasn't that it didn't 'call' for a refactor - it's that the team didn't respond to the problems by refactoring. They tried the following instead: heavy manual regression testing before release (once in two years), waterfalling, longer and longer feature/code freezes, keeping multiple branches around for different customers.

Managerial response was to hire additional mediocre developers, making the problem worse, but it wasn't like hiring better developers made developing immediately quicker and less risky. Paying that debt down to a reasonable level was impossible with mediocre developers would take ~36 months with good developers (also working on bugs/features).

>As for your second point, what should I do? Try to get it wrong? To get it working how?

You should do red->green->refactor.

After writing a failing test, your only priority should be to make the test pass. Not elegant. Just passing. Once it's passing, then make it elegant.

The reasons for this are twofold:

1) You're solving fewer problems at the same time. Something you want to avoid as much as possible as a developer is to have to juggle 40 different competing problems at the same time.

2) Refactoring-driven architectural decisions are ~95% of the time better decisions than those made during up-front design.

>We're not talking of premature optimization here

It's a closely related problem but it's not identical.

Re:Why I'm not a big fan of Scrum by lmm on Monday August 08, 2016 @11:31AM (#12248545)
What value comes of characterising it as "inadequacy"? I mean you may enjoy the self-flagellation but does it actually help plan or work effectively?

To my mind the "debt" metaphor captures important intuitions: it accumulates interest, slowly at first but rapidly if you have too much of it, it can look like it isn't a problem until it is, taking on more is often an easy way out of your current situation in the short term.

Re:Why I'm not a big fan of Scrum by crdoconnor on Monday August 08, 2016 @11:28AM (#12248509)
>I often have the impression that the term "technical debt" is just an euphemism to avoid admitting that someone in the team has produced poorly thought and poorly written code.

It's absolutely not that. Technical debt is a natural by-product of working even with the best coders. There's nobody out there who doesn't create it.

Better coders just produce it more slowly and clean it up more often.

>I'm not sure I ever found myself in the position of writing bad code just for the sake of speed

I could literally spend all of my time making code nicer and none at all developing features/fixing bugs. It's always a trade off between speed and quality.

Re:Why I'm not a big fan of Scrum by Udik on Monday August 08, 2016 @12:51PM (#12249120)
Of course. Some developers (or product owners, architects, managers) generate technical debt slower, some other generate it faster. Some generate a substantial amount of it for a task in which others would generate very little - in the same time frame. Then why don't we call it lack of skills? Sounds the same to me.
Re:Why I'm not a big fan of Scrum by crdoconnor on Monday August 08, 2016 @01:07PM (#12249242)
Because the same developer with the same skills can often ramp up technical debt to get a feature out in half an hour instead of a day, and there aren't any developers who haven't felt the pressure to do exactly that.

Ramping up technical debt isn't always about speed, either. It's sometimes about risk - it's often less risky in the short term to copy and paste a block of code than it is to change a block of code and risk breaking something else.

Re:Why I'm not a big fan of Scrum by Udik on Monday August 08, 2016 @02:08PM (#12249707)
True. The amount of technical debt produced is a function of the time constraints and the person skills. In turn, the time constraints can depend on the skills of other people in the organization at planning, designing, figuring out requirements, managing the team and the process, etc. Saying "ah sorry, we'll have to work one more week/ month on this because, you know, technical debt" is sweeping all these possible issues under one big carpet.
Re:Why I'm not a big fan of Scrum by crdoconnor on Tuesday August 09, 2016 @05:32AM (#12253446)
I don't see why. Technical debt is just a measure of how much crap there is in the code. It doesn't preclude having a discussion about how much that is to do with skills and how much that is to do with pressure/time constraints/existing technical debt.

The point of the dial is just to make the trade off between quality and speed that individual developers are making every day both explicit and management's responsibility.

It means if the dial is turned up to 100% management have no excuse for asking the question "why is our product a pile of crap?". It means also if the dial was at 60% for a year and a half the developers have no excuse for why the product is still riddled in technical debt, meaning that skills problems are distinguished from time constraints and managerial pressure comes with a cost attached.

Re:Why I'm not a big fan of Scrum by gmarx on Monday August 08, 2016 @12:55PM (#12249154)
I disagree. Even among those who routinely write good code (all of us in our own minds) the schedule tends to pressure you to solve the problem before you, the one in the story, without checking if anyone else has solved similar problems already. What tends to happen is you write your own solution instead of finding the similar solution and generalizing it. Then, after a year you have have a dozen related tasks performed in slightly different ways. If the underlying (e.g.) data structure change, now you need to alter each of the dozen different ways
Re:Why I'm not a big fan of Scrum by Udik on Monday August 08, 2016 @01:24PM (#12249361)
This sounds like a bad organization of the team, bad process or bad design. Clearly team members don't communicate enough, or groups of similar features have not been foreseen during the design phase, and the same code has been rewritten again and again by different people. This is not contingent "technical debt", this is a serious problem that needs to be addressed with changes in the process.
Re:Why I'm not a big fan of Scrum by gmarx on Monday August 08, 2016 @02:28PM (#12249839)
organization of the team and process? You mean the scrum process? Indeed, my point. Of course one can argue that no true scrum process would have such problems...
Re:Why I'm not a big fan of Scrum by Udik on Monday August 08, 2016 @02:48PM (#12249987)
Yes, totally agree with you. But then, why "technical debt"? No, there is something wrong here and this process needs to be changed. Somebody made the wrong decisions, at some level, and there is a very specific issue to be found, analyzed and solved.

And yes of course, as we all know scrum is by definition successful, and all the teams that fail are not following the true faith.

Re:Why I'm not a big fan of Scrum by JoeAltmaier on Monday August 08, 2016 @10:00AM (#12247786)
I see technical debt as being that code you haven't written yet. You just ignore the errors from misaligned data instead of writing the date sanitizer. You monitor and hand-reboot processes that leak instead of finding the leak/automating the reboot. and so on.
Re:Why I'm not a big fan of Scrum by new_hackers on Monday August 08, 2016 @10:25AM (#12247996)
I think the "speed" part is that once you realize it is bad code cause you didn't know how to do it better, you don't have the time to scrap it and start over.
Re:Why I'm not a big fan of Scrum by gearhart on Monday August 08, 2016 @08:34AM (#12247191)
When I read this I assumed you meant a dial that represents the current level of technical debt, rather than a dial that represents how much technical debt you're allowed to accrue.

The other interpretation might be a neat solution. Allow developers to indicate publicly what proportion of the time their last tasks took, they should have taken had there been no technical debt. It would handle the communication from developer into business-speak pretty effectively.

Re:Why I'm not a big fan of Scrum by ScottBurson on Monday August 08, 2016 @05:25PM (#12250990)
At the very least you need both dials! If you have only the one that management sets, saying how much time to spend refactoring, it will always be at 0. (Okay, they don't literally have to be dials, but there has to be some communication of the kind you describe, so management has some idea how much time is being lost.)
Re:Why I'm not a big fan of Scrum by crdoconnor on Tuesday August 09, 2016 @05:40AM (#12253471)
>At the very least you need both dials! If you have only the one that management sets, saying how much time to spend refactoring, it will always be at 0.

Management decisions are usually CYA based, and leaving the dial set at 0 both exposes them and gives developers a get out of jail free card.

i.e. leaving it at zero is suicide. That's the whole point of making it a trackable dial.

Probably what would happen in most cases is it would fluctuate between 30% during average times and 0% during crunch times.

Re:Why I'm not a big fan of Scrum by user5994461 on Monday August 08, 2016 @08:00PM (#12251649)
That seems utterly wrong to me.

I'd expect any manager worth is salt to put that at a 10% or 20% (basically anywhere NOT 0) and uses that number as a reminder to devs that part of the job description includes MAINTAINING the system in proper condition, not just piling up new stuff on top of the existing random stuff.

Same as a car needs regular maintenance, a dev project needs regular maintenance.

Re:Why I'm not a big fan of Scrum by daemin on Monday August 08, 2016 @09:22AM (#12247472)
One question I have is how does one actually objectively measure technical debt? I mean by anything more than a guess or intuition. Does every singleton/global variable count? Does every comment with a HACK count? What other factors contribute to technical debt, and by how much?
Re:Why I'm not a big fan of Scrum by crdoconnor on Monday August 08, 2016 @01:13PM (#12249288)
I've pondered this problem for a while and I think I narrowed it down to the following:

* Tight coupling (this would include global variables, among many other things)

* Lack of code cohesion

* Code duplication

* Code that doesn't fail fast (e.g. weak typing).

* Variable/class/method naming that is either not sufficiently disambiguated or is wrong.

* Lack of tools to run and debug code

* Lack of test coverage

Whenever I go looking for code to clean up this is what I keep an eye out for.

I'm pretty sure that each of these could be measured empirically somehow (I've read papers to that effect for a few), but we're not quite there yet in terms of tooling, or even in agreement over what technical debt actually is. Give it 5-10 years.

Re:Why I'm not a big fan of Scrum by lmm on Monday August 08, 2016 @11:38AM (#12248600)
There is no objective measure. Yesterday's good code is today's technical debt.

But at the same time there is definitely some underlying real quantity. Different developers may not agree on every single aspect, but they'll agree about the difference between a good codebase and a bad one, and it really does take longer to make changes to the bad ones.

So what can you do?

Re:Why I'm not a big fan of Scrum by new_hackers on Monday August 08, 2016 @10:28AM (#12248019)
I believe the technical debt could be measured as:

The time it takes to change code that is already written.

For instance, if you want feature N+1, but to do feature N+1 you need to change feature N, then the amount of time you spend changing feature N is the technical debt.

So when you are estimating, you could say: We need to refrob the whozzit to make it compatible with foo 2.0, then that work could be captured as technical debt.

Re:Why I'm not a big fan of Scrum by user5994461 on Monday August 08, 2016 @08:17PM (#12251709)
I do believe that this N+1 - N captures the idea well.

One issue though: If the requirements have changed, that is not a good metrics.

i.e. We did that theme blue for Iphone, now people wants it to be green AND on windows. It's not necessarily technical debt, it's cancelling everything we've done to make something else entirely (even though it may seem superficially similar).

If the requirements and/or features for N+1 ignore or counter the requirements/features from N, it's not necessary technical debt, it might be you've just got no idea what you're coding and you're running in circle.

Re:Why I'm not a big fan of Scrum by new_hackers on Tuesday August 09, 2016 @11:07AM (#12255018)
Agreed. One could argue that at time t+1, the product that meets the market need is the N+1 version. Therefore, even if feature N developed at time t was perfect for that time, it is still technical debt at time t+1. I could think of a lot of technical innovations that at their time were the perfect fit for the market, but at a future time become technical debt.

I think the point to take away is that software is just a tool, an artifact, and at the end of the day it just matters that it does what it is "supposed to do". However, civilization is dynamic, so we are constantly seeking to optimize an ever-changing potential function. So perhaps it is not the programmer that is running in circles, perhaps it is the market. So for the manager accounting for the technical debt, they must accept the change as a cost of doing business.

Re:Why I'm not a big fan of Scrum by daemin on Monday August 08, 2016 @11:10AM (#12248358)
That will mean Technical Debt is dependent on what features you want to implement as to how much code has to change to support it. Still makes it rather subjective and hand-wavy.
Re:Why I'm not a big fan of Scrum by douche on Monday August 08, 2016 @01:41PM (#12249507)
If the technical debt is in areas that you will very rarely go back into, then it could perhaps be considered low-interest, compared to technical debt in high-churn code paths.
Re:Why I'm not a big fan of Scrum by new_hackers on Tuesday August 09, 2016 @11:12AM (#12255074)
right, so the crux of the issue is that to understand how much technical debt you have, you must understand what the market wants, and what features you need to meet the demand. So I think it is extremely subjective. You could say "our product it perfect, it should never change". Thereby in itself you have accepted that all processes and information that create the product are also perfect, and therefore your technical debt is zero. You must pay nothing to achieve exactly where you want to be.

You could think of technical debt as the energy lost due to friction. It is the energy lost changing from one point to another in your domain space. Perhaps "technical friction" would be a better concept for software. However, that is even more hand-wavvy and harder to measure ;-)

Re:Why I'm not a big fan of Scrum by richardwhiuk on Monday August 08, 2016 @08:12AM (#12247074)
In my experience, you struggle to move that dial from 100%.
Re:Why I'm not a big fan of Scrum by crdoconnor on Monday August 08, 2016 @08:31AM (#12247174)
In my experience, once it becomes a tracked metric that can be used to destroy a manager's career you can bet the dial will start to move.
Re:Why I'm not a big fan of Scrum by st3v3r on Monday August 08, 2016 @03:07PM (#12250120)
Management is just going to leave it at 0% the whole time. Once in a great while, if you're lucky, you might get 5-10%
Re:Why I'm not a big fan of Scrum by mirekrusin on Monday August 08, 2016 @08:27AM (#12247155)
For most companies static 100% image would do for this dial.
Re:Why I'm not a big fan of Scrum by crdoconnor on Monday August 08, 2016 @08:32AM (#12247183)
Only if it's untracked. If it's tracked and the responsibility of management it'll go down.
Re:Why I'm not a big fan of Scrum by mgkimsal on Monday August 08, 2016 @08:22AM (#12247123)
I've been in situations like this, and when I've brought up techdebt issues, I get "YAGNI". I've tried to frame technical debt issues in terms of how it will impact future feature requests, performance, etc, and YAGNI is what normally comes back. Until... they actually NI. Then it's a hair on fire crisis. Fortunately have not been in that type of situation for years, but I know they still happen.
Re:Why I'm not a big fan of Scrum by WhitneyLand on Monday August 08, 2016 @10:09AM (#12247867)
For those that didn't know - "You aren't gonna need it" (acronym: YAGNI) is a principle of extreme programming (XP) that states a programmer should not add functionality until deemed necessary.
Re:Why I'm not a big fan of Scrum by mgkimsal on Monday August 08, 2016 @10:48AM (#12248205)
Sorry - thanks - was in a bit of a rush and forgot to add that.

"YAGNI" is... in general... not that useful when used by people who've never worked on a particular type of project, because, almost by definition, they don't what what they will and won't need.

And... defining "needs" is its own set of headache. Needed by who? I'll tell you what, we need to ensure we have a logging system in place that can alert folks, and we'll need the ability to view logs in production, and share access to those. Years ago I got "YAGNI" back on that, and months later... weird bugs that no one could reproduce, and the minimal logging in place was only accessible by one guy who was out of town for a week. But hey... we got those "rounded corners" to work in IE5 and IE6 with only an extra week of work - yay...

YAGNI is a good principle, but as with most ideas, you get problems when you introduce various types of people in to the mix. Someone who's never done a project type X should not be the one making YAGNI decisions when other people on the team have done multiple "project type X" before, and are trying to introduce basic requirements.

Re:Why I'm not a big fan of Scrum by abritinthebay on Monday August 08, 2016 @02:20PM (#12249791)
> the stories are always articulated in terms of user facing features

Reminder: the "User" doesn't have to be an external person to the team. It can be internal for tools, or a tech debt task for internal issues like the ones you mention.

Thinking Scrum is just about end/paying User stories is mistake #2 I see when people do Scrum (#1 is the classic "We're going to not actually do Scrum but call it Scrum" that leads to a lot of "Scrum doesn't work" articles itself).

Re:Why I'm not a big fan of Scrum by jroseattle on Monday August 08, 2016 @10:07AM (#12247847)
> Because the stories are always articulated in terms of user facing features they encourage developers to hack things together in the most expedient way possible and completely fail to capture the need to address cross cutting concerns, serious consideration of architecture, and refactoring.

This is one of our biggest challenges. Much of the work we're doing isn't confined just to a user feature, so square-peg-round-hole syndrome affects us a lot.