|
|
FoxPro Wiki!
|
Development PhilosophyAKSEL Services and Products are based on a simple axiom: Quality Work With Integrity. Proof of this axiom is evident in the work we do for our clients as well as in the products we develop. Our development process reflects this commitment to Quality. Loosely based on Microsoft's own Solution Framework (http://www.microsoft.com/msf) , every person involved in AKSEL has a commitment, not to just the current project, but the overall vision of each person, client and AKSEL as a whole. The AKSEL approach considers every project (be it small business consulting or product development) as its own product in a special market. The product-driven approach requires certain commitments:
Commitment to the CustomerAKSEL isn't interested in one-time customers. Although a client may only require a single job to be performed, AKSEL wants to maintain a relationship with each customer. This relationship may involve services at one time, products at another and also a fruitful relationship regardless. AKSEL does research on new products on a regular basis and want to ensure that our customers are getting the most out of their environments. For that reason, when AKSEL commits to a customer, it is a long-term commitment. Common VisionIn order to ensure that what is delivered meets your needs, AKSEL spends the time to help develop a common vision. This vision is used to guide the development process and help make overall decisions. For some clients, a vision is specific to a single product or project. For others, it defines their entire business. AKSEL can help build visions as well as ensure that during the development process, the vision is kept into check. Cycled ReleasesDevelopment projects tend to be large, even small ones. As a result, it is very easy for progress to be lost and people to get off track. AKSEL uses cycled releases both in-house and externally to ensure that customers see feedback at every stage of the project. Each Cycle is broken into four major parts although there may overlap between each part. Each part may not receive equal time, although the importance of each step is evident in our development cycle. Each part also is made up of its own milestones: each one ensuring a successful delivery and implementation. |
|
Last modified: 07/24/07 |