14 Best Practices Software Developers Should Never (Ever) Skip
At Revelry, we believe – no matter the project type or development methodology – certain engineering best practices should always be upheld. These fundamental…
Process
Process content on the Revelry Blog: Navigate our lab notes by using the tag system.
Connecting the Dots: Different Project Types, Same Best Practices
Revelry’s product managers and software engineers contribute to various types of development projects, depending on partner needs. To help our latest cohort of apprentices…
The Fractal Nature of the Revelry Software Development Process
“There’s a fractal nature to the Revelry software development process. Whenever I advise someone who is stuck using our process, I see this psychedelic,…
Online Planning Poker for Accelerated Decision Making
Planning poker is an important part of estimating time spent on a project. But how do companies that recently went remote do planning poker? Here’s how we do planning poker for remote teams.
Slack Communication With Clients and Partners — Our How and Why
At Revelry, we have a pretty solid internal Slack communication structure. Here’s how we collaborate with multiple innovation partners on Slack.
How Our One Week Sprints Are Like Blazing a Trail
This is how we keep track of the landmarks that tell us we’re still on the right trail. It’s not always a straight line, but the journey is beautiful.
7 Tips for Context Switching Without Losing Momentum
Our process requires trust and skill at context switching. Here are the best ways to make it easy for yourself and others to switch tasks and cope with juggling project work.
Why We Care So Much About Sprint Commitments (and we hope you will too)
Sometimes, clients even say “but I don’t care about the commitment.” Firstly, I question whether that is true deep down. It’s hard for me to imagine someone paying a significant amount of money to have a problem solved,and then not caring when that solution ships, or even which parts of the solution ship in which order.
“Call Your Shots” and Other SEAL Team Leadership Skills We Love
Everyone is a leader at Revelry, and it’s because we let the process take the lead. Hang on though – we’re not cultists. When the process doesn’t fit, we allow ourselves and our team to change it up. We make the process work for us when necessary, not the other way around.
Project Terminology: The 15 Most Common Revelry Terms
If you’ve ever wondered the difference between staging and production, or styles and UX, then this is for you!
Getting Things Done (GTD) with the Multi-Inbox Powerful Sweep
My History with Getting Things Done I’d like to share a technique I use to keep organized and reduce my anxiety about my todo…
Revelry Process : Design and Development for Growth
We work with our customers and partners to define project goals and objectives from a high level. Then we design and build. Then we release a thing and we start over. There is no point in detailing specifics on how we achieve our collective goals and objectives at the beginning of a project.
Faster Software Development with (Smart) Technical Debt
“technical debt” noun. the sum of costs owed to one’s computational progeny for past transgressions against their design and future well-being If you’re like…