Whether it’s a feature, a bug, or a regression, it’s all work. It all has the same level of prioritization before we add in the business context. This is how we decide what gets worked first.
agile software development
Agile software development content on the Revelry Blog: Navigate our lab notes by using the tag system.
I’ve chosen this specific list as part of an effort to foster a shared understanding of commonly used terms. This “glossary” doesn’t exist in a vacuum – it can (and should) continue to be challenged and evolve over time as our understanding changes.
The team that seeks out feedback and views it as an asset rather than a slap in the face is the team that delivers real value to clients.
When every day is “same same but different” as they say, it helps to rely on habits for staying on top of responsibilities. This way, we don’t slip into feeling reactive and stressed out with our workloads.
It’s too easy to drop the learning aspect from Agile when the default is to build. We believe in the value of design thinking principles, and our innovation partners benefit from the quick wins that come out of slowing down once in awhile. Here’s how we do it.
Speaking up about potential challenges is a normal and important part of our process. When a teammate raises a fire drill, available or relevant teammates participate in the topic thread. Sometimes, we resolve the issue in a few minutes. And other times, we identify a major challenge and take the conversation to the product owner to discuss next steps.
If you take a cross-section of developers, you’ll find some very mixed opinions about pairing. Some devs hate it. Some devs write blog posts about how great it is. Why is this? Let’s chat about why pair programming is awesome, and what you can do to level up your skills.
We have daily standups. We tried adding a thing called a daily 4:20. But in the end, we decided to improve our ticket comment writing game. And Aline led the charge on the how and the why.
If you’ve ever wondered the difference between staging and production, or styles and UX, then this is for you!
At its core, pairing is another useful strategy to work with your peers and get shit done. The best way to know what works for you is to take more opportunities to pair with others, think about what works and what doesn’t work, and continue to refine this skill set.