documentation/locale/es/LC_MESSAGES/getting_started.po

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
# 
# Translators:
# Alejandro Kutulas <alk@odoo.com>, 2018
# 
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 12.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-11-07 15:38+0100\n"
"PO-Revision-Date: 2018-10-19 08:15+0000\n"
"Last-Translator: Alejandro Kutulas <alk@odoo.com>, 2018\n"
"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: es\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#: ../../getting_started/documentation.rst:5
msgid "Basics of the QuickStart Methodology"
msgstr ""

#: ../../getting_started/documentation.rst:7
msgid ""
"This document summarizes Odoo Online's services, our Success Pack "
"implementation methodology, and best practices to get started with our "
"product."
msgstr ""

#: ../../getting_started/documentation.rst:12
msgid "1. The SPoC (*Single Point of Contact*) and the Consultant"
msgstr ""

#: ../../getting_started/documentation.rst:14
msgid ""
"Within the context of your project, it is highly recommended to designate "
"and maintain on both sides (your side and ours) **one and only single person"
" of contact** who will take charge and assume responsibilities regarding the"
" project. He also has to have **the authority** in terms of decision making."
msgstr ""

#: ../../getting_started/documentation.rst:20
msgid ""
"**The Odoo Consultant ensures the project implementation from A to Z**: From"
" the beginning to the end of the project, he ensures the overall consistency"
" of the implementation in Odoo and shares his expertise in terms of good "
"practices."
msgstr ""

#: ../../getting_started/documentation.rst:25
msgid ""
"**One and only decision maker on the client side (SPoC)**: He is responsible"
" for the business knowledge transmission (coordinate key users intervention "
"if necessary) and the consistency of the implementation from a business "
"point of view (decision making, change management, etc.)"
msgstr ""

#: ../../getting_started/documentation.rst:31
msgid ""
"**Meetings optimization**: The Odoo consultant is not involved in the "
"process of decision making from a business point of view nor to precise "
"processes and company's internal procedures (unless a specific request or an"
" exception). Project meetings, who will take place once or twice a week, are"
" meant to align on the business needs (SPoC) and to define the way those "
"needs will be implemented in Odoo (Consultant)."
msgstr ""

#: ../../getting_started/documentation.rst:39
msgid ""
"**Train the Trainer approach**: The Odoo consultant provides functional "
"training to the SPoC so that he can pass on this knowledge to his "
"collaborators. In order for this approach to be successful, it is necessary "
"that the SPoC is also involved in its own rise in skills through self-"
"learning via the `Odoo documentation "
"<http://www.odoo.com/documentation/user/10.0/index.html>`__, `The elearning "
"platform <https://odoo.thinkific.com/courses/odoo-functional>`__ and the "
"testing of functionalities."
msgstr ""

#: ../../getting_started/documentation.rst:47
msgid "2. Project Scope"
msgstr ""

#: ../../getting_started/documentation.rst:49
msgid ""
"To make sure all the stakeholders involved are always aligned, it is "
"necessary to define and to make the project scope evolve as long as the "
"project implementation is pursuing."
msgstr ""

#: ../../getting_started/documentation.rst:53
msgid ""
"**A clear definition of the initial project scope**: A clear definition of "
"the initial needs is crucial to ensure the project is running smoothly. "
"Indeed, when all the stakeholders share the same vision, the evolution of "
"the needs and the resulting decision-making process are more simple and more"
" clear."
msgstr ""

#: ../../getting_started/documentation.rst:59
msgid ""
"**Phasing the project**: Favoring an implementation in several coherent "
"phases allowing regular production releases and an evolving takeover of Odoo"
" by the end users have demonstrated its effectiveness over time. This "
"approach also helps to identify gaps and apply corrective actions early in "
"the implementation."
msgstr ""

#: ../../getting_started/documentation.rst:66
msgid ""
"**Adopting standard features as a priority**: Odoo offers a great "
"environment to implement slight improvements (customizations) or more "
"important ones (developments). Nevertheless, adoption of the standard "
"solution will be preferred as often as possible in order to optimize project"
" delivery times and provide the user with a long-term stability and fluid "
"scalability of his new tool. Ideally, if an improvement of the software "
"should still be realized, its implementation will be carried out after an "
"experiment of the standard in production."
msgstr ""

#: ../../getting_started/documentation.rst:80
msgid "3. Managing expectations"
msgstr ""

#: ../../getting_started/documentation.rst:82
msgid ""
"The gap between the reality of an implementation and the expectations of "
"future users is a crucial factor. Three important aspects must be taken into"
" account from the beginning of the project:"
msgstr ""

#: ../../getting_started/documentation.rst:86
msgid ""
"**Align with the project approach**: Both a clear division of roles and "
"responsibilities and a clear description of the operating modes (validation,"
" problem-solving, etc.) are crucial to the success of an Odoo "
"implementation. It is therefore strongly advised to take the necessary time "
"at the beginning of the project to align with these topics and regularly "
"check that this is still the case."
msgstr ""

#: ../../getting_started/documentation.rst:94
msgid ""
"**Focus on the project success, not on the ideal solution**: The main goal "
"of the SPoC and the Consultant is to carry out the project entrusted to them"
" in order to provide the most effective solution to meet the needs "
"expressed. This goal can sometimes conflict with the end user's vision of an"
" ideal solution. In that case, the SPoC and the consultant will apply the "
"80-20 rule: focus on 80% of the expressed needs and take out the remaining "
"20% of the most disadvantageous objectives in terms of cost/benefit ratio "
"(those proportions can of course change over time). Therefore, it will be "
"considered acceptable to integrate a more time-consuming manipulation if a "
"global relief is noted. Changes in business processes may also be proposed "
"to pursue this same objective."
msgstr ""

#: ../../getting_started/documentation.rst:108
msgid ""
"**Specifications are always EXPLICIT**: Gaps between what is expected and "
"what is delivered are often a source of conflict in a project. In order to "
"avoid being in this delicate situation, we recommend using several types of "
"tools\\* :"
msgstr ""

#: ../../getting_started/documentation.rst:113
msgid ""
"**The GAP Analysis**: The comparison of the request with the standard "
"features proposed by Odoo will make it possible to identify the gap to be "
"filled by developments/customizations or changes in business processes."
msgstr ""

#: ../../getting_started/documentation.rst:118
msgid ""
"`The User Story <https://help.rallydev.com/writing-great-user-story>`__: "
"This technique clearly separates the responsibilities between the SPoC, "
"responsible for explaining the WHAT, the WHY and the WHO, and the Consultant"
" who will provide a response to the HOW."
msgstr ""

#: ../../getting_started/documentation.rst:126
msgid ""
"`The Proof of Concept <https://en.wikipedia.org/wiki/Proof_of_concept>`__ A "
"simplified version, a prototype of what is expected to agree on the main "
"lines of expected changes."
msgstr ""

#: ../../getting_started/documentation.rst:130
msgid ""
"**The Mockup**: In the same idea as the Proof of Concept, it will align with"
" the changes related to the interface."
msgstr ""

#: ../../getting_started/documentation.rst:133
msgid ""
"To these tools will be added complete transparency on the possibilities and "
"limitations of the software and/or its environment so that all project "
"stakeholders have a clear idea of what can be expected/achieved in the "
"project. We will, therefore, avoid basing our work on hypotheses without "
"verifying its veracity beforehand."
msgstr ""

#: ../../getting_started/documentation.rst:139
msgid ""
"*This list can, of course, be completed by other tools that would more "
"adequately meet the realities and needs of your project*"
msgstr ""

#: ../../getting_started/documentation.rst:143
msgid "4. Communication Strategy"
msgstr ""

#: ../../getting_started/documentation.rst:145
msgid ""
"The purpose of the QuickStart methodology is to ensure quick ownership of "
"the tool for end users. Effective communication is therefore crucial to the "
"success of this approach. Its optimization will, therefore, lead us to "
"follow those principles:"
msgstr ""

#: ../../getting_started/documentation.rst:150
msgid ""
"**Sharing the project management documentation**: The best way to ensure "
"that all stakeholders in a project have the same level of knowledge is to "
"provide direct access to the project's tracking document (Project "
"Organizer). This document will contain at least a list of tasks to be "
"performed as part of the implementation for which the priority level and the"
" manager are clearly defined."
msgstr ""

#: ../../getting_started/documentation.rst:158
msgid ""
"The Project Organizer is a shared project tracking tool that allows both "
"detailed tracking of ongoing tasks and the overall progress of the project."
msgstr ""

#: ../../getting_started/documentation.rst:162
msgid ""
"**Report essential information**: In order to minimize the documentation "
"time to the essentials, we will follow the following good practices:"
msgstr ""

#: ../../getting_started/documentation.rst:166
msgid "Meeting minutes will be limited to decisions and validations;"
msgstr ""

#: ../../getting_started/documentation.rst:168
msgid ""
"Project statuses will only be established when an important milestone is "
"reached;"
msgstr ""

#: ../../getting_started/documentation.rst:171
msgid ""
"Training sessions on the standard or customized solution will be organized."
msgstr ""

#: ../../getting_started/documentation.rst:175
msgid "5. Customizations and Development"
msgstr ""

