



Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
A comprehensive guide to the salesforce development lifecycle, focusing on key concepts such as center of excellence, release management team, governance framework, design standards, change control board, executive sponsor, architecture review board, steering committee, charter, release categories, production development cycle, sandbox development cycle, development cycle for isolated development and testing, development cycle for multiple projects with integration, testing, and staging, developer template, ant migration tool, release train, release manager, sandbox type vs application, when to use change sets, when to use force.com ide, unmanaged packages, managed packages, and 9 steps to effective change management.
Typology: Exams
1 / 6
This page cannot be seen from the preview
Don't miss anything!




Center of Excellence (CoE) - A few stakeholders from different functional groups work together to ensure that changes support business goals and follow IT best practices and processes. Release Management Team - Responsible for planning, scheduling, and controlling the build, in addition to testing and deploying Releases Governance Framework - Improves coordination by ensuring all members of your team are working together to achieve project deadline Design Standards - Follow key standards for coding, testing, integration, large data volumes, and other areas that affect the services you share with other Salesforce customers. Change Control Board - Committee that makes decisions regarding whether or not proposed changes to a software project should be implemented Executive Sponsor - Champions the project by acting as the project's highest level change leader - communicates the importance to stakeholders and senior leadership; obtains go-ahead decision and collaboration; is accountable for success; exercise strategic control to achieve project objectives and business benefits. Architecture Review Board - They will be responsible for defining the overall structure of a program or a system. They will also be overseeing IT assignments that are aimed at improving the business and ensuring that all parts of the project run smoothly.
Steering Committee - Steering committee is a group of high-level advisers who have been asked to govern an organization or organizational segment and provide it with direction. Charter - Goals and the strategies to achieve with Salesforce. A clear charter helps the team to prioritize requirements, to focus on the area that meets their business goals as quickly as possible. Release Categories: Daily - Bug fixes and simple changes that do not require formal release management, including reports, dashboards, list views, email templates, and user administration. Minor - Changes with limited impact, such as a new workflow rule or trigger impacting a single business process. These releases typically require testing, but limited training and change management, and are delivered within a few weeks. Major - Changes with significant impact, including configuration and code changes with one or more dependencies. Because these releases greatly affect the user experience and data quality, they require thorough testing, training, and careful change management. Major releases typically occur once a quarter (or like Salesforce, three times a year). Releasing on the same day of the week for minor and major releases is a best practice. This allows for company-wide planning and sets expectations with your business users. In addition, don't schedule releases near holidays or other major events. Production Development Cycle - 1. Plan functional requirements.
developer user in the sandbox and assign it to the individual who will be developing there. When to use Ant Migration Tool - • Development projects where you need to populate a test environment with large amounts of setup changes - use automated scripts