Some Guidelines for Task Naming in Scrum/Kanban

Some Guidelines for Task Naming in Scrum/Kanban When writing the name of a task in a Scrum/Kanban list, it is essential to follow some ground rules to ensure clarity, standardization, and understanding among team members. Here are some common guidelines:

Brevity and Clarity Task names should be short and descriptive enough to convey the main purpose of the task. Avoid long or ambiguous sentences.

Action and Responsibility Clarity Use verbs in the infinitive to indicate the action to be performed. Include the name of the person responsible for the task, if possible, for ease of attribution.

Example: "Create new login form - John"

Priority Add a priority indicator if necessary. It could be something like "HIGH:", "MEDIUM:", "LOW:", or using numbers like "P1", "P2", etc.

Example: "HIGH: Solve shopping cart bug - Maria"

Associated Epic or Story If the task relates to a specific epic or story, it's helpful to reference it in the task name.

Example: "Epic #123: Implement payment system - Pedro"

Context If the task relates to a specific area of the project or involves a specific system component, it's helpful to include that context in the name.

Example: "Frontend: Create User Profile Page - Ana"

Due Date If the task has a due date, it's a good idea to include it in the name for easier planning.

Example: "07/31: Prepare presentation for client - Sales Team"

Consistency Maintain consistency in how tasks are named for readability and avoid confusion.

Avoid Jargon Use terminology that is understandable to all team members. Avoid technical jargon that may not be familiar to everyone.

Avoid Excessive Detail The task name should be concise. Avoid including excessive details that can be better described in the task description.

Keep in mind that these rules can vary from team to team, and the most important thing is to find an approach that works well for your specific context. The key is to ensure that everyone on the team clearly understands what the task entails, what needs to be done, and who is responsible for it.