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.
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.
Also, need to ask question should not require whole team meeting.
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.
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.
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.
That is regardless of agile or whatever development methodology you use.
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?
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.
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.
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.
This is the nonfalsifiability of a religion surfacing.
THIS is the problem. This very thing.
The implement is ALWAYS blamed.
That doesn't really have anything to do with agile or scrum though. Just add a refactor/investigation task to the backlog for the sprint. Those types of activities should be justifiable too. If your team doesn't allow those types of tasks for some reason, that's more of a team problem than a problem with agile.
Think of it this way, in relationships, business or otherwise, what's sub-communicated is just as important as what's explicitly communicated. Often it's more important. And what's communicated via most agile processes is that programmers are unimportant cogs with no business knowledge that can't be trusted to not stray from important tasks. I think that's ugly.
On my team, agile is a process used among peers to coordinate. No one is a cog. No one is checking up on anyone. We keep each other aware of what's going on because you have to in order to coordinate and collaborate. My manager is just one voice among many on the team. He isn't tasked with monitoring my work because I don't need a babysitter.
I'm sorry that you work somewhere where you feel someone's monitoring or checking up on you. Where I work that kind of situation is called a Performance Improvement Plan. If you're not in that situation and are a highly productive individual, then your culture is broken and you should look for a different job.
But you're wrong that agile and scrum are at fault. If you used any other process, you'd have the same problem.
Anecdotally, the last place I worked, I was on a small team that didn't really do agile. This was composed of some of the most competent, extremely smart people I've ever worked with that had decades of experience in the CAD field and had worked together for a very long time. We're talking people with like dual PhDs from very respected universities that have been working in the field for like 20 years; kept very sharp by going to C++ conferences, were very particular about testing and code reviews, and so on. I remember the corporate office tried to impose agile on these people, and after humoring it for about a month the whole thing was mercifully abandoned because everyone felt like it was ridiculous and it was slowing things down and causing a bunch of friction when some ridiculous consultant wanted us to do "planning poker". The only people that really wanted it in the first place were essentially remote project managers that were annoyed with these uppity engineers that thought they knew better (which frankly: they did; 20 years writing CAD software and you're going to learn a thing or two, whereas the project managers were pretty much just dabblers -- and when they couldn't convince people to do what they wanted by merits of their argument, they just wanted to install "process" to essentially strong-arm people into doing their will)
Part of the argument is that often the more junior members of them team know the surgeons are making mistakes, but there's no way for them to point this out without being bullied. Anectodes include the wrong leg being cut off while members of the medical team know it's the wrong one, but darent risk their career to mention it.
I'm not sure how this relates to your comment, except your line about other professions reminded me.
When you buy a grocery product you get a list of every ingredient and all the nutritional info.
It's nothing more than transparency and accountability. The one paying the money wants and deserves to know what it's for.
Also, software development is quite a bit different than other engineering disciplines, at least at the application development level.
If you can't answer "why are you working on this?" easily then you're not doing your job. And if you resent being asked the question, then you either are self employed or you forgot who pays your salary.
There have been a lot of times in other jobs where we'd have a slack in our schedule and I used the down time to make a change that was really necessary and took a minimal amount of time, mentioned it in a standup meeting, and got blasted for not working on our "commitments" for the "sprint" (even when I had nothing to do).
> The worst part is that it's not just management creating this mentality, it's the other programmers. I've noticed that younger more inexperienced programmers tend to crave the structure of agile, whereas the older more experienced programmers chafe at it.
> I think if programming had more of a culture of apprenticeship and mentorship, and a deeper appreciation that this is hard and it takes a long time to get good at it, our industry would be a lot healthier.
The amount of micro-management that goes into most programmers day to day work makes it extremely hard to be innovative, because you essentially have to justify what you're working on daily -- and any creative person knows that not every idea pans out. You need managerial support to occasionally make mistakes.
There have been a lot of times in other jobs where we'd have a slack in our schedule and I used the down time to make a change that was really necessary and took a minimal amount of time, mentioned it in a standup meeting, and got blasted for not working on our "commitments" for the "sprint" (even when I had nothing to do).
Companies always talk about wanting ideas from workers and how important innovation is, but they're not willing to extend the trust to their people to create an environment where that can happen. People naturally become disengaged when they're not trusted or valued.
The worst part is that it's not just management creating this mentality, it's the other programmers. I've noticed that younger more inexperienced programmers tend to crave the structure of agile, whereas the older more experienced programmers chafe at it. I think if programming had more of a culture of apprenticeship and mentorship, and a deeper appreciation that this is hard and it takes a long time to get good at it, our industry would be a lot healthier.