Plan work for the team
Whether you are starting a new team or you've stepped into an existing one, you'll need to plan work. Here's how planning looks for each typical project setup.
Scrum
Scrum teams need to plan ahead to make sure what they commit to each sprint can get done.
Plan sprints
All the planning action in scrum projects takes place in the backlog. This is where sprints are created and started, and where prioritization gets done. See Using your Scrum backlog.
Plan versions
A version is a set of features and fixes released together as a single update to your application. Assigning issues to versions helps you plan the order in which new features (stories) for your application will be released to your customers. See Configuring versions in a Scrum project.
Kanban
Kanban projects have less planning components because they are set up to be more of a continuous flow of work, such as work handled by service teams. Issues do need to be prioritized so that the most important work gets done next. See Monitoring work in a Kanban project.
Kanplan
If you work in KanPlan, use your backlog to prioritize issues so that the issues being worked on are always the most important.
