App Dev

VIEW PROJECT

bitbucket
Node.js
Slack Bolt
REST API
MongoDB
Typescript
Docker
CI/CD

Basecamp Message Monitoring App for Timely Customer Responses

Developing the Application:

I designed an application to keep an eye on Basecamp messages across multiple projects, ensuring timely customer responses.

Purpose:

TwentyFour introduced this system to transform customer service. By automating the tracking of Basecamp messages, it flags missed interactions. When it spots an unanswered message, it immediately alerts the team via Slack, organizing notifications by project and customer for quick follow-up. This Basecamp-Slack integration helps TwentyFour swiftly meet customer needs, boosting satisfaction and demonstrating our dedication to outstanding service with cutting-edge tech.

Achievements:

I led a project at TwentyFour to create this app, focusing on integration, frontend, and backend development. By adopting an event-driven design, I ensured the app could scale and respond instantly. Using CI/CD practices boosted our efficiency. I chose Node.js and microservices for a robust backend, while the user-friendly frontend enhances interaction. Additionally, my work with secure RESTful APIs, webhooks, token authentication, and two-step verification strengthened our data security, showcasing my ability to oversee comprehensive technical projects.

Token-based two-factor authentication and event-driven microservice architecture

UrgencyBot: Basecamp alerts in Slack, powered by webhooks & REST API.

Technical and Managerial Approach:

I managed this solo project with Scrum principles, focusing on flexibility, step-by-step progress, and regular feedback.

In Sprint 1, I analyzed business needs, designed the app, and began both frontend and backend development. This stage also included setting up webhooks and a Slack app for seamless event-driven communication. Committing to Scrum’s ethos, I ensured the end of each week brought a new, complete increment ready for potential use.

Sprint 2 was all about wrapping up the frontend, integrating all necessary features to tackle our challenges, and finishing the backend for operational support. True to Scrum, I wrapped each week with a portion of the product that could be launched, coupled with comprehensive progress reports to keep the development transparent and focused on customer needs.

Managing the project alone, I stuck to Scrum principles, marking each sprint with significant advancements and ongoing refinement. This structured, iterative approach underpinned the successful delivery of a functional system by January 15, 2024, underscoring the value of disciplined development in achieving project objectives.

Twentyfour
Copenhagen, Denmark
Integration of Twenty-four Slack systems and Basecamp system.
Completion Timeline:
Sprint 1 ran from July 15 to September 15, 2023.
Sprint 2 extended from September 15, 2023, to January 15, 2024.

2023-2024