If you’re looking to make the whole organization agile—through iterative work cycles, continuous improvement, and direct feedback from customers—fear has to be involved to some degree. But in order to foster a culture of honesty and trust, this uneasiness will have to be overcome.
One of the biggest myths in the world of agile development is that there is not enough time to do security testing. Sanjay Zalavadia shows you the most efficient and cost-effective way of performing security testing in an agile environment: by rolling it into each sprint incrementally, from day one.
We often attribute project delays to internal reasons, such as poor management, lack of collaboration, resource issues, and software quality, but there are often reasons that fall outside of the norm. Rajini Padmanaban provides some examples of these types of project delays and how to manage them.
As organizations embrace agile, requirements become a challenge because they must be considered and validated in each (short) sprint. Ideally, nonfunctional requirements should be a continuous focus throughout the project. Here are some ways to better address NFRs in an agile development lifecycle.
Agile doesn’t always require you to throw the baby out with the bathwater. Just because you plan to incorporate agile into your team (or even your entire organization), that doesn’t mean you need to scrap whatever other practices, such as outsourcing, or methodologies you’re using.
Documenting user requirements is always a challenging phase in software development, as there are no standard processes or notations. However, communication and facilitation skills can make this activity easier. Here are five techniques for converting user stories into testable requirements.
It’s crazy to think just how far we’ve come since the term "agile" was introduced into software development back in 2001, as it seems like just about every company is incorporating these faster, more collaborative techniques into development and testing teams. But can agile be considered a fad?
Single-point estimates, whether they are for a budget or a schedule, are never correct. Things happen. Demanding that your team provide you an exact number and then treating that as a guarantee is not being a good manager—or being agile. What if you could provide a different estimation leadership?
This issue of Better Software gives best practices that will improve your skills in a variety of categories, including agile, testing, DevOps, and process. These articles aim to better your professional lives so that you and your team can deliver software technology that delights customers.
Testers are very much still needed. However, with so many new technologies and roles becoming available, some testers may want to explore options for their career paths. Michael Sowers offers an agile approach to determining your career direction, evaluating the alternatives, and developing a plan.