Many teams do single-point measurements in their projects. But that doesn't give you a good long-term picture. When you look at multiple-dimension measurements—especially trends over time—you learn more. You can take those trends into a retrospective to investigate how your team could work better.
Testers are rarely part of an entrepreneurial startup team, but are there lessons for them in the lean startup approach? Lee Copeland says yes. The basic idea behind lean startup is that companies should focus their time and resources more efficiently, and this concept surely can benefit testers.
There is an ongoing debate concerning agile's viability within an organization compared to waterfall. More and more, agile seems to be the conclusion that major teams are arriving at, and Samsung is the latest company taking advantage of agile to get its products to consumers at a greater speed.
When it comes to DevOps, the goal is to move applications from development, to test, and then eventually to deployment as quickly and efficiently as possible. However, you can still be agile while having a safe, properly security-tested DevOps environment.
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.