Testing at the end of a development cycle is a common practice in traditional approaches. Unfortunately, it becomes an obstacle on your path to agility, slowing down your ability to deploy to production faster. Let’s take a look at what goes on in this testing phase, some potential causes and ideas for getting unstuck.
Do you know what expertise you need now, as you enter into an agile development environment? Unfortunately, we use the same word (“testing”) in agile, but it means something different from what you have seen and managed in prior non-agile projects. If your testers are writing test cases, tracking testing progress and recording bugs in a separate defect tracking system, stop now; you are using the wrong people to do the wrong thing.
Embedded products for automotive applications typically follow a very rigid development process. The details vary from Original Equipment Manufacture (OEM), however, the need for risk mitigation is the same. Development for vehicle systems can be quite costly. Additionally, mistakes can have a heavy impact on quality perception as well as legal ramifications.
When teams transition to agile development and the QA/testers continue to follow the same testing processes and tools they used before joining the agile team, you're asking for trouble. In this article, we contrast agile and traditional testing--and give an example of how a mind map can facilitate the testing process.
When technology shifts, you need to learn how to move into a new world. It can be frightening at times, but if you choose your path carefully, you can find new adventures and rewards. Keep these tips in mind.
by Kevin Aguanno, CSPM (IPMA-B), Cert.APM, PMP, PMI-ACP, CSM, CSP, FPMAC, FAPM
Trying to implement agile DevOps in a traditional DevOps environment is a huge challenge without first changing underlying governance practices. In this article, the author explains why--and identifies some success factors.
Testing is crucial to risk management, allowing components and systems to be put through their paces. Ignoring testing can lead to disastrous consequences, possibly even cancellation of the project. Gain an understanding of the purpose of different types of testing and where each type is appropriate.
Some topics in agile testing may point to dysfunctional organizational practices that are often taboo, off limits or avoided in regular conversations. In this article, we identify four such topics that need to be discussed and addressed for agile success.
When the business environment demands quicker turnaround time for business needs, approaches like DevOps help organizations meet them. At the same time, it also introduces additional challenges to project managers. In this article, we discuss what DevOps are--and the additional challenges that need to be handled by PMs when they adopt them in their projects.
The iterative nature of agile development poses key challenges when validating software for regulated industries. With thoughtful planning and careful execution, it is possible to achieve compliance through automated testing. Successful practices using automated validation testing and the steps a team can take to reduce validation cost and time at the end of a release cycle are discussed.
This is the fourth and final installment in this series on using the latest UX methods for focusing on the right problems and slashing requirements-based risks. In this installment, we will be validating designs, using our prototypes for conducting usability tests.
This procedure describes the process of testing software code or products by the test team. It documents the procedure for the entire testing cycle: generating test plans, scheduling tests, conducting tests and reporting test results. This procedure applies to new development, as well as major and minor releases, including customized solutions delivered to customers.
Do you know how to thoroughly and efficiently test the software product you have so painstakingly built? Don't risk delivering a faulty software product due to insufficient or unfocused testing. Use this list to check whether you are testing smart--or just testing!
Defining and measuring software quality attributes is critical to the success of any distributed application, and performance is no exception. Distributed applications must demonstrate performance in order to assure immediacy. Use this project plan to stay on top of your Performance Testing.
Selecting the right testing tool means you must look at a myriad of factors and how well each candidate tool meets your application's testing requirements. This form will help you evaluate the candidates and select the best testing tool for your app.
Use this template to keep track of crucial information for your Business Continuity Planning (BCP) and Disaster Recovery (DR) test report. This template includes sections for scope, acceptance criteria, assumptions, lessons learned and more.
"Things should be made as simple as possible, but not any simpler."