Process - Project Delivery

Overview
Project Delivery Methodology
1. Complementary Meeting & Cost Estimate
2. Project Scope, Schedule & Budget Definition
3. Develop & Test System
4. System Implementation & Training
5. Documentation & Support

The ESI Project Delivery process is managed completely by John H. Ellwood. Communication is paramount. John carefully documents project specifications so that the final product meets the required goals. This coupled with John's 10 years experience developing software applications and meticulous attention to detail, make ESI solutions successful.

All projects, regardless of size or complexity, will be executed according to ESI's clearly defined Project Delivery Methodology. By following this proven methodology, ESI and clients can effectively plan for systems that meet an established schedule and successfully achieve a measurable ROI.

Here's how John describes ESI's Project Delivery Methodology...
1. Complimentary Meeting & Cost Estimate


I prefer to meet with you in person, but can certainly conduct an interview over the phone should this be your preference. Through this meeting I will gather a preliminary understanding of your current resources and overall project goals. I will make any immediate recommendations and deliver a preliminary project estimate. If you decide at this point that you could use my services, we would form an agreement and proceed to Step 2. If the project is not a good fit for my expertise, I will do my best to refer you to a company who might help.

2. Project Scope, Schedule & Budget Definition - Final Agreement

This crucial step is where we make sure the project is clearly defined. I will collect and compile any existing relevant information that you may have to help define project guidelines. I will conduct interviews with designated functional representatives and document your operations workflow, deliverables and integration needs. Once you have reviewed and approved this documentation, I will produce final documentation of the scope, schedule, and clear definitions of how and when the project’s success will be measured. From here we will negotiate the Final Agreement for completion of the project.

3. Develop & Test System
Develop & Test System Prototype
I will produce a prototype for the solution as quickly as possible and test the fundamental system design and architecture. This prototype will be delivered for testing and review prior to further development to be sure the concept is sound and completely meets projects goals.

Develop & Test Final System
Once the prototype is deemed technically sound and functionally adequate, the final system solution can be completed and tested.

 
4. System Implementation & Training
Pilot Implementation & Training
Depending on the scale of the project and number of users, I usually recommend a Pilot Implementation in which key in-house staff are trained to use the system prior to implementation in production. By testing the solution in a simulated environment, unforeseen bugs can be identified and eliminated. This also allows key end-users a chance for final review of functional adequacy. At this point I also provide training for any in-house IT staff that will be administering the system.

Final System Implementation & Training
I will work with your staff to deliver the system completely configured with the clear, step-by-step documentation necessary for self-sufficient support. All end users will be trained.

5. Documentation & Support
Documentation
The scope of essential documentation inevitably varies with the complexity of the overall system. All completed projects will be delivered with at least enough written documentation to guide “mission critical” administration and maintenance of the system.

Support
Support for all projects will be established in a clear, concise Service Level Agreement (SLA). The agreement will be constructed to the level necessary to specifically address your needs.

Maintenance & Enhancements
Depending upon your needs, I offer a range of scheduled maintenance services. I will also always be on standby should you decide to enhance your system with additional components. I do not develop and run! In fact I’m counting on the fact that you’ll be coming back for more.