# data[].attributes.body
Good food

# data[].attributes.body
New knowledge on handling CTOS report.

# data[].attributes.body
Apparently, we brought forward and burned some points from Sprint 4 for development.

# data[].attributes.body
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...

# data[].attributes.body
Good OT food ,haha

# data[].attributes.body
No outstanding OT.

# data[].attributes.body
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.

# data[].attributes.body
Fail to have deskcheck
Still lot of wastage (bottleneck issue)

# data[].attributes.body
Not enough time

# data[].attributes.body
Forgetting what to do, how to do. Difficult to ask questions.
Not working fast enough.
Missing out on details.

# data[].attributes.body
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.

# data[].attributes.body
macam dun have leh
except go back earlier

# data[].attributes.body
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.

# data[].attributes.body
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.

# data[].attributes.body
To learn up more on the business in order to further understand the background behind each requirement

# data[].attributes.body
Fast engagement from people who needed the help

# data[].attributes.body
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.

# data[].attributes.body
Too much of fields for CTOS, need to wait for real data during integration.

# data[].attributes.body
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

# data[].attributes.body
Cannot receive instruction clearly,
Sometime need to ask many times,

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

# data[].attributes.body
1. User cant confirm the requirements (too much of U-Turn)
2. Not enough time to perform thorough testing

# data[].attributes.body
To refer back to Kanban board.

# data[].attributes.body
More study on project/task requirement.

# data[].attributes.body
Need to reduce other project Q1 issues, but the problem is Q1 keep appearing and Q2 solutions not able to help very well

# data[].attributes.body
Give more effort on documentation

# data[].attributes.body
Incremental progress and understanding of integration specs which is helpful to understand from a specialist POV

# data[].attributes.body
Stamina and patience to persevere to improve understanding and comprehension which takes time

# data[].attributes.body
Vitamin supplement for team to tahan long hours and exhaustion. Or fruits is ok oso =D

# data[].attributes.body
Better sprint planning. Break down the task better into smaller cards.

# data[].attributes.body
Conquer and divide strategy working out better with "development team" & "documentation team"

# data[].attributes.body
Resources like Andy and Lucas are split between multiple projects. PS more impacted then SE currently as SE at this stage still underutilized.

# data[].attributes.body
Work on weekend (Saturday)

# data[].attributes.body
3 points is underestimation for the Customer Onboarding stage for Context Architecture =(

# data[].attributes.body
Deskcheck KO this sprint 3

# data[].attributes.body
less burger

# data[].attributes.headline
Andy to prepare ERD for ACP (1st draft by 11th May)

# data[].attributes.subject
Andy to prepare ERD for ACP (1st draft by 11th May)

# data[].attributes.headline
Discuss with Foong Yen for 1st level PCS support issue (Joe)

# data[].attributes.subject
Discuss with Foong Yen for 1st level PCS support issue (Joe)

# data[].attributes.headline
Follow up with Ben Chee on security matrix issue (Joe)

# data[].attributes.subject
Follow up with Ben Chee on security matrix issue (Joe)