HealthEdge employs an Agile Implementation Methodology that ensures customers experience a timely, cost-effective and predictable implementation and successful transition to self-sufficient operation. Our field-proven approach provides faster and more predictable results and allows us to embrace change at all levels. Project risk is minimized by decomposing the implementation into easily achieved sets of objectives that provide frequent milestones by which to measure the overall speed and effectiveness of the implementation effort.

The “test-driven” nature of the methodology allows us to validate the implementation early and often thereby reducing project risk and eliminating late-stage surprises.

Unlike the traditional “waterfall” implementation approach that is used by many competing organizations, our Agile Implementation Methodology affords our customers numerous advantages including but not limited to the following:

  • Reduced Project Risk – The implementation is decomposed into sets of deliverables that can be easily tracked and measured throughout the implementation vs. the phase-based approach of waterfall that often disengages the customer for months at a time and is difficult to go back to earlier phases to incorporate changes.
  • Improved Project Transparency – Customers have full visibility into the work as it progresses and customer feedback is incorporated quickly. Real-time status updates, risk and issue management, and work completed against time elapsed (velocity) tracking significantly reduce the potential for late-stage surprises and drives the ability to make informed and good decisions at all levels throughout the implementation.
  • Continuous Knowledge Transfer – Customer staff increase their understanding of the system throughout the implementation through repeated cycles of design and configuration that lead to a much higher rate of acceptance against requirements and test results, better operational readiness, and overall self-sufficiency.
  • Consistent Improvement – The implementation and work methods improve steadily as the project team constantly evaluates the evolving implementation and its progress, obtains immediate feedback from customer’s staff and project stakeholders, and learns from their experiences.
  • Increased Agility – The iterative approach provides great agility in responding to unexpected events and provides the ability to easily address changes throughout the life of the implementation.

Our Professional Services team begins each implementation with a collaborative and interactive discovery process that engages customers in order to define requirements. We do this through a series of question and answer working sessions, which are conducted in person with each customer. At this time we will also review pertinent artifacts, documents, specifications, and existing processes and business operations. Findings are used to facilitate a high level solution design and to conduct the requisite project planning that is needed to get the implementation started.

Once requirements have been defined and a high level solution design is established we will then begin the collaborative process of developing and planning implementation iterations during which we will work with each customer to design, build, and test a set of deliverables within each iteration. Prior to commencing work on a deliverable, our Professional Services team will present relevant system functionality and issues for the customer’s consideration. This is done in order to better understand requirements before commencing the work. Once work begins we will meet with key staff to refine requirements for the deliverable. We will also work with the customer to define complete test cases for the requirements. These test cases will be used for numerous purposes including clarifying the requirements and testing and accepting the work during the iteration. By using these test cases, any issues with the requirements or the implementation can be identified and fixed early when the cost to fix is low.

HealthEdge adheres to a test-driven methodology when implementing configuration or any other form of development including interfaces, etc. This is done before a single line of code or configuration is written. In doing so, requirements are captured as stories, test scenarios, and detailed test cases all of which become vital documentation artifacts. The implementation begins with the analysis of the test cases and culminates with deliverables that are accepted based upon the successful completion of the test cases.