Add Blender support

Request

To be filled by the product owner

User story

Following the user story template, describe here your need. There must be at least one user story here.

Detailed problematic

Give some background to your request. Why you need it, what doesn't work with the current situation...

Current workflow

If applicable. If the request covers an already existing process, describe here each steps of it.

Suggested workflow

Optional. Step-by-step describing how the user would behave if the problem was solved.

Needed features

Optional. A list of the features requested. Split between short-term and long-term.

UI Mock-ups

Optional. Add here any draft of how should look the result of your request, if GUI.

Design

To be filled by the developer

This section's structure really depends on the request. But essentially, any developer reading the design should be able to start implementing it without thinking.

Scenario

How will the request be implemented. Which design pattern will be used...

Structure

How will the implementation be organized. Logical diagrams, UML charts, scripts file structure...

Research and development

Optional. If the request necessities exploring new territories (e.g. use of external libs), report here the conclusions of your tests.

Needed modifications

Optional. If existing code must be changed, list those changes here and check the effects of those modifications.

Pseudo-code

Optional. Fake-code can be very useful for finding the best structure, especially if building API features.

UI Mock-ups

Optional. Add here any draft of how should look the result of your request, if GUI.

Material

Sandbox material, used for tests, demos and research. Depending on the domain, it can be a scene, some files, a dataset...

Tasks

Tasks are to be updated at each major step of the sprint. Tasks must be as granular as possible. Tasks must be time-estimated.

• Redact request