Agile and ISO aren’t incompatible; it’s time to challenge conventional beliefs. In this article, Nathan Sykes makes the case for Agile and ISO.
At last month’s JAX conference, Thomas Much talked about pair and mob programming and how Agile becomes and remains successful. We caught up with him to talk about all this and more.
At last month’s JAX conference, Wolfgang Strunk explained how agile software development can help create a coherent architectural landscape in a large company. We caught up with him to dive deeper into the Agile topic.
Each Agile team is a cycling gear; a threaded organization is a humming machine. Implementing a Digital Thread means you will have access and agency over your full process information. Without one in place, your Agile approach is limited to the team level.
At last month’s JAX conference, Wolfgang Pleus talked about the growth of the Agile movement and the trends that are particularly exciting right now. We caught up with him to dive deeper into the Agile topic.
In this article, Danish Wadhwa debunks some of the most common misconceptions about agile. Are you doing it right? If not, this article should help you discern the truth from myths.
Agile development is great for a lot of things. However, it’s important to remember security issues in the development process. In this article, Jessica Cyrus goes over the best ways to make sure security concerns are adressed properly in the Agile development process.
Not all Agile implementations are done well. How can you tell that your team has done it right? Here are Gleb Bryksin’s six signs that a company has a successful Agile process.
Do agile and DevOps really go hand in hand in the real world? Can an agile transition be considered successful without DevOps? What do we need to understand about agile and DevOps? These are just a few questions that have remained unanswered. We talked to Zubin Irani, CEO at cPrime, a full-service consultancy that implements agile transformations and delivers agile solutions, about the importance of agile in today’s tech environment and what it means to be fully agile.
When the forefathers of Agile met to write the manifesto that provides the guiding principles of Agile software development, Wikipedia was just formed, the iPod hadn’t launched, and the first versions of IntelliJ IDEA and Eclipse were in beta. The principles of Agile have not changed. More than ever, we strive to satisfy the customer through early and continuous delivery of valuable software.
Each person has their own beliefs about technical debt, but the whole discussion can be summed up in only a few words: new technical debt is good and old technical debt is bad. “If only it were that easy,” some insinuate.
The same marketing hype that surrounded “Agile” has now switched to “DevOps”; the combination of the two is one way to solve all the issues that IT organizations have been known for. This has generated the chimera of the “full stack” developer, which simply means that now a developer is expected to do it all. What else could it mean?
In the sixth part of his common sense software engineering series, blogger Steve Naidamast gives us a valuable lesson: although many technical managers avoid using Function Point Analysis, this gem is one of the primary foundations in actual software engineering for developing accurate and sustainable project timelines.
Surely you’ve heard of the term Technical Debt something you incur when you don’t invest in a clean code basis from the very start. With time, hastily pounded out code becomes more and more complex and difficult to maintain, it no longer scales, etc., such that costs escalate disproportionately.