You are viewing a single comment's thread.

view the rest of the comments →


[–] notenoughstuff [S] 0 points 0 points (+0|-0) ago 

Reg. when software is ready, one also has to consider deadlines. In such a case, I would believe that it typically for most cases is a good idea to inform the relevant decision makers that are responsible for the given project or product whether you believe the goals can be reached, ask them how to prioritize, ensure that there are proper fallbacks if the deadline fails, and generally keep them well-informed such that they can take decisions. That does, as you say, depend on the case.

In any case, I strongly agree with you that prioritizing the company and keeping focus on how one can help the company achieve its goals are very important. And here I must apologize, for I believed the blog post cared more about how developers can do a better job, instead it indeed seems to "sell" things to developers, and I think that is similar to a lot of SCRUM marketing, because they tend to focus on how developers can be "empowered" (whether true, false or the opposite...) instead of focusing on how developers can better help the company, which ought to be the focus.


[–] roznak 0 points 2 points (+2|-0) ago 

You need a soft deadline. deadlines are important because then we wrap everything up to a complete functional project.

What would be better is to have a soft deadline, and make developers try to do everything they can in this given deadline with certain directions to follow to. Any good developer will optimize the time and resources because they love to create and also love to win.

This blog post indeed is trying to create a new hype because their previous hype failed. It is the exact same people that tries to cover up their previous mistake by introducing yet another method that will fail exactly the same way.