Roles and Responsibilities

by Dr. Jimeno A. Fonseca, 2020, updated by Shanshan Hsieh, March 2020

This is a guide of roles and responsibilities in CEA. We use this to more formally coordinate our work. To check who is currently holding each position, we invite you to check here for more information.

../_images/project_responsibilities.png

Product Sponsor (PS)

The Project Sponsor is the person that has overall responsibility and accountability.

Responsibilities

  1. Guarantee that our vision be successful by finding and securing the budget and ensuring that high-level organizational risks are mitigated.

  2. Champion the project based on whether the work fits our research needs and overall strategy.

  3. Empower the Product Owner to act for him/her on a more tactical basis.

Engagement

  1. Participate in the Roadmap planning and review event (see Activities).

Product Owner (PO)

The Product Owner is the voice of the customer and performs all tactical operations.

PO Responsibilities

  1. Guarantee our product success by acting as a conduit/facilitator for communication between the team and the customers.

The means to communication to the customers include:

  • Conducting Usability Tests

  • Organizing Teaching Activities

  • Maintaining Documentation

  • Maintaining CEA website

  • Maintaining cea@arch.ethz.ch

  • Distributing Newsletters

  1. Coordinate the Roadmap planning and review event (see Activities).

  2. Break down the overall vision into feasible and tactical pieces of work for the development team to understand and create.

  3. Prioritizing and selecting user stories. This entails grooming the product backlogs with the help of the Srcum Master.

The product backlogs contains issues that is labelled as Must-have and Should-have. Here are the details of the labels used to categorize new issues in the CEA:

Label

Description

Must-have

  • Features defined in the roadmap.

  • Bugs.

Should-have

  • Issues that can’t be categorized for the moment.

Won’t have

  • Features that are not in the roadmap.

  • Features that are hard to maintain. These features can become external modules of the CEA.

PO Engagement

  1. Participate in all Activities.

  2. One day per week on communication to the customer team and event coordination.

Scrum Master (SM)

The Scrum Master is the servant leader and maintainer of agile practices.

SM Responsibilities

  1. Coordinate all Activities that form the agile practices of the CEA.

  2. Coordinate the training of new developers.

    1. Introduce the functionalities in the CEA.

    2. Introduce the CEA-ecosystem

  3. Coordinate the training of the team

    1. Pair-programming sessions

    2. Refresher course on programming

  4. Support the Product Owner on setting priorities and grooming the product backlog.

  5. Maintaining the internal communication channel (slack).

Development Team (DT)

The Development team is the group of individuals who build CEA. His/her main responsibilities are:

  1. Create the best working software possible.

  2. Design, analyze, develop, test and document new features in CEA.

  3. Be self-organized and self-directed.

  4. Participate in all agile practices led by the Scrum Master (Activities).

Customer Team (CT)

The Customer team is the group of individuals who use CEA. They are not part of the CEA team, but their function is extremely important for the success of the project.

  1. Represent one or more User Personas in CEA.

  2. Validate CEA and give feedback to the Product Owner

  3. Communicate issues and new features to the Product Owner.