Say Hello to Roundup Roger
At Brewhouse, we spend Fridays doing creative work. During these wonderful days, we focus on interesting hacks and innovative projects. Over the last 10 weeks, I’ve been able to spend my Fridays working on a project with Philippe Creux called Roundup Roger. Roundup Roger is an open source tool to wrap-up a team’s day via email. A wrap-up is quite similar to an agile standup (or scrum), but at the end of the business day.
You’re probably thinking, “How anti-social of you!”. Yes, you’re right, we’re endorsing email correspondence over face-to-face interaction. But we’re talking about wrap-up meetings here, not beer Fridays.
The point of a wrap-up is to educate the team on:
- What you’ve accomplished during the last business day
- What you’ll be working on next
- Whether you’ve hit any blockers that are impeding your progress
Email works well in this situation because it prevents Chatty Carls from commandeering your meeting, and allows concise discourse that can be re-visited later if needed. Also, for those of us who have trouble with context switching, it can be easier to communicate the work you’ve accomplished by writing it out as opposed to communicating verbally.
Another benefit of an email wrap-up is a flexible response time. Some of our team members finish later in the day than others, and often accomplish a lot after the in-person wrap-up happens. With Roundup Roger, team members have the flexibility to respond to the reminder email at any time. As long as they send their email before the roundup is sent in the morning, their contributions will be included.
How Does Roundup Roger Work?
Reminder emails are sent out daily at a scheduled time. Each team member responds to the reminder email:
The following day, a roundup email is sent to the entire team with each member’s contributions from the previous day:
Roundup Roger is a Sinatra app, that capitalizes on Sequel’s ORM layer.
After using Rails over the last couple of years, I had become soft. It’s not the best realization to find you’ve become accustomed to having everything done for you. It took me a few weeks to stop trying to use ActiveRecord when querying the database and in the end, I had a good cry and got over myself. I then became much better at using the Sequel gem’s ORM layer.
I’ve also realized that Sinatra is not really a framework at all, but more of a library. I suppose this is why people call it a ‘micro-framework’.
“Hey Sinatra! Thanks for nothing!”
Jokes aside, Sinatra ended up being a great tool to solve this problem. As it turns out, we didn’t really need much of the ‘good stuff’ that comes along with Rails. The app itself doesn’t have a web UI and is meant to be run solely via scheduled tasks in production.
To build emails, we used Virtus to create a common interface for defining attributes. It allowed us to do things like this:
When a user replies to a reminder email, we retrieve the payload passed from Mandrill, and grab the name, email and body, such that we can later apply these to the roundup email.
When we build the roundup email, we strip each email body to remove signatures. This was somewhat tricky, as different email clients apply signatures differently.
We then separate each person’s contribution with a random ascii separator, because, WHY NOT?
We use Pony to send emails. This is where the magic happens…
Scheduling and Business Time
We use the Business Time gem to prevent reminders and roundups from being sent on weekends. Perhaps this item should be configurable for those of you who like to work on weekends (why??).
The Heroku Scheduler plans our tasks for daily execution.
We’d like to think setup is pretty simple. Just schedule the following two rake tasks based on your team’s needs:
There is also a
send_test_email rake task to test whether SMTP settings are configured correctly.
We Use This
Since we like to eat our own dog food at Brewhouse, we’ve been using Roundup Roger as part of our daily efforts for the last couple of months. Our hope is that others will find the same value that we’ve found. The more teams that try this out, the more we’ll know about how to improve it. As always, feedback and contributions are welcome.