Team‐workflow

Team Workflow

Roles

• PO (trainer): writes functional issues, answers questions, tests on staging, opens bug issues.
• Tech Lead (trainer): approves designs and helps when we are stuck.
• Developers: analyse, design, build, test and deliver tickets.

Ticket types

Type	Made by	Note
Functional issue	PO	We never edit it
Slice	Team	Part of a functional issue (kind: slice)
Dev task	Team	Follows one issue from start to finish (kind: task)
Bug	PO	Opened after a staging test

Life of a dev task

1. Analyze: write precise business rules and list our questions.
2. Design: wireframe, data dictionary, MCD, MLD.
3. Get approval: the trainer approves in writing. No code before this.
4. Build: database scripts, backend, frontend.
5. Test: Postman collection.
6. Review: a teammate reviews the pull request.
7. Deliver: merge to integration, deploy to staging, tell the PO.
8. Accept: the PO tests by hand.

Working together

• One feature at a time. We do not build ahead.
• Each developer owns one priority issue. A task can be split. For example add first, then modify, then delete.
• Shared things, like the country table, are designed by the ticket that creates them. Others reuse them.
• One global data model lives in the wiki.
• If we are stuck, we investigate first, talk as a team, then ask the Tech Lead and explain what we tried.
• If something fails or is late, we explain the cause and the fix, in a professional way.