#: ../../getting_started/documentation.rst:177
msgid ""
"Odoo is a software known for its flexibility and its important evolution "
"capacity. However, a significant amount of development contradicts a fast "
"and sustainable implementation. This is the reason why it is recommended to:"
msgstr ""

#: ../../getting_started/documentation.rst:182
msgid ""
"**Develop only for a good reason**: The decision to develop must always be "
"taken when the cost-benefit ratio is positive (saving time on a daily basis,"
" etc.). For example, it will be preferable to realize a significant "
"development in order to reduce the time of a daily operation, rather than an"
" operation to be performed only once a quarter. It is generally accepted "
"that the closer the solution is to the standard, the lighter and more fluid "
"the migration process, and the lower the maintenance costs for both parties."
" In addition, experience has shown us that 60% of initial development "
"requests are dropped after a few weeks of using standard Odoo (see "
"\"Adopting the standard as a priority\")."
msgstr ""

#: ../../getting_started/documentation.rst:194
msgid ""
"**Replace, without replicate**: There is a good reason for the decision to "
"change the management software has been made. In this context, the moment of"
" implementation is THE right moment to accept and even be a change initiator"
" both in terms of how the software will be used and at the level of the "
"business processes of the company."
msgstr ""

#: ../../getting_started/documentation.rst:202
msgid "6. Testing and Validation principles"
msgstr ""

#: ../../getting_started/documentation.rst:204
msgid ""
"Whether developments are made or not in the implementation, it is crucial to"
" test and validate the correspondence of the solution with the operational "
"needs of the company."
msgstr ""

#: ../../getting_started/documentation.rst:208
msgid ""
"**Role distribution**: In this context, the Consultant will be responsible "
"for delivering a solution corresponding to the defined specifications; the "
"SPoC will have to test and validate that the solution delivered meets the "
"requirements of the operational reality."
msgstr ""

#: ../../getting_started/documentation.rst:214
msgid ""
"**Change management**: When a change needs to be made to the solution, the "
"noted gap is caused by:"
msgstr ""

#: ../../getting_started/documentation.rst:218
msgid ""
"A difference between the specification and the delivered solution - This is "
"a correction for which the Consultant is responsible"
msgstr ""

#: ../../getting_started/documentation.rst:220
msgid "**or**"
msgstr ""

#: ../../getting_started/documentation.rst:222
msgid ""
"A difference between the specification and the imperatives of operational "
"reality - This is a change that is the responsibility of SPoC."
msgstr ""

#: ../../getting_started/documentation.rst:226
msgid "7. Data Imports"
msgstr ""

#: ../../getting_started/documentation.rst:228
msgid ""
"Importing the history of transactional data is an important issue and must "
"be answered appropriately to allow the project running smoothly. Indeed, "
"this task can be time-consuming and, if its priority is not well defined, "
"prevent production from happening in time. To do this as soon as possible, "
"it will be decided :"
msgstr ""

#: ../../getting_started/documentation.rst:234
msgid ""
"**Not to import anything**: It often happens that after reflection, "
"importing data history is not considered necessary, these data being, "
"moreover, kept outside Odoo and consolidated for later reporting."
msgstr ""

#: ../../getting_started/documentation.rst:239
msgid ""
"**To import a limited amount of data before going into production**: When "
"the data history relates to information being processed (purchase orders, "
"invoices, open projects, for example), the need to have this information "
"available from the first day of use in production is real. In this case, the"
" import will be made before the production launch."
msgstr ""

#: ../../getting_started/documentation.rst:246
msgid ""
"**To import after production launch**: When the data history needs to be "
"integrated with Odoo mainly for reporting purposes, it is clear that these "
"can be integrated into the software retrospectively. In this case, the "
"production launch of the solution will precede the required imports."
msgstr ""

#: ../../getting_started/documentation.rst:253
msgid "8. Support"
msgstr ""

#: ../../getting_started/documentation.rst:255
msgid ""
"Your Odoo Online subscription includes **unlimited 24hr support at no extra "
"cost, Monday to Friday**. Our teams are located around the world to ensure "
"you have support, no matter your location. Your support representative could"
" be communicating to you from San Francisco, Belgium, or India!"
msgstr ""
"Tu subscripción online incluye **soporte ilimitado 24 horas sin costo extra,"
" Lunes a Viernes**. Nuestros equipos estan localizados alrededor del mundo "
"para asegurar que tengas soporte, sin importar tu localización. Tu "
"representativo de soporte puede comunicarse contigo desde San Francisco, "
"Bélgica, o India!"

#: ../../getting_started/documentation.rst:260
msgid "What kind of support is included?"
msgstr "¿Qué tipo de soporte está incluido?"

