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 |
Roles and Responsibilities | Project team setup | |
Ways of Working | Agreed SDLC approach, and supporting systems | |
Business Requirements | Review of business requirementsProduct Feature Catalogue | |
Technical Landscape | Discuss the proposed technical frameworks/patterns/approaches Technical Architecture & Solution | |
Actions
Action & Owner | Description |
---|---|
Team |
PROJECT SUEZ |
Mark Blair |
|
Mark Blair / Alon |
|
Adam & Steve |
|
Adam |
|
Adam & James |
|
Adam & Luca |
|
Alon |
|
Adam |
|
Adam |
|
Adam |
|
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
Notes
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
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 |
Parking Lot
Raised by | Description |
---|---|
Mark Blair | Angular Playground vs Storybook |