ASQ Certified Software Quality Engineer CSQE Exam Questions

Answer : B

A 'Scrum of Scrums' meeting is structured most like a program review meeting. It is designed to coordinate efforts among multiple Scrum teams working on the same project. During this meeting, representatives from each team discuss their progress, impediments, and dependencies with other teams. This is akin to a program review meeting where higher-level coordination and integration of efforts are reviewed and managed.

Schwaber, K., & Sutherland, J. (2020). The Scrum Guide.

Larman, C., & Vodde, B. (2010). Practices for Scaling Lean & Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum.

Answer : C

Configuration Status Accounting (CSA) involves recording and reporting the status of configuration items throughout the lifecycle of a project. This includes:

Status of Configuration Items: Information about the current state of items, including version numbers and change histories.

Baselined Items: Items that have been formally approved and serve as a basis for further development.

Changes and Updates: Documenting any modifications made to the baselined items.

CSA ensures that all stakeholders are informed about the status and history of configuration items.

'Software Configuration Management Patterns: Effective Teamwork, Practical Integration' by Stephen P. Berczuk and Brad Appleton

IEEE Standard for Software Configuration Management Plans (IEEE Std 828)

Answer : C

Regression testing is crucial when releasing patches as it ensures that the new changes have not adversely affected the existing functionality of the software. It involves re-running previous tests on the modified software to confirm that the old functionalities still work as expected and that the new patches do not introduce new defects.

Partial releases, software rebuilds, and configuration management are important aspects of software maintenance, but regression testing directly addresses the risk of introducing new issues with patches.

'Software Testing: Principles and Practices' by Naresh Chauhan.

IEEE Standard 829-2008 for Software and System Test Documentation.

Answer : C

In a Scrum project, the responsibility for determining time estimates falls on the project team as a whole. This process occurs during the sprint planning meetings where the team collaboratively estimates the effort required for each task or user story. The Scrum Master facilitates this process, but the actual estimation is performed by the team members who will be doing the work. This collective approach ensures that estimates are realistic and based on the team's understanding and agreement.

Schwaber, K., & Sutherland, J. (2020). The Scrum Guide.

Cohn, M. (2005). Agile Estimating and Planning.

Answer : B

Management review meetings are typically held to examine aggregated performance information. These meetings focus on the overall progress, performance metrics, and strategic alignment of projects or programs. The goal is to ensure that objectives are being met, resources are used effectively, and any issues are addressed at a higher organizational level.

IEEE Std 1028-2008, which specifies various types of reviews, including management reviews.

'Software Engineering: A Practitioner's Approach' by Roger S. Pressman, which discusses management reviews in the context of software project management.

Answer : D

Graph Analysis: In the provided graphs, each graph represents the status of defects over time, divided into categories: Open, Fixed, and Tested and Closed.

Option A: Shows a large number of open and fixed defects with fewer tested and closed defects.

Option B: Indicates an increasing trend in tested and closed defects but still has a substantial number of open defects.

Option C: Shows a significant decrease in open defects and a substantial increase in tested and closed defects, indicating progress.

Option D: Depicts the fewest number of open defects, with the majority of defects tested and closed, indicating that most defects have been addressed and verified.

Conclusion: The graph in Option D, with the majority of defects tested and closed and the fewest number of open defects, suggests the product is most ready for formal release to the customer. This aligns with software quality assurance principles where minimal unresolved defects indicate readiness for release.

Answer : A

Scope Definition: In the waterfall model, the first step in release planning is to define the scope of the software. This involves understanding what the software is supposed to do, the boundaries of the project, and the major features and functionalities to be included.

Importance of Scope: Defining the scope provides a clear understanding and agreement among stakeholders about what the project will deliver, preventing scope creep and ensuring all parties are aligned.

Reference: Software Engineering Body of Knowledge (SWEBOK) and IEEE standards emphasize the importance of scope definition as an initial phase in project planning.