In agile project methodology, projects are divided into iterations called sprints, which have set durations and specific goals determined by the entire project team. Sprint planning involves assessing product backlog items, defining tasks, and documenting processes to ensure consistency and repeatability. Regular meetings and reviews at the end of each sprint allow for progress tracking and acceptance or rejection of completed work by the project owner.

2. In an Agile project methodology, projects are divided into
iterations, known as Sprints. Sprint essentially is a set period of
time, during which a specific task has to be completed, and be
ready for use, and review. Depending on the project, a Sprint
may last for as little as two weeks, or as long as a month, or
more. Proper planning of Sprints are the key, to an Agile
project’s success.

4. First, a Sprint planning meeting is conducted, which is attended by the entire
project team, including the business analysts, the testers, the developers and the
product owner. Decisions regarding everything, are made by the whole team.

5. The first thing that is decided on, is the duration of the Sprint. This decision is
made considering many factors, including the maturity of the processes. A team
with immature processes, require a longer Sprint. Sprint mature processes, find a
short duration, most apt.
The Sprint duration that is decided, is kept consistent throughout, till the end of
the project, to ensure rhythm, and system. This also helps make processes
repeatable, and allows understanding of product backlogs.

6. Once the Sprint duration is decided upon, the goal for each Sprint is decided. The
goals are decided based on objectives, and what can be achieved during a
specific time, that could positively contribute, to that objective. A little more than
what can be achieved, is generally planned for, just in case the team finishes a
goal, ahead of time. These extra tasks, are clearly identified as stretch tasks, and
they aren’t expected to be completed.
The team’s previous velocity helps make this decision well.

7. After that, Sprint requirements are clarified. Each item in the product backlog, is
scanned methodically. The product owner, then presents each item, from a functional
perspective. The team, then, discusses the items in detail, and comes to conclusions
regarding what to do, and how to go about doing it. All these discussions are
documented feature by feature.

8. The whole project story is then backed with sketches, frames and visuals so as
to describe its functionality, so as to identify scenarios, when the product is
being developed.

9. After each Sprint is commenced, the project owner steps back to let the team do
their work, as best decided by them. During the Sprints, the team holds regular
meetings, to discuss their progress, and to decide for solutions to the challenges
faced. It is essential for the project owner to attend these meetings (without
participating in answering questions).

10. At the end of each Sprint, the team puts forth its completed work and submits to
the project owner. The project owner then decided to accept or reject the work,
based on the criteria established at the beginning, when the Sprint planning took
place.