Tools and Systems
Source: New Employee Back-Office Orientation (2025-08)
Core Principle
“If it isn’t in Jira, it doesn’t exist.”
All work must be tracked in Jira. This is the primary communication and tracking tool for the development teams.
Collaborative Tools
Preferred: Google Workspace
While Microsoft Office products may be required when interacting with clients and partners, all employees should use Google Suite for internal work.
Why Google Suite?
- Better collaboration features
- Enhanced security
- Real-time co-editing
| Tool | Purpose |
|---|---|
| Docs | Documents, proposals, specifications |
| Sheets | Spreadsheets, data analysis, tracking |
| Slides | Presentations |
| Drive | File storage and sharing |
| GMail | Email communication |
| Meet | Video conferencing |
Communication
| Tool | Purpose |
|---|---|
| Slack | Real-time team communication |
| Confluence | Documentation wiki |
Business Systems
| Tool | Purpose |
|---|---|
| Salesforce | CRM and sales pipeline |
| QuickBooks | Financial management |
| ADP | HR and payroll |
Security Tools
| Tool | Purpose |
|---|---|
| LastPass | Password management |
| JumpCloud | Identity and access management |
| Sophos | Endpoint security |
Development Tools
Project Management
| Tool | Purpose |
|---|---|
| Jira | Issue tracking, sprint management, backlog |
| Confluence | Technical documentation |
Source Control
| Tool | Purpose |
|---|---|
| Git | Version control |
| Bitbucket | Git repository hosting |
Path2Response Internal Systems
BERT (Base Environment for Re-tooled Technology)
BERT is Path2Response’s unified backend application platform, consolidating internal tools into a single application with a common codebase. Named in August 2023 (submitted by Wells) after Albert Einstein’s pursuit of a unified field theory.
Design Goals:
- Common codebase across applications
- Serverless architecture
- Faster development and migration
Modules within BERT:
| Module | Function | Migration Status |
|---|---|---|
| Order App | Order entry and campaign management | ✅ Migrated (Shipment in progress) |
| Data Tools | Data processing utilities | Planned |
| Dashboards | Reporting and analytics | Planned |
| Response Analysis | Campaign response measurement | Planned |
Note: The legacy orders deployment (“Orders Legacy”) remains operational until Shipment functionality is fully ported to BERT.
Naming Convention: Sesame Street theme enables naming related tools (Ernie, Big Bird, Oscar, etc.)
See BERT Overview for complete documentation.
DRAX
DRAX is Path2Response’s reporting system that replaced the legacy Shiny Reports application. Part of the Sesame Street naming convention.
Processing Infrastructure
| Component | Technology |
|---|---|
| Spark Processing | AWS EMR (formerly Databricks) |
| File Storage | AWS S3, EFS |
| Database | MongoDB Atlas |
Data Partners
| Partner | Function |
|---|---|
| BIGDBM | External data enrichment |
| LiveRamp | Digital audience onboarding |
Security & Privacy
Security
- The CTO is Path2Response’s Security Officer
- Strong security across the organization
- Weakest link is you! - Don’t click on suspicious links
Privacy Compliance
| Term | Definition |
|---|---|
| PII | Personally Identifiable Information - limited usage |
| SPII | Sensitive PII (SSN, credit card, passwords) - NOT allowed |
| CCPA | California Consumer Privacy Act |
| CPRA | California Privacy Rights Act - current standard |
Path2Response is CPRA compliant.
Agile/Scrum Process
Sprint Cadence
- Duration: 2 weeks
- Start: Friday ~3:00 PM MT
- End: Friday ~2:00 PM MT (two weeks later)
Sprint Cycle
Product Backlog → Sprint Planning → Sprint Backlog → Daily Scrum (1 day)
↓
Sprint (2 weeks) → Review → Retrospective
↓
Release
Key Ceremonies
| Ceremony | Purpose |
|---|---|
| Sprint Planning | Select work for upcoming sprint |
| Daily Scrum | Daily standup - status and blockers |
| Sprint Review | Demo completed work to stakeholders |
| Retrospective | Reflect and improve process |
Key Concepts
- Backlog management
- Sprint execution
- Automation
- Processes
- Releases
- SCM (Source Code Management)
Related Documentation
- Development Process - Detailed Agile/Scrum process
- Sprint Process Schedule - Meeting schedules
- PROD-PATH Process - PM and Development interaction