As O3 World approached the age of 13 and we wrapped up a few long-term projects in the first quarter of 2018, we started to reflect on how much our process has grown. What started out as a few people all sitting together in an office, has turned into a 30+ team that is constantly interconnected using the industry’s best tools and agile methods.
While we’re still continuing to evolve, our weeks have gotten much easier when we have a plan. Hypothetically, here’s how we run the five days of agile for each of our various clients:
Monday – Sprint Planning
Sprint planning at its core function is to talk about upcoming features, assign resources and estimate the work.
At O3 World, we aim to broaden sprint planning to act as the regroup for the entire team.
In addition to estimating and assigning work to developers, we also focus a portion of the hour on a design review and retrospective.
It’s here that we also determine how long our sprint will be (one or two weeks) when we’ll release, what’s included in the release as well as talk through solutions.
Having sprint planning at the beginning of the week allows us to regroup after a long weekend and ensure everyone knows their priorities for the upcoming days.
Tuesday – Stand Up
The key to an efficient stand up is to physically stand up! We’ve found that when we reserve a meeting room and sit, we get too comfortable and off track.
This time is used for each member of the team to state three things: What they’ve been working on, what they’ll be working on and any blockers they’re experiencing.
It’s always best to try and stick to these three key facts before you start talking about potential issues or solutions.
Wednesday – Client Design Review
In an attempt to keep new features rolling out on a weekly or bi-weekly basis, we recommend reviewing design enhancements every week. It can be something as small as a field input change or something as large as a new feature, but it’s always worth it to share new ideas.
This is also a great way to keep the backlog grooming constantly moving. While most of us will always have to answer reactively to design requests, weekly design reviews are a great way to bring up new items from the backlog on a regular basis.
Thursday – Stand Up
Repeat Tuesday, but really take a little time, in the end, to dig into the problems that the team is facing. If they have gone four work days without experiencing something worth discussing together, it would be suspicious!
Friday – Client Development Review
Recapping the week with your client or Product Manager is a great way to keep them in the loop on the progress you have made throughout the week.
Instead of waiting until a feature is complete, try demoing the progress weekly. This will create transparency and will hopefully make them a larger part of the development process.
Reviewing work on a weekly basis also helps you catch discrepancies in requirements and expectations.
At an agency, there’s always room for change in any given day, but knowing what tomorrow could bring always seems to help. Try this out for one of our projects and let us know if you need help! We are always open to answering questions.