Agile Sprint Planning

This forum is for members to share and gain knowledge of Project Management. Got a question about project management? Need help with a problem? Wish to offer tips and advice? Post here.
Post Reply
New Member
New Member
Posts: 1
Joined: Fri 07 Mar 2014 6:35 am

Hello to all the community members. I am new in this forum and found this community is highly interesting. I want to know about agile sprint planning if any member has knowledge about this innovation.
User avatar
Site Admin
Site Admin
Posts: 495
Joined: Sat 19 Dec 2009 4:39 pm
Location: London

Hi Bennie,

I'm assuming you've read some of the on-line articles about Sprint Planning, and are no doubt aware it is part of the Scrum framework. I'm guessing you're asking about people's experiences using Sprint Planning.

I've used it on software development projects and found it particularly useful where the customer is not completely clear about their requirements. As each Sprint is between 2 and 4 weeks, it allows you to break the project into smaller pieces. The Sprint is a deliverable on the project, so the customer can provide feedback and items are added or adjusted for the next Sprint. Many of my customers like this approach because they see tangible progress every few weeks and can tweak the product as they go. It works as long as they have time to spend with you at the end of each Sprint.

It's not suitable for all projects, so it's best to think about when you would apply Scrum, and when a more traditional Waterfall method might be better.

Larry Port has put together a very good article on the subject called, Project Management the Agile Way

Hope this helps.
New Member
New Member
Posts: 2
Joined: Tue 19 Aug 2014 6:18 am
Location: Paris, France

Please read this carefully...

During a sprint, the development team delivers a certain portion, or a "slice" of the actual development activity to be carried out as defined in the product backlog. During a sprint, the development activity can include a host of other things in addition to the actual development work. This can include the documentation, user manual creation, testing and debugging functionality, or even checking cross platform compatibility. Each activity during the sprint can be understood as a task. When user stories are transferred to a sprint backlog by the product owner, the development team further segregates each user story into its individual tasks i.e. each story is broken down into smaller tasks to make it more manageable and develop able. Each user story is assigned a story point which determines its potential value. The story points help to generate an estimate as to how many user stories can be included in the sprint backlog based upon the team’s ability to carry out the development.

The entire development is carried out in the form of sprints. Usually, a sprint lasts for two weeks, however, technically they can extend up to three to four weeks depending upon how scum is being implemented by the product owner and the scrum master. Sprints are also known as "iterations" in more simple terms. Sprints are supervised by scrum masters. As per the scrum guide, a scrum master should be a passive participant during the sprint. His or her job is to ensure that the team members properly follow scrum rules when the sprint is underway. At the end of the sprint, user stories are developed into shippable products, each with its own functionality and importance.

Sprint planning meeting
A sprint planning meeting is held before the sprint commences. It is attended by the product owner, the team members, and the scrum master. During the sprint planning meeting, the product owner transfers some of the user stories from the product backlog into the sprint backlog for development purposes. The meeting is actually held in two parts:
  • First half of the meeting. During the first half of the meeting, the product owner explains about the user stories which have been included in the sprint backlog. He or she explains about the acceptance levels and the importance of the user stories to the stakeholders. Team members are free to ask questions to the product owner if they require explanations regarding some of the user stories.
  • The second half of the meeting. During second half of the sprint planning meeting, the team members breakdown the user stories in the sprint backlog into smaller, and more manageable tasks, which are taken up for development purposes. Generally, the team members decide unanimously how to distribute the tasks and user stories among themselves. Team members take up work as per their skill sets and development expertise.
Sprint retrospectives
A sprint retrospective meeting is held after the sprint is over. The main purpose of the meeting is to evaluate the sprint which has just completed, and what lessons should be learnt from it. A lot of discussion occurs during the meeting, and both the product owner and the scrum master try to envision what could possible go wrong in the future sprints. They contribute their expertise as well as their experience, and try to identify impediments, and seek solutions for potential problems which may occur in the near future.
Best Scrum tool ever developed.
Post Reply