AI1  Identifying Solutions
Control over the IT process of ...
identifying solutions
    with the business goal
    of ensuring an effective and efficient approach to satisfy the user requirements
     
      is enabled by
      • an objective and clear identification and anaylsis of the alternative opportunities measured against user requirements

        and takes consideration

        • Critical Success Factors that leverage
        • specific IT Resources and is measured by
        • Key Performance Indicators

Record of Assessment
Assignment ID:  * Enter Name: *

Reference Code: *

 Enter Location: * Tel. Num: *
Enter Full e-mail Address: *
  Control Objective:

Identifying Solutions. 
CRITICAL SUCCESS FACTORS
Selected Status
Description
*
There is good knowledge of the solutions available in the market
*
Practices are defined to address not only soundness of design and robustness of functionality, but also: operability, including performance, scalability and integration; acceptability, covering administration, maintenance and support; and sustainability, in respect of cost, productivity and appearance
*
Criteria for consideration of in-house development, purchased solutions and outsourcing options are defined
*
There is a general acquisition and implementation method or system development life cycle methodology that is clear, understood and accepted
*
There is a transparent, fast and efficient process for planning, initiation and approval of solutions
*
Key users are identified to support the solution analysis and recommendation
*
Solutions are constructed from pre-defined components
*
A structured requirements analysis process is implemented
*
There is a clear definition of supplier responsibilities
*
Use proven technology as a matter of principle and new technology only where needed, justified by a business case
*
There is awareness of the total cost of ownership of the solution
*
Security and control requirements are considered early on
KEY GOAL INDICATORS
*
Number or percent of projects restarted or redirected
*
Number or backlog of non-addressed solutions
*
Number or percent of solutions signed off by the chief technology officer or architect as in line with the IT strategy and IT architecture
*
Number or percent of solutions signed off by user as fully meeting user requirements
*
Number or percent of solutions that fully consider alternatives, feasibility and risk
*
Percent of implemented solutions formally approved by business owners and by IT
*
*
*
*
KEY PERFORMANCE INDICATORS
*
Time lag between requirement definition and identification of a solution
*
Number or percent of solutions returned from acceptance testing
*
Lag time before approval of identified solution
*
Number of projects involving users in requirements definition and solution selection
*
Number of solutions subsequently affected by significant change requests due to functional changes
*
*
*
*
*
*
*
*
*
*
  Conclusions:
* Non-existent 
The organisation does not require the identification of functional and operational requirements for development, implementation or modification of solutions, such as system, service, infrastructure, software and data. The organisation does not maintain an awareness of available technology solutions potentially relevant to its business.
* Optimised 
The organisation's acquisition and implementation methodology has been subjected to continuous improvement and has kept in step with changes in technology. It has flexibility, allowing it to handle the range of projects from large-scale, organisation-wide applications to specific tactical projects. The methodology is supported by internal and external knowledge databases containing reference materials on technology solutions. The methodology itself produces computer based documentation in a pre-defined structure that makes production and maintenance very efficient. The organisation is often able to identify new opportunities to utilise technology to gain competitive advantage, influence business process re-engineering and improve overall efficiency.
* Managed and Measurable 
The organisation has established an acquisition and implementation methodology, which has evolved to the point where it is unusual for it not to be applied. Documentation is of a good quality and each stage is properly approved. Requirements are well articulated and in accordance with pre-defined structures. The methodology forces proper consideration of solution alternatives and analysis of costs and benefits enabling informed choices to be made. The methodology is clear, defined, generally understood and measurable. Therefore, exceptions can be easily determined and corrected by management. Solutions respond efficiently to user requirements and there is awareness that forward looking solutions can improve business processes and the competitive solution.
* Defined Process 
The organisation has established an acquisition and implementation methodology, which requires a clear and structured approach in determining IT solutions to satisfy business requirements. The approach requires the consideration of alternatives evaluated against user requirements, technological opportunities, economic feasibility, risk assessments and other factors. The process is not, however, always followed for every project and depends on decisions made by the individual staff involved, the amount of management time committed and the size and priority of the original business requirement. Typically, the process is bypassed or considered to be impractical.
* Repeatable but Intuitive 
There is no formally defined acquisition and implementation methodology, but requirements tend to be defined in a similar way across the business due to common practices within IT. Solutions are identified informally based on the internal experience and knowledge of the IT function. The success of each project depends on the expertise of a few key IT individuals and the quality of documentation and decision making varies considerably. 
* Initial / Adhoc 
There is an awareness of the need to define requirements and identify technology solutions. However, approaches are inconsistent and not based on any specific acquisition and implementation methodology. Individual groups tend to meet to discuss needs informally and requirements are usually not documented. Solutions are identified by individuals based on limited market awareness, or in response to vendor offerings. There is little or no structured analysis or research of available technology.
Settings will expire on: 

(Do NOT edit.) Field set by Form.
Save and E-mail this form. (Saves only "*" fields & sends E-mail to address above):


Maintenance Functions

Note: If using Netscape on a Macintosh you may have to submit twice, the first will fail, or you can push the "Save Changes and/or Set New Expiration" then Submit.