/
Planning a Sprint

Planning a Sprint

Owned by Akshay Aggarwal (Unlicensed)
Last updated: Sept 01, 2020
2 min read

What is the purpose of the Article?

  • You will understand how to plan a sprint in Eshopbox

Audience

  • Project Managers

  • Software Development Engineers

Before you proceed further:

Read in detail about what is a Sprint and how it works in Eshopbox Jira Softwae

Before you plan a sprint

  • You are required to create a Version

  • You are required to create Epics

  • You are required to create a backlog

Planning a Sprint

  1. You are required to update your backlog.

    1. This implies that you need to ensure that the incomplete issues from the previous sprint are added in the backlog. How to end a Sprint and to move incomplete issues from a sprint to backlog.

  2. You will prioritize the User Stories in the backlog by assigning a priority level in the “Priority“ field. This will be done by PMs

  3. You will ensure the top priority User Stories and Tasks have “Tshirt Size” and “Story Points” field added accordingly.

  4. You will ensure that the combined “Story Points” of all User Stories and Tasks should be not more than 25 for a Sprint.

  5. You will add the selected User Stories, Tasks, and Bugs in the Sprint.

Fundamentals

  • Tshirt Size: A Tshirt Size is allocated by the assignee on the basis that how much time the assignee thinks would be required to complete this User Story as well as the complexity level of the issue. If it is extremely complex then select “Extra-large”. If it is not select “Small”

    • The available Tshirt sizes are:

      1. Small: you will assign a maximum of 2 story points in the field, “Story Points“

      2. Medium: you will assign a maximum of 5 story points in the field, “Story Points“

      3. Large: you will assign a maximum of 7 story points in the field, “Story Points“

      4. Extra-large: you will assign a maximum of 10 story points in the field, “Story Points“

  • Priority: Assign a priority value to each issue on the basis of business requirements and goals. The available priority field values in Jira are Highest, High, Medium, Low, Lowest. However. we shall be using only the following values:

    • High

    • Medium

    • Low

Glossary

PM: Project Manager

Related content