Salesforce Solutions
Efficient and user-friendly solutions for your sales-, service- and partner organizations.
Custom Solutions Delivery
Who am I...
How do I work...
What do I offer...
Who am I?
Hi, I’m Azzan. I help organizations enhance their sales and service processes on the Salesforce platform. With over ten years of experience building custom solutions on Salesforce I enjoy working with people by bringing improvements that optimize their day to day workflow on processes which are managed on Salesforce or in connected systems.
What is my background?
I started my experience on Salesforce classic and like many others extended this by adapting to lighting. Having helped several organizations migrate from classic to lightning I currently find myself mainly focussed on building solutions that work optimal in lightning enabled organizations.
So far I have had the opportunity to work in the following locations: Munich (Germany), Beerse (Belgium), Amsterdam (The Netherlands), Envigado (Colombia). I have done so remotely for the last eight years making me most familiar with how to get things done when collaborating with people online who are located in different time zones and locations and come from different cultures.
What am I good at?
Anything related to the sales cloud, service cloud or experience cloud.
Anything apex triggers, apex classes, batch classes, queueable classes, scheduler classes, apex test classes.
Anything related to rest or soap integrations, standard or custom web service endpoints, callouts to other systems.
Anything related to deployments and the metadata api including tools like Copado, Gearset, CircleCI, Flosum, DevOps Center.
Anything governor limits from cpu, heap size, soql, dml, emails, callouts.
Anything security from profiles, permission sets and groups, organization wide default, sharing rules, and session management.
Development Cycle
Communication
When working with remote teams communication is critical to get things done. I normally use Slack messaging to keep lines short using team specific channels through which things can be communicated quickly and efficiently with visibility towards all who are involved in the development cycle. Zoom as the main meeting application for any sprint specific or ad hoc meeting. Google for calendar management to have a clear visibility on any project related meeting and for emails in-case larger teams or external parties need to be involved in certain aspects of the development cycle.
Organization
To organize a development cycle I follow the scrum framework: having grooming sessions to further define requirements that are in the backlog, holding sprint planning sessions to identify the sprint goal and prioritize and allocate which requirements will need to be developed during the upcoming sprint cycle, using daily standups to provide status updates during the sprint cycle, having retrospectives to keep improving the development and delivery process. As a key application to manage the above process I use Jira to capture user stories, do backlog management, run sprints and to capture how things were developed, tested and delivered.
Development
To build solutions I use up-to-date sandboxes for development, partial or full copy environments for formal demos and testing and production only to deploy solutions too that have passed testing and final feedback. To keep track of changes that are being introduced I use github for version control with repository management and visual studio code for handling any apex, visualforce or lighting web component development.
Deployment
To handle deployments I use Gearset as the main application through which environment changes are being selected, compared, and deployed. I am familiar with and have used other applications like Salesforce’s DevOps Center or Copado and could also manage deployments using those or other tools like CircleCI, Flosum or Jenkins with GitHub. However in most cases Gearset is my go-to due to its ease of use and since it does not require a high technical effort to set up and adept to.
