View source for Process - Creating DevOps for an Opportunity

The intention of this process is to standardise the creation of DevOps jobs associated to an opportunity, for PS and R&D to work in a standardized way.

== Process ==
1.            New case is logged on salesforce and a devops job created – This will have a general heading for the project and will become the Parent case. All requests for estimate, spec, development, release requests(if they come through here), bugs/fixes will be added to this 1 case on here. 

2.            All cases from Salesforce will be assigned to the swimlane projects. 

a.            If it is a user story then after analysis a child job will be created and assigned to a member of the R&D team for estimate, spec, development / fix, test, release. The Parent case will always be left on this swimlane.

b.            The case assigned to a member of the R&D team for fix to be done.


3.            The R&D team will work on the case assigned to them and reassign back to the tester. 

Bug fixes will have a comment will be added using '''@boomi_integration''' so the customer can then be updated or specs/estimates issued. 

If estimate / Spec has been produced  a comment will be added using '''@boomi_integration''' so the specs/estimates can be issued to the customer. The case will then be added to the specs or estimates pending swimlane. Once approved a case will be added to the case for this to be scheduled for development.

4.            Owner of the salesforce case will update customer and send estimates and quotes on the salesforce case only.

5.            The child cases will be closed once software is released to test, the Parent case will not be closed until all the jobs and UAT have been done.


With the above this will give us full visibility of what is happening from both salesforce and devops.







[[Category:Processes]]