Showing posts with label Deployment Checklist. Show all posts
Showing posts with label Deployment Checklist. Show all posts

Wednesday, April 1, 2009

Who suppose to create a SAP deployment list?

Who suppose to create a SAP deployment list?


In our SAP BI project we are having this debate, who supposes to create a deployment check list. Is this Developers Job or is it Netweaver job or is it QA job. We all discuss on this topic.


As my 4+ SAP experience and SAP CML experience, it always developers who create a deployment check list with fully coordinates with QA and Netweaver. In this same organization, in SAP CML project, ours all Deployment Check lists are created by developers. So I believe in that school, that says “Deployments check list is purely developer’s job”. That we did in SAP CML go-live time.

Now this SAP BI, where all BA/PM and developer are arguing that it’s QA job. So guys in SAP BI projects now I’m creating a Deployment Check list, wow.


This is not very easy job. First get Change Review Number from CRC(Change Review Committee). After that document all changes to be happen in production. After that book a meeting with Netweaver, Developer, PM, BA, DBA.. etc. We mostly do meeting on every Wednesday. So today we have that meeting. Then document all steps need to perform during deployment in list. That includes your backup plan. After everyone agree on the list, that don’t happen in one short. You have to draft and then redraft until all agree. If all agree then finally is QA Sign off on deployment check list.


When QA finally gave sign off the list. Every thing needs to get in production move into production. One more thing you have to save this deployment check list in appropriate folder. Then send document link to whole team via email. We are saving all deployment check list in Deployment folder which is under QA folder which is in SAP BI folder. Mostly all clients do deployment on weekends.

Monday, March 23, 2009

SAP BI 7.0 Deployment Checklist

SAP BI Deployment Checklist

Hum, today we have some job in SAP BI. We are going in huge massive development in production this weekend. So QA sign-off will be in this Friday. I don’t know how the things move. I really have nothing to post at blog. Just some scrap. The big deal is creating deployment check list and then follow up sign-off. Let see what deployments check list is. Deployment Check list is step by step jobs/steps, responsible person who initiate it and estimated time process will take to complete. As well as how jobs inter dependent with each and which follow what. That’s it. It gives clear idea to team and to netweaver guys. This give clear pictures, how to transport and what is coming in production.

Here are more details of Development Checklist:
√ Change Review Number, if you have any number
√ Project Name
√ Deployment coordinator
√ Target Environment, e.g. Production
√ Task number: This is a Column having Task number. Start with Init
√ Task Description; Column
√ Person Responsible ; Column
√ Dependent Tasks; Column
√ Start Time ; Column
√ End Time; Column

This is typical one. We can add more stuff like the following tables:
√ Dependencies (Developers note: All object dependencies should be included in your project. Please check with others who might be using the objects to ensure they can be moved within your project and on your date requested)
√ Special Instructions(Developers note: Please include any special instructions or manual processes that also need to be completed for this deployment)
√ Special Test Requirements (QA note: Are there any special needs required in the testing environment (ie. Simulating tests on different run dates))
√ Data Requirements (QA note: Are there any special data requirements (ie. Specific test cases, golden data refreshes, etc)
√ Attachments
√ Contacts: like Contact Name and Phone number
√ Back out: If the programs that we are running are failed then we can clear the data in the tables and reload once again
√ Escalation Plan: In the event of any failure with data loads, the team member will immediately phone the deployment coordinator. The deployment coordinator will communicate to the team through a group email the status and if necessary contact the dependent resource and advice of new times.