Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current Restore this Version View Version History

Version 1 Next »

🌱 Feature specification

Title

Description

Anatomy diagram

Key to anatomy diagram

🧐 Specifications

Usage

Variations

Behavior

Style

📐 Additional guidance

Content

Accessibility

Mobile

Best practices

Related

Process:

  1. Create tickets for a new feature in Jira (

    1. Create an Epic with the feature name

    2. Break down tasks into separate tickets linked to the epic, each ticket should not be longer than 1 week of work, to make sure it can be implemented and tested in a two-week sprint.

    3. Estimate effort, add a description, flow, or any other information that is available.

  2. Tickets are added to the sprint.

  3. A ticket is implemented according to specification and functionality as described in spec. confirmed in QA process.

  4. If a ticket cannot be implemented as described in the specification, this could be due to technical reasons, bandwidth issues, priority changes…

    1. Reasons need to be brought up to the product manager (Nick).

    2. In a discussion a decision will be made to either follow the specification or alter it.

    3. If the specification is altered it needs to be written down and the Jira tickets need to be updated with new information.

    4. This goes back to point 3. ticket to be implemented according to the new specification.