ServiceNow Adaptive Implementation framework

[rajneesh7]

ServiceNow Adaptive implementation framework (SAIF) is a custom or an approach to deploy / deliver the instance. 

SAIF covers the best practices and methods to implement a solution - it has 4 main pillers

• ServiceNow Implementation Methodology (SIM)
• ServiceNow Technology
• ServiceNow Collateral & Assets
• ServiceNow Expertise

and the end requirement behind using SAIF would be 

• global consistency
• flexible
• support
• Dependable / Reliable

when we start with SAIF we simply talk about 5 main phases

• Initiate
• prepare
• Create
• Transition
• Close

all the phases above are included in SIM (ServiceNow Implementation Methodology).

since we started talking about SAIF lets list out some of the benefits of using SAIF.

• this is the best and fast method to deploy the solution to customers starts getting the outcome in very fast manner.
• customers get a dependable, repeatable, and efficient deployment using SAIF
• SAIF provides the best delivery approach to meet the demands of even the largest and most complex global customers
• SAIF utilizes ServiceNow’s core platform technology and applications such as: Project Portfolio Management; Agile Development; and Project Portfolio Suite’s etc. 

now when we have phases in SIM lets start with 

• Initiate :- 

this is a phase where our outcome is focussed to a set of document or notes related to what exactly needs to be accomplished. This is similar to define phase of SDLC where we need to document and define our objectives. During this phase there will be iterative interactions with clients / different stakeholders or the customer's for defining the end requirements.

• Prepare 

The second phase in development has always been crucial and critical. during prepare phase our focus is always towards designing the solution prototype or making the architecture with functional goals. here our end goal is to have at least 3 documents - BRD (business related document), FRD (functional related document) and a solution design(workflow). Based on these documents our other phases will be moving forward. we can have initiate a prepare phase together to get a quick and transparent design but it will add repetitions due to interference from other stakeholders. 

• Create

It is always recommended to start with this phase post we are completely prepared with the documents. In this phase generally develop the solution. 

in terms of implementation we work with customizations of instance to achieve the end result for customer. This phase includes UAT documents and other points highlighted during the scrum calls. 

• Transition

This phase is the deployment phase. It always starts with deploying the solution to dev instance and than move to production post successful testing by end users.

•  Close

This phase is a definite duration where we have post deployment supports and addressing the queries raised by stakeholders / end users. any of the minor query needs to be looked at a broad level and need to be highlighted and documented properly to keep the production environment intact. 

all the above phases are very crucial and should be followed in sequence to get a result faster.

thanks - Raj 

[G Balaji]

Looking forward to detailed write-up on phases. Thanks.

[Johny2]

Is there some training materials on lxp portal? Or how can I prepare for SAIF certification and how can I take that certification?