/
eGov DevOps Partners Operation mechanism

eGov DevOps Partners Operation mechanism

Owned by Gajendran C (Unlicensed)
Last updated: Sept 30, 2019
3 min read

Outsourcing Strategy:

Per env/per state ownership. Incrementally expand capacity and ownership. Current forecast is for 9 - 12 months. Quarterly review and revise.

 

 

Proposal:

  • We need to have a centralised program/Scrum manager to manage and facilitate between Implementation environment requests and partners .

  • Program manager reports to eGov DevOps and Infrastructure Engineering

  • Program manager takes care of the below

    • Owns every env from a single point of contact for both implementation team and partners

    • Monitor all the requests for the right SLAs and assignment to the right vendor.

    • Define SLAs and co-ordinate for closer.

    • Scrum meets for progress, addressing queries and facilitate between eGov DevOps if there are blockers.

    • On-boarding, documenting, training partners for the consecutive environments with the help of eGov DevOps.

    • Weekly reports and analysis on open issues, bandwidth, traction, etc.

    • Exercise priority, workflow, approval, SLA, assignment and address to the right person

    • Process discipline, security best practices despite the magnitude of requests.

    • Audit the workload, introspect, retrospect issues, build reusable utilities, etc..

    • NDA, Documentation of the various technical details.

  • eGov DevOps team manage the below

    • Evaluate partners, Training.

    • Security and Access management to the partners

    • Infrastructure and process management

    • Technical assistance to the partners

    • Unblocking if any hurdles

    • Implement and propagate new changes and innovations to the partners.

Process:

  • Implementation teams or other env specific Infra and DevOps request will be raised through Jira or email tickets.

  • Program manager reviews and modify the SLAs if necessary and updates the request with necessary details.

  • Track and assess the completion of the task from the respective counterpart.

  • Daily scrum meets to understand if there are any blockers or need help

  • Program manager co-ordinates with eGov DevOps team if help needed.

SLAs:

  • P0 - (Should be picked-up immediately/in few hours < 4 hours)

  • P1 - (Same day until EOD < 12 hours)

  • P2 - (Few days < 3 Days)

  • P3 - (Week < 2 weeks)

  • P4 - (Near future/Advance Intimation ahead of 3 weeks)

Type of Issues:

  • Stack: Microservices, ERP, Co-EX.

  • InfraProvision/Troubleshooting

  • NewFeature/Enhancements

  • AccessOps

  • GitOps

  • Deployment Support

  • Releases

  • CI-Pipelines

  • ProductionIssue

  • Troubleshooting

ENVs to be outsourced:

  • State env: As there are more incoming states, every env requires more attentions and quick SLAs from the Infrastructure, CI/CD Pipelines, D2D operations, monitoring, troubleshooting, etc.

  • Internal Dev, QA, Playground (Rainmaker, ERP, CO-EX): Outsourcing Day-2-Day operations will allow eGov DevOps team to focus on enhancements and innovations. Which is crucial to strengthen Infrastructure and DevOps solutions away from existing issues and keeping up-to-date with the Technology and best practices.

Tentative Dates:

  • We have been discussing with 3 partners and evaluating and interviewing the profiles for the fitment of the stack and the skills. (OptIT, GWL, MacroSkies)

  • Oct 1, 2019 On-board partners and train for 2-4 weeks to manage the Internal and Punjab Envs. (Microservices, ERP, Co-Ex, Portal, etc) – Status: Shortlisted the partner and the profiles.

  • Oct 1, 2019 On-board partner for AP. – Status: In progress

  • Oct 15, 2019 On-board partner for Bihar. - Status: TBD

  • Oct 15, 2019 On-board the Program Manager with the skills (DevOps, Technical Documentation, Training)

 

How are we going to monitor: (Sample Dashboard per environment)

 

 

 

Related content