ISTQB_TEST MANAGEMENT_ The Context of Testing_1.2.4 Test Management Activities for Various Software Development Lifecycle Models

 

Aspect Sequential Development Model (e.g., V-Model) Iterative Development Model (e.g., Scrum)
Estimation Early, detailed estimation for each test level (test plan fixed upfront). Iterative estimation done for each sprint or iteration, adjusted continuously.
Testware Complete set including test strategy, detailed plan, test cases, schedule, and reports. Focuses on acceptance criteria, definition of done; minimal documentation, adaptive artifacts.
Roles Traditional structure: test manager leads and manages test teams. Roles are more integrated; test manager acts as facilitator or coach; team collaboration emphasized.
Tools Primarily test management tools supporting phase-based testing workflows. Emphasis on CI/CD tools and automation platforms enabling continuous testing.
Testing Approach Testing scheduled according to project phases (design, development, integration). Testing embedded within iterations, focusing on fast feedback and adaptability.
Test Automation Strategic implementation; automation may be phased per test level or phase. Automation integrated from the start; emphasis on automated regression as part of CI/CD.
Monitoring & Reporting Milestone-based reports with optional dashboards at phase ends. Continuous real-time reporting, daily status updates, live dashboards for quick insights.
Metrics Traditional metrics such as test execution rates, defect counts per phase. Agile metrics like team velocity, sprint burndown, plus traditional quality indicators.


Q1:
Your organization uses the V-Model for most projects. You are asked to provide test effort estimates for an upcoming project. What is the most appropriate estimation approach?
A) Estimate iteratively for each sprint as development progresses.
B) Provide an early, detailed estimate for each test level before development begins.
C) Provide only high-level estimates and refine them later.
D) Avoid estimation and start testing once coding completes.

Answer: B



Q2:
In a Scrum project, which of the following best describes the documentation focus for testware?
A) Extensive test cases, plans, and reports documented upfront.
B) Acceptance criteria and Definition of Done, with minimal test documentation.
C) No documentation is required due to Agile principles.
D) Only defect reports and test logs are maintained.

Answer: B


Q3:
As a Test Manager in a Scrum project, what is your primary role?
A) Dictate all testing activities and decisions.
B) Act as a facilitator and coach to support the integrated team.
C) Manage all defect reports centrally.
D) Control the test schedule strictly according to phases.

Answer: B

Q4:
A Scrum team is planning their iteration. How should the test estimation be approached?
A) Provide a fixed estimate for all testing activities upfront.
B) Estimate test effort as part of the sprint planning, adjusting each iteration.
C) Do not estimate testing separately; rely on developer estimates only.
D) Wait until the end of the sprint to measure testing effort.

Answer: B


Q5:
Which tool type is most critical in supporting test activities in a continuous integration/continuous delivery (CI/CD) Agile environment?
A) Phase-based test management tools.
B) Defect tracking tools only.
C) CI/CD automation tools with integrated testing support.
D) Static code analysis tools only.

Answer: C

Q6:
In a traditional V-Model project, what is the typical timing for automation test implementation?
A) Automation is built-in from the start alongside coding.
B) Automated testing is planned strategically and can be implemented at various test phases.
C) Automation is not used in sequential models.
D) Automation happens only after the system test phase.

Answer: B

Q7:
What reporting style is typical in an Agile iterative model?
A) Milestone-based reports generated after phases.
B) Real-time dashboards and daily status updates.
C) Weekly detailed test execution reports only.
D) No reporting is needed in Agile.

Answer: B


Q8. (Agile vs Traditional – Estimation Focus)

You are a Test Manager overseeing a large financial application developed using Scrum. During the sprint planning meeting, a developer estimates 10 story points for a user story. The product owner asks you how testing should be estimated.
What is the best way to handle test estimation in this context?

A) Provide a fixed estimate for all testing activities for the project upfront.
B) Estimate test effort per user story during the planning session, aligned with iteration planning.
C) Postpone estimation until the end of the sprint based on actual test execution effort.
D) Use historical testing data from the V-model to predict effort.

Correct Answer: B


Q9. (Tools in Different Models)

Your organization is transitioning from a V-Model to an Agile development approach. During a tool audit, the management asks you to identify which tools are essential for the new Agile workflow.
Which type of tool is most aligned with the Agile methodology?

A) Static analysis tools focused on architectural reviews.
B) Test management tools integrated with CI/CD pipelines.
C) Phase-gated defect tracking tools.
D) Document-centric tools for traceability and compliance.

Correct Answer: B 


Q10. (Monitoring & Reporting Differences)

A project in your organization uses the V-Model. The QA Director wants to compare your reporting style with another team working in Agile.
Which of the following best describes how test reporting differs between these two models?

A) Agile uses milestone-based reports; V-Model uses continuous dashboards.
B) Agile relies on daily status updates and real-time dashboards; V-Model prefers milestone-based reports.
C) Both models require the same report structure and timelines.
D) Reporting frequency is the same, only terminology differs.

Correct Answer: B


Q11. (Roles & Responsibilities)

You’ve joined a Scrum team as a test manager. During the initial weeks, you notice no clear test management role.
How should you interpret your role in this Agile context?

A) Take full ownership of test planning, execution, and reporting for the entire team.
B) Become the central decision-maker and assign testing tasks to team members.
C) Act as a facilitator/coach, supporting team-wide quality efforts and test practices.
D) Report only to the project manager without interacting with the Scrum team.

Correct Answer: C 


Q12. (Testware Focus)

A client working with a sequential model asks for full documentation of all test artifacts. Later, they plan to move toward Agile.
What should you tell them about how testware differs in Agile?

A) Agile testware is exhaustive and includes test strategy, test plans, and detailed test cases.
B) Agile testware focuses on the Definition of Done and acceptance criteria, with minimal overhead.
C) Agile avoids all documentation to increase speed.
D) Agile testware includes only test scripts but no planning documents.

Correct Answer: B


Q13. (Automation Planning)

In a sequential development project, you want to plan automation. However, the same team also has experience in Agile.
Which automation approach best fits the V-Model compared to Agile?

A) In V-Model, automation is done at the start of the project.
B) V-Model automation is strategic and stage-specific, while Agile integrates automation from the start.
C) Both approaches require full automation before manual testing starts.
D) V-Model avoids automation entirely.

Correct Answer: B 

No comments:

Post a Comment

Lets Start...............

Cypress

Syllabus Q & A Set -1 Q & A Set -2