Anyone has experience with creating a project plan/checklist for software implementation? We have a vendor selected and need to implement the product. Appreciate any suggestions!
Thanks you Vincent. I agree testing would be a must for my project. I am not able to find any good templates. Do you recommend any templates that I can use?
A few of the many things to consider (depending on the scope of the implementation):
1. Data migration
2. Rollback plans
3. Integration with existing systems
4. Custom reporting
5. Training for your operational support folks
Kiron
Thank you Kiron for your valuable response. For the Rollback plans what steps(deliverables) would you consider putting in the work plan?
...
1 reply by Kiron Bondale
Nov 02, 2017 3:03 PM
Kiron Bondale
...
Chetna -
A rollback workpackage would usually include some of the following deliverables:
1. A plan including details on the conditions to trigger rollback, as well as any assumptions & constraints
2. Scripts, code or manual procedures to perform the rollback
3. Verification of the rollback process in a non-production environment
Thanks you Vincent. I agree testing would be a must for my project. I am not able to find any good templates. Do you recommend any templates that I can use?
Appreciate your time! Saving Changes...
Drake SettsuProject Manager / BloggerHi, United States
Have a risk assesment meeting with all the parties that will be using this software.
Make sure you have a disaster recovery plan inplace to properly backup your system and restore it in the event of a disaster. Saving Changes...
Thank you Kiron for your valuable response. For the Rollback plans what steps(deliverables) would you consider putting in the work plan?
Chetna -
A rollback workpackage would usually include some of the following deliverables:
1. A plan including details on the conditions to trigger rollback, as well as any assumptions & constraints
2. Scripts, code or manual procedures to perform the rollback
3. Verification of the rollback process in a non-production environment
Kiron Saving Changes...
Daniel KneipPM III| Moda HealthPortland, Or, United States
For the software go-live, I would normally create a separate go-live plan that contained the rollback plan in case things don't go as planned. In the work-plan I would track a task to develop and gain approval on the implementation plan. For Vendor software implementations, a good place to start is to ask the vendor for their project plan and use that as a starting point. Obviously you will have activities that may not appear on their plan. Marketing, internal documentation, etc. Saving Changes...
also consider the possibility to test the new software on a subset of your business/final users, after install it/configure it and migrate data to the new system. Maybe is later for this checklist on choosing new software: 1. Is hosted on the cloud or just must be installed on your enterprise servers. If installed, can be used from the internet on the future? 2. Require some concrete operative system or browser to work or is open to any OS, any browser, including mobile browsers. 3. I suppose the interface is a web app, is responsive? how is the experience from a tablet or mobile? Have a mobile UI available? 4. Who manage backups? Is easy to export all user data for a future provider change? 5. Is secured, both the server architecture and the client app? What maintenance need on security (minimum is update server software versions). 6. Is ready for future secure logins (digital certificates, LDAP servers, etc.)? 7. Are audits implemented on code? Can I trace who and when logged in and their activities on the app? 8. Are software architecture compatible with my organization standards and policies? 9. Are software prepared for high availability? Can I install a servers cluster, with no singular point of failure, now or in the future? If is an online product (SAAS), do you provide redundant servers to host my app and data? Do you sign a SLA (service level agreement) on request? 10. What support levels and maintenance contracts are available? 11. Do you provide training? Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
If your software is SAP then you have to take a look to the SAP´s implementation process. That will determine your plan. Some other software packs too. Beyond that apply systemic thinking. Do not think that it is about to implement software only. All your organization will be impacted. To understand how to apply it here an article I wrote and was published by the PMI and the IIBA as "best practices". Perhpas it will help you as a guide: https://www.projectmanagement.com/blog-pos...-right-solution Saving Changes...
Were you ever able to find a template? I am looking for something myself... has a nice thorough implementation plan (deployment, rollback, communication, training, etc). Not just a quaint little checklist. Here I can't find any good documents.
...
2 replies by Mary-Catherine Gerrey and Patricia Reigstad
Aug 28, 2019 10:32 AM
Patricia Reigstad
...
Mary-Catherine, did you find a template? I am in the same situation as you were in January. Thanks in advance.
Aug 29, 2019 8:24 AM
Mary-Catherine Gerrey
...
Unfortunately no. I had to piecemeal something myself together. I'm no longer at that company so I can't send you a version of what I had. I had sections like communication plan and testing plan. Implementation plan is different than deployment plan (which was a fun debate to have with people).
"In the real world, the right thing never happens in the right place and the right time. It is the job of journalists and historians to make it appear that it has."
