How We Do It
We have a process that is customer oriented and has proven itself time and time
again.
After an initial customer consultation, we attempt to get a broad overview of
the problems that need to be solved and determine a rough scope of work. We use
the information collected to give the customer a ballpark estimate of the time
needed for completion, the required amount of client assistance, and the cost
to develop. Although these estimates are unscientific they ensure both parties
are on the same page before committing further time and resources.
After both parties are satisfied that there is a fit we move on to the
requirements gathering phase. We spend more time up front on requirements than
most software shops. These requirements are collected into a document that is
first used to make sure that what we're going to deliver meets the client's
expectations. This document becomes the blueprint for our development work. By
eliminating ambiguity before development begins, we can give more accurate time
estimates and ultimately save the client money by eliminating a good deal of
the "false starts" that plague many projects.
When requirements gathering is complete we present a written specification to
the client, revising it, as necessary, until both parties are comfortable with
the design and estimated timeline of the solution.
After the specification has been finalized, but before development begins we
will work with customers to create a set of milestones. Each one of these
milestones specify a (cumulative) set of features that can be seen, used, and
tested. Although milestone based development creates some extra work on both
sides (time for your staff to test, time for our staff to package and deploy
something which can be touched by the end user) it benefit us both. It ensures
that we get feedback on our progress early at all stages, which has a positive
impact on the quality of the end product. It also allows the customer to know
exactly how their money is being spent and what they are getting.
The next step is to begin the actual development. We believe in writing good
software, maintainable by any competent programming shop. To facilitate this we
adhere to all industry best practices and maintain consistency across all tools
and platforms used. For example, if we're tasked with storing the inventory for
a business and writing tools to manipulate this information the client will end
up with, in addition to a working product, a well documented schema being
stored on a well known data base management system. In addition to using well
known tools, source code for all software written by Yye Software will be
delivered to the customer at the end of the development cycle or (if requested)
at specified intervals during development.
When development is complete we begin an internal test phase to ensure that the
performance of the product meets the specifications before delivering to the
client for their own internal testing. During this time we will address newly
discovered defects to the customer's satisfaction.
Upon completion of development and testing, we will then work with the customer
to deploy the application, utilizing our own staff or their own depending on
the need of the business. Initial deployment and the short period of time after
can be one of the more trying phases of the entire development process and we
take pride in being highly available and ultra responsive during this time.
Contact us today to see how Yye can deliver for
you!
|
Yye Software came to our place of business and
listened to our challenges. They were able to design a solution that fit
our needs as well as our budget.