What do i Know?

Sprint Planning [Sprint Meeting]

What is a Sprint?

A Sprint is a set period of time during which specific work has to be completed and made ready for the review. 

Typically, a sprint is about 2 weeks long and the stories/tasks taken for that period should be completed with in that time. 

Let us know certain things before going further in our discussion like product backlog , sprint backlog, sprint dashboard, stories, tasks, story points, backlog grooming, backlog refinement meeting etc.

A story can be a small thing like adding a button, a user to the system, discussing with the client etc. 

A task can be little more than a story that requires more effort like creating a basic login for the website, changing the database model to some extent, making calls to get new customers etc.

Product Backlog:

You can create as many stories/ tasks/ issues you can to deliver the product according to the requirements. In this backlog, all the stories/tasks/issues are related to that particular product itself.

Sprint Backlog:

While in the sprint meeting we add some stories/ tasks/ issues to the current sprint. Whatever are being added to the current sprint are named as sprint backlog items.

Daily Scrum [Stand-up]: 

Typically in a scrum team, people have a daily stand-up meeting for 15 minutes just to let the other team members know how they are doing with the tasks/ issues assigned to them.

Every team member answers three questions.

1. About the work they did yesterday?
2. About the work they are going to do today?  
3. Do they have any impediments while doing their work?

Example: Yesterday, I did create a login for the webpage. Today, I will research more about the single sign on needed for the login. One impediment being unable to access the portal because I don't have admin rights to it.

That's it. Simple. But gives an abstract picture to your team members of what you are doing.

Sprint Review Meeting:

In every sprint, team members setup a meeting with the product owners, stake holders to discuss about the work being done till that time. This helps the stake holders/ product owners have a look at their work and have a say about the development till date. Product owners/ stake holders can come up with their requirements/ changes in the requirements. The team members also ask for improvements and changes needed for the development needed further in the sprint. 

Sprint Retrospective Meeting:

At the end of every sprint [2-week period] all the team members are gathered for a sprint retrospective meeting where in each member of the team gets a chance to show case their accomplishments for that particular sprint. This review meeting allows the team members to review their work and get feedback from the team members. Depending on the feedback, the new stories/ tasks/ issues are created or the existing ones are changed. It might also affect the overall plan for the next sprint plan.

Backlog Refinement Meeting:

Unlike product backlog, backlog refinement meeting is discussing about all the requirements and splitting requirements in to several distinct user stories. You can create as many stories/ tasks/ issues you can to deliver the product according to the requirements. You discuss more about the type of product, the type of user, audience etc. This is also called "Backlog Grooming".

Story Points:

Points that are given to every story/ task/ issue depending upon their complexity to complete them. These points basically determine the complexity of the story/ task/ issue.

In general, sprint planning is taking tasks and completing them in the given time considering all other impediments.