Architect’s Approach to Governance

แชร์
ฝัง
  • เผยแพร่เมื่อ 17 ม.ค. 2025

ความคิดเห็น • 7

  • @AnnaSzabo
    @AnnaSzabo 8 หลายเดือนก่อน +1

    This was an incredible presentation and a really good watch while getting my pedicure done ✔️ Thank you ❤

    • @apexhours
      @apexhours  8 หลายเดือนก่อน

      Glad it was helpful!

  • @dattam8048
    @dattam8048 11 หลายเดือนก่อน

    Good guidance for developers who are looking to become architects

    • @apexhours
      @apexhours  11 หลายเดือนก่อน

      Glad you like it

  • @JonSchleicher
    @JonSchleicher ปีที่แล้ว

    not too much mention of governance-as-code in here...maybe one day salesforce
    a "COE" is either a center-of-empowerment or a center-of-employment. The latter is a middle-management layer that instead of driving quality practices, manages to convince leadership that throwing more bodies in a governance layer is the only way to keep up with the pace of the product teams.
    A governance/coe can be a Center-of-Employment and is a VERY REAL anti-pattern and is by no means a "myth". One of the biggest tells if a COE will fall into an anit-pattern is when there is a practice of functional teams in a "COE" --> release function, architect, product discovery, sustainment, help desk, qa (one function is only capable and responsible for quality in the entire organization ???... ). Not seeing a lot of room for cross-functional teams in these slides, so much for agility, enjoy those pre-built bottlenecks.
    A governance body, as a leadership body, has to be incredibly effective at supporting knowledge sharing, empowering flow, learning, establish the foundation for people and teams to learn and grow, continuous improvement, preventing repeated issues, improving daily work and much more than what is covered
    So much (not all) in this presentation is buds (big upfront design --> sprints --> big bang delivery aka waterfall )
    one other note- PLEASE PLEASE PLEASE DO NOT HAVE A PENCIL WHIPPING/GO NO GO GOVERNANCE PROCESS FOR RELEASING TO PRODUCTION. A release process has to be definitive and that doesn't happen with a random set of individuals that usually have not much more experience than the folks that built the updates but because the organization fundamentally doesn't apply self-awareness to what their coe is doing. What also happens, is that these governance gatekeepers open the gates freely for any governance team development work. People are SOOOO MUCH MORE CAPABLE THE CLICKING AROUND SIGN OFFS FOR DEPLOYMENTS

    • @JonSchleicher
      @JonSchleicher ปีที่แล้ว

      again, a center-of-employment is not a myth, it is very very very very real and hopefully this anti-pattern only impacts an organization and not the Customers its supposed to the support. Hopefully Customers have the law-of-2-feet available

  • @justindixon4068
    @justindixon4068 11 หลายเดือนก่อน

    Have to admit this wasn't a great presentation. The presenters rambled and rarely made insightful comments.