At its core, Salesforce is a highly flexible, scalable, and customizable platform that can enable pretty much any technical capability you can consider in running your business.

But, where do you start? Luckily you’ve found us here at theCodery, and we’re here to help.

Working with theCodery is as easy as 1-2-3: planning, analysis, and then build-measure-learn. Here’s where our minds are typically when we work with you through these cycles.

PLANNING

“If you fail to plan, you plan to fail.” – Benjamin Franklin

Business Team Planning with Post ItsYou would never build your home or an office without a plan. Technology solutions function in a very similar manner – a solid foundation on planning is the key to ensuring you deliver solid capabilities to your company within the constraints of cost, quality, and speed.

More importantly, managing to that plan, particularly when you hit the fun unknowns, and adapting is the key to project success. Sometimes good plans go awry – what do you do next? How do you pivot?

Working with theCodery means you’ll always have a solid path from beginning to end to get the work done. As much as we like straight lines, we find our paths can be jagged at times as we come across obstacles in the way. To us, the obstacle is the way – we accept this, we embrace this, and we work with you on how to move forward best.

What do your plans look like? They can take on any or all of these flavors – all areas where we specialize at theCodery to ensure a solid solution gets built fast and well:

    • DevOps: Environments, Source Code Management, and Continuous Integration Setup, Improvement, and Maintenance (for SFDX, Sandboxes for Single Orgs, and Developer Orgs for Package Development)
      • Github, Bitbucket, CircleCi, and Related Tooling Setups
      • Coding standards and design pattern implementation, with code reviews
    • Agile project management: Product Backlogs, Wiki and Document libraries, Definition of Ready (DoR), Definition of Done (DoD), and full scale tracker setups
      • Jira (issues, workflow, screens, permissions, custom fields, scrum & agile boards), Confluence (blueprints and wiki setups), Trello, Google Drive & Dropbox (documents and templates, and other agile tool setups
    • Organizational (structural) development, alignment, and enablement:
      • Quality Assurance (QA) strategy, test planning, test case, and test execution management (via Zephyr, ProVar, Selenium, and many other related tools)
      • Risk Management: risk tracker / risk log, risk management & escalation process design & implementation
      • Change management: change communications, power user and support communities (with change leads embedded in business), user acceptance testing (UAT), product ownership enablement, training, and supporting documentation (admin guides, user guides, quick reference guides, data dictionaries, solution design documentation for maintenance)
    • Governance and tracking: project reporting (velocity, burn downs & burn ups, release / sprint tracking, release plans, and roadmaps), steering committee and Governance structures
    • Incident management, support: process design, ticketing setup (Salesforce Cases, Jira, Zendesk), SLA management, ticket & cycle time tracking

ANALYSIS

“To understand is to perceive patterns.” – Sir Isaiah Berlin

business-analysis-strategy-planning-successAs we plan and tailor plans to your needs, we also aim to understand the context of your business specific to what we’re building in Salesforce. Hyper focus on the problem at hand we’re aiming to solve is critical to avoid wasting time on boiling the ocean – what headache needs to be cured? What opportunity are we opening up for you today?

While we can go deep into your pipeline and plan those things out, we typically aim to get right to that very specific thing you called us to solve today. The focus of our business analysis work is threefold:

  1. The better we nail down the problem clearly, the better we can identify the correct solution alternatives for you to consider
  2. The better the design up front, the lower the maintenance cost and higher performance to sustain your solution as you scale, grow, and adapt to an ever changing business climate
  3. The better we understand your business, the better we can hand you something you can build upon, extend, and customize long after we’re gone

As much as we love you, we know you want us in and out quickly, and that’s why this step is so crucial – let’s solve the right problems, correctly, up front and for all.

As we peel apart what needs to be done for analysis, we’re typically taking on these kinds of tasks:

  • Business analysis –
    • what specifically are you aiming to do with Salesforce? Who’s going to be using the application? What are they doing? What’s working well and not?
    • where does Salesforce fit in currently or will as part of your overall systems integration architecture? How are you looking to support Salesforce long after we’re gone?
    • What is the real business value of what you’re asking for? How can we get you to the highest ROI and quickest payback with your solution?
    • What makes sense to implement now vs later?
    • What do we need to consider on the people side of change?
  • Architecture analysis –
    • What existing metadata do you have in Salesforce? How well (or not) was this designed? Where can theCodery help fix your “sins of the past” and get you humming better?
    • What kind of systems integration architecture needs to be considered for this solution?
    • What kind of User Experience (UX) is required to implement your needs?
    • How can we design your solution to scale?
    • Where can we give you the capability to configure your solution, as much as possible, to minimize the maintenance overhead long after we’re gone
    • What exact tools on the platform make the most sense for your solution?

The list goes far beyond the examples here, but we aim to be as thorough as possible within the constraints of your budget and schedule. Our goal is not to run up the clock – it’s to maximize your ROI and payback ASAP, and minimize the risk of missing the mark (across many dimensions) on building your solutions.

BUILD-MEASURE-LEARN

“Progress in manufacturing is measured by the production of high quality goods. The unit of progress for Lean Startups is validated learning – a rigorous method for demonstrating progress when one is embedded in the soil of extreme uncertainty.” – Eric Reis, the Lean Startup

Build Measure Learn LoopAs much as we’d like to dive into building right away in a project, this step must follows some essential discovery, planning, and analysis) activities, as sprinting immediately without planning and analysis is typically highly problematic.

With the proper agile project management, product backlog, devops, and architecture work in place, and enough runway for a few sprints, we can get started on the build-measure-learn cycles as quickly as within the first week or two weeks of your project.

In many cases, you likely know exactly what you want and have the processes and tools in place to develop. In these scenarios, we play a heavier role as architects and developers, plugging and playing immediately into your setup. If not, we can augment your capabilities with solution architects, scrum masters, business analysts, product owners, quality assurance (QA) specialists, and much more.

This cycle is exactly what it says – we get you a working product increment in every sprint. You have the opportunity to test that increment with real, live customers immediately if you’d like (depending upon how we setup your testing strategy). With our sound source code and CI tools setup to complement this, we can even get you deploying tested components every sprint if you really wanted to, if it makes sense for business.

We’re agile evangelists, and firm believers in getting customer feedback early and often. After all, your users don’t typically know what they want until they get their hands on something. Our goal is to get you there ASAP, so you can have customer and end user validated solutions working as quickly as possible.

The worst thing you can do is build a shiny gold plated product, after investing tons of money and time, for it to be rejected by your users and customers, and you’re back to the drawing board again. This process of validated learning solves for that risk, and it works every time. Call us to talk about how it can work for you.

GETTING READY FOR CHANGE

“If you build it, they will come” is absolutely untrue. In many cases, your customers or users will be very comfortable doing what they’re doing today, even if you know it is exponentially more painful than what you’re about to introduce to simplify their lives.

Why? Because we are all human. Sometimes we’re just comfortable with what we know and don’t want to see that change. Sometimes we don’t want to admit that we’re afraid of taking on something new, especially when our paycheck depends on it. Would this change cause me to lose or diminish my bonus? If so, hell no.

While you could throw change at people quickly, this approach rarely (typically never) works. Change is a process that happens over a long period of time. From the inception of a project, you should have leaders in your business communicating the benefits of change, lending transparency to the development timeline, and giving people plenty of opportunities to test, train, and provide their feedback.

Change works best when we’re all on board, able to be heard and contribute our part. At theCodery, we’re thinking change management from day one.

Want it done right, the first time?

Partner with theCodery to build your product or setup your Salesforce, so it’s working for you, and not the other way around. Contact us today.