-
Notifications
You must be signed in to change notification settings - Fork 1
Roles and Responsibilities
Tim Johnson edited this page Oct 7, 2024
·
2 revisions
This document is for capturing who is responsible for what within the delivery team.
- Has overall responsibility for delivery against the challenge objectives and is the main point of contact for the ECMWF
- Is responsible for ensuring that the requirements are well understood and that the team is focussed on the most valuable work
- Has an eye on the flow of work, helping the team to overcome obstacles as they occur
- Encourages and facilitates continuous improvement of the delivery team
- Manages risks and issues
- Resolves conflict
- Chairs the weekly review meeting with the mentors
- Reports progress to interested parties
- Responsible for internal project administration
- Responsible for the documentation that is produced and the final handover to the ECMWF
- Has overall technical responsibility for the solutions delivered by the team, ensuring that they meet the needs of the ECMWF
- Has overall responsibility for the testing activities
- Manages the day to day team activities, which includes running the following meetings:
- The daily stand-up
- Backlog refinement
- Retrospectives
- Champions good coding practices and quality code
- Maintains the decision log
- Approves holiday requests
- Advises the team on how to process scientific data
- Performs analysis of the data and presents that analysis to the team and the mentors, to support decision making with regard to the evolution of the vAirify product
- Also performs the role of Developer, with a specific focus on processing of scientific data and its display to the users
- Develops solutions to meet client needs, taking a pragmatic approach to deliver high quality, fit for purpose results
- Aspires to use the most appropriate tools, techniques and practices
- Designs and estimates items of work to inform planning and facilitate stakeholder decisions
- Collaborates with other team members, helping others to overcome challenges and suggesting improvements to team processes
- Ensures that the delivered software is supportable, by writing clean code, refactoring as appropriate, and producing supporting documentation
Accountable for:
- Defining test approach and methods according to the project requirements
- Verifying product requirements are met
- Advising the team on product quality
Responsible for:
- Creating & executing test cases to cover basic capabilities of the product, reporting findings
- Creating test charters to cover areas of risk, executing them, and reporting findings
- Creating test cases for basic capabilities, and automate those necessary to repeat verify
- Raising bugs and re-testing them
- Verifying the testability of tickets in refinement
- All testing above unit testing
Getting Started and Overview
- Product Description
- Roles and Responsibilities
- User Roles and Goals
- Architectural Design
- Iterations
- Decision Records
- Summary Page Explanation
- Deployment Guide
- Working Practices
- Q&A
Investigations and Notebooks
- CAMs Schema
- Exploratory Notebooks
- Forecast ETL Process
- In Situ air pollution data sources
- Notebook: OpenAQ data overview
- Notebook: Unit conversion
- Data Archive Considerations
Manual Test Charters
- Charter 1 (Comparing ECMWF forecast to database values)
- Charter 2 (Backend performance)
- Charter 3 (Forecast range implementation)
- Charter 4 (In situ bad data)
- Charter 5 (Filtering ppm units)
- Charter 7 (Forecast API input validation)
- Charter 8 (Forecast API database sizes)
- Charter 9 (Measurements summary API input validation)
- Charter 10 (Seeding bad data)
- Charter 11 ()Measurements API input validation
- Charter 12 (Validating echart plot accuracy)
- Charter 13 (Explore UI after data outage)
- Charter 14 (City page address)
- Charter 15 (BugFix diff 0 calculation)
- Charter 16 (City page chart data mocking)
- Charter 17 (Summary table logic)
- Charter 18 (AQI chart colour banding)
- Charter 19 (City page screen sizes)
- Charter 20 (Date picker)
- Charter 21 (Graph consistency)
- Charter 22 (High measurement values)
- Charter 23 (ppm -> µg m³)
- Charter 24 (Textures API input validation)
- Charter 25 (Graph line colours)
- Charter 26 (Fill in gaps in forecast)
- Charter 27 (Graph behaviour with mock data)
- Charter 28 (Summary table accuracy)
- Re‐execute: Charter 28
- Charter 29 (Fill in gaps in situ)
- Charter 30 (Forecast window)
- Charter 31 (UI screen sizes)