Agile testing is commonly mistaken as only referring to the Quality Assurance/testers on the team. This is a destructive, limited view of this critical agile development piece. This article places the emphasis on the often neglected, misunderstood and essential collaboration tool.
Using continuous testing, one can immediately detect problems in code — before it’s too late and problems spread. Using a clever combination of tests, tools, and techniques you can tell right away when there’s a problem and it’s easiest to fix. The author uses a case study to illustrate the benefits of continuous integration (CI) and how it leads to better quality control (QC) and quality assurance (QA).
Question: I’m so confused. I was a Quality Tester at my last job, but here the employees seem to use the titles Quality Assurance, Quality Control and Testing interchangeably. I started out in a more traditional organization, but now I’m a tried and true agile believer. Since I have no job description, what are my responsibilities?
The three concepts are often used interchangeably. Ask what it means in your new organization and accept that as your role in your workplace reality despite the real definition.
Find the specific meanings for each term from a university professor in the town where you work. Use that information to correct the organization so that they use proper terminology.
Once you learn your job description from Human Resources, create a new title for yourself so that others can understand what you do. Perhaps Defect Engineer would be apt.
Since agile teams work without formal processes or documentation, there is no need to answer to a particular title. Everyone on the team is merely a team member.
For an agile project to progress smoothly, the backlog must be groomed and ready for each sprint. That work must be included in your project plan. This article gives you five points to consider when planning that work.
Custom software development is notoriously difficult to estimate. We start with vague ideas of what we want, expecting to fill in the details later. We’re usually doing something a little different than what we’ve done before, or completely different. How can we act more productively?
Have you realized that your organization is not putting enough attention on requirements? Wondering what types of tools are out there and how much they cost? Do you even need a tool? And if so, what kind?
The waterfall methodology for projects is aptly named, because it is equally painful to try to go back to prior phases of a project once the effort has advanced to the next phase. This article will outline two reasons to avoid waterfall, and three ways to approach software projects that are more useful.
If Kanban works well on specific software projects, can it be scaled to facilitate Lean throughout an organization? Here we look at how Kanban can be thought of as a general purpose change management approach for your organization.
Governance happens in projects all the time, and a well thought-out governance process can be a powerful project tool. In this article, we will examine why governance is necessary, where governance is most effective and how we as project and program managers can use governance to powerful effect.
In an attempt to help those of you struggling with Business Process Improvement and Business Process Analysis, our expert presents these “anatomical components” in terms of a series of rules so that you can use them in your efforts.
Standardization is the “copy and paste” method of process development. It’s as bad in spreading process through an organization as “copy and paste” is in code. Copying a working instance may be a good starting point, but it’s a bad destination. Creative work needs attentive thinking, even when deciding to not change the status quo.
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.
Being a strong tester means being critical and assertive. This ability is not easy to control and can lead to finding flaws in all sorts of everyday surroundings. How to communicate these errors and mistakes without being a first-class jerk is also difficult. Can you keep everyone's frown upside down?
"There is no shame in not knowing; the shame lies in not finding out."