Low-Code and Agile 2: A Winning Combination

For something as complex as software development, there can be no “right” way of doing things all the time. Each project has its own set of variables, challenges, and idiosyncrasies. And every developer has a preferred way of working, which makes it difficult to set any hard and fast rules. But this doesn’t mean you should dive into your development projects head first, without guidelines or a methodology—albeit a flexible one—to inform the way forward.

Agile Regression Testing: How to Do It Well

For teams following agile software development practices, regression testing is a must. Agile teams constantly make changes to live software that can introduce regressions (or, code changes that break the functionality of part of an app). Regression testing can keep teams from shipping critical bugs to production by confirming the most important parts of an app are still working every time new code is pushed.

App Development: 3 Ways to Add an API to Your App

Applications that use a REST API architecture are designed to be loosely coupled and transfer information quickly. While this architecture focuses on transferring data between clients/servers, it can also apply when interacting with other systems and users. In the world of app development, the need for better, faster, and easier-to-understand APIs is growing, and REST APIs are dominating the legacy modernization conversation.

Replacing the FMEA Risk Assessment: How to Manage Risk in an Agile World

Product failures and defects can occur on many different shapes and levels, impacting any part of the user experience, functionality, and even safety. In the past, organizations were taking the approach of of Failure Mode and Effects Analysis (FMEA) for risk assessment. This allowed teams to identify and prevent failure before a product or update is released.

What is Agile Methodology and How Does it Work?

Software is available everywhere we look. Any machinery we use associates itself with code that controls the way it works. Software teams work to write these applications, and many software developers band together to work on a single project. They keep working on ensuring that the application should work just as designed for the end-user when they deploy the code.

Agile Data in Financial Services

In financial services, data is essential for storing product information, capturing customer details, processing transactions and keeping records of accounts; the relationship between products and their underlying data has always been symbiotic. A significant amount of data infrastructure is static, fragmented across data silos or based on legacy platforms. This has created an impedance mismatch between products and the underlying data.

Starting your BDD journey in Jira with Zephyr Squad

In this 60-minute session, our experts will provide an overview of what is #BDD, and why it’s gaining popularity with #Agile teams around the world. If you have been on the fence about combing BDD and test management, this session will provide you with ample reasons why Zephyr Squad (formerly Zephyr for Jira) is your best companion in your BDD journey in Jira.

A Guide to Agile Development: Getting Started with a Checklist

I’m sharing my experience as part of transitioning various programs and projects in adopting agile principles, which in part or in total made them successful. This blog series will give a guideline of steps for an organization to successfully start Agile Transformation from scratch, from having no understanding of agile to being a successful team in delivering the objectives of the project.

Checklist of Canary Testing Frameworks

Agile development makes extensive use of tests to ensure new code doesn't introduce regressions. While certainly valuable, they don't prevent every problem from reaching production users. It's not feasible to have 100% test coverage, and even if there were, there's no guarantee the tests themselves are error-free. Canary tests add a layer of quality assurance to the Agile development process by letting you release the new code to a small set of actual users.