The Excelisys development process in a nutshell
(well, as short and concise as we could get it)

1. The Initial consultation Phase

You will initially speak to an Account Manager who will learn your dreams and desires and educate you in the ways of the glorious collective known as Excelisys. He will dazzle you with his objective insight. Together you will identify the problem(s) or issue(s) in your system. Unlike a dentist pointing out an embarrassing rotten tooth, thus exposing your shoddy personal hygiene, this encounter won’t be that awkward. Once the two of you have discussed options and potential avenues to explore, your account manager will provide a guesstimate of the time frame and cost your solution requires (a non–binding guesstimate mind you, cause we REALLY are still in the initial let’s–get–to–know–you awkward–first–date stage). This marks the beginning of our agile development process.

2. The Beginning of a Beautiful Working Relationship

You will love your Account Manager, and therefore hire us of course. But be warned, your Account Manager will turn you over to your Excelisys Project Manager and Lead Developer and instantly wash his hands clean of you. But you won’t mind, because you and your two new best friends at Excelisys will refine those solution ideas you and your Account Manager devised. Together, you will conjure up every possible objective, overturning every metaphoric rock in your stream of dream solutions. Based on your budget, timeframe and technology choices, you will arrive at a plan of action or actions. You and your team will be turned on to our online project management system, where you can post questions and files, and give feedback. We will of course document as much as we can and then provide a more detailed time and cost estimate. Then we roll.

3. Build. Reveal. Revise. Repeat.

So now the fun part: the implementation of the fix or the start of something big and new. This is the stage where we commence our techno wizardry, where the fingers meet the keyboards and your dream becomes a reality. (Over the top? Maybe. But maybe not. You’ll have to hire us to find out if we live up to our own hyperbole.) Based on your feedback from phase 2, we begin building the solution. We move seamlessly into the next phase of the agile development process, in which we present progressive “builds” of your solution for you to evaluate and test. Let us explain. For a moment, imagine your project as if it were a new house being built. Unlike many home makeover shows, we won’t reveal the finished product in one fell swoop. Instead, we’ll let you see what the foundation looks like, gather your feedback and proceed to the first floor. Then we’ll show you the first floor, ask some questions of our own and proceed to build the second floor, and so on, until the final shrub has been trimmed on your project’s immaculate metaphoric front lawn.

4. Testing, Testing, 1,2,3,4 – is this working?

Last, but not least...VOILA! We bring the finished solution online or allow access to view and play with the fixes that have been implemented. This is when you get to truly test–drive the implementations. As we begin user acceptance testing and debugging, you will play an integral role in identifying snags, snafus, and dare we say “bugs” in the deliverable. As the project requires and progresses, we will continue to build, revise and tweak until completion. But like all works of art, your “piece” will never really be totally complete (as we could tweak a solution for eternity), only abandoned at the brink of perfectionist–induced nit–picking insanity. However, we won’t stop until you are completely satisfied. And you will be. Trust us. And then when you are satisfied, we celebrate together!