acikyazilimagi / afetharita-roadmap Goto Github PK

License: Creative Commons Attribution 4.0 International

afetharita-roadmap's Introduction

Afet Harita Roadmap

Statement

In the aftermath of the earthquake in Turkey, there was no sophisticated emergency response system to turn to. Every moment counted as lives were on the line. But from this tragedy rose a movement of 20,000 contributors, determined to give a voice to the victims. The result was the Afet Harita Mapping Application, a cutting-edge open-source platform available for all. Our objective is to ensure that Afet Harita becomes the gold standard in disaster response, providing a crucial lifeline to those in need. Natural disasters may strike again, but our mission is to make sure that humanity is always ready to respond, in the name of those we have lost.

What is Afet Harita

Afet Harita is a tool designed as a open-source project to help emergency responders quickly identify areas affected by natural distasters and locate potential victims. Food locations, hospitals and other available services can be found in this application. The goal of this roadmap is to outline the development plan for Afet Harita, including the features and milestones that will be achieved over time.

Wiki

The most up to date detailed information will be published in the Wiki page of this repository. Afet Harita Wiki

Contributing to the Project

The Afet Harita open-source community welcomes contributions from anyone who is interested in helping. To get involved, you can join the community via their Discord channel. The team uses GitHub Projects to manage their work and communicate in the Discord server.

We hope this guide to the roadmap for Afet Harita is helpful in understanding the purpose and goals of the app. Thank you for your support and we look forward to your contributions!

afetharita-roadmap's People

Contributors

Stargazers

Watchers

Forkers

sercanerhan

afetharita-roadmap's Issues

[US]: Find my location

User Story - As a [persona], I [want to], [so that].

As a ER responder, I want to see my location on the map so that I can see the closest places to go for

Acceptance Criteria:

Success Criteria:

The location feature accurately identifies and displays the user's current location on the map in a timely and reliable manner.
The location feature is intuitive and easy to use, allowing users of all technical skill levels to quickly and easily find their location on the map.
The location feature respects the user's privacy and personal data, ensuring that user data is not collected or shared without the user's explicit consent.

[ACT]: Documenting achievements, could have been better and problems sections

Description

According to the decision that has been made at the meeting documentation for the below three sections should have been completed.

In the short term - What did we achieve?
What could’ve done better?
What kind of problems we had?

Items to Complete

In the short term - What did we achieve?
What could’ve done better?
What kind of problems we had?

Supporting Information (Optional)

https://github.com/acikkaynak/afetharita-roadmap/wiki/Mapping-the-Disaster:-The-Story-of-Afet-Harita

[ACT]: Confirming Provision Aid and Confirmed data

Description

Provision Aid and Confirmed data were used to come as 3-day cycles. It seems this process has been canceled. Must be confirmed with Frontend Team. There are no 12 hours of data. We need to document this.

Items to Complete

Follow up with Frontend Team
Document this information under Roadmap Repo - Wiki

Supporting Information (Optional)

[ACT]: Schedule Preparation

Description

A product Manager Shift schedule should be established. There is always a problem with finding available PM.

Items to Complete

Managers must be providing offline/online information.
We should prepare a post in the core team and pin this information.

Due Date

<date>

Supporting Information (Optional)

[TK]: Multi reason parameter filter (backend)

Description:

Acceptance Criteria:

Linked User Story:

[ACT]: Contact List Prep for all team leads

Description

Must prepare a contact list of all team leads for emergency reach out.

Items to Complete

Prepare a list
Publish a page wiki and link it Documentation page.

[ACT]: Onboarding Doc Prep

Description

Onboarding Doc must be prepared.

[TK]: NEEDS Request to AI (backend task)

Description:

needs: [
{"ilac": ["aspirin", "parol"]},
{"yemek": ["asdfdsa", "asdfads"]}
]

Acceptance Criteria:

Criteria 1: [Description of acceptance criteria 1]
Criteria 2: [Description of acceptance criteria 2]
Criteria 3: [Description of acceptance criteria 3]

Linked User Story:

[IN]: AfetHarita 2.0 Release - Pending

Description:

Our goal is to improve the overall user experience for our app, Afet Harita, by making it more user-friendly and intuitive. This includes updating the UI design, improving navigation, and streamlining the user flow.

Success Criteria:

Increased user satisfaction, as measured by a 10% increase in positive ratings in the app store
Improved user engagement, as measured by a 15% increase in average session length
Increased retention, as measured by a 20% decrease in churn rate

Risk & Challenges

User adoption of new features may be slow.
Changes to the user interface may confuse existing users.
Integration of new features with existing infrastructure may prove to be technically challenging.

Linked Initiative:

[TK]: Duplication Request to AI (backend task)

Description:

[Brief description of the task]

Acceptance Criteria:

