Skip to content

Thought: Using the Checklist to bridge the communication gap #12

@Macrofig

Description

@Macrofig

Specifically between different groups int he same team. i.e. Backend vs frontend vs devops vs users

I'm thinking that in certain questions, we can easily and quickly discover terminology differences between the different groups. By documenting these differences, we can iron out future issues that result from terminology confusion.

Saying something is on the "dev" server, for example, can mean different things to different groups.

I don't think the checklist is a place to capture this information but I think it's a starting point. Although, we should have a question asking if the team has a "Ubiquitous language" document.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions