Methods & Tools is a free software development magazine on Software Project Management, Software Testing, Agile,
Scrum, Lean, Kanban, Requirements, UML, Business Analysis, Programming, Coding, Databases, User Experience,
DevOps, Open Source Tools (Java, JavaScript, C#, .NET, PHP), Software Architecture, Mobile Apps, IoT, Blockchains

Recommended Software Development Articles

* What Happens to QA When AI Writes 100% of the Code? Today, you can find tools that generate code and AI-assisted test automation tools that will handle the quality assurance part. Is it the death of traditional manual testing? In this article, Rimpal Mistry reminds us that human validation is still needed to provide the final check of delivered software.

* Agile Teams: Building a Collaborative Scrum Team How do you get people to work effectively as a team? Instead of reorganizing every two weeks, maybe we should focus on what makes teaming work. Books and blogs focus on psychological safety, communications, trust, personal growth, and a shared purpose.

* QA Metrics That Still Mean Something in the AI Era Metrics exist to answer two questions: how good is the software we deliver, and is our testing approach actually working? AI-generated tests broke the old answers to both. QA metrics were never really about numbers. They exist to answer two questions. First, how good is the software we are delivering to customers? Second, is our testing approach actually working, or are we just going through the motions?

* How Software Testers Help with Requirements in Scrum As many testers have, I struggled in my first year on a Scrum team. How do I write tests without a spec? How do I know when I am done with software testing when there is no test plan? This article shows the important contributions that software testers on Agile teams can make in the requirements gathering activities of feature and user stories creation.

* Splitting Regression Tests on an E-commerce Backend In this article, Mikhail Golikov, the sole QA on a seven-team backend e-commerce platform, explains where each regression check belongs, in the browser or at the API. He shares the rule he actually uses, two bugs that only one layer could have caught, and the realization that finally made his browser suite small and stable.

* Tips and Practices for Optimizing the Processes of Web Product Performance Testing Head to any site in which testers and developers are seeking help on their testing, and you’ll see questions on which tools individuals should adopt, learn and use. This article tries to answer the question whether you should use Postman or RestAssured for API automation.

* A Software Tester Guide to Effective Bug Reporting One of the main responsibilities of software testers is to find and report issues with the software. We call these issues "bugs". Bugs can be found everywhere. Some are obvious while others are harder to find. It is up to the tester to thoroughly explore a given app or website, and look for ways to break them. Or in other words, expose bugs that can lead to a bad user experience. However, it is not enough to just know a bug exists. You need to properly report the bug, by writing a bug report, in order to get it fixed. Think of it this way: the better your bug report is, the higher the chances of getting the bug fixed. Essentially, bug reporting is a software testing skill, and one that is certainly worth having and improving. We have a few tips coming from an experienced software tester to help you master this skill. Let's take a look at why bug reporting is important and how you should report bugs effectively.

* The 12 Agile Principles Much is said and written about the Agile Manifesto, but there is less material out there around the 12 agile principles that go along with the manifesto. So Kevin Pedersen has put out there his own thoughts around these 12 sentences that help us understand how to apply the Agile Manifesto in your daily work.

* Eight Steps Program to a Lean Mean Kanban Machine Are you contemplating switching your Agile software development team from Scrum to Lean Kanban? The first step of recovery is to admit you have a problem ;O) This article provides an eight steps program to migrate your Agile software development team from Scrum to Lean Kanban practices, assuming an initial Scrum implementation.

* Six Key Event-Driven Architecture Patterns Learn six key patterns of an event-driven messaging architecture design that have facilitated creating a robust distributed system used by more than 1400 microservices. Some of the patterns here are more commonplace than others, but they all share the same principles. By using an event-driven pattern, you get less boilerplate code and more resiliency. In addition the microservices are much less coupled to one another as the producer does not need to know who consumes its data. Scaling out is easy as adding more partitions to the topic and more service instances.