|
At the end of this beginning part of the process, we expect to have produced a written
document that examines your current difficulties, outlines a
solution, and includes product specs, a timeline and cost
estimates.
Initially, Leepfrog will provide a rough estimate of the
project, based on what we perceive the challenges and deliverable
product to look like. The purpose of this phase is to manage
expectations, and make sure that the costs are in line with both
the budgeted amount and with the business case based on the
implemented software itself. Most software can be implemented under
a wide array of prices, depending on the amount of 'polish' –
testing, user interface enhancements, optimizations, and so on
– added to the product. It is important that the client work
closely with Leepfrog to manage the scope of the project at the
estimate phase, since the remainder of the project will be based on
assumptions and effort guidelines established at this
point. Examination of existing systems/programs
and how Leepfrog’s software might integrate with these
systems.
Typically, Leepfrog will provide several estimate ranges, based
on different end result philosophies:
- Prototype level. Enough of the implementation to get a
feel for the product and its usefulness within the problem
domain.
- Basic level. An industry-standard level of
implementation for custom software, which is appropriate for
deploying to a controlled audience or for giving a better
real-world implementation than a prototype. Supporting software
– portions of the software that internal staff access to
maintain the site – are very basic and may involve extra
steps which are hidden to the end user experience.
- Production level. Polished, easy-to-use optimized
software ready to be deployed to a large number of customers.
Regression tests and load testing have provided a detailed estimate
of how a particular application performs under increasing user
load. User interfaces are optimized for re-use, providing long-term
cost savings in maintaining the software.
This estimate should be used to make a “go/no-go”
decision before continuing onward to later stages of
implementation, or to use it as a basis for a budget
request.
Continue reading about the rest of Leepfrog's Methodology here:
| 