Criteria 1: [Description of acceptance criteria 1]
Criteria 2: [Description of acceptance criteria 2]
Criteria 3: [Description of acceptance criteria 3]

Linked User Story:

[US]: Collapsed Building Data

User Story - As a [persona], I [want to], [so that].

As an ER responder, I would like to see the collapsed buildings so that I can have a better understanding of the damage.

Acceptance Criteria:

User activates the building layer and a multi-select sub list appears with the following options (collapsed, major damage, minor damage, no damage).
The data should be accurate.
The user can click on a building to see more detailed information about the damage and address information.
The user can see how the data was produced in the detailed information when they click on the point.
Desktop view and Mobile view provides the same quality and level of information.

[US]: Include Next - Previous Button - PENDING

User Story - As a [persona], I [want to], [so that].

acikyazilimagi/deprem-yardim-frontend#550

Acceptance Criteria:

Accuracy: The confirmed location information displayed to the ER responder is accurate and up-to-date.
Efficient use of time: The ER responder is able to respond to emergency situations more efficiently by using the confirmed location information.
Efficient use of time: The ER responder is able to respond to emergency situations more efficiently by using the confirmed location information.

Success Criteria:

Confirmed Locations are displayed in real-time: The ER responder is able to see the most up-to-date confirmed location information in real-time.
Confirmed location information is accurate: The confirmed location information displayed to the ER responder is accurate and matches the information provided by the dispatch center.
Confirmed location information is easily accessible: The ER responder is able to access the confirmed location information quickly and easily, without having to navigate through multiple screens or menus.

Linked Epic:

[ACT]: Tooltips Creation

Description

As a user, I would like to see what the buttons on the website do so that I can understand the purpose of the buttons.

Acceptance Criteria

Each button on the website should have a clear and concise label that describes its purpose.
When the user hovers over a button, a tooltip or label should appear to provide additional information about the button's function.
Clicking on a button should trigger the expected action or behavior, and any errors or unexpected behavior should be clearly communicated to the user.
The buttons should be consistent in design and placement across all pages of the website, to provide a seamless and intuitive user experience.
If there are any variations or exceptions to the button behavior (such as for different user roles or in specific contexts), these should be clearly communicated to the user through tooltips, labels, or other means.
The button labels and functionality should be reviewed and tested regularly to ensure that they remain up-to-date and relevant to the user's needs.

[ACT]: Cybersecurity - Define Scope of Work

Description

We need to get in touch with cybersecurity. Define the scope of work

Items to Complete

Contact Cybersecurity
Update contact list of all team leads in Wiki (to be created)
Prepare a doc
Share the doc in Wiki

[ACT]: MosCoW Board

Description

Create a board as Must-Should-Could-Would.

[ACT]: Display Metadata for User - Legal Response

Description

We need to determine how we will move forward with displaying data information details.

Figma Link

Items to Complete

There is confusion with the confirmed option. This feature will help users to understand where the data is coming from.
If we release this feature, we must provide the source details. This includes where the data comes from etc. Also, this should be confirmed with the Legal team.
We should confirm with the legal team whether we will follow the legislation of EU, NA, or only Turkey. This application is moving forward in a more global sense.
Action Item 1 for Caner, Sena, Hande
Action Item 2,3 for Hande, Oguz

Due Date

<date>

Supporting Information (Optional)

There are ongoing discussion items. I will reference them here later.

[TK]: Cron Job Setup for Deduplication API for External Resources

Description:

Linked Issue: acikyazilimagi/deprem-yardim-address-api#29

feeds_location_202302121825.csv
feeds_entry_202302121508.csv

[ACT]: Figma link in Onboarding Docs

Description

The Figma link should be included in the onboarding docs.

[US]: Data Refresh Interval - PENDING

User Story - As a [persona], I [want to], [so that].

acikyazilimagi/deprem-yardim-frontend#632

Acceptance Criteria:

Accuracy: The confirmed location information displayed to the ER responder is accurate and up-to-date.
Efficient use of time: The ER responder is able to respond to emergency situations more efficiently by using the confirmed location information.
Efficient use of time: The ER responder is able to respond to emergency situations more efficiently by using the confirmed location information.

Success Criteria:

Confirmed Locations are displayed in real-time: The ER responder is able to see the most up-to-date confirmed location information in real-time.
Confirmed location information is accurate: The confirmed location information displayed to the ER responder is accurate and matches the information provided by the dispatch center.
Confirmed location information is easily accessible: The ER responder is able to access the confirmed location information quickly and easily, without having to navigate through multiple screens or menus.

Linked Epic:

[US]: Basemap-Layer Differentiate

User Story - As a [persona], I [want to], [so that].

As a user, I would like to see a clear difference between base map options and selectable layers on the map.
See attached.

