MARCUS & MLLICHAP ARE IN THEIR ELEMENT
Until we had Elements we didn’t have end to end DevOps.
Hear what they say about Elements
Any company in Salesforce or DevOps at all, really look at Elements.
JOHN EICHSTEADT III, SALESFORCE SOLUTION ARCHITECT & PLATFORM OWNER
I currently work for Marcus & Millichap as the Platform Owner and Solution Architect. One of the primary challenges I was looking to find a solution to help me handle was dependency analysis. I’d had a previous tool and it didn’t quite do what I wanted to do. I wanted something more extensible. The thing that makes the Element’s platform stand out the most is the way it was really designed from start to finish: the planning tools, whether it’s the requirements and stories, also being tied into the items in a process map; being able to create your own reference models for external systems, have everything kind of tied together into your user stories and create those additional dependencies. And then use that for planning for risk assessment.
It really was kind of an end-to-end tool for that, which I think the other ones were missing.
There were actually some really surprising ways it was integrated. The first was the requirement stories as we used JIRA. So, I didn’t think we were actually going to use that feature until they integrated it. And now they live in both places. And what that in turn has done is build stories from the process maps, because that is how we like to work. How my mind works. I like to lay something out and see that flow of these are the things that for the user. What needs to happen. These are the steps and the things that need to occur and then from there we can build those stories off that and those flow into JIRA and how we have them there.
And then the other piece on the process maps that really wasn’t expecting is how much our stakeholders love it. We started kind of building out this is sort of the idea of the feature. What does this need to do? And using sticky notes to list out all those little things. And then we turn those sticky notes into pieces of a process and then that eyes into our requirements and stories and it gives our stakeholders in the C-suite something visual to look at.
We’re able to map that out in Elements from on a kind of a story when this person changes teams, this thing happens, this thing happens, this thing happens and we could map all those out from the starting point and this is the triggering action. What are the pieces that it’s going to affect and what else needs to happen and what do we need to be aware of and write the stories from that. And I think that probably saved us a good two weeks on something that probably would’ve taken a month.
Until we had Elements, we really didn’t have an end to end DevOps process. It just helps us work the way each of us want to work and are used to working and what makes sense for us. Being able to use Elements to create the idea of the metadata before it’s actually there. So, you can use it in your stories and then once you actually create that metadata item in your system, it replaces it and you still have those connections in place. Elements is the only thing I’ve seen so far that has a proposed metadata function.
The Elements team has been great with helping me understand how I can get the most out of different features in ways that I hadn’t thought of originally. I would say to any business that is in Salesforce and DevOps at all, really look at Elements.
OTHER CUSTOMERS IN THEIR ELEMENT