News for hackers. Stuff that matters.
Re:Why ‘your’ programmers just want to code by vvanders on Saturday March 10, 2018 @11:28AM (#16559059)
That sounds like poorly run scrum more than anything else. I can't count the number of times I've thrown an "investigation" task on the backlog that may or may not have panned out.

Scrum is more about keeping your fellow engineers informed on what they are working on so incompatible things rise quickly. It shouldn't be used as a tool for micro management but instead reviewed at the end of each sprint.

Re:Why ‘your’ programmers just want to code by overgard on Saturday March 10, 2018 @12:28PM (#16559307)
The problem with "investigation" tasks or "spikes" is that it still boils down to essentially having to ask permission to do something. I really think extreme one-sided work transparency and a culture where everything is measured and permission has to be sought to work on something is entirely antithetical to encouraging creativity. Innovation tends to come from playfulness, and having to schedule a Jira task with a project manager for every idea is going to have a chilling effect.
Re:Why ‘your’ programmers just want to code by goalieca on Saturday March 10, 2018 @12:38PM (#16559351)
You’ve hit my first main point of hatred against agile. It’s really a form of micromanaging in disguise. They sell it as developer empowerment but that’s just cognitive dissonance.
Re:Why ‘your’ programmers just want to code by YeGoblynQueenne on Saturday March 10, 2018 @02:07PM (#16559700)
That depends on the company. Some companies (in my experience) do engineer-only scrums where programmers can talk about their blockers and ask for advice from seniors; others do mixed scrums where the engineers are basically reporting their progress to the product manager or someone, and where often technical questions are discouraged.

I'd tend to think the latter are "doing it wrong", but then again, who am I to say? I just know I much preferred working for the companies who did it the former way.

Re:Why ‘your’ programmers just want to code by watwut on Saturday March 10, 2018 @03:41PM (#16560061)
This idea that only managers micromanage and fellow engineers never do that us one of biggest agile fallacies.

Also, need to ask question should not require whole team meeting.

Re:Why ‘your’ programmers just want to code by mmcnl on Saturday March 10, 2018 @03:12PM (#16559939)
This is not a problem of agile, it's a problem with the implementation of agile. A company that tends to micromanage that implements agile will use agile to micromanage. It's unavoidable.
Re:Why ‘your’ programmers just want to code by 0x445442 on Saturday March 10, 2018 @03:31PM (#16560004)
I've heard various forms of this response before but I'm always confused by it. If agile isn't the offending processes in question then what is agile.

And if the response is it's a verb not not a noun then it's really nothing but good hackers employing tried and true practices.

Re:Why ‘your’ programmers just want to code by scarface74 on Saturday March 10, 2018 @05:49PM (#16560570)
Anytime someone complains about agile and then a "true believer" defends it as "that's not agile", it reminds me of the "No True Scotsman"
Re:Why ‘your’ programmers just want to code by dasmoth on Sunday March 11, 2018 @08:52AM (#16562789)
Quite. I’m sure I’ve seen “no true scrummaster” used in the past to describe this form of debate.
Re:Why ‘your’ programmers just want to code by fjsolwmv on Saturday March 10, 2018 @03:37PM (#16560044)
Nothing in agile stops you from creating experimentation tasks or simply spending time on whatever you want. It just asks you to honestly be aware of how you spend time.
Re:Why ‘your’ programmers just want to code by overgard on Saturday March 10, 2018 @07:45PM (#16561001)
Well, I'm pretty well aware of how I spend my time. Agile serves no purpose for me in that regard. The point of agile is so that others can track how I spend my time. Whether that's reasonable and if/when that's a good idea is entirely about context; but much like quantum mechanics, observing behavior can change it (positively or negatively).
Re:Why ‘your’ programmers just want to code by solipsism on Saturday March 10, 2018 @01:18PM (#16559499)
I can't imagine taking up an investigation of any significant size (say, more than a day) that I don't mention to my team. And yes that means putting it on a board. This isn't asking for permission. It's making others aware. There's a good chance someone on my team has some valuable input. Or awareness of what time doing may affect what they choose to do somehow.

Granted, my team is small and close-knit. But the idea that keeping others informed of what you're doing is considered "asking permission" points to some serious pathology on your team.

And that pathology is not agile or scrum. We do scrum, and I'm sort of lukewarm about how much I like scrum. But whether we're doing scrum or something else, I am completely empowered to make my own decisions about my work. And I simultaneously value that the rest of my team keeps me informed of what they're doing. This is how we kick ass.

Re:Why ‘your’ programmers just want to code by zukzuk on Saturday March 10, 2018 @11:46AM (#16559144)
And this is exactly why "agile" has become a religion more than anything — if it's not working, it's because you're doing it wrong. You just need to agile harder.
Re:Why ‘your’ programmers just want to code by scarface74 on Saturday March 10, 2018 @12:20PM (#16559281)
I've never seen agile work with sprints. Things change too fast and usually there are unknowns. I have seen Kanban work because it takes into account the reality that priorities change, and estimates are never accurate.

I am also a big believer in hard short deadlines when it comes to doing releases. When the deadline comes, release what you have ready and put it behind a feature toggle if needed to do a phased rollout.

Re:Why ‘your’ programmers just want to code by Bahamut on Saturday March 10, 2018 @11:57AM (#16559205)
To be fair, it really does sound like bad management - management shouldn’t be blasting an individual during scrum. Management also shouldn’t care if other work gets done as long as the core commitments get finished. Good management shouldn’t hamstring you like that - engineering doesn’t work like that.

That is regardless of agile or whatever development methodology you use.

Re:Why ‘your’ programmers just want to code by TheCoelacanth on Saturday March 10, 2018 @04:42PM (#16560319)
Management really shouldn't even be participating in any of the scrum meetings other than the sprint review. All of the other meetings are supposed to be just for the team itself.
Re:Why ‘your’ programmers just want to code by vvanders on Saturday March 10, 2018 @11:57AM (#16559202)
Well, there are no absolutes in this industry, if there were then we all wouldn't have a job since it would just be paint by numbers.

If a process isn't getting you what you want then change it. Is it any wonder that repeating a broken process gets you broken results each time?

Re:Why ‘your’ programmers just want to code by koonsolo on Saturday March 10, 2018 @02:22PM (#16559757)
If it's not working, why isn't it addressed in the retrospective? If you have a proper retrospective, you can change anything, even going from scrum to kanban.
Re:Why ‘your’ programmers just want to code by mmcnl on Saturday March 10, 2018 @03:16PM (#16559954)
This is 100% true. Who is holding you back to address things if they aren't working? I've literally never in my professional life have encountered a situation where honest feedback wasn't appreciated.

If you encounter situations where you are being micromanaged, try to place yourself in the role of the one who is micromanaging and try to see his challenges. That person is just somebody who is trying do his best. No one wants to suck the joy and energy out of his or her colleagues.

Re:Why ‘your’ programmers just want to code by lliamander on Saturday March 10, 2018 @01:49PM (#16559639)
When I've done R&D in an agile setting, usually the research was done outside of the scrum process, and once that was done then the development would be done in a standard scrum methodology.

The reason you can't really apply "Agile" to research is that having a useful product at the end of each sprint is a central to Agile development but runs contrary to the purpose of research.

Now, you still need to manage your research process. You need to identify the specific research questions you need to answer, and you need to bound the time investment. But let's not try too hard to shoehorn a methodology primarily oriented towards IT consulting into every other domain.

Re:Why ‘your’ programmers just want to code by 0x445442 on Saturday March 10, 2018 @03:24PM (#16559977)
How many points did you give those tasks? We're the points agreed upon by the team? Did the team and the business agree to the tasks being included in the Sprint during Sprint planning?

It sounds like you created the tasks yourself and added them to the backlog mid-sprint. If that's what you did I'd be totally cool with it but I can tell you a lot of "agile shops" would blow a gasket over that.

Re:Why ‘your’ programmers just want to code by Retra on Saturday March 10, 2018 @11:55AM (#16559193)
There is very little you have to add to "keeping everyone informed of what you are doing" to end up at micromanagement.
Re:Why ‘your’ programmers just want to code by vvanders on Saturday March 10, 2018 @11:57AM (#16559208)
Notice I said engineers and not management or everyone, very small but important difference.
Re:Why ‘your’ programmers just want to code by overgard on Saturday March 10, 2018 @12:53PM (#16559405)
The thing is though, the number of times I've seen engineers work on conflicting/redundant things without realizing it (outside of the agile/scrum environment) has been vanishingly small. And the places I've seen it it's always been on separate teams that would never have been part of the same scrum group in the first place (ie, it was an inter-team problem rather than an intra-team problem)
Re:Why ‘your’ programmers just want to code by CountSessine on Saturday March 10, 2018 @01:14PM (#16559486)
This rings true for me. At one of my former employers our scrum masters came up with this idea of a ‘scrum-of-scrums’ where team leads would get together once every month and have a standup to talk about things they’re working on that could affect other teams. But it became a painful waste of time because some of the participants didn’t understand that we didn’t want to hear them talk about every single task their team worked on. Then we tried ‘release-train’ planning where the whole company would do 2 day company-stand ups. That was even worse. The real problem was that the company had a weird cultural and engineering mismatch between hardware and software engineers and the upper management was too clueless and careless to coordinate between them.
Re:Why ‘your’ programmers just want to code by OnlyRepliesToBS on Saturday March 10, 2018 @12:15PM (#16559267)
> You're doing it wrong.

This is the nonfalsifiability of a religion surfacing.

THIS is the problem. This very thing.

The implement is ALWAYS blamed.