Poor requirements are one of the top reasons that failure rates for software projects are high in the United States. There are also a high percentage of schedule overruns, many due to creeping requirements. Indeed, technology requirements are the most critical aspect of a successful software deployment project, and managing these requirements are vital part of managing an organization’s implementation risk.
The Memex approach is to quickly and effectively gain a comprehensive understanding of requirements – before scoping, pricing and scheduling a project. A simple yet effective process allows both parties to agree on key project items prior to final project definition. This offers a comprehensive solution to the business issue, while protecting and maximizing the organization’s investment and reducing the risk of project overruns.
Furthermore, the Memex approach allows the client organization to control cost and risk of a project prior to committing resources, and provides them with a lower cost, lower risk environment in which to experience working with Memex.
The Memex collaborative approach utilizes both Memex and customer subject matter experts in a cross-functional team to determine solutions. Spanning approximately 3 weeks from inception to completion, it comprises the 5 stages detailed below:
Significantly, the outcome is often a combination of Memex & non-Memex products and services. Outcomes often include custom configuration, development where necessary, and takes into account existing systems and processes. Recommendations may also include methods for modifying and supplementing the existing environment.
Finally, Memex consultants understand additional challenges faced by organizations, such as limited funding and complex approval processes. That’s why Memex methodologies provide your organization with maximum information for informed decisions. And at the end of the process, your organization will have not only clearly defined project requirements, but also an action plan for implementation.