Attendees

Summary

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

What worked?

Good problem-solving from eslam and Yosef to solve the flowchart issue & good direction from mahmoud elbadryDetailed USs and very good adaptation in the breakdown of user stories in release planning from scrum team and Mohsen specifically.

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

Mohsen

1 -There is excellent collaboration between the Dev and QC teams.2- knowledge to EA product to be clear to the team

Moataz1- The USs is way better than before2- Collaborating is better 3- 2 dev members4- TL fully understands the project5- One business person is better than two 6- The data sheet is better and updated than before

Rezk:

A loving administrative effort by Eng. El-Badry.
A great effort and excellent work by Eng. Ahmed Youssef in using the new tool for meta model.
Flexibility in writing user stories by Eng. Mohsen.
Respectful collaboration within the team.
Great work and a cooperative attitude from Eng. Moataz.

ahmed youssef

writing user story with adding more details (good point in some stories, not all )
Knowledge Sharing

Elbadry

Great efforts by great team
Youssef & eslam did a massive work
Eslam & youssef did a massive work
Awesome team spirit
Great support from Mohsen & Moataz
Great follow up with essam & khafagy

What didn’t work?

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

mohsen1- missing roadmap to enhachment product. (enhancement from business starting and from sprintly output → we have to commit in a sync meeting before the sprint planning → we have to become more facilitators and have more adaptation in changes about the business

Moataz

ahmed youssef

What changes need to be made?

Moataz1- fully updated data sheet for system components relationships (po)2- need to add screens of what should be done in (user stories)3- need to classify business rules (users) of the system if it won't be mentioned in an upcoming user story (Enhancement)

Elbadry

The business team raised that we have a delay on tasks, but it's wrong.
Business team escalated a fake status about the deadlines. → Send MPM Report to senior management.
QC time is more than 80 % to be with us.
Conflicts in the requirements in Eslam M side.
Eslam M follow-up.
Raising a fake issue.

Rezk:

Making the user stories sequential at the expense of the requirements.(تم المناقشة في نقطة المهندس محسن خريطة المشروع)

ahmed youssef

Reworking of some pionts need QC to validate the story before planning.
Some bugs were opened not defined in the story as defined in the meeting or calls.