• 0 Posts
  • 64 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle


  • All the projects that have shittier outcomes in my experience is always waterfall. This is mainly because the stakeholders usually have this bright idea to be added in the middle of development that’s really need to be added at all costs and then got angry when the timeline got pushed because of their fucking request breaking a lot of shit.

    At least scrum has a lead time of around 2 weeks so that when someone has a idea we can tell them we’ll add it to the backlog and hope they forgot about it during the next sprint planning.








  • If you’re competent, a SM is invaluable, however it’s one of the easiest to replace role. As an example, almost all of the engineers in my division has a PSM I certification. So all the SM do is just facilitate meetings. When we started we have around 5 SMs but currently only have 1 because all of the SMs are redundant since the team already know how scrum works.


  • Google has this culture that you need to make something to be something, usually someone will have an idea to make a product, then the product is quite successful and they get promoted away from managing that product.

    Then someone gets assigned to manage that product, since that someone new also wants to make “something” to be something, they put their own spin on that product.

    Since they’re not the one who made the product in the first place, they missed what made the product great.

    This causes the product to lose quality, and therefore the user base. With a reduced user base, there’s no justification to keep the product alive, so Google pulled the plug on the product.

    It’s a vicious cycle that results in a lot of things made and killed by Google.