How do you not filter out those who aren't subscriptions? For instance my best buddy in high school. I know hundreds of people whom I would be happy to receive email from. They aren't really subscriptions.
I really wanted to like fish but it is so difficult to get it configured the way I would want to use it. I tried so many different ways and the barriers were just so high. It should not be so difficult to make a tool work the way I wanted to work.
I'm typing this on my Google pixel 6A using grapheneOS. I've been very happy with results. There have been a couple of friction spots, but nothing I've not been able to work through. The installation was remarkably simple.
I don't mean Scrum, I mean that people believe the this is Scrum.
Sprints DO have a break. The morning of the first day is just about figuring out what threat will look like. The afternoon of the last day is everyone talking about what they did during the Sprint. That is a full day of doing no coding and just talking with each other about the work. Every two weeks. If someone is forcing you to work in different way, then that's not Scrum.
The dev team is supposed to be encouraged by the scrum master to only take on the work that they can finish during the upcoming Sprint. If they take on too much work the answer is not to insist that they finish it but to ask what they need to understand better about their work. If someone is insisting that the Sprint backlog absolutely must be finished every Sprint, they aren't doing Scrum. As a corollary I hope no one is trying to insist that you do a release that coincides with the Sprint schedule. That's not scrum either.
Scrum is based on principles developed in the Toyota way. There are two pillars in the Toyota way, continuous improvement and respect for people. I'm sorry it sounds like you not lived with either of those pillars. I hope you find a scrum master who understands and can encourage this type of development.
By the way, I am a scrum master myself and this is how I treat my teams. I choose to trust them every time. And I encourage them to make good healthy decisions for themselves.
I know my comment is anecdotal but for me it's relevant.
I'm 60 years old. Up until about 25 I just listened to dentists. They drill-and-fill and I went along. No longer. In 35 years I've had one problem. I broke a tooth biting on a hard seed in some Indian food. I got a crown for that. A few years later the crown came off. I haven't bothered getting it replaced.
I don't have tooth pain. My teeth have not shifted. I still eat what I want. I'm careful with Indian food. :)
My takeaway? I'm not seeing the dentist until I'm in pain or something breaks. No one is drilling on X-ray shadows again.
It also matters what kind of shoelace you're using. With a boot lace a reef knot will struggle to stay tied simply because the lace can slip through the knot. And easy fix for this is to tie what I've heard called a superknot. The way that works is when you wrap the loose end around the loop wrap it twice around the loop before you pass it through and pull tight. This extra wrapping provides a grip that is better than a single wrap.
In my experience the typical flat cotton sneaker laces work fine with a regular reef knot. I also tie my shoes using the Ian way of creating the knot, if I'm wearing standard sneaker laces. It is much faster.
I like my Deck. I wish more games could adjust to the small screen better.
TEXT!
Text designed for giant flat screen TVs or even just modern monitors cannot just shrink down to that small screen. I do not have perfect eyesight. It is too often unreadable.
Do something about the text and the Deck will be as close to perfection as I could hope.
The way that your particular study was conducted might be interesting from a study standpoint but it doesn't match the typically accepted ways of doing agile development. For instance if you were studying metrics but not releasing those metrics immediately back to the Developers then there is no opportunity for them to improve from a feedback loop. This seems like a strong invalidation of the study itself.
I can touch type both qwerty and Dvorak and have been for almost 30 years. Dvorak definitely saved me from RSI. I was genuinely losing my hand use due to a data entry job in college. As a developer, I would not have been able to continue, successfully, without Dvorak.
I have never been that much faster on Dvorak because I keep stopping to think. Keyboard can't help that.
Beyond all that, Dvorak just feels good to use.
Although phones & other qwerty biased situations are a pain, I still think Dvorak was worth it.
I think maybe we agree on something. Religious fanaticism can break any good process. I see Scrum as a place to practice flexibility. Example: I have a dev team that is only two devs, a husband and wife team. We don't do standups because they are together all the time and don't need that feedback and daily planning.
I'll be adding someone to that team soon and will need to add some formality so that feedback and daily planning are sufficient.
I have no room for fanaticism in my processes. It breaks stuff.
I find these comments fascinating. Scrum formalizes using rules? Compared to what? Read the PMBOK and then say that. I do Scrum specifically because it drops all the rules and leaves it to the right smart people to figure things out. I can't even imagine how Scrum with lots of rules would work. I've done Scrum since 2004 (got the SM cert too) and I truly don't understand what you mean by that.
The idea that any project manager can be all that is so dangerously optimistic. And yes, I realize there exists some PM somewhere who proves it is possible to be a good project manager. But the existence of an outlier does not move the bell curve, it's part of the bell curve. Most PMs need to be taught to rely on their devs and product owners so they stop screwing up projects themselves.
There is nothing so dangerous as a bad manager, especially a manager who thinks, "I've got this....". And there are so many bad managers. Scrum helps mitigate this by spreading the responsibility around to the people most likely to get it, not by tossing rules at a team.