Agenda

Item	Description	Link
Introductions	Team introductions as necessary
Project Overview	Workstreams and aspirations / expectations within each	https://bigdigit.atlassian.net/wiki/spaces/VOY/overview?homepageId=2472280264#Charter-%F0%9F%9A%A2 Product requirements
Roles and Responsibilities	Project team setup	Roles and Responsibilities
Ways of Working	Agreed SDLC approach, and supporting systems	https://bigdigit.atlassian.net/wiki/spaces/VOY/pages/2575794214/Development+Engagement+Model#Agile-Process-%2F-Methodology
Business Requirements	Review of business requirements	Product Feature Catalogue
Technical Landscape	Discuss the proposed technical frameworks/patterns/approaches	Technical Architecture & Solution

Actions

Action & Owner	Description
Team	Create & Agree Project Name 01 Apr 2021 PROJECT SUEZ
Mark Blair	Set up call with Sergey V around microservices - potential add dedicated resource to support 31 Mar 2021
Mark Blair / Alon	Provide Luca with access to Angular Playground - holds everything except for base Kendo components 31 Mar 2021
Adam & Steve	Model Knauf fields into DOM 01 Apr 2021
Adam	Building Design into the Process - separate workstream? - do this in big picture 06 Apr 2021
Adam & James	Project Plan / Themes in Big Picture 06 Apr 2021 Big Picture, Miro, and Figma licences from Alon 06 Apr 2021
Adam & Luca	Start cataloguing required components 08 Apr 2021
Alon	Indigina email for Luca 31 Mar 2021
Adam	Get Stuart to manage the feedback / updated process 01 Apr 2021
Adam	Set up regular calls with various stakeholder groups Sprint Pre-Planning Sprint Retrospective & Planning Stakeholder Updates Daily Standups
Adam	Agree reporting with Semyon - by story or by task type (iTrans preferred)

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

Dedicated team - division of responsibilities

...

how do we measure business success of project?
reporting on hours would be by user and task type unless we ask otherwise
budget - what happens when the team structure changes, and what is min/max team size?
sprint pre-planning - dev team & product owner to agree priority & feasibility - flag if any blockers, or technical stories are needed

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

Raised by	Description
Mark Blair	Angular Playground vs Storybook