Topic: Best Practices

We share proven best practices in software development. We enlighten success stories that inspire and educate.

  • How to Take Over a Failing Software Project Step-by-Step

    According to the Standish Group, 30-40% of software projects fail and 75% go over budget. So, if you're an app owner or product manager facing a failing project, you're not alone. Fortunately, there are strategies for reviving a stalled software project. This article offers a comprehensive guide to successfully transitioning a failing software project to a new development team. The first step is acknowledging that your current approach…

  • App Owner and Tech Debt: Detecting and Managing the Unseen

    At last, you've found it - an article for understanding technical debt in software development with no tech background, focused on app owners needs, free of tech jargon and needless tech details! It finally explains in human language just what you need to know for decision-making. With over two decades in the IT industry, I am convinced that when a project is handled by experts, product owners don't need to know anything about the technical debt - that's the team's domain. So, if you are aware of this concept, it's a sign that your team has failed, and the problems are already…

  • Speed vs Quality: Which Is Preferred in Software Development?

    When developing an application or software, the question of whether to prioritize speed or quality often arises. Striking a balance between the two is crucial. In our article, we discuss how to find this balance and ensure both efficient development and high-quality outcomes. In September of this year, I was fortunate enough to visit the Seamless Saudi Arabia exhibition. After speaking with some attendees and exhibitors, I was able to identify several trends of the IT market in Saudi Arabia. One of…

  • When Business Should Care About the Quality of Their Software

    The article discusses the importance of balancing technical improvements with visible business benefits in custom software development. It highlights how poor architecture, slow development, and performance issues can impact a business. Custom software is written to help businesses make money. This is a very simple idea, and I hope that everyone would agree that it is true. Sometimes it happens that we meet business project owners who are more excited about the technologies and coding than about the business itself. But it is a rare case and not the one that helps the project be…