Risk-based testing allows project teams to focus their limited test efforts on the areas of the product that really matter, based on the likelihood of bugs in those areas and the impact of bugs should they exist. By using risk priority to sequence test cases and allocate test effort, test teams can also increase their chances of finding bugs in priority order and allow for risk-based test triage if necessary.
Software developers are not typically at the top of the organizational chart. Yet in some cases, developers are able to wield their knowledge and control of the code to hold management hostage to the developers’ own agenda. How can you avoid being taken hostage and losing control of your company and its software?
A switch to agile often conflicts with personal career goals such as maintaining the status quo and working no harder than necessary. These twenty guidelines will help you sabotage your agile project, helping you fail quickly and spectacularly.
Risk management is an illusion. We must recognize that software projects are inherently risky and admit to ourselves that it's not the known problems that are going to cause our projects to fail. It's the risks that are unmentionable, uncontrollable, unquantifiable, or unknown that make projects crash and burn.
As a new Army Ranger, Payson acquired many hard-earned lessons. But dodging snakes and alligators while navigating a Georgia swamp one moonless night, he learned two lessons in particular that can help project managers navigate their software projects.
Sometimes in testing we find problems that surprise us. And that's where risk-based testing comes in. Build your tests around "What if...?" statements to help you anticipate problems before they arise.
The Squall team’s product prototype pleases big client Acme. But when the client won’t budge on its strict quality, time, or budgetary requirements, the Squall team leaders determine that the best they can offer Acme is the truth.
Just when you think your application is free of defects, you find security vulnerabilities lurking beneath the surface. Penetration testing can help you get them before they get you. Ryan English discusses vulnerabilities and offers five steps to organizations looking to start a Web application security initiative.
Have misplaced priorities or a lack of focus allowed your development project to run wild? Don't let a stampede of defects, repairs, and requirements change drive your project. Follow Robert Galen's advice, and corral that development with release criteria.