- All
- Engineering
- Software Testing
Powered by AI and the LinkedIn community
1
Project scope
2
Testing strategy
3
Team capacity
4
Risks and uncertainties
5
Here’s what else to consider
Estimating testing effort in Scrum is not a simple task. It requires a good understanding of the project scope, the testing strategy, the team capacity, and the risks involved. In this article, we will discuss some of the factors that you should consider when estimating testing effort in Scrum, and how they can help you plan and execute your testing activities more effectively.
Top experts in this article
Selected by the community from 77 contributions. Learn more
Earn a Community Top Voice badge
Add to collaborative articles to get recognized for your expertise on your profile. Learn more
- Udish Vedantham Manager III, Quality | Amazon - Artificial General Intelligence (AGI)
6
- Muhammad Yahya Software Quality Assurance Engineer | Software Tester | Automation Engineer | Software Engineer
5
- David Akinyemi Senior Software Quality Engineer
5
1 Project scope
The project scope defines what features and functionalities are expected to be delivered in each sprint, setting the boundaries and assumptions for the testing scope. When estimating testing effort in Scrum, you should take into account the size and complexity of the user stories and tasks, as well as their dependencies and interactions. Additionally, you should consider the acceptance criteria and definition of done, which are used to determine when a user story or task is complete and ready for delivery, as well as the quality standards for the testing results.
Help others by sharing more (125 characters min.)
- Udish Vedantham Manager III, Quality | Amazon - Artificial General Intelligence (AGI)
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Start with your customer and acceptance criteria. Based on these, define what are your right quality KPIs to measure/assess - both functional and non-functional and have a clear Definition of Done. From the final launch date, work backwards and define what work needs to be delivered in which Sprint. Depending on the time and resource constraints you need to make right trade-off decisions to ensure optimum test coverage. Identify your dependencies, integrations and boundaries. Ensure you establish right test contracts with partner teams. Your team is the best judge of the efforts and you should do everything possible to support them to iterate over time and improve on the delivery pace as-well-as effort estimation.
LikeLike
Celebrate
Support
Love
Insightful
Funny
6
- Muhammad Yahya Software Quality Assurance Engineer | Software Tester | Automation Engineer | Software Engineer
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Scope of the User StoriesAcceptance CriteriaDefinition of Done (DoD)DependenciesRegression TestingTest Data and EnvironmentsTesting TechniquesExperience of the TeamVelocity and CapacityRisk AnalysisCommunication and CollaborationFeedback LoopsTooling and AutomationBuffer for Unknowns
LikeLike
Celebrate
Support
Love
Insightful
Funny
5
- David Akinyemi Senior Software Quality Engineer
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
As simple as Teams having a stated Sprint goal which is accompanied by a task/ticket and reviewed at every scrum ceremony will help monitor progress and ensure project is within scope .
LikeLike
Celebrate
Support
Love
Insightful
Funny
5
- Max Oliver PSM | GPMP | Agile Project Management | Machine Learning
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
The scope of the sprint is the most important step while testing an application. What are the focus areas and what delivers the most value should be clear in the scope.
LikeLike
Celebrate
Support
Love
Insightful
Funny
4
- Madhulatha Kancherla Gen AI for Leaders || SAF6.0 || CSM || Project Management
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Capacity Planning1) should understand the capacity to plan the iteration2) Scope takes the next lead once capacity is finalized to have achievable outcome
LikeLike
Celebrate
Support
Love
Insightful
Funny
4
Load more contributions
2 Testing strategy
The testing strategy defines how you will approach and perform testing in each sprint, including the testing objectives, methods, techniques, tools, and levels. When estimating testing effort in Scrum, you should consider the test coverage and depth, the test automation and manual testing ratio, and the test environment and data management. In particular, higher test coverage and depth will require more testing effort and resources; test automation can save time but requires initial investment; manual testing can be more flexible but requires more human involvement; and the test environment and data management can affect the testing effort and quality.
Help others by sharing more (125 characters min.)
- Dekanath Vivekanandan
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
1. Have an objective for each sprint2. Start early testing procedures, even before code is defined.3. Select the technique which is to be used to drive the testing.
LikeLike
Celebrate
Support
Love
Insightful
Funny
3
- Santa Singh Project Management | IT | Quality Assurance | Critical Software Analyst | Salesforce | API | SaaS | PaaS |
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Part of the test strategy-should also be identifying the parts of testing that requires repetitive steps should be scripted. Automating requires frameworks but simple small steps should just work with small scripts giving out expected results.
LikeLike
Celebrate
Support
Love
Insightful
Funny
2
- Gaurav Agrawal QA Manager | PMP®| OTT
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Testing strategy plays big role while estimating efforts as that defines what percentage will be automation and how much manual effort is required.
LikeLike
Celebrate
Support
Love
Insightful
Funny
1
- Jasbir Singh Test Automation Evangelist | Passionate Advocate for Excellence in Software Quality | Agile Practitioner | Team Leader - "Quality is not an act, it is a habit"
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Within agile frameworks like Scrum, it’s crucial to recognize that an effective testing strategy can’t be all static but should evolve sprint by sprint, based on team dynamics and the shifting demands of the development lifecycle. A thoughtful balance between automated and manual testing, coupled with a keen understanding of test coverage and resource allocation, plays a critical role in meeting the sprint goals.
LikeLike
Celebrate
Support
Love
Insightful
Funny
1
- Muhammad Ali
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
In the Testing Strategy we should consider following things.1. Identify the type of testing needed (e.g Unit, Integration, UAT)2. Identify the different test levels as different testing levels may require different time requirements
LikeLike
Celebrate
Support
Love
Insightful
Funny
1
Load more contributions
3 Team capacity
The team capacity defines how much work the team can handle in each sprint, taking into account the team size, skills, availability, and collaboration. When estimating testing effort in Scrum, you should consider the testing roles and responsibilities, skills and experience, and collaboration and communication of the team members. These aspects can affect the testing effort and quality depending on the level of competence, confidence, creativity, alignment, feedback, and transparency of the team members.
Help others by sharing more (125 characters min.)
- Vivek BR, MBA Director, Engineering (Healthcare) - Principal Tech Manager - Software Engineering I MBA | 4X International Tech Award Winner l 11.5k+ LinkedIn l Published Author | LinkedIn Top 1% Voice in IT
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Estimation is majorly driven by team`s capacity, assess the team's capacity by reviewing the number of testers, their skills and bandwidth. Factor in if testers split time with other responsibilities. Evaluate previous testing velocity to understand execution rate. Along with it, collaborate with testers to plan achievable testing goals for each sprint based on team capacity, balancing quality needs with realistic output. Continuously inspect and adapt as capacity changes each iteration.
LikeLike
Celebrate
Support
Love
Insightful
Funny
3
- Jason Nwakaeze Python |Django |NodeJS| MongoDB| Kubernetes |AWS
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Estimating testing effort in Scrum is no walk in the park. It's all about juggling different factors to get it right.Team capacity is a major factor. It's all about the team's size, skills, and how well they work together. Knowing this helps set realistic goals for testing in each sprint.These considerations are game-changers. They help teams plan better, deliver top-notch software, and stay on track with project deadlines. It's like having a roadmap for testing that keeps everyone moving in the right direction.
LikeLike
Celebrate
Support
Love
Insightful
Funny
3
- Manisha Jalal QA Specialist at McAfee
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
In Scrum, team capacity is great to sprint workload based on size, skills, availability, and collaboration. Estimating testing effort involves considering team roles, skills, experience, and communication, impacting effort and quality based on competence, confidence, creativity, alignment, feedback, and transparency.
LikeLike
Celebrate
Support
Love
Insightful
Funny
1
- Muhammad Ali
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
In Team capacity we should see the Velocity and Historical data.1. Use the team's historical data and velocity to estimate testing efforts.2. Review the past sprints to understand how much testing was done in similar situations.3. Team experience and expertise should also be considered.
LikeLike
Celebrate
Support
Love
Insightful
Funny
1
- Gaurav Agrawal QA Manager | PMP®| OTT
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Team capacity is important for estimating efforts as this has to b divided into RBS to have better understanding and helps to give efficient effort estimations.
LikeLike
Celebrate
Support
Love
Insightful
Funny
Load more contributions
4 Risks and uncertainties
The risks and uncertainties define the potential issues and challenges that can affect the testing process and outcome. Estimating testing effort in Scrum requires consideration of aspects such as risk identification and analysis, risk response and contingency, and risk monitoring and control. Risk identification and analysis can help anticipate and mitigate testing effort and quality issues, while risk response and contingency can help adjust and recover from them. Risk monitoring and control can measure and improve testing effort and quality issues.
Help others by sharing more (125 characters min.)
- Shyamalee Bhand Two decades of Test Delivery and Project Management experience | Test Transformation | TPI expert | SAFe-Agilist | Project Leadership
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Many a times stories or some enhancements are added midway in the sprint, which has a big impact on testing. As testing team acts as a quality gatekeeper, they have responsibility to complete testing and certify the user stories. But adding items in between jeopardizes the timelines and is a risk to test completion and thus quality of code.
LikeLike
Celebrate
Support
Love
Insightful
Funny
4
- Dekanath Vivekanandan
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Identify the risks as early as possible, try to reduce mid way addition of requirements to the sprint which jeopardize the entire sprint at times. Always have a contingency plan in order to meet the "Definition of Done".
LikeLike
Celebrate
Support
Love
Insightful
Funny
1
- Nithin M C# and Java Automation Test Lead, Consultant at Worldline
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Risks are always present in any project. Antocipat stand and common risks with similar projects is the key. Also leaving room for unforseen challenges.Get team ready for risk mitigation plans and get the disaster recovery in place.
LikeLike
Celebrate
Support
Love
Insightful
Funny
1
- Ergün Kaldırım QA Engineer at CloudNesil
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Big features not epics should not be added in the middle of the sprint. For example accounting, billing features. All the tasks details should be prepared on well defined with screenshots or snapshots. Manual test employees and Automation employees should be separated.
LikeLike
Celebrate
Support
Love
Insightful
Funny
- Gaurav Agrawal QA Manager | PMP®| OTT
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Risk and uncertainties should be tracked in risk register and Risk management plan should be in place at the time of preparing the Project management plan
LikeLike
Celebrate
Support
Love
Insightful
Funny
Load more contributions
5 Here’s what else to consider
This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?
Help others by sharing more (125 characters min.)
- Apeksha Dalvi-Chawan 2 x LinkedIn Top Voice | Certified Scrum Master | Test Lead | Mentor | QTP Certified | ISTQB CTFL®
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Although direct replication of effort estimates from past projects may not be advisable, there is value in leveraging historical data for insights. By scrutinizing previous projects, one can discern recurring patterns, extract valuable lessons, and identify factors that have historically influenced testing efforts.
LikeLike
Celebrate
Support
Love
Insightful
Funny
1
-
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
There are multiple factors we need to consider when giving estimations for test. Of course, project scope is at its top. Total timeline for the project is decided based on the complete project scope. When it comes to the agile, scope is the stories taken in to the sprint. Story point estimations include both development and test effort required for that story to be delivered. When test estimations are given, we need to consider the test coverage and depth related to the stories taken in. From that test scope we need to decide on how many tests we are going to automate and how many manual test cases are there. In order to do this requirements should be clear.
LikeLike
Celebrate
Support
Love
Insightful
Funny
1
- Muhammad Ali
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Few more things to consider.1. Identify and account for any external dependency that may affect testing.2. Implement feedback loops within the team to continuously improve estimations.3. Collaborate closely with the development team to understand the implications details.4. Clearly define the definition of done. Ensure that the testing criteria is well defined and agreed upon by the team.5. Complexity of a system or new feature (under test) should also be considered before giving estimations.
LikeLike
Celebrate
Support
Love
Insightful
Funny
1
-
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Other considerations for me are remember it's a "whole team approach". If you still rely on testers to do all the testing the effort estimate is affected.If I know the product owner values quality and testability when factoring user stories that's a win.If I know the devs value unit testing and code quality that's a win.If QA are the only ones considering quality then your estimate is much larger.
LikeLike
Celebrate
Support
Love
Insightful
Funny
1
- Kanwaljeet S. Associate Principal Engineer at Nagarro, ISTQB CTFL, MCTS, MCP, Test Automation Frameworks, Testing Processes, Artificial Intelligence, Mentoring and Leading
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
Collaboration with Development Team is an essential factorRegularly collaborating with the development team to understand the technical aspects of user stories, example: discussing with developers may reveal complexities that impact testing, influencing effort estimatesThere should also be Reassessments and AdjustmentsRegular reassessment and adjustment of estimates based on actual performance and evolving project dynamics too has an impact, example, if the team faces unexpected challenges during testing, they should be open to revising estimates for future sprints
LikeLike
Celebrate
Support
Love
Insightful
Funny
Load more contributions
Software Testing
Software Testing
+ Follow
Rate this article
We created this article with the help of AI. What do you think of it?
It’s great It’s not so great
Thanks for your feedback
Your feedback is private. Like or react to bring the conversation to your network.
Tell us more
Tell us why you didn’t like this article.
If you think something in this article goes against our Professional Community Policies, please let us know.
We appreciate you letting us know. Though we’re unable to respond directly, your feedback helps us improve this experience for everyone.
If you think this goes against our Professional Community Policies, please let us know.
More articles on Software Testing
No more previous content
- You're struggling to attract clients as a freelance software tester. How can you build a strong client base? 6 contributions
- You're facing tight project deadlines for testing. How can you avoid last-minute rushes and ensure quality? 3 contributions
- You're facing conflicting feedback on test outcomes. How do you ensure accuracy in software testing? 3 contributions
- Your team is feeling the strain of regression testing in a CI/CD workflow. How can you boost their morale? 3 contributions
- Here's how you can promote work-life balance for software testing managers while maintaining productivity. 6 contributions
- You're juggling new feature testing and regression testing in Agile. How do you prioritize effectively? 1 contribution
- You're striving for success in software testing. How can you avoid the pitfalls of being overly assertive? 3 contributions
- You're facing critical testing issues with developers. How do you effectively convey the urgency? 2 contributions
- You're faced with last-minute changes from clients. How do you uphold top-notch software testing standards? 3 contributions
- Here's how you can hone the key skills that software testers need for future career success. 1 contribution
- Struggling with time constraints in continuous integration testing? 2 contributions
- Here's how you can maximize artificial intelligence in software testing. 2 contributions
- Developers are clashing over bug severity opinions. How can you help them find common ground? 6 contributions
- You're faced with conflicting stakeholder feedback. How do you balance it with your test results analysis? 6 contributions
No more next content
Explore Other Skills
- Programming
- Web Development
- Machine Learning
- Software Development
- Computer Science
- Data Engineering
- Data Analytics
- Data Science
- Artificial Intelligence (AI)
- Cloud Computing
More relevant reading
- Software Testing What strategies can you use to handle changes in testing requirements during a Scrum sprint?
- Software Testing How can you use Scrum testing tools and techniques to ensure a well-defined, prioritized product backlog?
- Scrum How do you write and execute Scrum test cases?
- Scrum What are your tips for meeting Scrum testing standards?