Sprints are a predetermined period of time (typically shorter than one month) at the end of which a complete and potentially releasable product should be completed. It’s important that, during the sprint, no changes are made to the scope that might cause the goal of the sprint to not be achieved and that quality goals are not decreased. 

Before a sprint is begun, sprint planning must occur. This is typically a meeting during which the scope of the sprint is determined and tasks are assigned from the backlog to the appropriate sprint based on estimated level of effort and relevance to the sprint goal. All tasks assigned to a sprint should keep the sprint goal in mind.

The Assembla cardwall is an organized view of your Assembla tickets. Because tickets on the cardwall can be filtered and moved, it's a great way to see who is working on what, what tasks need immediate attention, and what stage of development each task is in.

Cardwall columns can be sorted by either Ticket Status, Assigned User, or Sprints. Open the Options menu to select how columns will be sorted, choose which columns should be shown, and choose how tickets are sorted within each column.

Using all three of the available cardwall column views is especially useful for product owners to manage their sprint both during planning and backlog grooming before the sprint begins as well as during the sprint to manage developer workloads.

These alternate views can be saved using the Save filters button to save the view as either a personal or team filter.

Personal and Team filters can be created by opening the Filters menu above the cardwall. All ticket fields (including custom fields) can be filtered by in Assembla. Save and name a filter for it to appear in the filters list, which can be found in the dropdown to the left of the Filters menu.

Additionally, both the Filters and Options menu can be pinned to the right side of the screen by selecting the pin symbol. The menus will remain in place while the screen is scrolled if the pin is selected.

To enable nested tickets view on your cardwall, open the Options menu and select the Show Child Tickets box. 

Once nested tickets view has been enabled, child tickets will be hidden below their parent tickets. Select the > button to expand all of the child tickets below the parent ticket.

Note: Regardless of what status, assigned user, or sprint column the sub-ticket is assigned to, it will always be displayed below the parent ticket, in the parent ticket’s assigned column. Dragging a sub-ticket to another column, will remove the relation between the parent ticket and the child ticket. Conversely, dragging a ticket from another column to the child tickets will create a relationship between that ticket and the (new) parent ticket.

Need help? Contact us at support@assembla.com.