How to use Assembla for Agile Sprint Planning and Management

Claudia Fernandes
Claudia Fernandes
Last updated on May 14, 2024

For software development teams that have adopted the Agile Scrum methodology, sprints play a key role in product delivery. Integrating these sprints within the platform hosting your Git, SVN, or Perforce projects can significantly boost the speed, precision and security with which you deploy your software.

Assembla’s robust cloud project management tool supports Agile sprint planning, allowing software development project managers to centralize development in a single, secure and compliant platform

Below is an overview of how your software development team can use Assembla to map out your sprints, tasks and dependencies.

Assembla Tickets

Assembla Tickets is our answer to the Scrum Board. Below are Assembla’s main sprint planning and project management features you can leverage to organize your tasks, prioritize workload, beat deadlines and ship great products.

Scrum board

Ticket creation

When you create a new ticket, you can set the plan level, i.e., turn it into either a Story for a Sprint or an Epic. When you create child tickets of an Epic, you’re creating a Story. When you create child tickets for a Story, you’re creating Tasks. Learn more about using Stories and Epics.

Ticket Creation in Assembla

Establishing Estimates

By setting estimates, you enable the use of Story points (or Hours), which allows you to get a sense of the effort required to complete it. This helps manage the workload and understand the progression of the sprint. How to add Estimate fields to tickets.

Ticket Estimates in Assembla

The Cardwall view

Cardwalls are columns and are the primary way to view Epics, Stories and Tasks. Because the Cardwall columns can be customized, filtered and moved, they’re a great way to organize, prioritize, assign tasks, and manage workloads and generally keep track of the progress. Categorize columns according to your regular workflow. Learn more about Cardwalls

Classic CardWall View in Assembla

Switching columns

Columns can be used to view things other than tasks. View by Ticket status, Assigned Users or Sprints. Sorting columns is the best way to see who is working on what, what tasks need immediate attention, and what stage of development each task is in. See the Options menu to customize your view further.

Switching view in Assembla

Filtering Tickets

Use the Filters to view only certain tasks. View by Priority, Status, Stories (Milestones), Plan level, Tags, Related ticket numbers, and more. You also have the ability to save filters, name them and assign them to a team. By selecting certain tasks and naming them, eg, “QA”, you have the ability to give the QA team visibility only into the tasks that are closely tied to their work.

Filtering tickets in Assembla

Show column as Milestones (Sprints)

As the Sprint progresses, you may face an unexpected roadblock or identify members of the development team with too much workload, for instance. In these cases, sorting columns by Milestones (or Sprints) can help you defer tasks to future sprints, or revert them back to the product backlog, improving prioritization and workload management. More on Milestones

The process for doing this is the same as the method for switching columns, which was explained earlier.

Switching columns in Assembla

Linking Tickets to Commits

The ability to connect Commits to Tickets is a powerful organizational tool. This provides clear traceability between the planned tasks and the actual code changes and helps ensure that the development work is aligned with the initial planning. The PO is also given superior progress monitoring abilities. How to link commits to Tickets

Linking tickets to code commits in Assembla

Milestones (Sprints) Reporting

The Tickets tool features a Cumulative Flow Diagram (CFD) within the Metrics subtab. This CFD, an integral component of the Assembla Tickets tool, serves as a highly valuable management report. Offering profound insights into your development process, the diagram visually represents the number of tickets in each status column over time, providing a comprehensive understanding of the workflow dynamics. Learn more about sprint reporting

Milestone metrics

New to Agile Project Management?

If all of this sounds great but your software development team hasn’t fully delved into agile project management, below is a condensed summary of what it entails. For more detailed information, go to

What is Agile Sprint Planning?

In Agile Scrum methodology, a sprint is a time-boxed period during which a team works to deliver a potentially shippable product feature. Sprint planning is the meeting that happens at the beginning of each new sprint that allows for the development team, the Scrum Master and the Product Owner, to all be on the same page regarding the work ahead.

  1. Introduction and Context Setting: The Product Owner provides an overview of the prioritized items in the product backlog, usually in the form of user stories.
  1. Review of Product Backlog Items: The team may seek clarification on any ambiguities, and discussions may take place to ensure a shared understanding of the work.
  1. Estimation: The Development Team estimates the effort required for each backlog item. This is often done using relative sizing, such as story points. Estimation helps the team understand its capacity for the sprint and guides the selection of items for the sprint backlog.
  1. Selection of Backlog Items: The team collaboratively decides which backlog items to bring into the sprint based on their priority, estimated effort, and the team’s capacity. The selected items form the sprint backlog, representing the work to be completed during the sprint.
  1. Commitment and Sprint Goal: The team commits to delivering the selected backlog items by the end of the sprint and this commitment forms the basis for the sprint goal, representing what the team aims to achieve during the sprint.
  1. Tasks Breakdown: The team breaks down the selected backlog items into smaller tasks and sub-tasks. Task breakdown provides a detailed plan for how the team will approach and complete the work.
  2. The definition of “done”: The team collaboratively defines the criteria that must be met for a backlog item to be considered “done.” This ensures a shared understanding of the quality and completeness expected for each item.

Go to our support pages to learn more about Assembla’s cloud project management tool and how it aligns with the Agile Scrum methodology.

Get Source Code Management Tips in Your Inbox
The reCAPTCHA was invalid. try it again.
By registering, you confirm that you agree to the processing of your personal data by Assembla, Inc. as described in the Privacy Statement. Assembla, Inc. is part of the Idera group and may share your information with its parent company Idera, Inc., and its affiliates. For further details on how your data is used, stored, and shared, please review our Privacy Statement.
Claudia Fernandes
Claudia Fernandes
Claudia, Assembla's Content Marketing Manager, brings over 7 years of experience in crafting content for global SaaS companies. She is enthusiastic about DevOps, cloud computing and the intricacies of the software delivery pipelines. She loves to learn from the experts at Assembla and guide readers through the ever-evolving SDLC landscape.
© 2024 Assembla - All Rights Reserved

Select AWS Region

Pick the region closest to your team for faster performance.

Select AWS Region

Pick the region closest to your team for faster performance.