It is interesting to note that the term bucket is used in several ways with technology. Wikipedia lists the technical uses of the term bucket.
Bucket is also a useful metaphor when trying to figure out how to evaluate a software as a service (SaaS) provider and solution. What are the “buckets” for evaluation requirements? As the Wikipedia article states: “A bucket must exist before anything can be put into it.”
The buckets for an IT professional are a bit different than some of the counterparts in an enterprise – e.g. the legal team or purchasing – when evaluating SaaS providers and solutions.
In my conversations with enterprises, the most common buckets that IT professionals create for SaaS evaluation criteria are:
- Business criteria
- Pricing and billing
- Service levels and service level agreements
- Support and communication
- Technical criteria
Putting criteria into these buckets then becomes a time consuming and significant undertaking – an exercise that I have been working on for that last several months. Keep in mind, this list excludes the SaaS solution specific buckets such as user experience, clients, solution features, and mobile support.
The key is to ensure it doesn’t become “bit buckets”, as defined by Wikipedia as someplace where something goes to disappear irreversibly, but rather “documentation buckets” in which criteria can be added or modified based on the latest information and requirements.