Task created in Product Backlog or Sprint Backlog

Hi Pradeep,

What would you think where the task should be created, product backlog or sprint backlog?

Scrum.org doesn't say where the "task" is created and didn't use this word. But it tells that enough details that changes the progress can be understood in a Sprint backlog. So, answer to your question is sprint backlog, task is a finer piece of work. If product backlog is defined in story wise then sprint back log will have tasks grouped under the strory

Siva

The Sprint Backlog is a subset of the Product Backlog.  The tasks are based on the shared "definition of done" that the team understands to be the overall requirements for delivering backlog items.  The important thing is that the stories end up clearly broken out into tasks by the end of Sprint Planning.  With that in mind, I'm not sure it matters whether the Product Owner breaks out the tasks in the PB, or the Development Team does in the SB, as long as the Sprint Goal is agreed upon and adhered to when determining those tasks.

Of course, the Development Team will typically be more familiar with the tasks required to complete a story, so I would still encourage this to happen in the Sprint Backlog, and to keep the Product Backlog from getting too granular.

Bear in mind that work ought to be planned in a timely manner. The precocious identification of technical implementation tasks before Sprint Planning, when work is still being refined on the Product Backlog and may not yet have been committed to, could be wasteful.

Scrum guide states, the Sprint Backlog contains the Product Backlog items selected for the sprint, plus a plan for delivering the product increment and realizing the Sprint Goal. This provides the guidelines that 'What' is part of Product Catalog and 'What + How' is part of Sprint Backlog; makes more meaningful to have How part (tasks) in Sprint Backlog.