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 you can filter and move tickets on the cardwall, it's a great way to see who is working on what, what tasks need immediate attention, and which tasks are in what stage of development.

Click the Options (cog) icon, and you can sort cardwall columns by Ticket Status, assigned User, or Milestones (Sprints). Additional settings include how to sort columns, display which columns, and choose how to sort tickets within each column. Be sure to click Save filters after making any changes. Name your view and even select whether this filter is available to your team or only to you.

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

Create personal and team filters by opening the Filters menu. Assembla can filter all ticket fields including custom fields. Just like the cardwall Options, be sure to click Save filters after making any changes.

Additionally, you can pin both the Filters and Options menus to the right side of the screen by selecting the pin symbol. The menus 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 then select the Show Child Tickets box. 

Once nested tickets view is enabled, child tickets are 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 is always displayed below the parent ticket, in the parent ticket’s assigned column. Dragging a sub-ticket to another column removes the relation between the parent ticket and the child ticket. Conversely, dragging a ticket from another column to the child tickets creates a relationship between that ticket and the (new) parent ticket.

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