Attendees

Summary

A sprint summary of what worked and what didn’t work.

What worked?

- What processes worked?
- Did the team try something new that worked?

mohsen

I am pleased with the drawing concept proposed by Islam Rizk
Eslam Rezk:
1. sprint simple , flexibility
2. cooperative team
3. user story and task is clearness
4. real bugs

(Moataz)1. More flexibility in (sprint 2)2. More workarounds by Dev team help business logic3- more than 1 spike made by Dev team for EA graph model4. More cooperation by the Business & Dev team 5. Flexibility in meeting time

The user story was good in writing the description, not like sprint one.
mohssen (supporting and fast replay ) .

What didn’t work?

- What prevented the team from achieving a goal?
- What was a source of frustration?

There are some details in the project not good in the implementation, and that make conflict with the business need. → We have to commit in sprint planning attending (Scrum team)→ We have to listen to sprint planning record if we missed the meeting (Scrum team)→ We have to commit on fully understanding the USs as we can ------------------------------------------------------------------------------------------------------

Eslam Rezk::
for the first time there is no something prevent achieving goal

mohsen

the devolpment team not responded to study some requirements
The product still doesn't work dynamically

What changes need to be made?

- change time standup to 10 am

There is no documentation for the old version of the system

Eslam rezk:i need more speed in accepting merge requests → Communication

(Moataz)1- Need to specify in US enhancements that reflect on the same logic or the whole system 2- need to do more exploratory testing for the whole system to cluster bugs and do more enhancements