Learning the ways of Agile project management using Asana and AI Studio

[lpb]

Briefly, because I feel it’s hard to weigh in on workflow design unless we’re all looking at the workflow in detail and communicating interactively…

Consider some other options too, if you haven’t already:

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…

Best Practices for Managing & Archiving Sprints

@Kevin_Moore3, My preferred approach is to recast that project as “Current Sprint.” One time, archive the previous sprints’ tasks to either a) their own individual archived projects, or b) one archived project with sections for each past sprint. First make the project(s) and sections you need, then multi-select each sprint’s tasks, sprint-by-sprint, and use the bottom multi-select toolbar to add them to the desired project (and optionally section) and then remove from the Current Sprint projec…

Thanks,

Larry