Senior Staff

Robert Glass states in Software Runaways, Lessons Learned from Massive Software Project Failures, that 42% of projects failed due to lack of senior staff.

Ed Swartz has over 25 years software development experience in an extensive range of areas:

Given this extensive experience Ed can bring this expertise to your project:

• In-depth understanding of the software development process.
• How to write project specifications which leads to project success.
• Superb software design skills.
• Professional approach.

Process

Process is an ordered sequence of steps to help you walk from a starting point to a goal. Expert software developers use process to lead a project from conception, through development, and to completion of a quality product.

Without process bad things happen. High costs, long development time, etc.

Our process for creating quality software is:

1. We learn your objectives.
2. We write project specifications.
3. You review the project specifications.
4. We design the software.
5. We create and test the software.
6. You test the software.
7. We fix problems and you test.
8. You use the software.

We Learn Your Needs and Goals

Many software developers rush to coding and create applications which do not meet the clients needs. The result is high development costs, lost time and frustrated clients.

During our initial conversations we ask insightful questions and listen carefully to learn and understand your needs and goals.

Project Specifications

According to Software Runaways, the major reason for failed projects is a lack of or poor project specifications.

We write project specifications that accurately reflect your needs and goals.

Good Communication

During the development process we need to ask you questions to refine our understanding of your objectives. Poor communication during this period results in web software which does not match your objectives. Causes of communication problems:

• you are busy and are unable to devote sufficient time to discussions;
• impatience; and
• using poor communication tools such as email exclusively.

Hallmarks of good communication are when both parties:

• devote sufficient time to discuss the project details;
• are patient; and
• use good communication tools;

Effective communication ensures that the product we produce will match your objectives.

Good Design

Poor design leads to software which does not function properly, has poor performance, and does not meet your needs and goals. The resulting software is commonly called "spaghetti" code. Bad? Yes, because it wastes your time and money.

We carefully design all components resulting in well organized and working software.

Develop Small Projects

Large projects are cumbersome, complex, costly, and have long development cycles which delay realizing income.

A better approach is to chunk the project into a series of small projects.

Use Evolutionary Approach

See Development Evolutions for details.

Your Involvement is Essential

Your involvement is essential to success of the project, without it failure results.

You need to set aside time to discuss your business needs and goals, review project specifications, prepare and provide us with material, such as, content, images for the application and test the software during development.

Set Reasonable Schedules

Tight schedules increases errors and poor design of your software.

We Respond Promptly to Inquires

Developers who respond slowly delay your project.