Tech Insights

The benefits of decomposing your business’s large monoliths are well established. Your company’s systems may have started small, and their simplicity may have allowed for rapid initial development. However, as they’ve grown, complexity has increased, and work has slowed. It’s time to break things up into loosely coupled systems so that a slowdown in one area doesn’t affect the whole system, and multiple teams can make rapid iterations without getting bogged down in negotiating dependencies with other parts of the system.

Now the question is how. You’ve got ideas, and some of the components to break out seem obvious, but do those ideas add up to a coherent vision that puts you where you want to be a few years down the road? Or are you likely to hit stumbling blocks, like systems not getting the data they need via a reasonable path, complications arising from unexpected dependencies, or user experiences made complex by asynchronous data? Where should you start if you want to avoid troubles down the line?

Our mission is to help companies adopt new ways of working and approaches to software delivery, while simultaneously embedding culture change through upskilling and empowering their teams. That’s why we’ve written so many articles about team development over the years. Here are some of the highlights and key takeaways to help leaders develop teams that drive innovation and customer value.

For the sixth consecutive year DragonSpears, a Midwest-based software consulting firm has been named one of “Chicago’s Best and Brightest Companies to Work For®” in 2022. This award is presented by the National Association for Business Resources (NABR).

According to Roman Pichler, the ultimate responsibility of a Product Owner is to ensure that the product creates value for its customers and the company. Creating an effective product requires a deep understanding of what customers and users need, insight into existing functionality, and a vision of opportunities for improvement. Then the Product Owner must turn those needs into features, break them down into incremental User Stories, and convey the requirements back to the development teams.

After migrating to AWS or refactoring your current cloud architecture, you may be surprised by the size of your monthly AWS bill. Even with the breakdown of what you’re being charged, if your bill is higher than you estimated, it’s not always obvious what’s causing it. Every scenario is uniquely different, but here are some ways to troubleshoot your AWS budget and decrease costs.