Salesforce Change Management - Part 1 of 4 : An Overview | Archana Rajendran | Skillshare

Playback Speed

  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x

Salesforce Change Management - Part 1 of 4 : An Overview

teacher avatar Archana Rajendran, Salesforce Consultant

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Lessons in This Class

6 Lessons (19m)
    • 1. Course Introduction

    • 2. Change Management An overview

    • 3. Benefits of Change management

    • 4. Key Stages of Change Management

    • 5. Development Methodology Options

    • 6. Develop a Change Management Strategy

  • --
  • Beginner level
  • Intermediate level
  • Advanced level
  • All levels
  • Beg/Int level
  • Int/Adv level

Community Generated

The level is determined by a majority opinion of students who have reviewed this class. The teacher's recommendation is shown until at least 5 student responses are collected.





About This Class

Welcome to the course series on "Salesforce Change Management" from Archana Rajendran. This course is probably one of the most complete and comprehensive online courses you will ever get to see covering Salesforce Change and Release management concepts from end to end. And no doubts,at the end of course you will become an expert in handling change and release management activities in Salesforce.

The course series covers all the following topics necessary to become a successful Release Manager -

> Explain the benefits of change management
> Discuss the key processes of change management
> Understand the tools/processes to be successful
> Develop a change management strategy
> Handle metadata effectively
> Change sets
> Snapshot

The course series is divided into four smaller parts to help you understand the concepts better.

Part 1 - Salesforce Change Management : An overview ( this course )

Part 2 - Salesforce Change Management : Managing Sandboxes

Part 3 - Salesforce Change Management : Manual and Automated Metadata Export 

Part 4 - Salesforce Change Management : Metadata Deployment

Happy Learning!!

Meet Your Teacher

Teacher Profile Image

Archana Rajendran

Salesforce Consultant


Hi Achievers!

Welcome to the World of Salesforce - World's #1 On-Demand CRM!!!

My name is Archana Rajendran and I am a Salesforce Certified Professional with over 15 years of IT experience exclusively in the field of CRM. I started my career working in Siebel CRM and then in Salesforce CRM. I am Salesforce certified and I hold the following certifications in Salesforce - 

- Salesforce Certified Administrator

- Salesforce Certified Advanced Administrator

- Salesforce Certified Platform App Builder

- Salesforce Certified Sales Cloud Consultant

- Salesforce Certified Developer

There are two main reasons that drives me to do these trainings - one, my passion towards teaching and two, undoubtedly salesforce. My in... See full profile

Class Ratings

Expectations Met?
  • Exceeded!
  • Yes
  • Somewhat
  • Not really
Reviews Archive

In October 2018, we updated our review system to improve the way we collect feedback. Below are the reviews written before that update.

Why Join Skillshare?

Take award-winning Skillshare Original Classes

Each class has short lessons, hands-on projects

Your membership supports Skillshare teachers

Learn From Anywhere

Take classes on the go with the Skillshare app. Stream or download to watch on the plane, the subway, or wherever you learn best.


