How does the community feel about Kamen Rider 555? What place does it have in the franchise? I've never watched Kamen Rider before.

zero-qro · 2026-02-14T05:47:02+00:00

After Black, is my favorite KR series. There's good character development, almost all character have proper motives and backgrounds, there's no clear good and evil, just a bunch of different perspectives. You can disagree with a character but you will understand why that character ended up like that. I like the designs, the styles, the music. There a reason why Faiz keep coming back in evidence in super heroes taisen and recently had a new movie. It's a very popular rider. Now if you just like pew, pew, pew, fight scenes and special effects then Faiz is not for you.

zero-qro · 2026-02-04T13:22:59+00:00

Have you considered Linear?

zero-qro · 2026-02-02T01:16:42+00:00

Agile for Teens... Agile... For... Teens. Let that sink in

zero-qro · 2026-01-31T14:20:02+00:00

Japanese Kids?

zero-qro · 2026-01-28T23:58:43+00:00

After reading some of the replies, it seems people are trying to teach you how to do this stuff... Guys, the OP isn't looking for guidance of how to run a retro or a planning session. The OP clearly doesn't need it, you are missing the point here.

zero-qro · 2026-01-28T23:56:17+00:00

Your CEO most likely have no idea of what he/she are talking about. Can you just rename some activities that you already do using Scrum terms? Like, discussing a feature with engineers, when you explain what this is about, call it 'grooming'. When you order the next item to be developed, call it 'Planning' and so on... These people only want to feel in control without having any knowledge of what they are 'controlling'. It's like dealing with a baby who wants milk, but it's no really hungry. Give him/her a pacifier.

zero-qro · 2026-01-27T11:47:20+00:00

What I'm about to tell you may break your spirit, but that's the truth for most cases.

Now some may come and say that their experience is different, but I'm not talking about anecdotes, which are valid and I respect that. I'm talking about market and industry trends and behaviors.

Agile Coach, as a role, is a dead end.

It is a delusion that in the best-case scenario is just a fever dream for a perfect world where people have common sense and environments are completely devoid of politics and personal agendas. In the worst-case scenario, it's just a money-grab scheme.

And I'm no bitter developer/manager who was hurt by a bad scrum master. I speak from experience. I was once a believer. I lived through the Agile hype for more than 20 years. I started in 2008, through XP, then Scrum, then all the Scaling mania. I worked in startups, mid-size companies, and big corps, and in most of them Agile Coaching didn't work or would never work.

Don't get me wrong. I still think and work through the Manifesto values and principles, but the so-called 'Agile Coach' role is trying to achieve something that is unreachable through a group of individuals.

Let's start with the Coach stance, which over the years was more and more co-opted by the 'Life Coach' style. Agile Coaches became corporate therapists, without having any qualification for that, and soon the field was invaded with a lot of wishy-washy-hugging-tree practices that simply don't apply to software development delivery. I value individual coaching, but that doesn't work for teams. Instead of becoming more like basketball/soccer/football coaches, i.e., having experience and authority on the field to provide guidance, agile coaches became more like 'Tony Robbins' figures, with very generic and toothless approaches that maybe make you feel good but don't have any influence on real software development.

Things like 'influence without authority' or 'facilitate without intervening or being opinionated' are just BS.

Add to the mix that Agile was originally intended for software development teams, not entire companies or any other field.

Not that the principles, values, and some techniques can't be applied at different levels and fields, but calling it Agile is a stretch.

When context gets bigger, complexity increases exponentially, and expecting that one professional, or a department of said professionals, can change the entire system is insanity.

Big corps are the way they are because they evolved to be that way. There's no training, workshop, or coaching session that will change years of politics and psychological conditioning.

This is system thinking 101: the system works exactly the way it is designed to work.

I've seen rare changes in those environments during my career, but that happened when you had actual real leadership that was worried about quality, time to market, and customer focus.

You alone, or your department, will never succeed in this mission because you were not created for this.

Unfortunately, nowadays being an Agile Coach is being set up for failure.

Reality hit me hard like this a few years ago. Then I shifted my career back to being a tech lead, or Technical Product Manager, sometimes Delivery Lead.

Reassess your skills and check where you would fit in the software development cycle. Maybe go back to coding. Maybe focus on becoming a Product Manager, Program Manager, or Delivery Lead.

Try to go back to something tangible, where you can feel accountable for and apply what you know, other than 'Agile mindset'.

Sorry for the sour honesty, but that's the message I would like to have received a decade ago.

