Roadmap VS Quality

[andor.gellenhidi]

Still, I think it's impossible to make such distinctions, because both factors are very important. It is important that the project team act within the framework of the roadmap and that all this is done qualitatively

[Bolt Brownie]

What do you think is more important for a project: to deliver everything in time, even though the quality will be lower; or make reasonable delays but deliver a really nice project that the team is confident in?

That is a tough question. Quality is of course the most important thing in my opinion, but there is no such thing as perfection. So if you keep searching for it, there are chances that you will never end up delivering anything, and the ideas get lost. You need a commitment between those two things and see what your public needs. Keep delivering things that are stable, even though they are not perfect yet, and keep that perfection as a goal for future development.

[LodisMcguire]

For me it's better for the team to make reasonable delay and they deliver the perfect form of the project.They must let the the investor know what is the development progress of the project step by step though.By delivering the perfect form of the project,it will make a new investor to join and make that project very popular.But,if they release it with many defect,investor will run away and abandoning that project one by one.

[Gaaara]

What do you think is more important for a project: to deliver everything in time, even though the quality will be lower; or make reasonable delays but deliver a really nice project that the team is confident in?

It is obviously necessary that the quality of the projects remains because even if the roadmap hasn't been followed it is okay as long as the delays are necessary. They both affect the project but the quality will be more destructive than following roadmap either way if one of them fails, it will always affect the outcome.

[batang_bitcoin]

What do you think is more important for a project: to deliver everything in time, even though the quality will be lower;

I'll go with the quality, I don't care if they will deliver their road map late as long as quality is at its finest.

Yeah. However, have just thought that on the other hand, road map is one of the first documents that potential investors rely on, while making a decision on investing. So road map should be solid, but as I ve stated many times before, at the final stages of development road map is no more the most important think.

Road map is a very solid requirement for a project to go but in every rule there is an exception right? And if that exception is like making the quality better then that is an understandable reason. Go for a road map that will be delivered in time but later on the devs will start going out and cashing out and will show no effort. Its a good thing to see devs are working hard to their project and they are dedicated to it because it only shows on how they want the project to succeed along with their investors.

[jondel]

What do you think is more important for a project: to deliver everything in time, even though the quality will be lower; or make reasonable delays but deliver a really nice project that the team is confident in?

Of course quality is more important than roadmap. But before they make the roadmap, surely they have done research, studies, time estimates, costs and others. A timely project with a schedule will make investors more confident with the project. For that reason, a good project must have a strong community and all problems arise need to always be communicated with investors or supporters. So if there is a delay from the roadmap can be tolerated.

[Malaya]

The quality is definitely important but following the roadmap could lead to trust. It could be better if this two principles will be valued and practiced at the same time.

[Pattart]

What do you think is more important for a project: to deliver everything in time, even though the quality will be lower; or make reasonable delays but deliver a really nice project that the team is confident in?

But I think there is something that is not in accordance with their plans and expectations. as crowdfunding that accumulated does not match their expectations so developers extend the live of ICO and so on. I think if it's reasonable I think it's not a problem to revise the existing roadmap of course the goal to make the project of ICO quality be better

[udidrone]

What do you think is more important for a project: to deliver everything in time, even though the quality will be lower; or make reasonable delays but deliver a really nice project that the team is confident in?

i think the first option is more important. about quality it still can be fixed but update from devs of a project is more important and it is make investor/users believe they still active to develop their project

[BTCwin1]

I think open source is the key to a project.
No matter how good the white paper and the technical route, everything is visible from the code.

[mrproblem]

What do you think is more important for a project: to deliver everything in time, even though the quality will be lower; or make reasonable delays but deliver a really nice project that the team is confident in?

For a project you first decide your key performance indicators.
This can be budget realization , project scope realization or schedule realization.
This key performance can be decided with investors or your big mama ( main sponsor ).
so it is about what client wants

[Guryon_master]

What do you think is more important for a project: to deliver everything in time, even though the quality will be lower; or make reasonable delays but deliver a really nice project that the team is confident in?

If the reason of the delay is for the great news and everything is in order that is reasonable and better than delivering it on time but there are some that needs to be clear, I go on the delay. This is far greater and convincing for success.

[sksshopee]

Roadmap to a Culture of Quality  is a tool for change management as it offers guidance on transformational change from the current organizational culture to one that fully embodies quality.

[dibonag]

quality is important for sure, but I'm sure also that roadmap should be respected as much as possible

[ommochain]

Of course quality is the most important. A quality project has very detailed information in all aspects and a good communication channel to attract more attention from players and to sell more tokens for sale at a later date Preparation of project development.

[Alerter]

Delays are normal since project team have done some real things, not just fancy presentations and tweets.
Look at SpaceX Falcon Heavy delays history.

[paulmaritz]

What do you think is more important for a project: to deliver everything in time, even though the quality will be lower; or make reasonable delays but deliver a really nice project that the team is confident in?

In my opinion it is important to under promise and over deliver. However, it is normal for unexpected external factors to come into play. It is then best to adjust accordingly based on the new set of information available. The aim in most instances should be to deliver quality work instead of rushing to get things done. Now of course if you're a first mover in a market, it is best to have something on the table than to wait too long!

P.S. A fully baked cake should taste better than a half baked one. 

[UAE Seasider]

I think if they are all going to be honest every startup will most likely face delays in delivering the working project afterwards. It is important to deliver things in a good timeframe as it inspires confidence but also good communications can help smooth out the frustration that comes from delays. So I think timescales and communications would be the most desirable. Products are constantly being updated to solve bugs and enhance functionality that is a fact of life.

[sourish]

Definitely quality, there is no doubt about it. As for time, a project serious about its quality would factor in the time too, and any delays despite that should be well worth the wait. Its a great question deriving an interesting concensus for such policy makers.

[Dydot]

I believe in a quality job. So for me, if there is any reason to delay the timeline of a project in order to get the job done, it is okay.