1. Course Introduction: Hello. Welcome to skill share. Do you ask? Were to become a salesforce release manager or you're someone who would want to stay as an admin or developer. But with more knowledge on Salesforce releases. Then you are the right place. Welcome to my course on Salesforce Change Management. Ah, complete and comprehensive online course you will never get to see covering the interim concepts off Salesforce change and release management. First of all, let me introduce myself. My name is Martina Rajendran. I'm a salesforce dot com certified professional with over 15 years off experience in the field, off AARP and CRM. Apart from my role as a sales force consultant, I do a lot of corporate trainings in house trainings and also worked as an external faculty . And as you see, I hold several certifications and salesforce on in the schools on Salesforce Change Management. We are going to learn about the benefits off change management, the various key stages off change management, the development methodology options, the change management strategy sandbox and the various sandbox types that we have in salesforce. How to create a sandbox on Woodrow. How will establish a deployment connection, how to delete the sandbox. How to do a sandbox? A refresh? And what does Meta data? How do we do? Meta data export? How do we use a full store? Come, I d on. How do we use force dot com? See Ally to perform automated meditator Export. What does metadata deployment and water all the radius tools using which we do better Later deployment starting from chain sets forth dot com i d snapshots packages releases What not the whole objective Off the schools is simple, Straight, clear To make you a successful release manager capable of handling Salesforce releases although yourself for your convenience and ease off learning, I have split the entire coast into four parts. The first part gives an overview about salesforce change management. Part two will be about managing sandboxes In Part three. We'll discuss about metadata on how to perform agitator export Andan Part four will talk about meditator deployment on the various tools we have for doing matter, data deployment and salesforce. The one that you're currently watching is Part one, which basically gives you an overview about salesforce. Change and release management. Once you're done with this, please do check out the other parts as well. Happy learning 2. Change Management An overview: First of all, let's understand what has changed management. So what do you think has changed management? He's just about the court. Change that riddle? No, definitely not. Change Management is a practice off providing a consistent, manageable process for controlling change in your business, and that change can be to your data Modern are epics cold are declaring process, or even the man with procedures that we do, and all the techniques on the process that we discussed that we learn to love the course very much applies to sales, close service clothes or even any of the custom applications on implementing change. Management is definitely very essential for any business. Initially, when we started our business with cells hosts, it was pretty simple. Just one project, one face andan like product. One face toe Project one face three than project to project to be with multiple projects, right with multiple changes on Salesforce in itself goes for three releases in the year spring released summer release Winter released. So how do we manage all these? How do we manage all these changes? So here comes the concept of change management. Having a perfect change management process in place definitely helps us to successfully manage a continually evolving environment 3. Benefits of Change management: No. Let's understand what all the videos benefits off. Change Management on Effective change Management provides numerous benefits benefits to the project's benefits to the users on benefits for the project cost. With respect to the projects on Effective change, management keeps the project aligned with the business goals and strategies, and ensures that the project is delivered in a timely manner on definitely reduces the risk on increasing the quality of the project. I'm with respect to the users. They received timely training if required on effective change. Management also helps in providing an efficient feedback loop for the users. So we understand what they think about the application, how it is productive for them, because users are definitely the endpoint who used the application on benefit, all of the application so ineffective. Change management definitely helped in providing an efficient feedback you on an effective change. Management has also got a positive impact on the project costs because it helps us to keep the project in control to keep the change is in control because we know which all changes were working on which all changes will go live. Those changes are not conflict ing with anyone off the existing functionality, thereby reducing lot of testing affords and Bach fixes, which keeps your project costing control, thereby giving a higher rate of return on investment. 4. Key Stages of Change Management: OK moving on now let's understand what all the key stages off change management the key stages off change management are actually map to two key groups of people the business team on the technology team. And for a successful change management, we should follow the simple four step process Step one, collect ideas and request from users. So when we talk about request, basically can be of any form, it can be major business initiatives can be minor business changes or even system defects or bugs or performance enhancements. Basically off any form, the records can be off any form, so Step one is all about collecting ideas and request from users. Steptoe, Step two is analyzing and prioritizing request. So now that we have collected all the request, we goto prioritize them. We goto analyzed them so that there is a balance in the user option. There is a balance in the innovation. There is a balance in the new functionality. You have to maintain a balance between all these by analyzing and prioritizing the request that he go live as part off that particular release. Step three con figuring and developing enhancements, which is where we actually do the development of the release management on in the forthcoming sessions will be discussing about the various tools that will be using for that on finally step for training and communicating to the users after the release. Be actually do this as a part of the post release activities, we train the users. We communicate all the enhancements that we have made to the application so that they can make the best use offered. So this simple forced a process for sucks the foot change management. Let's understand each of the steps. Indeed, there Step one, collecting ideas and request from users. Actually, every project every business has their own ways, their own methods off collecting the ideas and records from the users. Some projects they user the chatter group. They create a public group. Very users can post ideas, which they use as a means for collecting the request. In some projects, they use salesforce ideas when they can pull the idea and they can hold for the particular idea and depending on old, they pick request on in some products the user. The case object the case object within. You can raise a case on all those cases will be accumulated in the backlog. And then like you work on the backlog, you analyze your priorities. The requested is there in the backlog. And then, like you work on that. So there are different methods, different approach that we use in different business for collecting the records for the users and steptoe. We know analyzing and prioritizing request as we discussed earlier, every project has got their own ways. They don't means off collecting the request. Okay, so now that we have collected all the request to all the requests are there in the back. Look. So how do we analyze them? How we prioritize the request given this is a very, very key process in change management. Because you got to analyze, you go to prioritize a request and see which has to go first, in which you were released, that you're working on or in the forthcoming girlies. So bitch, I'll request has to be put together for a particular release. So this step completely talks about how do we analyze a request that we have on? How do we prioritize them? So we prioritize request based on the overall business goals and strategy and who defines these business schools that doesn't stakeholders. They define the business goals right, so we know what the business goal, and we prioritize the request based on the business goals on. We prioritize the request in such a way that it is high are oi driven means the return on investment is high. So depending on that to be prioritized, that request. But definitely yes. We do need to have a small amount of budget for minor enhancements as well, because in many times were you and these miners changes makes our gives a very big impact today and uses to say, for example, that they want a particular business process have to be changed in a particular way so that it can consume or its can take away most of their manual effort on war forward. Several reasons. So the even these minor changes they makes very good business impact. So as part of this change management, we need to have some space, have some budget for those minor announcement last week, and once we are done with this analyzing and prioritizing the request, then we go to configure and developed enhancements on this is where we actually do the development. Father particles release management. So in real time, then we actually work on these changes. When we actually work on the request, we do either daily releases. We do minor leases on below major releases. So what are these daily releases? As you know, as it say's daily releases. So definitely these are the minor changes that we work on. It might be some back fixes are it might be some minor business conflagration that to like sacred off. One report that you are some dashboard, that you do all these like it falls under the daily leases. Ah, but then, like even if it's a day, literally, they just guard definitely ensure that the end users are communicated about the change. It might be even just a simple mail sufficient. But then we just going to ensure that the induces are communicated on those changes online . It releases these miners. Leases are kind of new business functionality that we implement on the generally the target , these minor leases a monthly onda. We definitely got rules some testing for these minor releases because it is new functionality that is implemented. So we just gotta ensure that it is not conflicting with anyone off the existing functionality. So definitely we gotta concentrate on testing when we don't minus releases on major releases. Major releases are major business initiated that you improvement in sales force on generally these major leases. They have a major impact on the application, so we target them on a quarterly basis, like an off four times in a year. And they're definitely like as it is, major release we got to do. We got to spend significant amount of time in testing on Definitely. Training is very, very essential for major release, generally for major release, it is kind of a classroom training wherein, like you bring in all the end users you bring in, like all the business units which are related to that, and then give a training in the classroom training, letting them know that the minute business initiated that you have taken and how you have implemented that in Salesforce, what will be the releases, the daily release or minor release or major release? The development process remains the same on this development process that, you see is very much aligned over the normal standard software development process that we have via start off with any change in the development environment on then, like we moved to the integration environment, where in, like you check with all the integration points that you have any organization. And then finally the U 80 environment to bed in the induces also do their testing. And finally after it this tested after it works fine, like after a leaders assigned off by all the stakeholders. Then finally move the change to production and all these lower environments that is development, integration and unity. These little sandboxes on finally dismal to production on that these sandboxes, either they can be a full data fan box. Generally the your eighties of food or a sandbox on the development environment on the integration environment, like it can be developer, sandbox or develop a pro sandbox, and it is totally up to the business. It is totally up to the business to design on, like which kind off a sandbox they want for which environment. But in the overall development process, it reminds the same beat. The minor leagues are major release on a daily release. The process remains the same. Any change, say, for example, you create a report. First Luna Development Environment and then, like movinto integration environment movie to you. We didn't move to production finally, but these environments, like it was just kind off the generalized films that I have a problem here that is a development integration, you ready in the force basically from product to product. Some project called the tube 80 some project called the staging. Some project cause it pre prod Eurydice shortly up for the business up for the project on. For this process, off development and deployment will be using various tools on before coming. Factions will discuss about the various tools that will be using for deployment off data from development to integration. Integration to you. Ready You ready to production? Say, for example, like you create a workflow rule in development environment. How would you deploy the metadata from death to integration? How would it deploy the married A. From integration to you? Ready? So there are multiple tools that we can use and salesforce for deployment of meta data on before coming, sections will be discussing in detail about each of the tool and how to be used. Those tools for migrating the meta data and the final step US. Training and communication be the daily rallies beat a minor released beat a major release Communicating to the end users Communicating to the respective business units and the stakeholders is very, very Yasin Shit. Say, for example, today literally ugly is like regardless and in the mail communication as simple as that to let the users know off the change that you have basically made with the May Day literally and for my releases, you definitely got to document the changes you're going to document, which are all the business units between all the stakeholders will be affected by that and for major release, as we discussed earlier. Definitely we have we got have some sort off classroom training. They're in the U in white, all the business units, all the stakeholders, all the end users were related to that and explain them about the major release that you have done explained them about the business, in fact, that you have done using the changes that you have made him salesforce 5. Development Methodology Options: and with respect of the development, there are a different development methodology. Options that we have three options that we have are either Ajai are what a fly it can be a hybrid, basically hybrid off, agile and waterfall. The Ajai methodology is actually the recommended approach for developing sales for solutions. Our platform is designed to optimize the time to value, and there are numerous that want ages by adopting the agile metrology we can very was the risk. Definitely. And there is a high level of disability in a jail metrology because, like we see, like what all the changes that I have got to be impacted are to be implemented in the near future. What was all there in the backlog and how it is impacting the users and all these and the adaptability to the business requirements is very high on we very much focus on the business values. These also must be very advantages off agile methodology. And waterfall is basically a project management approach, and it's being used for a long time. On is very often the method used by many system integrators honey Ajai, water for project radios, its product timeline or rather, than the feature, said Delhi would in the given trees. Onda Linley considerably advantages off for wonderful metrology. It is basically a stage development. So we understand in with stage we arse and we have a good visibility off what we are actually and where we are with respect to the product. And it provides good documentation for each and every stage that we follow. In the waterfall model, we have some specific set of documentations to be Delhi were so documentations and documenting all the business processes waterfall modern that is definitely a big advantage . And third metrology auction that we have is hybrid basically a hybrid off agile and waterfall. So in this hybrid model, we start with the kind of a waterfall model wherein we gather all the requirements on. Then, like we slowly moved to the agile metrology. So here, like we gather all the requirements and then let me go the different faces off a job. So here we have advantages. Definitely yes. And we have some dessert mint ages as well. Sometimes sometimes these requirements phase can take a significant amount of time, and then the scope, like river meets, define it. So there are less chances that we can modify that in the later stage. But definitely yes in a hybrid has got its own advantages. Were in like you have good visibility off the project on again. Better implement a project so that so. These are the three metrology options that you have when you consider development, and it's totally up to the business, totally up with a project with metrology auction that they fall. Onda, like as a person as you start working in a project, are even like when you are in the project. This is definitely important for you to understand with Mitt that all do they work in whether they follow the agile metrology or the world for metrology or the hybrid mythology . 6. Develop a Change Management Strategy: in this lecture. Let's understand the 10 steps to develop a change management strategy. So what? All the 10 steps Step one. Document the Project Goals and Strategies Steptoe Document the Change man. It's been processed on widely communicated to your business team on technology team. Step three. Gather business requirements and ensure that they induce a feedback loop is created Step for on a laser requirements. Step fight. Once the analyzer requirements, you gotta prioritize our requirements on Communicate the roadmap. Say, for example, which all requirements will be part of the minor leagues, which all requirements will be part of the major leagues and all these steps. Six. Design Who is going to do the enhancement either The business analyst. Are the developers going to do the enhancement? So in case of the developer, it can be in house developer or it can be some integration partners who is doing the enhancement? Step seven designed the delivery metrology that suits your business. That's what your project and Step eight is to select the correct tools. So which tool that you're gonna use for deployment. The various tools for deployment will be discussing in the later sections and step nine is straining the end users once they're done with the development. Once you're done with the deployment, one changed her life. The users have to be trained on the changes that you have made us part of the particular release and finally go to deploy the changes. So these are the 10 steps to develop a change management strategy.