|
How Testers Can Add Value Earlier in the Development Lifecycle Before you can achieve continuous delivery, you need to first start implementing continuous integration. Some say CI is just for developers, but testers also play their own important roles. This article describes solutions that will help you add value to the development lifecycle—whether you work in an agile, DevOps, or traditional context.
|
|
|
Are You Ready for Go-Live? 8 Essential Questions As real and daunting as scheduling pressures can be, they have to be balanced with the consequences of a potentially disastrous premature go-live. Don’t let all the reasons a system simply "must" be implemented by a target date overwhelm compelling evidence that it is not ready. Consider these eight questions honestly first.
|
|
|
Six Tips for Building a Better Load Testing Environment Building a realistic test environment is essential for the success of your load testing, but it is also a challenging task that can require resolving technological, organizational, and security issues. This article can serve as a roadmap for building a faster and more efficient load testing environment that leads to quicker deployments.
|
|
|
Building Software Development Dashboards with Key Performance Indicators Key performance indicators help managers gauge the team’s progress, understand what phase the project is in, and figure out where costs, goals, or processes need to be adjusted. This article details some typical KPIs to be used in dashboards to provide business analytics and communicate information in the most useful way.
|
|
|
The New Gives and Takes in a Software Tester’s Role As champions of product quality, software testers have an increasing responsibility in empowering the team to understand and own quality themselves. Testers need to optimize their efforts by giving away some tasks to others on the product team and taking on newer tasks to align with a more focused approach. Read on to realize what you should give up or take on.
|
|
|
Do Your Demos Smell? In the agile world, there is a concept of “smells,” or symptoms that things aren’t going well. Introduced by Kent Beck and expanded on by practitioners, smells now describe problems involving adoption, coaching, design, code, and teams. When we see these symptoms, we can identify opportunities to improve.
|
|
|
Product Backlog Hygiene: Prepare to Be Groomed How do you start with a product backlog when you’re transitioning to agile? In this article, Darin Kalashian shows us how a cross-functional team at the product owner level creates a product backlog.
|
|
|
Transition to Agile: Large Technical Debt, Small Project When you transition to agile and you have a reasonably size codebase, chances are quite good that you’ve been working on the product for a while. You certainly have legacy ways of thinking about the code and the tests. Now learn how to work yourself out of the technical debt you have accumulated.
|
|
|
Changing Iteration Contents Mid-Sprint Johanna Rothman writes on how she facilitated a project management clinic in which she overheard this statement: "We have a product owner who persists in changing the contents of the sprint during the sprint. This is difficult for us. It costs us to change the content." To Johanna, this is a huge pain and it is similar to multitasking.
|
|
|
Driving Efficiency and Effectiveness with Web Analytics and Risk-Based Testing Web analytics can help you deduce, reduce, and prioritize your testing efforts. Learn how to gather and use qualitative and quantitative information about your users and the risks that can threaten your software's success.
|
|