Before starting any project we need to create a product backlog. It replaces the traditional requirements specification artifacts. This is essentially a list of the goals that need to be achieved in order to create a finished product.

Print is an iteration, a time boxed effort in which we produce a specified working software. During a sprint planning session, we set a sprint goal and create a sprint backlog from the product backlog.

In the second part of Sprint planning session we break down the stories in sprint backlog into tasks which can be tracked easily. The tasks are then checked for dependencies and the required time is estimated. 

This is time where the actual coding, testing, UI designing, technical writeups, etc. are performed. We stand for 55-minutedaily scrum meetings to sync everyone with the latest made development this improve communications.

This is not a separate phase at the end of coding as done typically, rather it is done inside the sprint. When the stories are ready for review, they are tested according to the accep-tance criteria of the stories.
The bug is fixed and retested if required.