Open HarshadRanganathan opened 2 years ago
Feedback form, Learning sessions, sharing credit, Rotation of scrum master, Rally updates, PR reminders
Video calls Tech Lead Feedback Learning Sessions Sharing general updates, what's happening around us, future roadmap with the team Thank you's
Achievements Journal, Team Responsibilities
Work assignment, holiday plan Assign work for each resource each day Have some docs in backlog that could be picked up if blocked on any other issues
Support team with processes rather that as an individual e.g. docs
Discussion Points:
[1] Lack of motivation within the team [2] Collaboration with external teams [3] US delivery management without supervision/support [4] Pre mortem goals Build architecture patterns for the cloud More automation around Infrastructure Provisioning Roll-out Well Architected framework for - AWS, Kubernetes Increased collaboration with other cloud teams Evolving Platform Team concept - Increased collaboration with Platform Tech Leads Building self-sufficient team [5] External Comms [6] Individual feedback [7] Support tasks [8] Exposure to team around - Support, Debugging, Prod Release [9] Rotation of responsiblities [10] PR's
Also, things to be considered for cloud migration –
Aspect | Standalone Application | Capability on Platform |
---|---|---|
Architecture and Security Reviews | Get proposed arch and infrastructure patterns reviewed and approved by Security Team | Adopt the existing security patterns and go for security review in case of any major arch changes |
Infrastructure | Build new environments from the ground up | Leverage existing and provision additional resources as necessary |
Implementation Strategy (CI/CD, Code, Test, etc.) | Set it up as you see fit for team. Can adopt patterns from the existing teams as well. | Embrace the practices from the platform engineering team and add additional ones if necessary |
Code Starter Kits: | Build one news and/or adopt and customize existing ones from other teams | Adopt existing ones from platform teams and customize components if necessary |
Community Support | Team will get up to speed on the UHG ecosystem, procedures and controls but can get additional support as needed | Help on offer from Platform team. Can't expect Platform team to support us in every step of the way though! |
UHC.OPEN/Code reusability | Isolated applications have limited opportunities for inner source. Right mindset can still get things done. | Platform Engineering opens up synergies for collaboration and reuse. |
Technology Upgrades | No dependency on other teams to pilot things. Free to execute disruptive things as long as business is not impacted | Collaborate with Platform team on new implementations. Need to take the entire platform ecosystem into consideration for impact! |
Cost | It depends on what we can reuse? Should also take time invested by team in learning and building everything from the ground up | Reusability plays a big role in cost numbers |
Speed to Market | It depends on what we can reuse? Should also take time invested by team in learning and building everything from the ground up | Reusability plays a big role in speed to market |
Enterprise Direction | Isolated applications are still in use, depends on the use case and timeline. | Platform Engineering is the new normal! |
https://threadreaderapp.com/thread/1542061516912037890.html
Questions to ask to determine whether something is really urgent
https://martinfowler.com/articles/scaling-architecture-conversationally.html