Mais conteúdo relacionado

Similar a DevOps Journey - BCITO Te Pukenga Presentation - Copado additions v2.pdf(20)

Mais de Anna Loughnan Colquhoun(20)

DevOps Journey - BCITO Te Pukenga Presentation - Copado additions v2.pdf

  1. An evolutionary DevOps journey at BCITO Te Pukenga.
  2. BCITO Te Pukenga
  3. The Journey Three years journey Three phases 1.Continuous deployment culture 2.Moving to one integrated platform 3.Integrating Automation tools with our new environment
  4. DevOps cycle
  5. First Year Coach the team in Agile delivering Be cohesive as a team and not working in silo Have process in place so that we were not constantly reactive to request of the business Somewhat implement Scrum/Lean framework
  6. Second Year Team that adapted to a new way of work jumped on the Agile Train Employed new staff – looked at mindset and adaptability first and good strong engineering skillset second We focused a lot of style of communication for each team and how to collaborate with the business
  7. Third Year • As the team we started the DevOps way of Code – Test – Deploy – Release • Started implementing automation tools and improving our Quality Test Strategy • Fixed tech debt – our code coverage was 5% we needed to be at 75% • Then we looked at Copado – towards the end of year 2022
  8. Gap Analysis • Copado Team can access to a business case tool • They helped us and advised through the process, and it was very transparent • We reviewed Bitbucket, Azure, AWS, but Copado still scored high as fit for purpose CI/CD tool for our environment
  9. Copado Salesforce Continuous Deployment ▪ The GSD Team is currently manually deploying Hapai changes into Production. ▪ This creates many inefficiencies such as: ▪ Manually tracking metadata changes ▪ Manually running tests, not having a shared system of record ▪ Inefficiencies in rolling back deployments ▪ Lead time between development and feature in production is currently 4 weeks ▪ Out of sync sandboxes causing unnecessary overhead and difficulty for development Problem to Solve ▪ Copado is native to Salesforce. ▪ The Delivery Team tested a couple of tools Bitbucket and Copado ▪ Bitbucket required external knowledge or an investment upfront ▪ Copado is known by an extensive dev network globally, and also both of our internal delivery team is Copado certified which means internal experience already. Market Analysis ▪ Copado is used by a large number of global clients (Coke, Banking and other Government agencies). ▪ Provide an extensive network of user support ▪ Upskill our user with Copado Academy ▪ Once implemented is easily scalable Customer Segments ▪ The team will naturally evolve in a DevOps structure • Release Manager • 2 Admin users ( shared between PO, Agile Team Lead, Test Lead) ▪ 3 User Admin (these will be shared between Carlo, Vasu, Bill and one tester) Delivery Structure ▪ If teams can coordinate more easily without being burdened by inefficient processes, they have more time to deliver features. More value is delivered to the business. Mission & Vision ▪ N/A. As mentioned there are many tools out there that enables continuous delivery of features and value. However, we found that since Copado is native to Salesforce, and due to the inside skills and knowledge it would be easier to implement and maintain the tool. • Also cost wise it is quite competitive with the other tools. Competitor Analysis
  10. Deployment Tool Highlights_Copado • Deployments from one org to other org for both Metadata and Data Deployments are handled • User stories will be synced with Copado hence can select and commit the data to the feature branch accordingly • Git operation are performed very well to the repos • Can track deployments under user stories to track the stage of deployment reached • It has an inbuilt apex test run and static code analysis that helps the deployment process alongside better error handling • Minimize overlaps and component conflicts resolution on Metadata • Supports goal of accelerating releases, allowing minimum risk to deployments providing insight into performance through analytics • Package Once, Deploy to All- destructive pipeline creation ‘mass back promote’ from an upper environment to all of the lower environments that are behind, with a minimum of 3 clicks!
  11. Return on Investment • It will reduce the efforts to create package.xml manually and deploy the changes • Another positive impact is this can track commits to an org to iterative if it's traversed in an organized way and does not need separate maintenance • Copado provides a complete package of maintaining the development and repositories in a common platform. When pipelines are set that changes will move from one org to the final org in a very organized manner • Creates pull requests and performs static code analysis at the time of deployment of the changes. One can choose if we need to deploy all changes • Automates many of the manual, repetitive tasks while also providing wizards for on-boarding and repository-related tasks. • Copado standardizes and automates complex deployments across all environments thus speeding up deployment time while greatly reducing errors and failed deployments.
  12. Copado Implementation : • We were assigned an implementation team. • We had few scheduled weeks of collaboration between our delivery team and the Copado implementation team • We had training from Copado on how to kick it off once implemented. • We have regular monthly meetings with Copado to check how we are doing, and if there are any issues that they can address • You really build a partnership with Copado and that they are not just your provider
  13. Life with Copado : • A release is taking us between 5-20 mins compared to 6 hours. • Overall team increased happiness and job satisfaction. • The team has more time to innovate and continuously improve. • There is overall less stress • Quality has improved. • Copado keeps all the environments in sink. • If something goes wrong, Copado has the ability to address it quite well.
  14. In conclusion : • Establish a good team and culture that foster collaboration and innovation. • Implement good release process practices that initially doesn’t involve automation for the sake of automation. • Clean up tech dept • Integrate automation tools • Reach out to Copado if that is something you would like to pursue. • Thank you ☺
  15. Kia ora from Copado
  16. Who is Copado? ‘20 VALUE STREAM MGT ‘22 DevOps Exchange & Testing ‘20 DEVOPS ANALYTICS ‘19 DATA DEPLOY ‘19 CONTINUOUS DELIVERY ‘18 COMPLIANCE HUB ‘17 VALUE BASED PLANNING ‘16 COLLABORATIVE DEVELOPMENT ‘15 RELEASE MANAGEMENT ANY CLOUD ! Labs ‘20 Labs ‘20 Summer ‘21 Summer ‘21 Pilot ‘21 ‘21 ‘21 ‘21 CLOUD SECURITY #1 DevOps For Salesforce 1200+ Customers Low-Code Leader Multi-cloud SF Native UX 70K Best Support $1.6B Valuation 500+ Employees $260M Invested Trained & Certified
  17. How can you start your DevOps journey?
  18. Why Customers Purchase Copado Step 1) Register on Trailhead
  19. Why Customers Purchase Copado Step 2) Register on the Copado Academy (
  20. Connect with us Managing Director APAC Alliances Director ANZ/SEA +61 452 438 678 Linkedin +61 420 582 272 Linkedin