ClickUp is designed to be easily adaptable to many workflows, especially development workflows such as Kanban, Scrum, and Agile in general.
ClickUp utilizes the scrum methodology within the Agile workflow system. If you’re interested in learning more about agile, check out these helpful blog posts for the basics of agile and how to implement agile in your project management workflow.
Manage Sprints in ClickUp
Break your large projects into smaller chunks of manageable work, called Sprints.
Apply the Sprints ClickApp to any Space, select the Sprint duration, and create Sprints without searching for dates again. You can even automate your Sprints using this ClickApp!
Using our Sprints ClickApp you can choose to use a Sprint to manage your team's workload using the following features:
- Sprint Dates: Sprints are required to have start and end dates.
- Sprint Statuses: Sprint Statuses are indicated by the color of the icon in the hierarchy and in the color of the Sprint dates at the top of the List view. Not Started (Gray) In Progress (Blue) Closed (Green)
- Spillover Tasks: Any tasks not marked
Closedwhen your Sprint ends are considered Spillover Tasks to be completed in the next Sprint.
- Total Estimation: The total amount of work you have in your Sprint is summarized at the top of your Sprint. You configure what estimation method is used on the Sprint Settings.
Business+ users can turn on Sprint Automations within Sprint settings.
You can even convert Lists into a Sprint, create Sprint folders, and view the progress made in Sprint folders using Burn Up and Burn Down charts in your Dashboard.
For more information on how to use or install, view our Sprints ClickApp Doc here!
How to best setup ClickUp for an Agile - Scrum workflow:
Start with the Hierarchy
Your Workspace is the company you work for, which includes members from every department within your company, but agile is typically implemented only for members in your development/engineering Space.
Recommendation: Use a "Development" Space
Spaces let you customize what your engineering team needs to effectively set up an Agile workflow. We’ll come back to the details for this, but essentially we want to enable features, statuses, and integrations that are required for an efficient development team.
Recommendation: "Frontend", "Backend", "Bugs", "Features", or "Sprints"
Folders will serve as categories for different parts of your product development. For example, at ClickUp we have Android, iOS, Frontend, Backend, etc Folders in our development Space. Folders organize your Spaces and contain Lists (Sprints) and tasks.
Recommendation: "Features", "Bugs", or "Sprint 1"
Lists are the ultimate containers for your tasks and are perfect for housing for your backlog items. This is where all the tasks live that get your Sprint done! Use our Tasks in Multiple Lists ClickApp to add your tasks to Sprints.
Tasks are the true action items within ClickUp. For each sprint to be pushed into production, each of its tasks should be completed as well. Tasks that need to be pushed into the next sprint can be easily moved.
Other Features, Views, and ClickApps
Now, we need to set up the statuses for your task workflows. This is an essential component of the Scrum methodology. Select our Statuses, and then click Scrum to access our pre-formatted Statuses for this workflow. You can also customize your own statuses and save them as a template for use in other Folders.
Tags can serve as the means by which each task within a sprint is organized. For example, there can be tags added for tasks that are bugs, hot-fixes, and server issues, just to name a few. Also, simply adding a
Sprint tag to your tasks can help clarify imminent action items.
Integrating with Github is perfect for a Scrum workflow since being able to push and fork into different environments is essential for the development process. GitHub lets you track issues, commits, and really anything you need to know about a task within the task’s activity log. This makes it easier to keep track of the Status of a development task.
Use Time Tracking with Time Estimates? ClickUp calculates how much time remains for the Sprint. This feature is available for each task and is cumulative for the entire List that those tasks live in. This allows you to have a clear understanding of how long it will take to complete a task and/or List, while also giving you a rough idea of how productive your team members are.
Setting a task to recur at a given date or interval comes in handy when there are repeating actions that need to be completed within a certain sprint, such as Q/A within a Development Space or outreach within a Marketing Space. This feature can be set for each task or subtask created within a Sprint.
Start and Due Dates
The entire Agile workflow relies on having goals with a beginning and end! Start and due dates complete that. Just add a date that a task should be started by as well as its due date and you will have the ability to filter by start and due date, making it easier for the product owner or scrum master to evaluate where in the development cycle they are.
Link Tasks to Represent Epics
There are three different ways you to simulate epics for your engineering projects within ClickUp!
- (RECOMMENDED) Linking Tasks & Tasks in Multiple Lists: Use our task linking feature to relate tasks that are part of the same project. Create one task that represents the epic and then relate all the other tasks that comprise the feature to the epic task. When it comes time to add your tasks to a Sprint, leave your Epic on the roadmap.
- Tasks in Multiple Lists: When you create tasks in your Sprint, add them to a second List with the name of the project or initiative. In this scenario, that second List becomes your epic.
- Task Container: Create a task to represent the epic and create tasks from within the description of the epic. You can also manually place links to the related tasks in the description of the epic.
The best way to use
linked tasks with the Sprints ClickApp is to create a List to represent your project or feature. Then, create a task to represent an epic or project in that List. We find it helpful to name it something like
Awesome Feature [EPIC].
With the Task in Multiple List ClickApp turned on, add the task
Awesome Feature [EPIC] to a secondary List, like your roadmap. In the same project List, create tasks for that project or feature. Use the
Link tasks feature to relate these tasks to the
Awesome Feature [EPIC].
In Sprint planning, move the tasks that are related to the epic into an upcoming Sprint or use Tasks in Multiple Lists to add them to the Sprint. For bugs, just add them into the Sprint as a secondary List.
Tracking Sprint Progress in Dashboards
Dashboards come loaded with many widget options, but the most valuable here are our sprint widgets. The real power being able to customize how and what data you want to see. Build a Dashboard per team or create a master Dashboard pulling key data from all your team.
We include many of the core report types used in agile methodology. These include:
- Burn Downs: For measuring your rate of completion against a target line to help visually see your pace.
- Burn Ups: Giving you a clearer view of work completed against the backlog of work - easily see changes in scope.
- Cumulative Flow: See your tasks move across statuses and visually see bottlenecks in process before they get too big.
- Velocity: For gauging the average completion of work per sprint integrations, helping you better estimate for future sprints.
Important: You will need an Unlimited Plan to access Dashboards, and a Business Plan to have access to custom graphs and velocity chart.
Tracking Sprint Progress in Box view
Progress and Planning
Under Settings, toggle
Show time estimate on to see the time people have estimated vs. what they've actually done:
It's the perfect way to manage timelines for your sprints!
Workload and Capacity
As we see above, Alex K (the user second from left) could probably use more tasks because he seems to be almost done with everything assigned to him.
Plus, we can see that Wes (left) has a lot more work than everyone else.
Other ways to manage your Daily Scrum in ClickUp
Sprint Automations allow you to set and forget Sprint management so you can focus on your actual work and less on the admin side of Sprints!
This view allows the user to have a more day to day view of a Folder’s progress; it's helpful for Scrum Masters in particular, as well as for product owners. This view is essentially a Kanban board.
If a task or Folder can’t be completed until a certain task is completed, then product owners can set a dependency as a blocker. This makes it so that certain tasks must be completed for other tasks to be completed afterward.
Use Milestones to signify the end of a big group of tasks, such as a new feature being released. Quickly identify which tasks are Milestones by the icon and bolded task name!
Check out this page for more inspiration on setting up your agile ClickUp team!