Back

Planning in Scrum

A scrum project has extensive planning built into the framework, starting with the Initiation phase , where the Project Vision, which defines the goals and objectives, is created, the team is selected and the requirements are documented as epics. A preliminary estimation of the risk and complexity of each epic is done and they are prioritized by highest risk first in the Product Backlog.

Enough information about the product is now known to do the long-range planning in the Release Planning meeting, where the timing and frequency of releases is determined as well as the number of days in a sprint. Apart from the drawing up of epics, virtually the whole of Initiation is devoted to some form of planning.

The sprint, which is Scrum’s iteration, always starts with a Sprint Planning meeting. During this meeting, the work to be done is decided upon and moved to the Sprint Backlog, and each story that is moved is broken down into tasks. At the end of the session, the amount of effort to be put into each story and task is known. The end date for the sprint was defined during initiation, so the sprint is time-boxed.

Recommended Further Reading

The following materials may assist you in order to get the most out of this course:

Translate »