Topic: Roadmap VS Quality - page 2. (Read 440 times)
I don't believe in roadmaps. I prefer when developers come out with strong releases and short-term plans. Long-term ones better just to be stated without a deadline. Like Nexus team for example. They doing a great job without too much of an attention.
Reasonable, honest roadmap without any certain delay. Some can be accebtable but it becomes routine then how can we trust them.
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?
As an investor, I think its is the road map. Specially if your a professional, you should follow the initial agreement for the investors to trust your project. That's why before you could create a god project, everything must be establish first to gain more investment because people are expecting the team to deliver.Nice project varies on the uniqueness of the platform which stands out in the market. Also quality should also not suffer during the establishment of the road map.
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.
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.
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.
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.
Delays are normal since project team have done some real things, not just fancy presentations and tweets.
Look at SpaceX Falcon Heavy delays history.
Look at SpaceX Falcon Heavy delays history.
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.
quality is important for sure, but I'm sure also that roadmap should be respected as much as possible
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.
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. 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
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.
No matter how good the white paper and the technical route, everything is visible from the code.
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 
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 
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.
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.
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.
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.
Jump to: