User stories - Webinative/keyframes GitHub Wiki
This app primarily serves video editors (creators) to help them manage their workflows and client approvals from a single window.
Here are the high-level steps involved in the video creation process.
- The client shares the script for the video in text format.
- The video editor submits an audio recording of the script (the voice overlay).
- The client then reviews the tone, pauses, duration of the audio. They may approve or ask for changes.
- Upon approval, the video editor starts storyboarding the key moments in the video and submits the images with detailed description.
- Then client then reviews the visuals, style, composition, etc. They may approve or ask for changes.
- Upon approval, the video editor starts creating the video (animations, transitions, etc) and submits a full low-resolution version of the video.
- The client then reviews the video and can approve or ask for changes.
- Upon approval, the video editor submits the high-resolution video.
The video editor could be working on multiple videos for one or more clients.
Roles
- Site admin
- Video editor
- Client
1. Video Editor
As a Video Editor, I can
| Story ID | Story |
|---|---|
| 1.1 | create a project/board to manage workflows for that project. |
| 1.2 | invite one or more clients to be part of the project. |
| 1.3 | invite one or more video editors to be part of the project. |
| 1.4 | create a [ticket](/Webinative/keyframes/wiki/Ticket-flow) (to create a new video) by specifying the necessary attributes - title, content (script), preferred duration (in minutes/seconds) and due-date. |
| 1.5 | browse through tickets in my project. |
| 1.6 | assign a ticket to myself or other video editors in the project. |
| 1.7 | progress the ticket through multiple predefined states. |
| 1.8 | add comments/queries in a ticket so that I can communicate with all stakeholders from within the ticket. |
| 1.9 | upload images and videos in tickets. |
| 1.10 | request a review for a comment or an attachment (image, audio, video or pdf) |
| 1.11 | set a time limit (max 30 days) when asking for a review (1.10). If the client fails to respond within the time limit, the content is deemed approved. |
| 1.11 | receive email notifications about review decisions (accepted/changes requested). |
| 1.11 | switch between tickets and projects seamlessly. |
2. Client
As a Client, I can
| Story ID | Story |
|---|---|
| 2.1 | join one or more projects through an invitation link from video editors. |
| 2.2 | create a [ticket](/Webinative/keyframes/wiki/Ticket-flow) (to create a new video) by specifying the necessary attributes - title, content (script), preferred duration (in minutes/seconds) and due-date. |
| 2.3 | browse through tickets in projects. |
| 2.4 | receive email notifications about review requests. |
| 2.5 | act on reviews requested by the video editor (approve or ask for changes). |
| 2.6 | add comments/queries in a ticket so that I can communicate with all stakeholders from within the ticket. |
| 2.7 | upload images in tickets. |
| 2.8 | switch between tickets and projects seamlessly. |