Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<ol> <li>Not understand/knowing who you are competing with.</li> <li>Not understanding/knowing your target market.</li> <li>Not including your customers in the design phase.</li> <li>Not spending enough time gathering product requirements.</li> <li>Spending too much time gathering product requirements (analysis paralysis).</li> <li>Not enough marketing.</li> <li>Have a strong team so you can trust the people you hire to do their job.</li> <li>Be prepared to do whatever it takes to succeed (ethically of course).</li> <li>Not having a direction (business plan).</li> <li>Not having goals or having unreachable goals.</li> <li>Not understanding cash flow. There are a vast number of profitable businesses who do not succeed because of clash flow issues. Just because you sold a 1000 units doesn't mean you can afford to pay your staff and or other expenses. As I have heard it before "Cash is king!"</li> </ol> <p>These are just some things that might get in your way. I would recommend not only worying about the business side, but worry about what are reasons software projects fail. There are numerous books about how to collect requirements, produce quality code, testing code (e.g. TDD), project methodolgies (e.g. XP, Agile, ...), and many more topics.</p> <p>Your startup will likely fail if you can't deliver a product or if you can't deliver a product that doesn't solve the problem.</p> <p>Finally, it is hard to judge success if you don't define what it means to succeed. Is it staying in business, doubling your revenue in 1 year, breaking the $250,000 mark, or doubling your staff size. You need to define what it means to succeed not only in your business, but with each product you create.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload