ThinkTank Meetings: Difference between revisions

From Javul
Jump to navigation Jump to search
VisualWikitext
No edit summary
No edit summary
 
(53 intermediate revisions by 3 users not shown)
Line 5: Line 5:
*'''Marko Cadsawan's ideas:''' [https://drive.google.com/drive/folders/18u0mIY7TpVKxJxN4h6suo3ZWTqaEwsdd?usp=sharing Marko's Shared GDrive]
*'''Marko Cadsawan's ideas:''' [https://drive.google.com/drive/folders/18u0mIY7TpVKxJxN4h6suo3ZWTqaEwsdd?usp=sharing Marko's Shared GDrive]
* '''Dev's Ideas:''' [https://drive.google.com/drive/folders/128388fqInTQphyDsdDzUO3FmBRSTs-mm Google Drive]
* '''Dev's Ideas:''' [https://drive.google.com/drive/folders/128388fqInTQphyDsdDzUO3FmBRSTs-mm Google Drive]
* Bilal's ideas: [https://drive.google.com/drive/folders/1NpQCjAsNg25q1FdRepFqtk4GvNxAlOvg?usp=sharing]


Guidelines for Submissions:
;Guidelines for Submissions:
* Our work is focused on the technical side of things: How our website should work, what functionality it would provide
* Focus only on ideas that are very specific and relevant for that week's plan
* Propose what can be done to the current version of the Visual Design (if one is available for that week). Make a Copy of the current design and edit as needed.
* Our work every week is focused on the technical side of things: How our website should work, what specific functionality it would provide
* Research existing websites and tools to get ideas
* It is difficult to process a lot of theory. Presenting theory is ok, if it can be shown how it can be implemented on our website in a visual way
* Propose new/original ideas when possible (ideas don't have to be perfect, they can also just be starting points)
* Propose what can be done to the current version of the Visual Design (if one is available for that week). Make a Copy of the current design and edit as needed
* Research existing websites and tools to get ideas and see how they can be implemented on our designs
* Propose new/original ideas when possible (ideas don't have to be complete or perfect, they can also just be starting points). Find ideas already implemented by looking at the Prototype links above
* Perfectly ok, in fact you are encouraged to take someone's idea from below and improve it so definitely examine ideas that have been selected before.
* Make a new file for each week
* Make a new file for each week
Note: A best attempt is made to select good ideas but some ideas may be missed. If you think something could be very beneficial and needs another look let me know.


{| class="wikitable"
{| class="wikitable"
Line 22: Line 26:
* Looked at the [https://docs.google.com/presentation/d/1tPpuYZktzO8ioIx-ub1RHaSeQqGFonCNYupeNx1_bbw/edit#slide=id.p Project Overview]
* Looked at the [https://docs.google.com/presentation/d/1tPpuYZktzO8ioIx-ub1RHaSeQqGFonCNYupeNx1_bbw/edit#slide=id.p Project Overview]
* Planned for working on the Taxi app idea (will last multiple weeks)
* Planned for working on the Taxi app idea (will last multiple weeks)
|| Example
|| -
|| Research existing Taxi app related issues and imagine how people online would work through those issues.
|| Research existing Taxi app related issues and imagine how people online would work through those issues.
|-
|-
Line 34: Line 38:
* Group voted for using a forum as opposed to an email list for discussions ([https://www.reddit.com/r/open_collab_society/ new sub-reddit])  
* Group voted for using a forum as opposed to an email list for discussions ([https://www.reddit.com/r/open_collab_society/ new sub-reddit])  
||  
||  
* Mark: (1) raised issue about bad-faith editing /Issue verification [2] (2) Add columns for Budgets for each objective in the Objectives table (shown on the Home page) [2] || Continue simulation of Taxi app (go through Ideas, Issues, Tasks)
* Mark: (1) raised issue about bad-faith editing /Issue verification [2] (2) Add columns for Budgets for each objective in the Objectives table (shown on the Home page) [2]  
* Joy: Good effort on analyzing specific Taxi issues [3] (apologies, perhaps I didn't clarify properly. We just had to analyze how the system would work instead of looking at the specific issues given as examples)
|| Continue simulation of Taxi app (go through Ideas, Issues, Tasks)
|-
|-
| 3 || Sunday Dec 19, 2021
| 3 || Sunday Dec 19, 2021
Line 42: Line 46:
* Reviewed [https://docs.google.com/drawings/d/1ib84GP008sghYOgb3quqZGB1WJBqEEkxS-Sg_MpbTzY/edit Taxi App Business] mockup home page again
* Reviewed [https://docs.google.com/drawings/d/1ib84GP008sghYOgb3quqZGB1WJBqEEkxS-Sg_MpbTzY/edit Taxi App Business] mockup home page again
* Discussed Issue resolution with team and got feedback; creating software spec  
* Discussed Issue resolution with team and got feedback; creating software spec  
|| - || Analyze other websites to see how they resolve issues
||  
Joy: We can look at your rewards system analysis when we visit this topic later
 
Mark: (1) Interface design effort [4] (2) Object number shown in tables to help identify objects, however this could be placed differently to take less space, or only shown on the Detailed view [1] (3) Gantt chart for Objectives [2]
|| Analyze other websites to see how they resolve issues
|-
|-
| 4 || Dec 26, 2021  
| 4 || Dec 26, 2021  
||  
||  
* '''Analysis For review''': [https://docs.google.com/document/d/1bQy1zRIaL-lnccOY5B0YJaMWsmkRBYMbBcBao4twEG0/edit?usp=sharing Joy] | [https://docs.google.com/spreadsheets/d/1AoINboKzEDwMg6yCRIOzgwgIkmqtCTndKfnbEk7QOSk/edit?usp=sharing Mark]
* '''Analysis For review''': [https://docs.google.com/document/d/1bQy1zRIaL-lnccOY5B0YJaMWsmkRBYMbBcBao4twEG0/edit?usp=sharing Joy] | [https://docs.google.com/spreadsheets/d/1AoINboKzEDwMg6yCRIOzgwgIkmqtCTndKfnbEk7QOSk/edit?usp=sharing Mark] (revisit later)
* Decision to continue analyzing Issue handling on other websites (focusing on resolution, answers, responses from people etc and how the best responses are chosen). Thats what we'll do next week.  
* Decision to continue analyzing Issue handling on other websites (focusing on resolution, answers, responses from people etc and how the best responses are chosen). Thats what we'll do next week.  
|| Example || Start looking at individual Issue pages and taking a close look at what happens there from Issue reporting to resolution and task creation. Focus on resolving a single issue and look closely at what activity takes place. We look at Issue creation, definition, sub-issues (if any), a 'Resolution Wiki' and how Tasks are defined and linked
||  
Joy: (1) Gantt chart for progress [2] (2) Chat for the team however its already implemented in our Prototype design [2] (3) Tags for issues [1]
 
Mark: (1) Tags for issues [1]
|| Start looking at individual Issue pages and taking a close look at what happens there from Issue reporting to resolution and task creation. Focus on resolving a single issue and look closely at what activity takes place. We look at Issue creation, definition, sub-issues (if any), a 'Resolution Wiki' and how Tasks are defined and linked
|-
|-
| 5 || Jan 2, 2022  
| 5 || Jan 2, 2022  
Line 85: Line 97:
|| Dev: Add Upvote/Downvote counter next to the issue (this exists in our Ranking system) [2]. Tags in Issues for skill-matching [2] || For the next few weeks, we will research problem-solving software and tools, any methods they use and see how any of that can be used for our Taxi app business. (some problem-solving theory is ok)
|| Dev: Add Upvote/Downvote counter next to the issue (this exists in our Ranking system) [2]. Tags in Issues for skill-matching [2] || For the next few weeks, we will research problem-solving software and tools, any methods they use and see how any of that can be used for our Taxi app business. (some problem-solving theory is ok)
|-
|-
| 11 || Feb 27, 2022 || '''Analysis For review''': || Selected Ideas || Plans for next week
| 11 || Feb 27, 2022 || '''Analysis For review''': Problem Solving-- [https://docs.google.com/document/d/1vELQY_wiE2cko5cu38htMzkawjo4IG_psB3FUanfIFk/edit Joy] -  [https://docs.google.com/document/d/1ejcqc2J6VunzsqPIKA__TKF7akWFsFeNnhrjacMjAGo/edit?usp=drive_web&ouid=100959973373050589963 Dev] - [https://docs.google.com/document/d/1v33KjP_AHbORZoCxnVnxWQsegWQmDj5nNbXBsKKbmX4/edit?usp=sharing Mark] (stackexchange)||
Selected Ideas : Joy: 'Resolution wiki' (or issue wiki) could have guided sections for Root Causes. Possibly needs more study [2] -- Mark: (1) Quality control/guided process to help users create higher quality data entries [2]. (2) General process of submitting something and guided through it [1]
|| Using Google find as many "problem-solving" software and tools as you can and then if you have time and if that information is available, make a summarized list of their key features and think about how we can use it for our project. Search terms can include alternative words for example problem solving software/tool, solution finding software, problem management software, etc.  A small amount of problem-solving theory is ok.
|-
|-
| 12 || Mar 6, 2022 || '''Analysis For review''': || Selected Ideas || Plans for next week
| 12 || Mar 6, 2022 ||
|-
'''Analysis For review''': [https://docs.google.com/document/d/1pv-caXnhGrF6hqhzMmIs-h7g6sGKx3q0/edit Mark] | [https://docs.google.com/document/d/1_UO6k0wygsbp_1_a8qKy9UTH9wb_1WBczLMhgHYzxNc/edit?usp=sharing Joy] | [https://docs.google.com/document/d/1SuSUjifNbZL1i-BTWUWyREd-U1RScuF637Z0GupfGLw/edit?usp=sharing Dev] 
| 13 || Mar 13, 2022 || '''Analysis For review''': || Selected Ideas || Plans for next week
||  
'''Mark''': [https://docs.servicenow.com/bundle/sandiego-it-service-management/page/product/problem-management/task/investigate-root-cause.html Service Now, Root cause analysis] {{br}} '''Joy''': [https://www.sysaid.com/it-service-management-software/problem-management SysAid Problem Management], [https://haloitsm.com/problem-management-software/ HaloITSM Problem Management], [https://freshservice.com/it-service-management/problem-management Freshservice] (see root cause analysis feature) {{br}} '''Dev''': [https://www.moresteam.com/engineroom/features.cfm Engineroom] (discover solutions), [https://www.softexpert.com/produto/problem-management/ SoftExpert Problem Management], [https://www.servicenow.com/products/problem-management.html ServiceNow] (Problem Management) {{br}}{{br}} Others: [https://www.causelink.com/how-it-works CauseLink], [https://realitycharting.com/root-cause-analysis-software RC Pro Root Cause Analysis Software] (found via search term: 'root cause analysis problem solving software')
 
|| (1) Understand what task management is (see Prototype website description). We are focusing on how tasks are created, assigned, completed and evaluated). A special focus on Task Bidding (when multiple people are involved).
(2) Do an initial search to find tools and websites that focus on Task management. Make a list of those tools, no analysis needed. Include this list of your initial research in the first section of your analysis.
(3) Revisit that list to find the best tools you can which are most related to Task management. No discussion or analysis is needed on other topics or anything which does not give us new information. Focus on finding the Best and Most Relevant tools with unique features. thank you
|-
|-
| 14 || Mar 20, 2022 || '''Analysis For review''': || Selected Ideas || Plans for next week
| 13 || Mar 13, 2022 ||
'''Analysis For review''': [https://docs.google.com/document/d/1gc12SXVBjxl3EgB9Np-uFZgdcZtIVVVzg3XDkozDGFM/edit?usp=sharing Joy] |  [https://docs.google.com/document/d/1ue6tqQkxejlPbqRAOnPx_A7PNf1rf6EO81_agxo1VKI/edit?usp=sharing Mark] | [https://docs.google.com/document/d/1Kk5VGFLeebkCCKxVzlY-w3gQ7yPxtalVyjtTUybThjc/edit?usp=sharing Dev]
|| Selected Ideas || (no plans for next few weeks, taking a break to catch and re-evaluate)
|}
|}


==Tentative Plan for Meetings==
==Tentative Plan for Meetings==
Line 102: Line 121:
** Issue Detail Page
** Issue Detail Page
** Problem-solving software
** Problem-solving software
** Task Management (all stages: creation, assignment, completion, evaluation etc)
** Task Management (all stages: creation, assignment, completion, evaluation etc) + Flowchart
** Connecting all these: Skill-matching, task skills for searching, recommendations etc
** Reward/Motivational Systems
** Reputation systems (Idea points, Activity points). Also linked to Rewards/Motivational systems
** Ideas
** Ideas
** Objectives
** Objectives
** Connection all these: Skill-matching, task skills for searching, recommendations etc
** Misc topics:
** Reward/Motivational Systems
*** Solutions database: If a solution has been found, it should be easy to find it for others who want to know (how do we design this). Example: Loud vehicles with illegal exhaust modifications (how to deal with this)
** Reputation systems (Idea points, Activity points). Also linked to Rewards/Motivational systems
*** Analytics (what kinds to have)
** Re-assess previous topics and look at the existing system from an over-all view
** Decision Making module (community owned businesses and others need this module)
** Decision Making module (community owned businesses and others need this module)
* Interface customization
* Interface customization
* Administration (moderation), Interface setup (e.g. Defining types of Issues, tags, categories)
* Administration (moderation), Interface setup (e.g. Defining types of Issues, tags, categories)
* Unit Generalization/Creation (for other types of units)
* Unit Generalization/Creation (for other types of units)
* ...
* ..

Latest revision as of 04:12, 19 February 2023

Project Links

This is a ThinkTank for designing a website that helps people solve problems in society and manage their related tasks and goals and get rewarded for it. See Project Overview (Google powerpoint)

Guidelines for Submissions
  • Focus only on ideas that are very specific and relevant for that week's plan
  • Our work every week is focused on the technical side of things: How our website should work, what specific functionality it would provide
  • It is difficult to process a lot of theory. Presenting theory is ok, if it can be shown how it can be implemented on our website in a visual way
  • Propose what can be done to the current version of the Visual Design (if one is available for that week). Make a Copy of the current design and edit as needed
  • Research existing websites and tools to get ideas and see how they can be implemented on our designs
  • Propose new/original ideas when possible (ideas don't have to be complete or perfect, they can also just be starting points). Find ideas already implemented by looking at the Prototype links above
  • Perfectly ok, in fact you are encouraged to take someone's idea from below and improve it so definitely examine ideas that have been selected before.
  • Make a new file for each week

Note: A best attempt is made to select good ideas but some ideas may be missed. If you think something could be very beneficial and needs another look let me know.

Week # Date Meeting Minutes Selected Ideas/Inputs Plan for next week
1 Sunday Dec 5, 2021
  • Looked at the Project Overview
  • Planned for working on the Taxi app idea (will last multiple weeks)
 - Research existing Taxi app related issues and imagine how people online would work through those issues.
2 Sunday Dec 12, 2021
  • Analysis For review: Joy | Mark
  • Reviewed Taxi App Business mockup home page
  • Issues/Questions raised:
    • Nuno: The difference between Objectives and Tasks is not completely clear and may confuse people. Updated the Guides explaining the different concepts used on the website. See here
    • Alex: How would interface work when the business is just being initiated? - (great question; we will have to revisit this later. Currently looking into community owned businesses and how they're formed). We'll have a site-wide guide later.
  • Group voted for using a forum as opposed to an email list for discussions (new sub-reddit)
  • Mark: (1) raised issue about bad-faith editing /Issue verification [2] (2) Add columns for Budgets for each objective in the Objectives table (shown on the Home page) [2]
 Continue simulation of Taxi app (go through Ideas, Issues, Tasks)
3 Sunday Dec 19, 2021
  • Analysis for review: Joy | Mark
  • Reviewed Taxi App Business mockup home page again
  • Discussed Issue resolution with team and got feedback; creating software spec

Joy: We can look at your rewards system analysis when we visit this topic later

Mark: (1) Interface design effort [4] (2) Object number shown in tables to help identify objects, however this could be placed differently to take less space, or only shown on the Detailed view [1] (3) Gantt chart for Objectives [2]

Analyze other websites to see how they resolve issues
4 Dec 26, 2021
  • Analysis For review: Joy | Mark (revisit later)
  • Decision to continue analyzing Issue handling on other websites (focusing on resolution, answers, responses from people etc and how the best responses are chosen). Thats what we'll do next week.

Joy: (1) Gantt chart for progress [2] (2) Chat for the team however its already implemented in our Prototype design [2] (3) Tags for issues [1]

Mark: (1) Tags for issues [1]

Start looking at individual Issue pages and taking a close look at what happens there from Issue reporting to resolution and task creation. Focus on resolving a single issue and look closely at what activity takes place. We look at Issue creation, definition, sub-issues (if any), a 'Resolution Wiki' and how Tasks are defined and linked
5 Jan 2, 2022 - Next week we'll focus on resolving a single issue and look closely at what activity takes place. We look at Issue creation, definition, sub-issues (if any), a 'Resolution Wiki' and how Tasks are defined and linked
6 Jan 9, 2022 - (break for next few weeks)
7 Jan 30, 2022 Looked at work from Jan 9.
  • (Joy): Issues Kanban Board (vertical columns for In-Work, Resolved, etc Example), Color coding for various items. (later) custom work flows. Business rules (zoho) || Continue looking at issue details, focusing on new features. Resolving issues, solutions (wiki, collaborative type of work, multiple users involved)
8 Feb 6, 2022
  • Analysis For review: Joy
  • Trying a new approach from today, the team will be directly editing the Visual designs in Google docs and we'll meet to review suggested changes. First design is the main page: Taxi App Home page. Ideas previously submitted can be used if needed.
  • Joy: (1) When submitting an issue or idea, search existing entries and let user know e.g. "These previously submitted issues may be related to your issue." (2) 'Save as draft' for all website items that can be submitted || -
9 Feb 13, 2022

Mark [PD]: (1) Data Analytics: Page showing analysis of data in the Unit (tasks completed, in progress, analysis of funds etc), and (later feature) allow customization for what to show on home page [4] (2) Add option for Tabbed view of items on home page [3] (3) Add Item number somewhere for easy reference [2] (4) Add total number of items in the table next to Headings eg. Issue (54) [2] (5) Filter and Search bars [2]

Joy: (1) Add scrolling for items in the tables [2] (2) show Idea/activity points near User profile icon [2] (3) Search bar [2] (4) Link to Reward System, 'How it Works' kind of link [2]

Dev (1) Move out 'completed' task numbers from Analytics [2] (2) show Total tasks completed as separate number [2] (3) Display live view of data (real time updates) [1] (4) Add upvote/downvote for user who upvoted or downvoted a specific issue (? unsure if we should add this)

Directly edit Issues detail

10 Feb 20, 2022

Analysis For review: Mark: Issue Page View (updated), Home Page View (updated) - Joy's work (see Analysis and Process at end) - Dev's work

Dev: Add Upvote/Downvote counter next to the issue (this exists in our Ranking system) [2]. Tags in Issues for skill-matching [2] For the next few weeks, we will research problem-solving software and tools, any methods they use and see how any of that can be used for our Taxi app business. (some problem-solving theory is ok)
11 Feb 27, 2022 Analysis For review: Problem Solving-- Joy - Dev - Mark (stackexchange)

Selected Ideas : Joy: 'Resolution wiki' (or issue wiki) could have guided sections for Root Causes. Possibly needs more study [2] -- Mark: (1) Quality control/guided process to help users create higher quality data entries [2]. (2) General process of submitting something and guided through it [1]

Using Google find as many "problem-solving" software and tools as you can and then if you have time and if that information is available, make a summarized list of their key features and think about how we can use it for our project. Search terms can include alternative words for example problem solving software/tool, solution finding software, problem management software, etc. A small amount of problem-solving theory is ok.
12 Mar 6, 2022

Analysis For review: Mark | Joy | Dev

Mark: Service Now, Root cause analysis
Joy: SysAid Problem Management, HaloITSM Problem Management, Freshservice (see root cause analysis feature)
Dev: Engineroom (discover solutions), SoftExpert Problem Management, ServiceNow (Problem Management)

Others: CauseLink, RC Pro Root Cause Analysis Software (found via search term: 'root cause analysis problem solving software')

(1) Understand what task management is (see Prototype website description). We are focusing on how tasks are created, assigned, completed and evaluated). A special focus on Task Bidding (when multiple people are involved).

(2) Do an initial search to find tools and websites that focus on Task management. Make a list of those tools, no analysis needed. Include this list of your initial research in the first section of your analysis. (3) Revisit that list to find the best tools you can which are most related to Task management. No discussion or analysis is needed on other topics or anything which does not give us new information. Focus on finding the Best and Most Relevant tools with unique features. thank you

13 Mar 13, 2022

Analysis For review: Joy | Mark | Dev

Selected Ideas (no plans for next few weeks, taking a break to catch and re-evaluate)

Tentative Plan for Meetings[edit | edit source]

Discuss the following topics, create visual designs and decide on functionality:

  • Taxi App:
    • Home page
    • Issue Detail Page
    • Problem-solving software
    • Task Management (all stages: creation, assignment, completion, evaluation etc) + Flowchart
    • Connecting all these: Skill-matching, task skills for searching, recommendations etc
    • Reward/Motivational Systems
    • Reputation systems (Idea points, Activity points). Also linked to Rewards/Motivational systems
    • Ideas
    • Objectives
    • Misc topics:
      • Solutions database: If a solution has been found, it should be easy to find it for others who want to know (how do we design this). Example: Loud vehicles with illegal exhaust modifications (how to deal with this)
      • Analytics (what kinds to have)
    • Re-assess previous topics and look at the existing system from an over-all view
    • Decision Making module (community owned businesses and others need this module)
  • Interface customization
  • Administration (moderation), Interface setup (e.g. Defining types of Issues, tags, categories)
  • Unit Generalization/Creation (for other types of units)
  • ..
Retrieved from "https://javul.org/mw/index.php?title=ThinkTank_Meetings&oldid=1927"