Skip to content

Proposition for cross functional teams #1

@yungwarlock

Description

@yungwarlock

Hi, I'm really happy to find to something like this. I've been giving a lot of thought on this lately.
I just needed your thoughts on this.

Take an hypothetical team of engineers that are organised based on certain feature that would be deployed both on the backend on client applications (web, mobile and via public APIs). So each team is responsible for the servers and client packages. How would their organise the code to reflects their team while allowing easy sharing of common packages between teams. Example would be a hashing library or a Hero component package.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions