# production.s

## Owner: [Xavier Lefèvre](https://github.com/xavierlefevre)

## Description

* The project needs to be placed in front of its end users as fast as possible, the team needs to do the necessary for this as soon as the second sprint starts.

## Impact

* Showing a MVP as soon as possible to end users is a mean to avoid as much as possible waste and un-necessary developments (hence spendings) for un-wanted features. The risk to waste a lot of money in developments is much higher than the risk to be repelled by your customer base for a small clean feature.

## Checks

* [ ] Every week, take a "Launch in production" ticket.
* [ ] Create a "In production" ticket in your "Done" columns in order to specify which dev has been launched or not, and keep a trace of it for future "LIP".
* [ ] For micro-services, check each and every API when you launch in production.
* [ ] When developing, always think about the retro-compatibility of your changes in the back-end (versioning) to make sure that people who do not have the last version of the app don't get un-wanted bugs.

## Bad Examples

*TBD*

## Good Examples

*TBD*


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://bamtech.gitbook.io/dev-standards/project-standards/project-success/production.s.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.