ClickUp is designed to be easily adaptable to many workflows, especially development workflows such as Kanban and Agile. Particularly, Agile is dominating tech right now as one of the best workflows for development.
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 on the basics of agile and how to implement agile for your project management.
How to best setup ClickUp for an Agile - Scrum workflow:
1. Start with the Hierarchy
Your Team 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.
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.
Projects will serve as categories for different parts of your product development. For example, at ClickUp we have Android, iOS, Frontend, Backend, etc Projects in our development Space. Projects organize your Spaces and contain Lists and tasks.
This is where Sprints are hosted. Each List should represent an individual sprint with an additional List titled “Backlog”. New features and aspects of a product will be developed within these Lists and archived when completed. Lists function perfectly as Sprints, since each List can hold many tasks as apply to it. Also, Lists can have start/due dates, details, an entire activity thread thread, and so much more! We’ll even let you color code your sprints (Lists).
Tasks are the true action items within ClickUp. That is what will populate each Sprint (List). 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.
2. Utilize ClickUp’s features, Views, and ClickApps
Now, we need to set up the statuses for your sprint’s workflow. This is an essential component of the Scrum methodology. I would recommend you select our Custom Statuses then click Scrum, to access our already pre-formatted Statuses for this workflow. You can also Customize your own statuses and save them as a template for use on other Projects.
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, can create a solid alternative to using Lists as a way to organize your sprints. For example, when there are many tasks across various spaces, instead of creating a list within each space, it would be better to add tags to each task that is part of a certain Sprint.
Having an integration with Github works perfectly 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 are cumulative for the entire sprint (List) those tasks live in. This allows you to have a clear understanding of how long it will take to complete a Task and or Sprint, while also giving you a rough idea of how productive your team members are.
Setting a Task to occur at a given date/time 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.
Another essential aspect to the Agile: Scrum workflow is the Backlog vs Sprint distinction. The ability to organize things based on priority makes this a breeze as any lower priority Tasks as indicated by the flag icon can be moved into a backlog list and each Task with more priority can be moved to a more active 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.
3. Utilize ClickUp's functionalities to manage your Daily Scrum
A display of the ClickUp dashboard, which allows for a high level overview of the Project being worked on, especially helpful for Product Owners. Also, using the me view within Box View, makes daily scrum meetings a breeze, by offering a way to see the Tasks that have been worked on yesterday as well as what needs to be completed for the rest of the week!
This view allows the user to have a more day to day view of a project’s progress, helpful for Scrum Masters particularly as well as Product Owners. In addition this view works perfect for a kanban setup since you can create a Task within a certain status and you can layer each Task within that Status.
If a task or project 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 in for other tasks to be completed afterwards.