M1 Retrospective: What to commit to

hanz105 / INF2001-Team-Project-P8-3

0 stars 0 forks source link

M1 Retrospective: What to commit to #37

Open AstralAurora opened 10 months ago

AstralAurora commented 10 months ago

What has been done in M1 that can be brought to M2, values, good things etc.

StevieeeLau commented 10 months ago

M1 Report's introduction and project scope, can be carried forward to M2.
Software Requirements are done well, therefore there isn't a need to bring them forward to M2.

Cassandra-Fu commented 10 months ago

i. M1 software requirements no change ii. M1 Use Case Diagram must be updated and improved to be carried forward to M2 Diagrams. iii. Work Break Down Structures need to broken down futher into smaller and more specific tasks. iiii. Work Delegation in Kanban Board needs to be more systematic and clear to everyone.

hanz105 commented 10 months ago

Most of the use case descriptions were well done.
Software requirements were well done.

EvanChua22 commented 10 months ago

Use Case Diagram and Descriptions modified further to carry to M2
All the software requirements done well so no need to carry to M2