Getting from concept to reality can often be very difficult. One of the ways we help our clients get traction against goals and plans is through a methodology we call Agile POC.
The proof-of-concept, or POC, is where the rubber meets the road when it comes to validating the fit and finish of an IAM technology for an organization. Exploring a vendors “wares” and evaluating it against your organizations unique requirements is an important function of the architecture group within IT, though this exercise often involves stakeholders from the technology domain and other stakeholders as needed.
Getting a POC started requires a solid understanding of the needs of the business, program goals and the technical requirements within the domain. The Chief Architect, Enterprise Architect and IT Architects who participate generally already have illustrious careers with decades of experience in their respective disciplines, if not direct experience in the IAM systems being evaluated. In particular, preparation for a successful POC requires socializing high value use cases and specific requirements with key stakeholders and the collection and dissemination of information from the following sources:
- Business requirements documents
- Vendor sponsored whitepapers
- Analyst reports and industry reviews
- Seminars and conference presentations (often available on YouTube)
In order to maintain objectivity throughout the duration of a vendor evaluation and POC, a common a set of criteria is used for weighting and scoring. At a minimum, the requirements should be categorized into the following sections:
- General Use Cases
- Technical Requirements
- Security Requirements
- Customer Service & Support
- Business & Legal
We consider it a success when the agile POC is completed and an executive readout and recommendations are presented to the steering committee.