...
Action & Owner | Description |
|---|---|
Team | Create & Agree Project Name PROJECT SUEZ |
Mark Blair | Set up call with Sergey V around microservices - potential add dedicated resource to support |
Mark Blair / Alon | Provide Luca with access to Angular Playground - everything except for base Kendo components |
Adam & Steve | Model Knauf fields into DOM |
Adam | Building Design into the Process - separate workstream? |
Adam & James | Big Picture, Miro, and Figma licences from Alon |
Alon | Indigina email for Luca |
Objectives
Project Plan & Communication - Status Updates, etc
More information on the system requirements
Agreement on agile process, team operation etc
First steps on technical/team standup
Responsibilities - putting items on the backlog, refinement, definition of ready
Tooling - Team Gantt, JIRA, Big Picture etc
Clarification of interactions with other projects
Bounded context & microservices, break down application as much as possible
How to implement the design process within the overall approach
...
Persisted storage layer (e.g. database)
Service definition - CRUD operations
Validation
Interactions with other services?
Frontend Interactions
Split stories into two:
Frontend / Backend
Frontend steps:
Ready for Design
Start Design
Refine Design
Finalise Design (agreed)
Develop Design
Deployment process - allow each service to be deployed independently, allow for A-B testing in time etc (i.e. not monolithic deployment)
iTrans PM - 5th
Backend Dev - 5th
UI Dev (Senior) - Push back a little
UI Dev - Maybe swap for backend?
Risks/Issues
Risk/Issue | Type | Mitigation |
|---|---|---|
Spec not detailed enough in time | Risk | Ensure sufficient detail for development team to start prototype designs using agreed frameworks/patterns |
...