Please enable JavaScript.
Coggle requires JavaScript to display documents.
Software Arch - 8/25/2020 - Coggle Diagram
Software Arch - 8/25/2020
[Brett] RCA on a one or more issues
Feature Toggles - I
consolidating our various flavors
using them consistently, not misusing them
finding good bounded contexts for microservices - IIII
[Dean] pragmatic patterns for us to follow - IIII5 II
boy scout rule in PRs, even if only slightly better - enforced by approvers
smaller methods, quit adding to the large method
make a helper class
make an abstraction when possible
close feedback loop on gotchas
Brett's factory example
Hopkins blob data break because of undocumented but known WCF change process
put refactoring tasks on every backlog for moving forward (example .svc files moved to factory blah, blah, blah)
Team formation, adding members, working agreements, etc - IIII5 II
Designated Team Lead is the voting member?
Others could attend as well
Post results of our discussions on #team_dev and gather membership from the participation there
Is limiting size even something we care about?
What about rotating members?
1.5x the count of sprint teams
Break into sub-committees to own certain parts
PR Approval Process - IIII5
streamlining it
at least one PR approver per team?
What is the charter/mission of this group?
Shared understanding of technical direction
collaborative decision making/ consensus is the preference
provide direction & guidance to all devs for specific things we should be doing on our sprint teams to improve payroll and move toward target state
guide and protect the roadmap for our modernization work
pragmatic solutions for problems across all teams
populate and prioritize the tech debt work on the non-functional backlog; provide development management with needs to campaign Product to include in upcoming sprints