 |
Page History
...
| Author | Category | Card Title | Comments |
|---|---|---|---|
What went well
| Description | Author |
|---|---|
| Neo4j technical research and DevOps went well | Amit |
| Get clarity with point system | Dimitri |
| The sprint was well planned. | Ming |
| Data have been successfully loaded. Data transformation worked well. | Kevin |
| Have all the information needed to carry out my tasks. | Yizhen |
| Good team work that helped clear potential risks to the project | Ajay |
| Good to have wireframe and also FE team was very help to visualize the project | Ann |
| Scrums have been going well, short and concise. Key information is shared. | Mark |
| Team came together nicely | Ye/Pihl |
What could have gone better?
| Description | Author |
|---|---|
| No proper designated space to manage team documents | Mark/Amit |
| No road map for data milestones, so couldn't map exactly to the FE pages | Amit/Dimitri/Mark |
| More communication between FE and BE so team can understand each other better | Ming/Yizhen |
| Tickets need to be broken down better and need to be documented better | Phil/Ye |
| Need road map for all components to plan for QA activities | Ann/Mark |
| Hard to map tickets in each sprint to QA activities | Ann |
| Data loading tasks were not planned well. | Mark |
Tickets
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
