Retro AMB #2 by Chen Joe

ZH

y_zhihon — 2018-04-27 08:48:05 UTC

Good food

Jimmy

2018-04-27 08:48:11 UTC

New knowledge on handling CTOS report.

Joo Hui

2018-04-27 08:49:21 UTC

Still doubtful of feasibility and effectiveness of Context Architecture Diagram in the form we are using it and how it is actually going to help in terms of long-term referencing or just create more unnecessary unwarranted constant reworks or lead to more generation of further documentation. This task does feel redundant if not properly managed and handled...

Conifa

ndawula75 — 2018-04-27 08:49:26 UTC

No outstanding OT.

Jason

2018-04-27 08:49:31 UTC

Apparently, we brought forward and burned some points from Sprint 4 for development.

Ding

dingchenw1234 — 2018-04-27 08:49:34 UTC

Good OT food ,haha

Lucas

2018-04-27 08:49:35 UTC

1. Initial Sprint Dev Point was 33. Managed to burn more points up to 49.
2. Able to clean up most of the linkage problem from Customer Prospecting up to Customer Onboarding.
3.

Joe

ckkjoe — 2018-04-27 08:50:07 UTC

Fail to have deskcheck
Still lot of wastage (bottleneck issue)

ZH

y_zhihon — 2018-04-27 08:50:14 UTC

Forgetting what to do, how to do. Difficult to ask questions.
Not working fast enough.
Missing out on details.

Conifa

ndawula75 — 2018-04-27 08:50:15 UTC

Not enough time

Jason

2018-04-27 08:50:24 UTC

1. Not familiar with the business of Commercial Loans.
2. Constantly changing FSD and its contents are not really uniform between mockup and field descriptions. Some field parameters are also illogical.

Joe

ckkjoe — 2018-04-27 08:50:31 UTC

macam dun have leh
except go back earlier

Mel

meliza_caroline018 — 2018-04-27 08:50:41 UTC

1. Progress on the development much more better than before.
2. At least we reach Chapter 6 for our documentation. (Half way to go)
3. there are context diagram and field mapping to refer to.

Mel

meliza_caroline018 — 2018-04-27 08:50:46 UTC

1. Too many documentation to do but too little time.
2. Not much time for me to review and brief juniors. Therefore, there might be items missing from documents.
3. Things were changed in middle of sprint and we are nt focusing on our kanban board.

Jason

2018-04-27 08:51:09 UTC

To learn up more on the business in order to further understand the background behind each requirement

Andy

2018-04-27 08:51:25 UTC

Fast engagement from people who needed the help

ZH

y_zhihon — 2018-04-27 08:51:51 UTC

Take down notes. Ask more questions. Work faster and more effectively (As in doing everything correctly). Understand more and better the terms, and on what we need to do.

Andy

2018-04-27 08:52:02 UTC

1. Too many last minute meeting, presentation, requirements,
2. Difficult to get engagement from COE
3. Lucky not too many demanding task from programmer, else we are so screwed

Jimmy

2018-04-27 08:52:02 UTC

Too much of fields for CTOS, need to wait for real data during integration.

Ding

dingchenw1234 — 2018-04-27 08:52:04 UTC

Cannot receive instruction clearly,
Sometime need to ask many times,

Lucas

2018-04-27 08:52:22 UTC

1. Better FOOD. <> burger.
2. Showcase preparation
3. Table design for ICA (since we are not using Analyst)
4. No work on weekend

Lucas

2018-04-27 08:52:36 UTC

1. User cant confirm the requirements (too much of U-Turn)
2. Not enough time to perform thorough testing

Mel

meliza_caroline018 — 2018-04-27 08:53:39 UTC

To refer back to Kanban board.

Jimmy

2018-04-27 08:53:56 UTC

More study on project/task requirement.

Andy

2018-04-27 08:54:02 UTC

Need to reduce other project Q1 issues, but the problem is Q1 keep appearing and Q2 solutions not able to help very well

Ding

dingchenw1234 — 2018-04-27 08:54:15 UTC

Give more effort on documentation

Joo Hui

2018-04-27 08:55:35 UTC

Incremental progress and understanding of integration specs which is helpful to understand from a specialist POV

Joo Hui

2018-04-27 08:56:51 UTC

Stamina and patience to persevere to improve understanding and comprehension which takes time

Joo Hui

2018-04-27 08:57:54 UTC

Vitamin supplement for team to tahan long hours and exhaustion. Or fruits is ok oso =D

Joo Hui

2018-04-27 09:00:11 UTC

Better sprint planning. Break down the task better into smaller cards.

Joo Hui

2018-04-27 09:00:52 UTC

Conquer and divide strategy working out better with "development team" & "documentation team"

Joo Hui

2018-04-27 09:04:03 UTC

Resources like Andy and Lucas are split between multiple projects. PS more impacted then SE currently as SE at this stage still underutilized.

Joo Hui

2018-04-27 09:08:48 UTC

Work on weekend (Saturday)

Joo Hui

2018-04-27 09:10:12 UTC

3 points is underestimation for the Customer Onboarding stage for Context Architecture =(

Joo Hui

2018-04-27 09:17:14 UTC

Deskcheck KO this sprint 3

OT every weekday until 21/5 Showcase

ckkjoe — 2018-04-27 09:24:22 UTC

DeskCheck every Tue and Thurs (Lucas)

ckkjoe — 2018-04-27 09:24:40 UTC

Food Manager (Jason)

ckkjoe — 2018-04-27 09:25:30 UTC

less burger

Andy to prepare ERD for ACP (1st draft by 11th May)

meliza_caroline018 — 2018-04-27 09:25:42 UTC

Get Vitamin (Mel) and Fruits (Joe)

meliza_caroline018 — 2018-04-27 09:28:25 UTC

Discuss with Foong Yen for 1st level PCS support issue (Joe)

ckkjoe — 2018-04-27 09:32:43 UTC

Follow up with Ben Chee on security matrix issue (Joe)

ckkjoe — 2018-04-27 09:45:14 UTC