Skip to content

matinayo/voice-based-kanban-board

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

20 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

voice-based kanban board | novel-interaction

Voice-Based Kanban Board | NOVEL INTERACTION

Read report

Kanban board - It helps manage projects by tracking and organizing tasks, moving them between stages to ensure progress, avoid bottlenecks, and evaluate the end-to-end process.
This Kanban board uses spoken instructions to move tasks between stages and manage workflow.

PROTOTYPE
The developed prototype is targeted toward computer science students and assists them in their day-to-day activities.
Some features implemented in the prototype are:

  • Updating the status of a task across the Kanban board using voice commands
  • Updating a title of a task using voice commands
  • Conservations with the application

Features and Command Phrases
Some of the major features and activating commands of the voice-based project management system expected by the system as input are listed below.
  • Updating a Task:
    To start an update operation of a task, the following command phrases act as a trigger:
    • update
    • set
    • change
    • alter
    • modify
    • edit
    • correct
    • make
  • Updating a Status of a Task:
    To update a status of a task, the update operation would have already been triggered, and updating the status would act as a follow-up event, the following phrases act as a trigger for updating a task:
    • inprogress
    • progress
    • pending
    • completed
  • Valid Task ID: In updating a task, a task ID would be used to identify a task, and a valid task ID acts as a trigger to identify a task.
    Examples to be used in this project are:
    • M22
    • M16
    • M19

    The system would be able to engage in dynamic conversations listening for trigger commands in a particular stage of a conversation between a user and the system and the user does not need to restart every conversation with the system. This would be done by using stages for each conversation where a particular stage would be listening for a certain set of commands to activate a function. If in any case, the system encounters an error, the system would be able to resume its initial stage from a previous conversation and carry on with the user creating a more natural conversation between the user and the system.