Acceptance Criteria:

When the map is first loaded, the base map should be displayed with a clear visual distinction from the selectable layers.
The base map should be labeled as such, and the user should be able to distinguish it from the selectable layers.
When the user selects a layer, the base map should remain visible and the selected layer should be clearly highlighted.
The user should be able to easily distinguish which layer is currently selected.
If the user selects multiple layers, all selected layers should be clearly highlighted and differentiated from the base map.
The user should be able to easily toggle layers on and off without affecting the base map.
The selected layers should be positioned above the base map in the layer stack, to clearly indicate their overlay on the base map.
The user should be able to easily return to the base map view without any confusion or difficulty.

[US]: The information "How the data is sent, verified, used" should be added - PENDING

acikyazilimagi/deprem-yardim-frontend#831

User Story - As a [persona], I [want to], [so that].

As a ER responder, I want to see confirmed locations so that I don't waste time at incorrect locations

Acceptance Criteria:

Accuracy: The confirmed location information displayed to the ER responder is accurate and up-to-date.
Efficient use of time: The ER responder is able to respond to emergency situations more efficiently by using the confirmed location information.
Efficient use of time: The ER responder is able to respond to emergency situations more efficiently by using the confirmed location information.

Success Criteria:

Confirmed Locations are displayed in real-time: The ER responder is able to see the most up-to-date confirmed location information in real-time.
Confirmed location information is accurate: The confirmed location information displayed to the ER responder is accurate and matches the information provided by the dispatch center.
Confirmed location information is easily accessible: The ER responder is able to access the confirmed location information quickly and easily, without having to navigate through multiple screens or menus.

Linked Epic:

[IN]: Afet Harita Mobile - PENDING

Overview

A brief description of the initiative and its goals.

Background

A more detailed explanation of the context and need for the initiative.

Objectives

List of specific, measurable objectives that the initiative aims to achieve.

Stakeholders

List of individuals or teams who will be impacted by the initiative.

Success Criteria

List of specific, measurable criteria that will be used to determine whether the initiative was successful.

Dependencies

List of any external factors or other initiatives that this initiative depends on.

Timeline

An estimated timeline for the initiative, including key milestones and deadlines.

Budget (If needed)

An estimated budget for the initiative, including any necessary resources and funding.

Risks

A list of potential risks associated with the initiative and strategies for mitigating those risks.

Product Strategy Document

Description

Writing the Product Strategy Document for the Afet Harita to cover our focus areas to enlighten the roadmap vision and the strategy.

Success Criteria

Should be published in the repo
Should cover focus areas
Should identify our focus areas clearly

[US]: User Guide

User Story - As a [persona], I [want to], [so that].

acikyazilimagi/deprem-yardim-frontend#832

On process.

Acceptance Criteria:

Accuracy: The confirmed location information displayed to the ER responder is accurate and up-to-date.
Efficient use of time: The ER responder is able to respond to emergency situations more efficiently by using the confirmed location information.
Efficient use of time: The ER responder is able to respond to emergency situations more efficiently by using the confirmed location information.

Success Criteria:

Confirmed Locations are displayed in real-time: The ER responder is able to see the most up-to-date confirmed location information in real-time.
Confirmed location information is accurate: The confirmed location information displayed to the ER responder is accurate and matches the information provided by the dispatch center.
Confirmed location information is easily accessible: The ER responder is able to access the confirmed location information quickly and easily, without having to navigate through multiple screens or menus.

Linked Epic:

[EP] Improving Filter Structure for Map

Description

With the latest updates that were deployed on 12 Feb, the filter structure of the map has been negatively affected. Some data were implemented as layers and some filters were not related to these layers. This has made it difficult to return the right data when combining filters and layers, and they were not useful for all purposes of the map.

Objective

The objective of this epic is to improve the filter structure of the map so that it returns the right data and is useful for all purposes.

Solution

Divide the filters into three groups: victims' information, help calls, and services. Each group will have categories with multiple selection options. The layers will only have visible map type (satellite, etc.) and map content (heat map and markers).

https://www.figma.com/file/ndZkyLsSzpXtEbGGcBxyOa/Afetharita-filtre-yap%C4%B1s%C4%B1?node-id=0%3A1&t=p57hLhvoECs6yFGs-0

Filter Updates are below:
https://www.figma.com/file/sctw6xtcdoFOfmE0gC97Ft/Afet-Harita---Afetharita.com?node-id=5383%3A11160&t=453ihQvDDpYAOPkT-0

https://www.figma.com/file/sctw6xtcdoFOfmE0gC97Ft/Afet-Harita---Afetharita.com?node-id=5383%3A11182

Benefits

