Closed Aparna1Gopal closed 1 year ago
Progress: "What is the current status of your project? What have you completed and what is left to do?"
Working on the following related Issues: (Research resources and progress are interconnected) https://github.com/hackforla/access-the-data/issues/191 https://github.com/hackforla/access-the-data/issues/192 Website User Flows and Wireflows https://github.com/hackforla/access-the-data/issues/145 Currently set up GitHub issues and relevant resources to start on the Research Plan and proceed.
Blockers: "Difficulties or errors encountered." None, as have met with PMs last week to streamline steps related to the product pivot
Availability: "How much time will you have this week to work on this issue?" 6-10 hours
ETA: "When do you expect this issue to be completed?" Ongoing Plan on completing Research Plans for all three above issues this week and create the survey design draft copy for https://github.com/hackforla/access-the-data/issues/191
Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.
Notes
Resources: Gap Analysis
UX MATURITY GAP ANALYSIS Benchmark your UX operation against global best practices
Gap analysis https://www.designmethods.co.uk/ux-strategy/gap-analysis
GSoD 2021: Perl’s Content Audit and Gap Analysis uxplanet.org https://uxplanet.org/tagged/gap-analysis
Unbridged Knowledge Gaps Hurt UX https://www.nngroup.com/articles/unbridged-knowledge-gaps/
Resources: SWOT Analysis
https://www.uxpin.com/studio/blog/competitive-analysis-for-ux/
Resources: Competitive Analysis
https://careerfoundry.com/en/blog/ux-design/competitive-analysis-ux/
https://xd.adobe.com/ideas/process/user-research/guide-to-competitive-analysis-ux-design/
Notes
Steps for Research Plan
Notes
The dependent issue https://github.com/hackforla/access-the-data/issues/191 is currently collecting automated data (for the next 4-5 weeks)
In the meantime, this dependent issue is being worked on https://github.com/hackforla/access-the-data/issues/192, to triangulate with above issue
Progress: "What is the current status of your project? What have you completed and what is left to do?"
Based on Slack communication with PM Lucy C, currently working on this issue while the dependent issue https://github.com/hackforla/access-the-data/issues/191 collects data
Cleaned up the Action items and getting it ready to launch the research with projected timelines
Formulating the Research Plan
Blockers: "Difficulties or errors encountered." None
Availability: "How much time will you have this week to work on this issue?" 6 hours
ETA: "When do you expect this issue to be completed?" 4-5 weeks
Pictures: "Add any pictures of the visual changes made to the site so far." N/A If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.
Progress: "What is the current status of your project? What have you completed and what is left to do?" Formulating Research Plan
Blockers: "Difficulties or errors encountered." None (Will be seeking feedback from PMs and UX Leads once Research Plan is complete)
Availability: "How much time will you have this week to work on this issue?" 6 hours
ETA: "When do you expect this issue to be completed?" Please check projected Timeline under Action Items
Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.
Notes:
SWOT versus Gap Analysis
SWOT has a set framework, whereas a gap analysis can be what you make it
The SWOT analysis uses a simple four-block grid framework to help managers visualize their business from four set perspectives. Although every SWOT analysis is a bit different — with varying outcomes and conclusions — the structure is always the same: strengths, weaknesses, opportunities, and threats.
SWOT is great for organizations starting out, while a gap analysis is great anywhere, anytime Another way that SWOT and gap analyses differ is in when they are best put to use. As a sweeping, big-picture analysis, a SWOT analysis is a great tool for businesses just starting out or when assessing the viability of a new business idea. It’s also appropriate when a business is looking to pivot in another direction or enter a new market.
Although an organization can easily adapt a SWOT analysis for any kind of process or project — even smaller ones — it’s particularly useful when a company is trying to understand its position and potential with a bird’s-eye perspective of the business landscape.
@mxajPrice An FYI, I have currently been working on this issue https://github.com/hackforla/access-the-data/issues/192 as I await the data collection on dependent issue https://github.com/hackforla/access-the-data/issues/191
Hence, I am moving https://github.com/hackforla/access-the-data/issues/192 back into in progress.
And moving https://github.com/hackforla/access-the-data/issues/191 into prioritized backlog for its current data collection duration.
CC: @lrchang2
Progress: "What is the current status of your project? What have you completed and what is left to do?"
Tasks currently working on:
Blockers: "Difficulties or errors encountered." None (Will be seeking feedback from PMs and UX/Dev Leads once Research Plan is complete)
Availability: "How much time will you have this week to work on this issue?" 6 hours
ETA: "When do you expect this issue to be completed?" Please check projected Timeline under Action Items
Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.
Progress: "What is the current status of your project? What have you completed and what is left to do?"
Tasks currently working on:
Blockers: "Difficulties or errors encountered." None (Will be seeking feedback from PMs and UX/Dev Leads once Research Plan is complete)
Availability: "How much time will you have this week to work on this issue?" 6 hours
ETA: "When do you expect this issue to be completed?" Please check projected Timeline under Action Items
Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.
Progress: "What is the current status of your project? What have you completed and what is left to do?"
Tasks currently working on:
Blockers: "Difficulties or errors encountered." None (Will be seeking feedback from PMs and UX/Dev Leads once Research Plan is complete)
Availability: "How much time will you have this week to work on this issue?" 6 hours
ETA: "When do you expect this issue to be completed?" Please check projected Timeline under Action Items
Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.
Progress: "What is the current status of your project? What have you completed and what is left to do?"
Tasks currently working on:
Blockers: "Difficulties or errors encountered." None (Will be seeking feedback from PMs and UX/Dev Leads once Research Plan is complete)
Availability: "How much time will you have this week to work on this issue?" 6 hours
ETA: "When do you expect this issue to be completed?" Please check projected Timeline under Action Items
Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.
Notes:
Resources for Gap Analysis:
A Guide to Competitive Analysis for UX Design Jill DaSilva https://xd.adobe.com/ideas/process/user-research/guide-to-competitive-analysis-ux-design/
Top Things to Know About UX Competitive Analysis Kim Purcell, uxplanet.org https://uxplanet.org/top-things-to-know-about-ux-competitive-analysis-d91689fd8b36
Resources for Accessibility Audit: Introduction to Web Accessibility EdX course (Free)
Progress: "What is the current status of your project? What have you completed and what is left to do?"
Tasks currently working on:
Usability Testing (first click tests)
Blockers: "Difficulties or errors encountered." There is a task limit of 2 minutes on the free version of Usability Hub. This means it will be difficult to test on all 5 selected CKAN websites. Exploring Optimal Workshop as an alternative. (Will be seeking feedback on Research Plan from PMs once Research Plan is complete)
Availability: "How much time will you have this week to work on this issue?" 6 hours
ETA: "When do you expect this issue to be completed?" Please check projected Timeline under Action Items
Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.
Notes:
Free version of the usability testing tools have limited features Can only test two CKAN websites at one time. Testing the intial 4 CKAN websites given by the PM. These four websites are recorded in this issue.
Progress: "What is the current status of your project? What have you completed and what is left to do?"
Tasks currently working on:
Desk Research: https://github.com/hackforla/access-the-data/issues/192#issuecomment-1291442023
Usability Testing (first click tests)
Slack Communication regarding re-using question from LinkedIn, to maintain consistency and obtain different user personas while testing for use flows of CKAN websites https://github.com/hackforla/access-the-data/issues/229 Slack communication: https://github.com/hackforla/access-the-data/issues/192#issuecomment-1301774443
Blockers: "Difficulties or errors encountered." https://github.com/hackforla/access-the-data/issues/192#issuecomment-1293205687
Availability: "How much time will you have this week to work on this issue?" 6-8 hours
ETA: "When do you expect this issue to be completed?" Please check projected Timeline under Action Items
Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.
Notes
Slack Communication:
Hannah Sangra What do you love most about open source data? (Or can ask: what is your favourite use of open-source data?) Increased transparency/reduced corruption Can be used to promote social good (activism) Democratisation of data Promotes innovation (economic value) Other (please comment) What statement best describes your relationship with open-source data? I love open-source data! I use it regularly I’m somewhat familiar with open-source data I don’t use open source data I don’t use open-source data, but I would like to :eyes: 2 :raised_hands: 1
Lucy Chang thanks for this hannah! I like the 2nd question the best. i think it will give us more diverse people versus #1 which i think is leading. Also, I believe that Matt Kushin and Steffie Kim are now using "open access data" in their a/b test. Can we confirm alignment on what term we're using? (edited)
ajPrice I lean towards the first one, I particularly like that it invites people to add a reply we did not even think of. Could give us more insight. Agree with Lucy that we should align on terminology. Also, saying “open access data” includes the word “access” which I think draws the mind to our project.
Hannah Sangra Thanks all! I think the first is more engaging and the second is better for recruitment purposes. I’m leaning towards the second. I prefer open-source data - it’s what it’s commonly referred to
Matt Kushin Great question. Yes, open-access is the preferred term over open-source. :slightly_smiling_face: Explanation For terminology, I think there is a lot of confusion around nomenclature when it comes to open. One thing we are working to make consistent is the use of certain terms. We pivoted to ‘open-access’ data following a clarification from Judson at a September meeting. My. notes from that meeting are: “It was stated by a project team developer, Judson, that the term ‘open-source’ is inaccurate as it pertains to the data, as open-source refers to the source code. But, the project is ‘open-access.’ The term ‘open-access data’' should be used instead.” Resources We’ve been recently working to codify terminology to help with consistency in a glossary of terms. At the moment, our live document glossary of terms is available on the wiki. https://github.com/hackforla/access-the-data/wiki/Copy-Guide Direct link: https://docs.google.com/document/d/1D1UZvIPaN2UlQbezxVlBv2EY34FburAguWZTs4l4x5w/edit?skip_itp2_check=true#
Aparna Gopal Hi Hannah Sangra Just an FYI. I am using/repurposing the second question for the 'usability testing of CKAN websites' issue that I am working on. This will help to maintain consistency across the research content in ATD projects. Also, that question feels like it might be a great way to filter out different user personas who might respond. I am planning on circulating a Pilot of this usability test soon, so you will have a preview of it. Thanks!
Progress: "What is the current status of your project? What have you completed and what is left to do?"
Tasks currently working on:
Desk Research: https://github.com/hackforla/access-the-data/issues/192#issuecomment-1291442023
Usability Testing (first click tests)
Slack Communication regarding re-using question from LinkedIn, to maintain consistency and obtain different user personas while testing for use flows of CKAN websites https://github.com/hackforla/access-the-data/issues/229 Slack communication: https://github.com/hackforla/access-the-data/issues/192#issuecomment-1301774443
Blockers: "Difficulties or errors encountered." https://github.com/hackforla/access-the-data/issues/192#issuecomment-1293205687
Availability: "How much time will you have this week to work on this issue?" 6-8 hours
ETA: "When do you expect this issue to be completed?" Please check projected Timeline under Action Items Need to start recruiting research participants next, once pilot is completed
Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.
Notes Definition of Open Access Data
Zoom chat communication:
Matt K I can provide one, Hannah. This is the definition we used in the A/B test:
"Open-access data refers to data that is feely available for anyone to access, use, download, analyze, copy, or redistribute"
Notes: One on one with Lucy C, PM on November 14, 2022 (Monday)
Comparative Analysis:
Additional Notes for next steps:
Progress: "What is the current status of your project? What have you completed and what is left to do?" https://github.com/hackforla/access-the-data/issues/192#issuecomment-1317137257
Blockers: "Difficulties or errors encountered." None Currently re-working and re-strategizing based on feedback during one-on-one meeting with PM, based on ATD product vision
Availability: "How much time will you have this week to work on this issue?" 3-6 hours
ETA: "When do you expect this issue to be completed?" 4 weeks
Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.
Notes
Additional Resources
https://www.nngroup.com/articles/thematic-analysis/ https://www.userinterviews.com/ux-research-field-guide-chapter/research-analysis https://usabilitygeek.com/how-to-do-ux-competitor-analysis/ https://uxplanet.org/top-things-to-know-about-ux-competitive-analysis-d91689fd8b36 https://xd.adobe.com/ideas/process/user-research/guide-to-competitive-analysis-ux-design/ https://www.uxpin.com/studio/blog/competitive-analysis-for-ux/ https://gathercontent.com/blog/2-ways-to-boost-ux-through-content-usability-analysis https://www.usertesting.com/blog/content-testing-and-measurement https://maze.co/blog/content-testing/
Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered." None Currently re-working and re-strategizing based on feedback during one-on-one meeting with PM, based on ATD product vision
Availability: "How much time will you have this week to work on this issue?" 3-6 hours
ETA: "When do you expect this issue to be completed?" 4 weeks
Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.
Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?" 4-6 hours
ETA: "When do you expect this issue to be completed?" By end of Jan
Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.
Notes:
Based on 1-1 with PM, AJ during team meeting today (January 11, 5PM-6PM PST), the following was discussed https://github.com/hackforla/access-the-data/issues/192#issuecomment-1378299535
The issue is being cleaned up to focus on a specific area of comparative analysis (assessing data points across 5 selected CKAN websites, conduct gap analysis with ATD website and present research findings). This aligns with current product roadmap and is also re-scoping the issue to create more immediate & targeted impact.
The Action Items have been edited and re-written based on the re-scoping
This issue has been converted from 5 point to 3 point based on the current re-scoping
The depreciated items are noted below for documentation & records
DEPRECIATED [To Copy in the Comments section and delete this section from Action Items] Comparative Analysis of CKAN websites [Projected timeline end-to-end 2-3 weeks]
Accessibility audit [Projected timeline end-to-end 1-2 weeks]
Create Wiki Issue and complete Wiki for the following
Track in a separate issue First click tests (unmoderated usability testing) of CKAN websites Usability Testing (first click tests) [Projected timeline end-to-end 4-6 weeks]
Create Wiki Issue and complete Wiki for the following
Progress: "What is the current status of your project? What have you completed and what is left to do?" Completed Research Plan in Dovetail. Transferring this to ATD Google docs Setting up the study in Dovetail to analyse the 5 selected CKAN websites
Blockers: "Difficulties or errors encountered." None.
Availability: "How much time will you have this week to work on this issue?" 4-5 hours
ETA: "When do you expect this issue to be completed?" Aiming to complete a rough draft of the comparative analysis to discuss at next week's Team meeting
Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.
@Aparna1Gopal Please add update using this template (even if you have a pull request)
Progress: "What is the current status of your project? What have you completed and what is left to do?" Blockers: "Difficulties or errors encountered." Availability: "How much time will you have this week to work on this issue?" ETA: "When do you expect this issue to be completed?" Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
Progress: "What is the current status of your project? What have you completed and what is left to do?" Completing Research Plan for the issue, Identifying the correct methodology & documenting it step by step.
Blockers: "Difficulties or errors encountered." Time, will be sharing this research plan during this week with the PMs, & then proceeding to the analysis
Availability: "How much time will you have this week to work on this issue?" 4-6 hours
ETA: "When do you expect this issue to be completed?" Next week
Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.
@Aparna1Gopal submitted her research plan to PMs on 30 January for review. We will start looking at this at the PM meeting on 31 January.
Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered." None Depends on the feedback whether major or minor changes
Availability: "How much time will you have this week to work on this issue?" 4-6 hours
ETA: "When do you expect this issue to be completed?" 2 weeks
Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.
Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered." None
Availability: "How much time will you have this week to work on this issue?" 4-6 hours
ETA: "When do you expect this issue to be completed?" 2 weeks
Progress: "What is the current status of your project? What have you completed and what is left to do?" Set up the study in Dovetail to start collecting & analysing the data Working through the 5 CKANs
Blockers: "Difficulties or errors encountered." None
Availability: "How much time will you have this week to work on this issue?" 4-6 hours
ETA: "When do you expect this issue to be completed?" 1 week
Notes: @Aparna1Gopal https://github.com/hackforla/access-the-data/issues/191#issuecomment-1161162468
Competitor websites identified based on PMs' product vision. Contacted PM (Lucy C & AJ) via Slack. Below are the websites to be tested on:
https://africaopendata.org/ https://hri.fi/en_gb/ https://data.gov/ https://data.humdata.org/
I am going to be adding https://data.gov.sg/, as well due to their active use of iconography/favicons on their website.
@Aparna1Gopal Please add update using this template (even if you have a pull request)
Progress: "What is the current status of your project? What have you completed and what is left to do?" Blockers: "Difficulties or errors encountered." Availability: "How much time will you have this week to work on this issue?" ETA: "When do you expect this issue to be completed?" Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered." None Just taking more time than planned as the CKAN websites are dense
Availability: "How much time will you have this week to work on this issue?" 4-6 hours
ETA: "When do you expect this issue to be completed?" 1 week
@Aparna1Gopal Please add update using this template (even if you have a pull request)
Progress: "What is the current status of your project? What have you completed and what is left to do?" Blockers: "Difficulties or errors encountered." Availability: "How much time will you have this week to work on this issue?" ETA: "When do you expect this issue to be completed?" Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
Progress: "What is the current status of your project? What have you completed and what is left to do?" Completed: Completed the data collection across 3 CKAN websites on Dovetail Left to do: Data collection across 2 CKAN websites, compare & contrast with ATD Website, complete the report
Blockers: "Difficulties or errors encountered." The websites are dense so picking & choosing which aspects to collect & analyse. Based on last week's team meeting, only focusing on the aspects that aligns with ATD's vision.
Availability: "How much time will you have this week to work on this issue?" 4-6 hours
ETA: "When do you expect this issue to be completed?" 1 week
Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.
@Aparna1Gopal Please add update using this template (even if you have a pull request)
Progress: "What is the current status of your project? What have you completed and what is left to do?" Blockers: "Difficulties or errors encountered." Availability: "How much time will you have this week to work on this issue?" ETA: "When do you expect this issue to be completed?" Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
Progress: "What is the current status of your project? What have you completed and what is left to do?" Completed: Data Collection - Completed the data collection across 5 CKAN websites on Dovetail. Used the elements on CKAN closest to current ATD prototype to compare. Left to do: Data Analysis (thematic analysis), compare & contrast with ATD Website, complete the report Also met with 311-data PM team to discuss ATD's Comparative analysis strategy (knowledge transfer)
Blockers: "Difficulties or errors encountered." Nothing in particular. Just sorting through the different CKANs.
Availability: "How much time will you have this week to work on this issue?" 4-6 hours
ETA: "When do you expect this issue to be completed?" 1 week Presenting draft of the report next week at team meeting
Pictures: "Add any pictures of the visual changes made to the site so far."
Progress: "What is the current status of your project? What have you completed and what is left to do?"
Completed: Data Collection - Completed the data collection across 5 CKAN websites on Dovetail. Used the elements on CKAN closest to current ATD prototype to compare.
Left to do: Data Analysis (thematic analysis), compare & contrast with ATD Website, complete the report
Added another CKAN website to the Analysis (opendata.swiss). Based on last week's team meeting & this website serving as a good example of a potential CKAN to replicate for ATD.
Blockers: "Difficulties or errors encountered." Nothing in particular. Just sorting through the different CKANs.
Availability: "How much time will you have this week to work on this issue?" 4-6 hours
ETA: "When do you expect this issue to be completed?" 1-2 weeks Working on draft of Research results & findings
Pictures: "Add any pictures of the visual changes made to the site so far."
Progress: "What is the current status of your project? What have you completed and what is left to do?"
Completed: Data Collection - Completed the data collection across 6 CKAN websites on Dovetail. Used the elements on CKAN closest to current ATD prototype to compare. Added another CKAN website to the Analysis (opendata.swiss). Based on team meeting consensus, this website serves as a good example of a potential CKAN to replicate for ATD.
Left to do: Data Analysis (thematic analysis), compare & contrast with ATD Website, complete the report. Towards the end of the analysis & putting together the draft report. Working on draft of Research results & findings.
Blockers: "Difficulties or errors encountered." None
Availability: "How much time will you have this week to work on this issue?" 4-6 hours
ETA: "When do you expect this issue to be completed?" 1 week
Pictures: "Add any pictures of the visual changes made to the site so far."
@Aparna1Gopal Please add update using this template (even if you have a pull request)
Progress: "What is the current status of your project? What have you completed and what is left to do?" Blockers: "Difficulties or errors encountered." Availability: "How much time will you have this week to work on this issue?" ETA: "When do you expect this issue to be completed?" Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
Progress: "What is the current status of your project? What have you completed and what is left to do?" Completed Affinity Mapping & Data Analysis Putting together the Wiki & Report
Blockers: "Difficulties or errors encountered." None
Availability: "How much time will you have this week to work on this issue?" 4-6 hours
ETA: "When do you expect this issue to be completed?" 2-3 days
Pictures: "Add any pictures of the visual changes made to the site so far."
Progress: "What is the current status of your project? What have you completed and what is left to do?"
The following documents are being worked on:
Blockers: "Difficulties or errors encountered." None
Availability: "How much time will you have this week to work on this issue?" 4-6 hours
ETA: "When do you expect this issue to be completed?" 2-3 days
Pictures: "Add any pictures of the visual changes made to the site so far."
@mxajPrice @Cathyyyyyyyy
This is complete.
Overview
Action Items
Comparative Analysis of CKAN websites
Documentation
Resources/Instructions
Selecting UX RESEARCH METHODS Research Plan for UX studies Usability Testing: Gap Analysis Inclusive Design and Accessibility Usability Testing: First Click Tests Sample Size: Selecting the right sample size in your UX Research Likert Scale Competitive/Comparative Spreadsheet for Website Template
Google Drive
Wiki
TEMPLATE FOR PROJECT PROGRESS
Progress: "What is the current status of your project? What have you completed and what is left to do?" Blockers: "Difficulties or errors encountered." Availability: "How much time will you have this week to work on this issue?" ETA: "When do you expect this issue to be completed?" Pictures: "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either:
ask for help at your next meeting put a "Status: Help Wanted" label on your issue and pull request put up a request for assistance on the #access-the-data channel.