Team Roles
LINAGORA’s Software teams involve different roles:
Developers are not described here but obviously represent an important part of the teams.
You may also be interested about mailing-lists and Twake channels.
Product Owner
A Product Owner is in charge of a coherent set of Software solutions that address a business set of features.
That can be (as examples) Inbox, Calendar, Contacts, file sharing, etc.
A product owner is the ultimate person accountable for the global user experience:
- Design
- Usability
- Correctness of the displayed information
- Scalability
- Interoperability and integration with other products / projects
Product Owners tasks are:
- Get knowledge about the eco-system related to their business concerns (through regular meetings with users and customers, technological watch, etc).
- Build the roadmap for its product (in relation with Sales/Pre sales teams, as well as the marketing team, and its development team).
- Communicate the roadmap to stake holders and development team (including the BA).
- Coordinate vision and roadmap with other Product Owners. The objective is to get a coherent Software Suite (by following coherent targets and being smart with cross-project functionalities).
- Take responsibility of the Open Source community around the project(s).
Business Analyst
A business analyst is a person that will transform the PO’s vision and roadmap into concrete material that developers, UI/UX, and to an extent QA, will use to deliver the features.
The Business Analyst got frequent talks with the PO, in order to align the concrete features with the vision/strategy. He (or she) must also bring feedback to the PO at the end of features development.
Business Analysts tasks are:
- Maintain the development backlog.
- Translate a roadmap item into concrete user stories.
- Follow the development team during the development phase to adjust development and answer questions.
- Test the features at the end of a development iteration and provide a critical feedback.
Technical Leader
A technical leader is in charge of the appropriate performance of the technical aspect of the task. He is the one ensuring that the code / API and the solutions delivered by his team are correctly designed, organized, maintained and documented.
Technical Leaders tasks are:
- Design the solution according to roadmap items and user stories.
- Bring valuable inputs to BA and PO regarding the global consistency of the solution.
- Know the level of technical debt and work with the PO to ventilate its reduction tasks in the roadmap.
- Provide guidance to the developers regarding the implementation details.
- Take time to test alternative / new technologies.
DevOps
A DevOps is in charge of ensuring that the code produced by developers is able to be configured, deployed, monitored, backed-up, updated, on production systems.
DevOps tasks are:
- Create and maintain the deployment artifacts of the Software components. Those artifacts will be used on production systems.
- Help developers to ensure that the delivered solutions bring relevant traces and logging.
- Help developers to ensure that the solutions data can be backed-up.
- Review the security aspects of the delivered solutions and deployment artifacts.
- Help developers to set up continuous integration and continuous deployment for their project(s).
- Work with other DevOps to standardize processes, test new approaches, ensure compatibility between the deployments of Software stacks.
- Work with exploitations teams to understand the deployment target.
Quality Assurance
QA tasks are:
- Define test plans, by using the roadmaps and working with PO.
- Work with BA to build the test case base on the user story.
- Work with TL to apply the working process between the development team and QA.
- Update test cases, scenarios and assertions, verify issue resolutions and confirm fixes are correct.
- Discuss with developers about issues or bug reports if necessary.
Communication Channels
There are channels for the different tribes (groups of people having the same role in different teams).
Notice that QA is not a tribe at the moment.
| Tribe | Mailing-List | Twake Channel |
|---|---|---|
| PO | po-tribe@linagora.com | here |
| BA | ba-tribe@linagora.com | here |
| TL | tl-tribe@linagora.com | here |
| DevOps | - | here |
| QA | - | here |