Developers should be informed transparently about the next things that they are going to do since it impacts their mentality as well as their accountabilities.
A view of Vung Tau beach |
First thing first, the Product Owner plays a very important role in understanding the business of the projects clearly and planning the User Stories for Development Teams. For Development Teams, we have two roles related to a project including Owner and Maintainer. The following are the definition and responsibilities for each role:
Project Owner
The Owner is normally assigned to the team that created the project at the beginning. It is known as the long-term project of the team. Therefore, the members of the Owner have almost knowledge of the projects including the history (i.e decisions made), business logic, and technologies used.
- Maintain a good system design (code) of the projects. Therefore, they are mandatory to review code (pull requests) from other teams.
- Maintain the related documents of the projects (Confluence pages, README)
- Maintain the CI/CD tools (i.e Git repositories, Container images, Build jobs, OpenShift projects, etc) of the projects. Therefore, full permissions for these tools are granted to the Owner.
Project Maintainer
The Maintainer is the team who joins to support the projects for a period of time in case the team having the ownership can not work on the requirements. The maintainer team has some basic knowledge and worked on the project in the past on some components. However, the maintainer might not have knowledge of the overall project, the business requirements, or the history of the project. The support of the team having ownership might be required.
Comments
Post a Comment