3 ms·
An enterprise would have a process for you to follow. It will most likely mandate that for each change / deployment you will have to submit an Request For Chang
by ToFab123 8y ago
An enterprise would have a process for you to follow. It will most likely mandate that for each change / deployment you will have to submit an Request For Change (RFC) explaining the purpose of the deployment, backup procedure, roll back procedure. The will have a form you to fill out.
It will, with almost certainly, not be you that performs the installation / deployment. It will be someone else and he will use the instructions you provide in the RFC
<How will I manage to keep the software updated with the latest features
You will not or rather, every time you want to update it you must submit a new RFC. Enterprises are not interested in "the latest" features. The are interested in stability. So a stable product might never be updated unless there is a compelling business case for why it should be updated.
You will (most likely) not get access to the servers or infrastructure and you can not just log onto some server and upgrade / change something. Everything you do will have to be tested and approved in multiple environment (test and preproduction) before it hits production
- tixocloud 8y agoThanks - I'm assuming that every enterprise could potentially have their own process/infrastructure of which we'll have to decide how we can fulfill? Is it common to say we can serve enterprises and then after contract negotiations, build the deployment specifically for the client? I've seen virtual appliances, physical appliances, zipped files, etc. but not sure what's the most common or easiest method. Seems like there isn't an easiest/standard method and it differs client by client.
- ToFab123 8y agoYes, all have different processes, but they all speak the same language. You should take a 1 - 2 days course in ITIL, so you use the same terms as they do. https://en.wikipedia.org/wiki/ITIL https://en.wikipedia.org/wiki/ITIL