I want to ask for example for our case , we divide User story into : Front-end Task , Back-end Task , e2e task , for me for the Front-end task it contains a lot of things to do m to implement and to fix , So should I suggest during the retro that we should divide the Front-end task into more smaller tasks ?
Hi , thanks for your reply , currently I don't feel in good situation ,because while planning the User story will be divided in Front-end Task and Back-end Task , an d the front-end should cover all the details UI UX and specific scenarios .., so currently I asked that front-end task should be divided in small one better for review and testing and even implementation
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I want to ask for example for our case , we divide User story into : Front-end Task , Back-end Task , e2e task , for me for the Front-end task it contains a lot of things to do m to implement and to fix , So should I suggest during the retro that we should divide the Front-end task into more smaller tasks ?
Hi Ahmed!
Yes. It will be better if the frontend tasks are further broken down for the ff. reasons:
It will be ideal if you’re able to raise this during your retro. Hopefully, I answered your concern.
Hi , thanks for your reply , currently I don't feel in good situation ,because while planning the User story will be divided in Front-end Task and Back-end Task , an d the front-end should cover all the details UI UX and specific scenarios .., so currently I asked that front-end task should be divided in small one better for review and testing and even implementation