Draft of process description

[marcoala]

Readable version of this proposal:

https://github.com/festicket/front-end-meta/blob/marcoala/process/conventions/process.md

[rlengvenis]

I would say this step should be done before estimations. Imagine a case, we agreed to complete X tasks during a sprint. When a person starts to work on a task, he suddenly finds out, that backend is not ready, or some other stuff is missing, than needs additional time. Thats were we finish with < 2 tasks done a week.

The way I see it. Everyone should spend 20 mins before sprint planning to get accustomed with tasks and see if there are any inconsistencies (BE from BE perspective, FE from EF and etc).

Then, during sprint planning we will be able to address these things and can use free amigos approach to deal with all issues before doing estimations what tasks will be done during next sprint.

The way we did in my previous job is that we split tasks between team members and did 20min reviews each taking to look to 3/2 tasks. So no need to you Marco to look at all tasks by yourself

Without 20min reviews we are having meetings, where noone knows deeply all the context around the ticket and a lot of issues are missed during estimation

[marcoala]

To address the size of the ticket we have the backlog grooming session (aka preplanning).

If you discuss every ticket in details during planning/preplanning you will have constantly half of the team idle during the meeting, since only a few people work at each ticket.

Three amigos can be done between preplanning and planning. But when you pick it up you should verify that everything is clear to all the people involved.

Also that is the complete list of checks, hopefully, a good part should already be covered during the meetings, so when you pick the card there is very little to do.

In general, I think that the main point is what to do, and what is the deadline to do it (before start writing code). If you want to do that slightly differently and before is completely up to the implementer.