In-sprint automation is a serious affair, an ambitious goal! It always surprises me how organizations and teams just start on it without proper readiness and planning. And then they fail! Miserably and the team, QA engineers, or some such entity is to blame. Frustrating to say the least. In-sprint automation is doable but not always possible in all teams. If not planned and executed correctly this goal can quickly become a distant dream.
As the name suggests, in-sprint automation is automating and developing the user story in the same sprint. Easier said than done. The team will need to overcome several challenges before getting to this state.
Here is a checklist to check if a team is ready for In-sprint automation.
- Does your organization’s culture support fast-paced development and testing? Fast-paced development means blockers are few, infrequent, and quickly resolved. This ensures the team does not spend sprint time working or waiting for them.
- Is your automation framework flexible and exhaustive? If you have been adding methods to your framework with every automation test case you code then it’s probably not matured as yet. A good framework is like the ingredients of a recipe and if they are prepped the dish can be cooked in minutes.
- Do the team members know the product and process well enough to work together? This is important because several testing tasks are dependent on an understanding of the product and the process.
- Do you have a plan to address technical roadblocks in automation? A strategy is needed when QA or dev gets stuck at a technical challenge and a route needs to be defined so that other tasks are not affected.
- Are you planning to automate all the scenarios of a user story? This is like making the wedding cake, decorations, makeup yourself a few hours before your wedding. You run the risk of not completing it in time and with poor quality.
- Do you have enough QA resources? Manual and automated? Needless to say, resources play an important factor in automation.
Unless the above questions are answered to satisfaction aiming for in-sprint automation is not an achievable goal to set. In-sprint automation should be initiated by the team and not dictated by management!