our process

You're going to like the way we work.


We refer to our implementation approach as Agile Transparency. We work efficiently and collaboratively. Our clients always know exactly what we’re doing, how we’re doing it and when work will be delivered - no surprises. We’re fully committed to the success of every BrainJocks client. And, of course, we’re always looking for new ways to improve.

process flow


Our projects move quickly, with short sprints and frequent deliverables. We collaborate and communicate with our clients daily to track changes and stay on top of requirements. Quality Assurance is involved early and testing is performed daily to ensure our work is the best it can be. We constantly monitor scope and adjust deliverables based on dependencies and the needs of the project.

We are transparent.

We are in constant communication with each other and with our clients. Project teams sit together in an open environment, so collaboration is as easy as turning your monitor toward your neighbor or poking your head over the divider.

If we see a red flag, we assess its impact and notify you immediately so that we can work together toward a solution. We tell our clients and partners everything - what we’re delivering, how much it will cost, how long it will take and how the overall project will be impacted.

We communicate through sprint meetings, reports, statistics, documentation and updates to the project environment. We use the latest technologies -- like Slack and Atlassian -- to make it simple and efficient for the entire team to communicate and collaborate.

“BrainJocks has a very good agile process with front runners holding people accountable. The project management discipline helped me out tremendously. BrainJocks is always transparent, so there are no surprises.”

Deslie Quinby, tripFiles

We implement using a componentized approach.

We break web applications down into simple building blocks, or components, using our BrainJocks SCORE development framework. We find commonalities and patterns in the design and UX that will allow us to share and reuse components across the site or even across multiple tenants in an enterprise. We reuse as much as possible to achieve brand consistency and reduce implementation costs.



Define site architecture (typically needed for multi-brand enterprise and multitenant solutions but may also be recommended to maximize the success of less complex projects).


Gather business requirements and integrate them with technical requirements. Analysis includes defining required customizations, estimation and agreeing on scope. This is captured in documentation used to guide the project.


Develop in sprints, complete all testing, enter site content and launch. Based on project scope, this could include a single site, multiple sites and/or an enterprise layer.


Write reference guides and instructions for both content administrators and developers.


Train the client’s team, any implementation partners and agencies on the solution.


Address any bugs, questions or issues that arise after launch.