AIM Methodology

AIM Methodology
Click to edit Master subtitle style
SLK Software Company Confidential Information. All rightsrights reserved.document cannot be Copied, Re-distributed, Transmitted or Printed without the the written SLK Software Company Confidential Information. All reserved. This This document cannot be Copied, Re-distributed, Transmitted or Printed without written permission of SLK Software Services Pvt. Ltd permission of SLK Software Services Pvt. Ltd
(1) 1
Definition
Application
Implementation Method is a proven approach for all the activities required to implement applications. Its a encompasses a project management methodology with documentation templates that support the life cycle of an implementation. The A.I.M. methodology can actually be used for any type IT software implementations however the value of A.I.M is within the documentation template. The software includes the documentation templates, manuals and an html website to manage these templates.
SLK Software Company Confidential Information. All rights reserved. This document cannot be Copied, Re-distributed, Transmitted or Printed without the written permission of SLK Software Services Pvt. Ltd
(2) 2
A complete, effective toolkit

Deliverable Template
Pre-seeded content & sample data
Customizable work plans
Detailed Task Description
Project Management Support

(3) 3
AIM : Implementation & Life cycle

(4) 4
There are eleven processes of implementation

1. Business Process Architecture 2. Business Requirement Definition 3. Business Requirement Mapping 4. Application and Technical Architecture 5. Build and Module Design 6.Data Conversion 7. Documentation 8. Business System Testing 9. Performance Testing 10. Adoption and Learning 11. Production Migration
(5) 5
A.I.M. methodology life cycle
(6) 6
Definition
You
plan the project. Review the organizations business objectives. Understand the business processes. Evaluate the feasibility of meeting those objectives under time, resource, and budget constraints.
(7) 7
Operation Analysis
Project
team develops Business Requirements. Assess the level of fit between the business requirements and standard application functionality. Gaps are identified and corresponding solutions developed. Solutions for gaps evolve into detailed designs during Solution Design.
(8) 8
Solution Design
Develop
the detailed designs to meet the future business requirements. Project team members create detailed narratives of process solutions developed during Operations Analysis. Supporting business requirements may require building application extensions to standard features. The project team carefully scrutinizes these solutions and chooses the most cost effective alternatives.
(9) 9
Build
Coding
and testing of all customizations and other custom software. Coding & testing of enhancements, data conversions, and interfaces. Policy and procedure changes relating to business process modifications are developed. Business system testing is performed to validate that the developed solutions meet business requirements.
(10)
10
Transition
Deploys
the finished solution into the organization . The project team trains the end users. Technical team configures the production environment and converts data. Transition ends with the cutover to production, when end users start performing their job duties using the new system.
(11)
11
Production
It
marks the last phase of the implementation, and the beginning of the system support cycle. The Information Systems (IS) personnel work quickly to stabilize the system and begin regular maintenance.
Provide
system.
the ongoing support to the organization for the remaining life of the
Compare
actual results to project objectives.
(12)
12
Advantages
Good
for complex and big projects as it reduces the risk of ERP projects. Builds documentation library, knowledge management, project communication made easy and reference material. Readily available formats.
(13)
13
Disadvantages
Difficult
to scale down the AIM process for small companies. Cost involved with documenting every task of project tasks. Small customers prefer custom formats to AIM formats. AIM formats are not completely required for simple processes.
(14)
14
Standard myths about AIM Methodology

Many
consultants and project managers think it is too vast and not fit for practical situations which is not true. Consultants think it is the responsibility of project manager alone to know about the complete AIM methodology and not required at consultant level. Too much of documents and template which is not required AIM does not provide flexibility to suit various scenarios / industries. Consultants unable to grasp easily the methodology. Consultants feel it is too difficult to understand themselves and making the client to understand. Clients are reluctant to read the documents and sign off the project deliverables.
(15)
15
Actual Facts about AIM Methodology

AIM like any other project management tool advises the project managers to take best possible decision and provides only a basic framework. It is not mandatory to use all templates. In some of the implementation which are very small. AIM provides lot of flexibility and modify the templates to suit your requirement and convince the client. Consultants should go through the AIM documents and understand what is the purpose of each template and which one will best fit to client based on Business and Implementation approach. The contract entered with client should specifically mention what are the project deliverables agreed as part of the project
(16)
16
Thank You
SLK Software Company Confidential Information. All rightsrights reserved.document cannot be Copied, Re-distributed, Transmitted or Printed without the the written SLK Software Company Confidential Information. All reserved. This This document cannot be Copied, Re-distributed, Transmitted or Printed without written permission of SLK Software Services Pvt. Ltd permission of SLK Software Services Pvt. Ltd
(17)
17

AIM Methodology

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

AIM Methodology

Caricato da

Copyright:

Formati disponibili

AIM Methodology

Click to edit Master subtitle style

A complete, effective toolkit

Pre-seeded content & sample data

Customizable work plans

Detailed Task Description

Project Management Support

AIM : Implementation & Life cycle

There are eleven processes of implementation

A.I.M. methodology life cycle

actual results to project objectives.

Standard myths about AIM Methodology

Actual Facts about AIM Methodology

Potrebbero piacerti anche