A full sandbox would be appropriate for diagnosing reports of poor performance when accessing certain Visualforce pages, as it provides a complete copy of the production data and metadata, which allows the developers to replicate and troubleshoot the issue in a realistic environment. A partial copy sandbox would not be appropriate, as it only provides a sample of the production data, which may not reflect the actual volume and complexity of the data that affects the performance. A developer sandbox would not be appropriate, as it only provides a copy of the production metadata, but not the data, which makes it impossible to test the performance of the Visualforce pages with real data. A developer pro sandbox would not be appropriate, as it also only provides a copy of the production metadata, but not the data, which makes it impossible to test the performance of the Visualforce pages with real data.

A source control tool provides the ability for distributed teams to work in isolation, as they can create branches and merge their changes later. It also provides the ability to backup code/configuration changes, as they can be stored in a remote repository and retrieved if needed.

The Tooling API is the best choice for the team that wants to use SOQL queries to retrieve and make changes to smaller pieces of Salesforce metadata through their Java application. The Tooling API provides access to metadata objects such as Apex classes, triggers, workflows, validation rules, custom objects, and fields. It also supports CRUD operations, as well as executing anonymous Apex code. The other APIs are not suitable for this use case, as they either deal with larger metadata components (Metadata API), user interface components (User Interface API), or data records (Any Salesforce API).

A single-org strategy is the best option for UC, as it will enable them to achieve business process standardization among all business units, which is the main goal of the CEO. A multi-org strategy would make it harder to enforce consistent processes and policies across the different business units, and would also increase the costs and complexity of managing multiple orgs. A common managed package could help with some aspects of standardization, but it would not cover all the possible scenarios and customizations that UC might need.

 The two actions that can effectively contribute to the quality and agility of the team are: Define and follow code standards, and use static code analysis tool in the pipeline before manual code review. Code standards can help ensure consistency, readability, and maintainability of the code, as well as reduce errors and bugs. A static code analysis tool can help automate the code review process and identify any issues or violations of the code standards before the manual review. Choosing the most senior developer to help the technical lead or skipping the code review are not effective actions, as they can lead to more errors and delays.

Creating an unmanaged package of the app and deploying it in NTO’s org is the best option for having ETO’s Sales Optimization app in NTO’s Salesforce org in the shortest possible time. An unmanaged package is a collection of components that can be easily installed and customized in another org. Unlike a managed package, an unmanaged package does not have any restrictions or dependencies on the source org, and does not require a security review or approval from Salesforce. Creating a managed package, creating users in ETO’s org, or building the app from scratch in NTO’s org are not as fast or efficient as creating an unmanaged package.

The Scrum value that is compromised by this bad practice is courage, because the teams should be transparent about progress and speak up when they need help. Courage is one of the five core values of Scrum, and it means that the team members have the courage to do the right thing and work on tough problems. By not updating the status of their work in progress, the team is hiding potential issues and risks, and not being honest with themselves and others.