Please enable JavaScript.
Coggle requires JavaScript to display documents.
Product (risks (Lack of an architect (On the ground to help guide, sell…
Product
risks
TeamTurnover
Skillset seams to have the correct skill sets
35 points per sprint
Companicy planning
Lack of communications between finlocker and daugherty development teams
Client has an issue prioritization of backlog
Id Single product owner
No one to break ties between the product owner
Aglie training for FinLocker
Versioning between Client versions of the product
lack of a stagency
Lack of an architect
On the ground to help guide
sell them on the value of architect
Team self architect
Senior developer having the role
Don't call them an architect
cicd complainence
Operational
more than one person to do deploment
Dev Ops
Code Reviews
Document the pipeline
UI / UX Relationship
VP Relationship
Ownership of Features bounce between people
Micro Services adds complexity
pains / concerns
pain points
Database
Code first
schema
single ownership
No Architect on the project
have someone take less points to do architectural role
Lack direction on architecture
performance issues
solution with over 100 projects
Split up Release issues
PFM performance issues
implement lazy loading
package updates
Backend
SQL query optimization
Backend full data set
communication channel between development teams is very important
Slack
Open channel to communicate with FinLocker team