Assembla Tickets is powerful and flexible, but it can be daunting to use if you are just starting out. There are many ways to configure milestones and ticket lists and custom fields and status values to fit a customized process. Most users just want to get started quickly with a process that already works.
Agile Planner is the solution. It's implemented on one page with popup details.
Agile Planner is compatible with existing tickets and milestones. You can view your existing tickets in the Planner or start in the Planner and switch to the cardwall or a customized list view.
There is a difference in how Planner organizes tickets. If you are a current user of Assembla tickets, you probably sort tasks using milestones and priority. You lay out your roadmap with sequential milestones. Some customers use milestones as containers for other things such as clients or products. Inside a milestone, you mark a ticket with Priority. If you mark a ticket as "Highest" priority, it floats to the top in all of our default views and gets a bright color. Setting a priority is a fast way to sort, which is why I created this implementation.
Planner replaces the two ideas of milestone and priority with one concept: sorting. Tickets go into one backlog milestone, and you drag-and-drop to sort them. They stay in place even if you change the priority. This sorting process gives you more precise control over the list of tasks and it is easier to set up.
Is it simple? Here on one page are the complete instructions for using Agile Planner, including for Scrum and Kanban.
If you have an existing project, and you go to the Planner subtab, the Planner will ask you to select Current and Backlog milestones from your existing list of milestones, or create new milestones, which it will name "Current" and "Backlog".
Make a plan by sorting the Backlog list of tasks into the order that you want to work on them. Move urgent tasks to the top. Move tickets from the top of Backlog to Current with the "Load" button, or by dragging them manually.
The simplest way to sort is to use the arrow icons for "Send to top" – send a ticket that you want to work on now to the top of the Backlog, and "Send to bottom" – send a ticket that you do not want to work on now to the bottom of the backlog. You will see these icons in the New and Backlog columns. You can also sort with drag and drop.
Enter a capacity on top of the Current column. Capacity is the number of points that you want to see on your Kanban board. Add estimates to tickets. Select "Load" to move tickets into Current. Do this frequently so that you always have approximately the right number of Current tickets. You will see your current tickets on the Cardwall in a traditional Kanban board view.
With a Kanban or lean process, you want to control the number of tasks (WIP or Work In Progress) so that someone is working on each task, and no task is just waiting. This simple tactic allows you to deliver each task as quickly as possible, which is efficient, and very satisfying. You can ensure that each task is being worked on by controlling the number of tickets, not the size of the tickets. We often recommend an estimate setting of "Do not estimate" (which will load ticket counts and not points), and a capacity that allows one, two, or three tickets per team member.
To start a sprint - Enter a capacity. Select "Load" to move tickets into Current and start your iteration.
To finish a sprint - "Show closed tickets" in the Current column. You will see all of the closed tickets in the Current milestone. Select "Close Iteration". This will close and rename the Current milestone. Give this old milestone a name that describes your sprint or release. It will create a new Current milestone, and move any open tickets to that new Current milestone.
With a scrum or iterative process, you will want to estimate the total amount of work that you can do in an iteration. Use Small/Medium/Large or integer points.
A project owner can select several estimate types on the Settings page (shown above).
We match these points with a "Capacity" – the approximate number of points that your team can work on at one time. If you do not enter a capacity, and you do some work, then we will calculate capacity from historical velocity – the number of points in tickets that are closed in the last week.
Estimates do not need to be accurate. Even simple estimates will help you work on approximately the right number of tickets. It is more important to sort your tasks in priority order. If your tickets are sorted correctly, you will always be working on the most important tasks.
Switch to the Cardwall view to see your Current tasks in a Scrum Board or Kanban Board format.