Naming Convention
Can anybody provide suggestions for a naming convention for tasks and projects? Would love to hear some ideas!
Il semble que la page que vous recherchez n'existe pas dans votre langue. Mais nous proposons d'autres contenus en français ainsi qu'une assistance en français.
En quoi pouvons-nous vous aider ?
Learn. Share. Discuss.
Can anybody provide suggestions for a naming convention for tasks and projects? Would love to hear some ideas!
Folllowing List for Post: Naming Convention
[this list is visible for admins and agents only]
Here's how we do it:
Project Name
This one is a no brainer as we have job numbers opened in our accounting system so the projects are ##### Website Updates for Client.
Task Name
Tasks should always be actionable or illustrative of the final expected state. "Build Task List Breakdown" or "Add Coupon Code" or "Code Instagram Feed on Homepage" the next right action to do.
Description
This should have the detail. Sometimes we write up User Stories in here but mostly we just create a brief description and the Acceptance Criteria (how we know it's done).
Hey Devon, thanks for posting that 🙂
I've moved your post to Best Practices section as it seems it will fit better here. I'd also suggest checking out this post on Naming Conventions 👍
Let me know if that helps
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Hi Devon, we use an identical naming convention to what Tom posted above. Because we're a physical product development company, our projects are SKU # - PRODUCT NAME. Just as Tom mentioned, we use an action verb to begin our task titles and then what the action is applied to. Cheers!
Love your idea! We have been using Action Verb + Project Name + MM.DD.YY! The naming convention works well, I just wanted to see everybody's bright ideas!
Thanks!!