Pre-Programming FAQ
Here’s an unusual programming FAQ that doesn’t offer any definite answers for a very good reason: the answers must come from you. Consult it each and every time you think about developing a software program, for the answers will glean some critical marketing information, and literally answer whether you should go with an idea or simply dump it.
Do I have a relevant mission statement?
Every serious project starts off with a mission statement since it helps programmers focus and develop professional strategies from the start. Some questions to answer when designing a new software program are:
NOTE: If you plan on developing a software program that’s based on two or more of these licenses, you’ll need to create a separate plan for each.
Is there a market for my program?
STOP HERE and perform an internet search for the application area your product will be in. Study the resulting pages to see what’s already developed and what hasn’t been developed, and note the names, average price, and any indication of sales made for this type of product.
Don’t forget to check where these products are promoted because if you decide to develop a similar software program, you’ll want to position your software in the same place. If you find the market is already saturated to death, work on developing a completely different software program – one that will fill a niche, and address the concerns of today’s issues.
Who will use my program?
Establishing the software program’s type, market, and audience will help you later decide what features to include, and how to appropriately design it for your audience.
When should I expect to release my program?
A Schedule Estimate contains estimated dates of completion for the software program’s development – answering how long you’ll spend time on planning, designing, constructing, testing, changing, and correcting things. Be aware that you won’t know all of the estimates at this point, and because this is a document that’s constantly updated, nothing you write in is set in stone.
What are the risks involved?
While you’re thinking about the software program’s mission, market, and release, note how you think you can compensate for its shortcomings through a Risk Management Plan. A Risk Management Plan helps you determine what strategies you’ll use to overcome obstacles during development. Some obstacles you can expect to encounter are delays, problems with equipment, budget cuts, lack of support, insufficient skills, etc.
