# Sprint Planning A sprint for us is usually two weeks long. ### What is it? A collaborative effort facilitated by the project manager. The project manager explains the backlog and defines the sprint goal. The team then defines the work and effort needed to meet the goal. This is done before the start of the sprint. It sets the roadmap for the team with a clear idea about what is intended to be done. ### Tips * *Eye on the clock:* Keep it constrained to a max of one hour per sprint. * *Fixed Goals:* Gather feedback from the previous sprint and with the product vision in mind prepare a goal. * *Outcome driven:* Don’t go into the depths of how each task should be done and who will do it. Rather focus on gathering estimates. * *Trust-based environment:* Estimates are not commitments. Team members should be able to freely estimate stories without judgment. Velocity over time will naturally increase. * *Always be humble* --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://playbook.wednesday.is/project-management-playbook/our-approach/agile-ceremonies/sprint-planning.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.