You have reached the maximum number of projects per task

[Ranan_Liechtenstein]

I have a General Kanban Board in Asana that shows all the projects running during the year (if I’m not mistaken, it was created as a “project”). Each week I create a new project that represents the current week’s sprint (to make grouping and management easier). This sprint is also set up using a Kanban board template.

Within each sprint, I create a task that is then converted into a project (this is the actual project I manage). There are some rules configured in both the sprint project template and the Kanban project template so that every task that’s created, converted into a project, and moved across the sprint Kanban columns is also mirrored on the General Kanban Board. The idea is to manage execution within the current sprint/week while keeping the general Kanban for visibility and traceability.

This means that every week a new sprint is created, and any activities not finished in the previous sprint are carried over to the current one. When we tried to do this, we received the message: “You have reached the maximum number of projects per task.” As a result, the projects from the previous sprint could not be carried over to the current sprint.

Could someone explain why this message appeared, what we can do to resolve it, and whether the way we’re managing/monitoring/controlling this workflow is the best approach?

@Thais_Soares_Ramos

[Danni_VanguardCC]

Hey @Ranan_Liechtenstein thanks for posting. I would have a backlog and a seperate ever green sprint board where tasks move in/out.

Don't look back in anger - Agile Sprint and Retrospectives in Asana

Agile working methods are becoming increasingly popular—especially a sprint approach to managing work. I can show you how to approach Sprints in Asana in this short (ish) guide. First, you must input your projects into Asana with the tasks listed to enable this to work well. Then what you need to do is create a Sprint Planning Board. In this board, you will “Multi-home” your tasks from all your projects into one place to plan your Sprint. You can bulk multi-home from the projects (by selecting …

[Ranan_Liechtenstein]

ok. Do you have a step by step tutorial where I can follow and implement this? And what about that kind of issue “You have reached the maximum number of projects per task”? Can I solve this kind of problem without changing all my templates and way of work? Because if I have to change it all now, I will have to start all from the bignning, change all the way of work and train everybody again in the new way.

[lpb]

@Ranan_Liechtenstein,

There’s some more relevant info in my Community Tips > Forum Leader tips post:

Ongoing Processes: *Current* Project, Aging, and Archiving Best Practices

Do you annually recreate some projects so you can update for the new year, like 2023 Marketing Requests? Or even worse, frequently recreate monthly or weekly projects, for example, Week 24 Dev Sprint? Stop that! (I’ll explain . . .) For ongoing process projects, like a marketing or operation team’s workstream, where work flows in, is actioned, then completed only to be replaced by more work, there’s a simple tweak you can make to simplify and clarify. Just recast that project instead as “ever…

I’m afraid there would be rework for you and a new process for your team, but perhaps a one-time correction would set you all up with something more sustainable. Or perhaps you could adapt the suggestions to better fit your needs.

Thanks,

Larry