#: ../../getting_started/documentation.rst:262
msgid ""
"Providing you with relevant material (guidelines, product documentation, "
"etc...)"
msgstr ""
"Proveerte con material relevante (guías, documentación de producto, etc...)"

#: ../../getting_started/documentation.rst:264
msgid ""
"Answers to issues that you may encounter in your standard Odoo database (eg."
" “I cannot close my Point of Sale” or “I cannot find my sales KPIs?”)"
msgstr ""
"Respuestas para asegurar que puedes encontrarte en tu database de Odoo "
"stándar (ej. \"No puedo cerrar my Punto de Venta\" o \"¿No puedo encontrar "
"los KPI's de ventas?)"

#: ../../getting_started/documentation.rst:266
msgid "Questions related to your account, subscription, or billing"
msgstr "Preguntas relacionadas con tu cuenta, subscripción, o facturación."

#: ../../getting_started/documentation.rst:267
msgid ""
"Bug resolution (blocking issues or unexpected behaviour not due to "
"misconfiguration or customization)"
msgstr ""
"Resolución de problemas (bloquear problemas o comportamientos inesperados no"
" por desconfiguración o customización)"

#: ../../getting_started/documentation.rst:269
msgid ""
"Issues that might occur in a test database after upgrading to a newer "
"version"
msgstr ""
"Situaciones que pueden ocurrir en una base de datos de prueba despues de "
"actualizar a la nueva versión "

#: ../../getting_started/documentation.rst:271
msgid ""
"*Odoo Support does not make changes to your production database, but gives "
"you the material and knowledge to do it yourself!*"
msgstr ""
"*Soporte de Odoo no hace cambios a tu base de datos de producción, pero te "
"entrega material y conocimiento para que lo hagas tu mismo!*"

#: ../../getting_started/documentation.rst:274
msgid "What kind of support is not included?"
msgstr "¿Qué tipo de soporte no está incluido?"

#: ../../getting_started/documentation.rst:276
msgid ""
"Questions that require us to understand your business processes in order to "
"help you implement your database"
msgstr ""
"Preguntas que requieren que entendamos tu proceso de negocio para así "
"ayudarte a implementar tu base de datos"

#: ../../getting_started/documentation.rst:278
msgid ""
"Training on how to use our software (we will direct you to our many "
"resources)"
msgstr ""
"Entrenamiento en cómo usar tu Software (te direccionaremos a nuestros "
"variados recursos)"

#: ../../getting_started/documentation.rst:279
msgid "Importation of documents into your database"
msgstr "Importación de documentos en tu base de datos"

#: ../../getting_started/documentation.rst:280
msgid ""
"Guidance on which configurations to apply inside of an application or the "
"database"
msgstr ""
"Guía en qué configuraciones aplicar dentro de una aplicación o la base de "
"datos"

#: ../../getting_started/documentation.rst:281
msgid ""
"How to set up configuration models (Examples include: Inventory Routes, "
"Payment Terms, Warehouses, etc)"
msgstr ""
"Como fijar modelos de configuración (Ejemplos incluyen: Rutas de Inventario,"
" Términos de Pagos, Bodegas, etc)"

#: ../../getting_started/documentation.rst:283
msgid ""
"Questions or issues related to specific developments or customizations done "
"either by Odoo or a third party (this is specific only to your database or "
"involving code)"
msgstr ""
"Preguntas o situaciones relacionadas a desarrollos específicos o "
"customizaciones hechas por Odoo o un tercero (esto es específico sólo para "
"tu base de datos o código involvente)"

#: ../../getting_started/documentation.rst:287
msgid ""
"You can get this type of support with a `Success Pack <https://www.odoo.com"
"/pricing-packs>`__. With a pack, one of our consultants will analyze the way"
" your business runs and tell you how you can get the most out of your Odoo "
"Database. We will handle all configurations and coach you on how to use "
"Odoo."
msgstr ""
"Puedes tener este tipo de soporte con un `Success Pack <https://www.odoo.com"
"/pricing-packs>`__. Con un pack, uno de nuestros consultantes analizará la "
"manera que manejas tu negocio y decirte cómo puedes obtener lo mejor de tu "
"base de datos de Odoo. Manejaremos todas las configuraciones y te "
"entrenaremos en cómo usar Odoo."

#: ../../getting_started/documentation.rst:292
msgid ""
"Our support team can be contacted through our `online support form "
"<https://www.odoo.com/help>`__."
msgstr ""
"Nuestro equipo de soporte puede ser contactado a través de nuestra `forma de"
" soporte online <https://www.odoo.com/help>`__."