I'd prefer quality of course.
But I guess any of the variants will lower investors loyalty to the project.
Topic: Roadmap VS Quality (Read 457 times)
both actually will really affect the price, since the news is really important on crypto world.
If we planning to hold the coins for short term, then choose Roadmap even though the quality will be lower.
But if we planning to hold the coins for long term, then choose Quality
If we planning to hold the coins for short term, then choose Roadmap even though the quality will be lower.
But if we planning to hold the coins for long term, then choose Quality
I think projects can make slight delays but let there be a good quality product . Many of course believe the opposite which is not good
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?
there is no benchmark in the benchmark of an ico.
myself, always judging from the whole to know if ico is really potential and has a road map. but the most important thing is, I always liked having a sophisticated technology base.
These are very important, because if a team does not have to complete in time for ICO project development, that means that the road map to reach, or the team's technical team is not good, unable to complete the development.
These are important, but the team is more important. Team who will carry them out.
It depends on your point of view. If you are a simple investor and have plans for the near future - compliance with roadmap is more important. If you have long-term plans, quality project implementation is better. The fact is that the deviation from the road map causes the cost to fall for a relatively short period of time. Technical errors can cause more serious difficulties and lower prices.
Both are important essence for a coin.Roadmap specify the particular project direction,its purpose,its scope,Project durability and viabilty,promise to deliver whatever is committed whereas quality is another important factor for success of a project depends upon its quality,for example technical superiority,efforts of development team.Suppose Mercedes Benz is superior to Toyota because of clear road maps of its services and no compromise on quality in similar we can differentiate Road map and quality.When the above both the factors are well organized then that coin is for longer existent and would attract larger market attraction.
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 choose the second variant: better to wait and get a good product than get a lot of problems because of fast launch. I`m still patiently wait for Exscudo or Tezos for example, despite the fact that already more than half year passed. 
of course quality is the right choice even though all goes slow but the team already gives the quality of hard work then all will be good and surely later will make the price become increasing
Yes, quality is the most important part in the project. But it manifests itself not only in the product. Drawing up a roadmap and clear implementation is also a quality. It is important to remember that the project does not consist only of developers. Marketing, management, legal support, advisers - all these are also important parts of the project. So the choice between roadmap and quality is not worth it. All of them are a manifestation of quality.
Roadmap or Quality, Of course I have to admit I prefer for a quality compared to Roadmap. Because the Roadmap I often meet is not appropriate. If Quality is good it will follow the Roadmap.
Roadmap use by everyone which provided by each ICOs in the market quality cannot be give by everyone.Each project has good team in the company and market and these companies use to give the proper care for your technology.If team is recurited by good people work can be increase and quality may be good and increase surely.
On time on target is more preferable in cryptocurrency ecosystem. Cryptocurrency is a very fast market with fierce competition. The fast and the best usually win in this game not the slow and the best.
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.
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.
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.
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?
Between roadmaps n quality from a project is interrelated with each other
But for creating a project with a timely road map with good quality is quite difficult, there must be a neglected one of them.
I think quality is more important, because the quality as a determinant of success or not from a project.
So no problem there is a delay if it can create a big and successful project.
The process is time consuming
which for a long time the result will not cheat.
In my opinion, I do not trust these so-called ICO team, responsible for your own investment, I will own regular study their open source code, if the code quality is very general, so I think I will sell these tokens, rather than holding a long 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?
Between roadmaps n quality from a project is interrelated with each other
But for creating a project with a timely road map with good quality is quite difficult, there must be a neglected one of them.
I think quality is more important, because the quality as a determinant of success or not from a project.
So no problem there is a delay if it can create a big and successful project.
The process is time consuming
which for a long time the result will not cheat.
I think timely distribution is better than waiting for better results but should delay some time, because for timely division it will make it easier to find or work on other projects.
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.
Agree. There should be a vision what the team will do in the long run. But short term goals are much more reliable and trustworthy
Jump to: