Standard Operating Procedure

sop-team-3.0.0

Team

In some cases, an individual may take on more than one role within a team. While this can be a valuable asset in certain situations, it is important to consider that the inability to focus on a specific role might result in a less effective performance compared to someone who can dedicate their full attention to a single role.

---

DBA

Responsible for DataBase Administration - such as automating database backups, software upgrades, optimizing indexes, etc.

Designer

Responsible for the interface “look and feel.”

Developer

Responsible for the implementation of the solution in accordance with the blueprints. Following a “mission command” principle - the developer is responsible for the micromanagement of the lower-level implementation details of the solution.

DevOps

Responsible for the infrastructural foundation that the solution is built or depends upon.

Lead Developer

Responsible for mentoring other developers in the project, in accordance with standards and practices regarding the solution.

Product Owner / Domain Ambassador

Responsible for change request approval and order of the project folder.

Project Manager

Responsible for time management and prioritization in relation to the project budget and timetable.

QA

Responsible for the Quality Assurance of the solution.

Scrum Master

Responsible for organizing tasks, issues, and the storyboard.

Solution Architect

The solution architect is responsible for the articulation of the solution, responsible for the blueprint or the map used by the rest of the team to know what to do and why they are doing it.

Team Lead

Responsible for the people in the team, their equipment, and resources.

Technical Writer

Responsible for writing and/or generating the documentation of the solution.

UX

Responsible for the User eXperience - meaning the user interface flow.