By improving the filter structure, the map will be more user-friendly and provide accurate data. This will make it easier for users to find the information they need and make better-informed decisions. Additionally, having a clear and organized filter structure will improve the overall functionality of the map.

Acceptance Criteria:

User clicks on the "Resque Help (Afetzede Bilgileri)"
Then time and source sub-filters appear
AND user clicks Time and sees the options listed in the ER diagram.
Then user clicks source AND sees the options listed in the ER diagram
If user clicks Confirmed (Teyitli), then the following options Confirmed(Teyitli) and Social Media appear
User can one or both of them AND map is updated based on the selection.

Each filter group has multiple selection categories.
Filter and layer selection options return the right data when combined.
Filter structure is user-friendly and easy to understand.

Success Criteria:

Increased user satisfaction with the map, as measured by a user survey or feedback mechanism.
Improved accuracy of data returned by the map, as measured by comparison to a trusted data source.
Increased usage of the map, as measured by tracking the number of unique users and the frequency of use.
Improved decision-making ability for users, as measured by feedback from users and stakeholders.

Risk & Challenges

There may be ongoing maintenance and support associated with the new filter structure, which must be taken into account.
User adoption of new features may be slow.
Changes to the user interface may confuse existing users.
Integration of new features with existing infrastructure may prove to be technically challenging.

[TK]: Notify Time is Incorrect. Label should be Notification Time

Description:

The date calculation is incorrect and the label should be notification time instead of notify time.

Acceptance Criteria:

The date calculation is fixed and now displays the correct date.
The label "Notify time" is changed to "Notification time" throughout the relevant system or documentation.
The change is made in all applicable languages and translations.
The change is reviewed and approved by the relevant stakeholders, such as the product owner or project manager.
The change is tested to ensure that it does not introduce new bugs or issues.
The change is deployed to the relevant system or systems.
The change is communicated to relevant users, if applicable.
The change is documented in relevant release notes or other documentation.

Linked User Story:

[ACT]: Doc Translation

Description

There are many docs that must be translated. We should get their translation team's help with translation.

[US]: Focus User Location

User Story - As a [persona], I [want to], [so that].

acikyazilimagi/deprem-yardim-frontend#547

Acceptance Criteria:

Accuracy: The confirmed location information displayed to the ER responder is accurate and up-to-date.
Efficient use of time: The ER responder is able to respond to emergency situations more efficiently by using the confirmed location information.
Efficient use of time: The ER responder is able to respond to emergency situations more efficiently by using the confirmed location information.

Success Criteria:

Confirmed Locations are displayed in real-time: The ER responder is able to see the most up-to-date confirmed location information in real-time.
Confirmed location information is accurate: The confirmed location information displayed to the ER responder is accurate and matches the information provided by the dispatch center.
Confirmed location information is easily accessible: The ER responder is able to access the confirmed location information quickly and easily, without having to navigate through multiple screens or menus.

Linked Epic:

ACT - Documentation & Confirmation of DepremYardim Data implementation to AfetHarita

Meeting Defined Action

There is a form at https://depremyardim.com/. We are not sure if the data coming from depremyardim is getting implemented to AfetHarita.

Success Criteria

This information should be documented and published in Github Roadmap Repo

Due Date

ASAP

Supporting Information

[US]: Hospital Data Driven from Google API

User Story - As a [persona], I [want to], [so that].

As a user, I would like to see more details about the hospital locations such as phone number.

Currently, Hospital data is driven from Ahbap and we only have the hospital name. Instead, we should use Google API data so that we can also other information such as phone numbers,

Acceptance Criteria:

All hospital data in the system is updated to include additional information, such as phone numbers and addresses, retrieved from the Google API.
The integration is documented, including details such as how the API data is retrieved, how often it is updated, and any limitations or restrictions on its use.
The integration is reviewed and approved by relevant parties, such as the legal or compliance team, to ensure that it complies with all relevant regulations and policies.
Any necessary training or guidance is provided to relevant system users, such as data entry staff, to ensure that they know how to properly use and interpret the new data.
A plan is put in place to periodically review and update the Google API data to ensure that it remains accurate and up-to-date.
A feedback mechanism is put in place to allow users to report any issues or errors with the integrated data, and a process is established to promptly address and resolve any reported issues.
[ ]

Success Criteria:

Hospital data in the system must be updated with additional information retrieved from the Google API, including phone numbers and addresses.
The updated hospital data must be tested and verified to ensure that it is accurate and reliable, with a maximum error rate of 1%.

[TK]: Enhancement on map layer

Define your request

Relocating the map layer button.
In our new map design, the map layer button is expected to be at the bottom left corner of the map.
Some areas (Ahbap Konumları, Hastaneler, Sıcak Yemek and Teleteyit) are expected to be removed from map details.
Map type will stay constant.
Map details( markers and locations) are going to be enabled by default.