translationStudio Requirements
These are the requirements and specifications for translationStudio. The projects using these requirements are
Format
The requirements are written in Gherkin so that they can be ran through Cucumber. You can also read about Gherkin at Behat. The documentation there is a little cleaner.
Purpose
These requirements provide a unified definition of features to be implimented in tS. This allows for more reliable testing, better collaboration, and helps to maintain focus on the long term goals of tS.
The practical application of these requirements will be in the establishment of acceptance tests. We will potentially use PioneerJs to run these tests.
Process for Adding Features
To better control new features in Translation Studio we use a simple triage system to evaluate features and assign them to the correct work queues. The process will be as shown in the following workflow.
Triage: Determine the correct priority, labels, flesh out details, split to atomic units of work (could be multiple repo backlogs)
Controlled by Product Owner and Lead in each repo (e.g. Jesse, Joel, Vicky)
Lead in each repo creates issue in their queue
Discussed by Team as needed
Weekly meeting unless other urgent need arises