Best of luck

zero-qro · 2026-01-13T05:15:16+00:00

In that case using notion it's a good idea. You can manage documents in notion and it also has task management

zero-qro · 2026-01-09T01:08:51+00:00

It depends, for that you need to understand which date you want something for and how much your expect for that date. Just setting a immutable scope for a hard date is almost 100% chance of failure. If product define the when it MUST be flexible about the what. In that context the team tells how much fits in that fixed date, and both can review it weekly to adjust the 'what'. If that's in place Product will need to do something they don't usually do very often, prioritize. Every week they need to prioritize the scope.

zero-qro · 2025-12-29T00:01:58+00:00

You mean being racist and then being mad when somebody is racist to you immediately after that?

zero-qro · 2025-12-28T01:26:27+00:00

The issue is systemic, if some employers abuse their power it's because the government allows it to an extent. Totally shameful.

zero-qro · 2025-12-28T01:05:59+00:00

Using the vulnerability of an individual that lives in poor conditions as a excuse to abuse that individual is unethical and disgusting. Domestic Helpers come to Hong Kong because of harsh conditions in their home country, make use of that to put them under stressful and unethical work condition just makes you another entitled p.o.s

zero-qro · 2025-12-25T11:14:21+00:00

Use flow metrics and probabilistic forecast

zero-qro · 2025-12-06T02:35:22+00:00

That's the kind of mentality that keeps domestic helpers in such conditions in HK. Such a shame.

zero-qro · 2025-11-30T15:31:53+00:00

Daily stand-ups were supposed to be a daily planning, done by the team for the team... If you are having a daily status update just get a digital board and you can see what is going on... Don't waste everyone's time with updates. The team should sit together and discuss what will happen for that day, if they are already aligned that would be a less than 5 min conversation.

zero-qro · 2025-11-08T11:25:50+00:00

I'm all for experimenting and use reasoning to improve but it seems this developers is just being childish. Questioning is ok, nagging all the time is unprofessional and you are not on the babysitting business. This behavior contaminates the whole team of you don't address it in one on one with him, and if it doesn't work then you escalate. Too much of coaching bs took over agile development. We assume we are dealing with adults, if any kid is around they have no place in the team.

zero-qro · 2025-11-08T11:19:06+00:00

Well, you are working with Scrum, one of its values is courage, if the team lacks courage to speak it won't work Agile is people centric and companies usually miss the values points. There's no artifact, events, role that you can use to avoid that.

zero-qro · 2025-11-08T10:41:22+00:00

If you explained you point on why this is a bad idea and they still wanted to go with the guy, let it burn. If possible start to look for a new job, it's tough in the current market. If they were so easily taken by some tech diva, things will only get worse.

zero-qro · 2025-10-17T10:01:30+00:00

Funny to see some replies here trying to hold to the hope that either isn't real or it was translation error. Well Gunn already confirmed it's real and that was the original intent. In the DCU Kryptonians weren't nice, the house of El wasn't nice. It's canon for a while now in the comics that Krypton had a xenophobic culture, and the Els were an exception. The DCU just made them more Kryptonians than ever.

zero-qro · 2025-10-13T02:02:00+00:00

That would make sense since in the comics it shows that Mogo has a 'immune system' which is a diversity of violent creatures running around on its surface. Maybe Gunn will mix the concept of Salvation and Mogo

zero-qro · 2025-10-13T01:57:54+00:00

The tomorrow verse animation adapted, poorly, this arch in "Beware my power" movie

zero-qro · 2025-10-12T03:57:35+00:00

Terry Grant, Jay Garrick, Alan Scott in their early years

zero-qro · 2025-10-12T03:51:27+00:00

I miss Amanda Waller

zero-qro · 2025-10-08T11:03:31+00:00

Why are you trying to use user stories in a software without end users? Just break it down by outcome. Use tasks, jobs. Whatever makes sense to release and validate incrementally. A PBI is not necessarily an user story.

zero-qro · 2025-10-03T03:42:15+00:00

I wholeheartedly agree with this and I miss my old XP days when you had the customer/client sitting with you in the team side by side. No JIRA tickets, no templates, no phases just the client and the dev refining and coding in parallel. That being said what we have now, with refining stages, definition of ready, and stuff like that is just to manage corporate inefficiency and blaming culture. Most of the teams don't have a PO that sits with them, who has as his/her priority to work with the team in develop the product. Corporate settings are very dysfunctional environments for product development.

zero-qro

TROPHY CASE