Good with 3-6 people who are prepared, ie. what are the designs/requests/requirements. Many times PM thinks its a small feature or vice versa when all engineers

Good with 3-6 people who are prepared, ie. what are the designs/requests/requirements. Many times PM thinks its a small feature or vice versa when all engineers give a big/small estimate; they get a reality check, same can be said about backend and frontend. And it is good to discuss different PoV between the numbers. I don't think you necessarily need the poker meeting part if you are able to prepare, discuss, estimate with other means; but if you have team members not able to put the time in for whatever reason it can be good to put some scheduled time in for it.