Spec & UAT process

Guilherme Pereira

[Specification] Why we need it?

Customer

Developers

• Includes features to customer requirements
• Describe the scope of work
• Provides a reference to developers

Designers

[Specification] Hubstaff Structure

• Goals
• How others do it*
• How it works*
• Requirements
• Wireframes/Mockups
• Technical implementation

* these are optional

[Specification] Tools

• Hubstaff Tasks*
• Google Docs
• Mockups
• Invision

* these are optional

[UAT] Why we need it?

Developers

Quality Assurance

• designed to cover all the functional scenarios
• the strategy is outlined during the planning step

[UAT] Hubstaff Structure

• Details
  • ​​Specification URL
  • Review App URL
  • PR URL
  • QA Card URL​
• Demo*
• Standard tests
• Edge case tests*

* these are optional

[UAT] Tools

• Hubstaff Tasks (QA Card)
• Google Docs*
• Heroku (Review app)
• Github (Labels)

[UAT] Failing at QA

• Create a checklist of issues/suggestions inside QA Card
• UAT should be reviewed if necessary

[UAT] Passed at QA

• Update github labels
• Move the QA card

Questions ?