Engineering Process Certification Assessment
-
What does the "S" in "SE Team" denote?
-
Solutions
-
Sustenance
-
Service
-
Sustaining
-
This assessment is intended to assess your knowledge on Engineering Processes. Prior to taking this assessment, please be sure you have full comprehension of the Engineering Process Documents on the Process Guidance library. The Process Guidance document can be found here.
This assessment is mandatory for all product development team members.
Question(s) may have one or more correct answers. Choose See moreall the options for those questions.
Quiz Preview
- 2.
What is the typical methodology used in our Sustaining Engineering teams?
-
Agile
-
Sustenance
-
Scrum
-
Kanban
Correct Answer
A. KanbanExplanation
The typical methodology used in our Sustaining Engineering teams is Kanban. Kanban is a visual project management system that helps teams to visualize their work, limit work in progress, and improve overall efficiency. It allows teams to track and prioritize tasks, and ensures that work flows smoothly through the different stages of the process. Kanban is known for its flexibility and adaptability, making it a popular choice for teams working on sustaining engineering projects.Rate this question:
-
- 3.
Which of the following is a characteristic of a Kanban team?
-
Has a continuous inflow of work.
-
Inflow is accomplished using a "push" approach.
-
Holds a weekly standup meeting.
-
Is used in Aptean SE only to fix defects.
Correct Answer
A. Has a continuous inflow of work.Explanation
A characteristic of a Kanban team is having a continuous inflow of work. Kanban is a lean methodology that focuses on visualizing and managing work in progress. It emphasizes a "pull" approach, where work is pulled into the system based on the team's capacity and the availability of resources. This ensures a steady flow of work and prevents overloading the team. Holding a weekly standup meeting is not specifically a characteristic of a Kanban team, as it is a common practice in many agile methodologies. The statement about Aptean SE is unrelated to the characteristics of a Kanban team.Rate this question:
-
- 4.
In IBOP/Pivotal, what type of entity is used to represent a defect?
-
Defect
-
Bug
-
Change Request
-
REA
Correct Answer
A. Change RequestExplanation
In IBOP/Pivotal, a change request is used to represent a defect. This suggests that when a defect is identified, it is categorized as a change request rather than a separate entity like a defect or bug. This implies that the process for addressing and resolving defects in IBOP/Pivotal involves submitting a change request to make the necessary changes to fix the defect.Rate this question:
-
- 5.
In TFS, what type of work item is used to represent a defect?
-
Defect
-
Bug
-
Change Request
-
REA
Correct Answer
A. BugExplanation
In TFS, the type of work item used to represent a defect is called a "Bug". This work item is specifically designed to track and manage software defects, allowing teams to effectively identify, prioritize, and resolve any issues or flaws in the software development process. By using the "Bug" work item type, teams can ensure that defects are properly documented, assigned, and resolved in a systematic manner.Rate this question:
-
- 6.
What does the acronym REA stand for ? Please fill answer below.
Correct Answer
Requests for Engineering Assistance
Request for Engineering AssistanceExplanation
REA stands for Requests for Engineering Assistance and Request for Engineering Assistance. This acronym is commonly used in the engineering field to refer to the process of seeking help or support in engineering-related matters. The use of both variations of the acronym suggests that either form can be used interchangeably to convey the same meaning.Rate this question:
- 7.
Which of the following is not a benefit of monitoring the Defect Backlog?
-
Assessing the effectiveness of an SE team.
-
Determining how much work to do each week.
-
Evaluating the work remaining.
-
All of the above are benefits.
Correct Answer
A. All of the above are benefits.Explanation
Monitoring the Defect Backlog provides several benefits. Firstly, it allows for assessing the effectiveness of the SE team by tracking the number of defects resolved and the rate at which they are resolved. Secondly, it helps in determining how much work to do each week by identifying the number of defects that need to be addressed. Lastly, it enables evaluating the work remaining by keeping track of the number of open defects. Therefore, all of the given options are benefits of monitoring the Defect Backlog.Rate this question:
-
- 8.
Which of the following is a bug type in TFS that is not counted in the SE Defect Backlog?
-
Compatibility
-
Documentation
-
Enhancement
-
Legacy
Correct Answer
A. EnhancementExplanation
Enhancement is a bug type in TFS that is not counted in the SE Defect Backlog because it refers to the addition of new features or improvements to existing functionality. While defects and bugs are typically focused on fixing issues or problems, enhancements are about enhancing the product's capabilities. Therefore, enhancements are categorized separately and are not considered as part of the defect backlog.Rate this question:
-
- 9.
Which of the following statements about Marketable Features are (is) True:
-
Most granular unit of work planned for a team
-
Based on feature ideas from Customers, Field, Industry trends
-
Reviewed by Portfolio Planning Team and are then assigned to a release
-
Details are captured in the Doc plan
-
Reviewed by SCRUM team during Pre-Planning
Correct Answer(s)
A. Based on feature ideas from Customers, Field, Industry trends
A. Reviewed by Portfolio Planning Team and are then assigned to a releaseExplanation
Marketable Features are the most granular unit of work planned for a team. They are based on feature ideas from Customers, Field, and Industry trends. These features are reviewed by the Portfolio Planning Team and are then assigned to a release. The details of these features are captured in the Doc plan. However, there is no mention of the SCRUM team reviewing them during Pre-Planning.Rate this question:
-
- 10.
One of these statements about BRDs is False. Identify it:
-
Assists feature development throughout the project
-
Includes position of competitors
-
May have one or many MFs associated with it
-
Created by the Portfolio Project Manager
Correct Answer
A. Created by the Portfolio Project ManagerExplanation
The statement "Created by the Portfolio Project Manager" is false because BRDs (Business Requirements Documents) are typically created by business analysts or product managers, not by portfolio project managers. BRDs assist in feature development throughout the project, include the position of competitors, and may have one or many MFs (Market Factors) associated with them.Rate this question:
-
- 11.
Which of the following statements about Use Cases are (is) True:
-
Onus of creating and testing the Use Case lies with the QA member
-
Describes the most frequently occurring outcome of an attempt to accomplish a particular goal
-
Estimated using confidence level
-
Should be stack ranked against one another, within the same marketable feature
Correct Answer
A. Should be stack ranked against one another, within the same marketable featureExplanation
Use Cases should be stack ranked against one another, within the same marketable feature. This means that when prioritizing Use Cases, they should be ranked in order of importance and value within a specific feature that is marketable to customers. By stack ranking the Use Cases, it helps to determine which ones should be implemented first based on their significance and impact on the product. This allows for efficient planning and development of features that align with the overall goals and objectives of the product.Rate this question:
-
- 12.
Which of the following are (is) False about a Task ?
-
Lowest level work item
-
User-focused
-
Estimated during sprint planning
-
Tracked using a burndown chart
-
Time remaining and completed work fields are filled in daily
Correct Answer
A. User-focusedExplanation
A task is not user-focused. Unlike user stories, which are focused on the end user's needs and requirements, a task is a more detailed and specific piece of work that needs to be completed to accomplish a user story. It is typically a lower-level work item that is part of the implementation process and is not directly related to the user's perspective.Rate this question:
-
- 13.
In which of the following does a Documentation member track work done to update a user manual?
-
Marketable Feature
-
BRD
-
Use Case
-
Task
Correct Answer
A. TaskExplanation
A Documentation member tracks work done to update a user manual in a Task. A Task is a specific activity or assignment that needs to be completed as part of a larger project. In this case, updating a user manual would be a specific task assigned to the Documentation member. The other options, Marketable Feature, BRD (Business Requirements Document), and Use Case, do not specifically refer to tracking work done to update a user manual.Rate this question:
-
- 14.
The System Analyst is primarily responsible for:
-
Marketable Feature
-
BRD
-
Use Case
-
Task
Correct Answer
A. Use CaseExplanation
The System Analyst is primarily responsible for creating use cases. Use cases are a way to capture and describe the interactions between users and a system. They outline the steps and actions that a user takes to achieve a specific goal. Use cases help to define the functionality of a system and ensure that it meets the needs and requirements of the users. They are an important tool in the analysis and design phase of software development.Rate this question:
-
- 15.
Which of the following are (is) NOT stack ranked?
-
Marketable Feature
-
BRD
-
Use Case
-
Task
Correct Answer
A. BRDExplanation
Stack ranking is a process of evaluating and ranking items based on their importance or priority. In this question, the options are "Marketable Feature," "BRD," "Use Case," and "Task." The correct answer is "BRD" because a BRD (Business Requirements Document) is not typically stack ranked. A BRD is a document that outlines the business requirements for a project or product, and it is used as a reference for the development process. However, it is not directly ranked or prioritized like marketable features, use cases, or tasks.Rate this question:
-
- 16.
Which stack rank indicates the item with the highest priority?
-
100
-
Greatest number
-
0
-
1
Correct Answer
A. 0Explanation
The stack rank indicates the priority of the items, with the highest priority being indicated by the number 0.Rate this question:
-
- 17.
A marketable feature should be delivered:
-
In 1 release
-
In 1 quarter
-
In 1 sprint
-
Across 4 sprints
Correct Answer
A. In 1 releaseExplanation
The correct answer is "In 1 release." This means that a marketable feature should be delivered within a single release of a product or software. A release typically refers to a version or update that is made available to users. By delivering the feature in one release, it ensures that it is complete and ready for use by customers or clients. This approach allows for better planning and management of development efforts, as well as providing a clear timeline for when the feature will be available to users.Rate this question:
-
- 18.
Why should tasks be of a lesser duration?
-
Clearer objectives
-
Perfect burndown
-
Less confusion
-
More accurate estimates
-
Assigned to one person
Correct Answer(s)
A. Clearer objectives
A. Less confusion
A. More accurate estimatesExplanation
Tasks should be of a lesser duration because it allows for clearer objectives. When tasks are broken down into smaller, manageable chunks, it becomes easier to define what needs to be accomplished and how to measure success. Additionally, shorter tasks lead to less confusion as team members have a clear understanding of what needs to be done. It also enables more accurate estimates as it is easier to estimate the time and effort required for shorter tasks. Assigning tasks to one person also helps in ensuring accountability and clarity in responsibilities.Rate this question:
-
- 19.
Which tasks must be updated at the end of the sprint?
-
Tasks that have original estimates
-
Tasks which are not closed and/or tasks with remaining hours.
-
None of them, the tasks can be left alone
Correct Answer
A. Tasks which are not closed and/or tasks with remaining hours.Explanation
At the end of the sprint, it is important to update tasks that are not closed and/or tasks with remaining hours. This is because these tasks may not have been completed within the sprint and need to be carried forward or reassigned to the next sprint. By updating these tasks, the team can have an accurate understanding of the progress made and plan accordingly for the next sprint.Rate this question:
-
- 20.
I have a Use Case which is not finished at the end of the sprint. What should I do?
-
Close it and raise another
-
Move it to the next sprint by changing the iteration path
-
Leave it alone
Correct Answer
A. Move it to the next sprint by changing the iteration pathExplanation
If a use case is not finished at the end of the sprint, the best course of action would be to move it to the next sprint by changing the iteration path. This allows the unfinished use case to be carried forward and prioritized in the next sprint, ensuring that it is completed in a timely manner. Closing it and raising another use case would create unnecessary duplication and confusion, while leaving it alone would result in the use case being neglected and potentially forgotten.Rate this question:
-
- 21.
Who has a Home Page in TFS?
-
All teams, one for each team
-
Scrum teams, one for each team
-
One for each product
Correct Answer
A. All teams, one for each teamExplanation
In TFS (Team Foundation Server), each team has a Home Page. This means that all teams in TFS have their own individual Home Page. This allows each team to have a dedicated space where they can access and manage their project-related information, such as tasks, backlog, and progress. Having separate Home Pages for each team helps in organizing and streamlining the work within TFS, ensuring that each team has a centralized location to collaborate and track their specific project requirements and goals.Rate this question:
-
- 22.
What information is shown on the Home Page ?
-
Sprint burndown for Scrum teams
-
Metrics relevant for the team
-
Information about Engineering Processes
-
Information about builds
-
Project risk register
Correct Answer(s)
A. Sprint burndown for Scrum teams
A. Metrics relevant for the team
A. Information about buildsExplanation
The Home Page shows the sprint burndown for Scrum teams, metrics relevant for the team, and information about builds. These pieces of information are important for the team to track their progress, measure their performance, and stay updated on the status of their builds. The sprint burndown helps visualize the team's progress towards completing their tasks, the metrics provide insights into their performance, and the information about builds ensures that the team is aware of any updates or issues related to their software development process.Rate this question:
-
- 23.
What can you find under "Approved Process Guidance Documents"?
-
General information about Scrum and Kanban development practices.
-
Dashboards and metrics for Aptean development teams.
-
Documents which tell you about the Aptean Engineering Processes and what you should do day to day.
Correct Answer
A. Documents which tell you about the Aptean Engineering Processes and what you should do day to day.Explanation
Under "Approved Process Guidance Documents," you can find documents that provide information about the Aptean Engineering Processes and guide you on what you should do on a daily basis. These documents likely outline the standard procedures, best practices, and recommended actions to follow in order to ensure efficient and effective engineering processes within the organization.Rate this question:
-
- 24.
How often should you enter time on tasks?
-
All the time.
-
At least once per day and whenever a task is completed.
-
Only when you complete a task.
Correct Answer
A. At least once per day and whenever a task is completed.Explanation
Entering time on tasks at least once per day and whenever a task is completed ensures accurate tracking and documentation of the time spent on each task. This practice allows for better project management, as it provides real-time updates on task progress and helps identify any potential delays or bottlenecks. Additionally, entering time regularly ensures that the time spent on each task is recorded promptly and accurately, reducing the chances of forgetting or misrepresenting the actual effort put into the task.Rate this question:
-
- 25.
What do you do if you have no task to book your time against?
-
Add a new task.
-
Go on to something else.
-
Add your time to the closest task you can find.
Correct Answer
A. Add a new task.Explanation
If you have no task to book your time against, the best option would be to add a new task. This allows you to allocate your time and ensure that you are productive. By adding a new task, you can effectively manage your time and prioritize your workload. This also helps in maintaining a structured schedule and avoiding any wasted time.Rate this question:
-
- 26.
Which fields should you set when completing a task?
-
Assigned To
-
Remaining
-
State
-
Activity
-
Completed
Correct Answer(s)
A. Remaining
A. State
A. CompletedExplanation
When completing a task, you should set the fields for Remaining, State, and Completed. The "Remaining" field indicates the amount of work left to be done on the task. The "State" field represents the current status or progress of the task. The "Completed" field indicates whether the task has been finished or not. By setting these fields, you can track the progress and completion of the task accurately.Rate this question:
-
- 27.
Which fields should you set when starting work on a task?
-
Assigned To
-
Completed
-
Remaining
-
State
-
Activity
Correct Answer(s)
A. Assigned To
A. StateExplanation
When starting work on a task, it is important to set the "Assigned To" field to indicate who is responsible for completing the task. This helps in ensuring clear accountability and avoiding confusion. Additionally, setting the "State" field is crucial as it allows tracking the progress of the task and providing visibility to others involved. It helps in identifying whether the task is in progress, completed, or pending. The other options mentioned, such as "Completed," "Remaining," and "Activity," may be relevant but are not essential for initially starting work on a task.Rate this question:
-
- 28.
What should you do when you are working on a task with another team member at the same time?
-
Let the other person continue booking their time.
-
Assign the task to yourself and start booking your time.
-
Create a new task for your work.
Correct Answer
A. Create a new task for your work.Explanation
When working on a task with another team member at the same time, creating a new task for your work is the appropriate action to take. This allows both team members to track their individual progress and time spent on the task separately. By creating a new task, each team member can accurately record their own contributions and avoid any confusion or overlap in time tracking.Rate this question:
-
- 29.
Which of the following activities is a Developer responsible for?
-
Architecture
-
Coding
-
Code review
-
Unit testing
-
Release notes
-
Acceptance Criteria
Correct Answer(s)
A. Coding
A. Code review
A. Unit testingExplanation
A developer is responsible for coding, code review, and unit testing. Coding involves writing the actual program or software using programming languages. Code review is the process of examining the written code to ensure it meets quality standards and follows best practices. Unit testing involves testing individual components or units of code to ensure they function correctly.Rate this question:
-
- 30.
Which of the tasks is the responsibility of a QA member?
-
Release Plan
-
Acceptance Tests
-
Sprint retrospective
-
Use case Test Cycle
-
Integration tests
-
Sprint goals
Correct Answer(s)
A. Acceptance Tests
A. Use case Test Cycle
A. Integration testsExplanation
A QA member is responsible for conducting various types of tests to ensure the quality of the software. Acceptance tests are performed to validate if the software meets the requirements and expectations of the stakeholders. Use case test cycle involves testing the software's functionality based on different use cases. Integration tests are conducted to check the interaction and compatibility of various components of the software. Therefore, the responsibility of a QA member includes performing acceptance tests, use case test cycle, and integration tests.Rate this question:
-
- 31.
A Scrum Master is responsible for the quality of a release.
-
True
-
False
Correct Answer
A. FalseExplanation
A Scrum Master is not directly responsible for the quality of a release. The Scrum Master's main role is to facilitate the Scrum process and ensure that the team is following the Agile principles and practices. The responsibility for the quality of a release lies with the entire Scrum team, including the Product Owner, Development Team, and stakeholders. The Scrum Master may support the team in identifying and addressing quality issues, but they do not have sole responsibility for it.Rate this question:
-
- 32.
Executives are responsible for the Product priorities and budget.
-
True
-
False
Correct Answer
A. TrueExplanation
Executives are responsible for the product priorities and budget because they hold the highest level of authority and decision-making power within an organization. As leaders, executives are responsible for setting the overall strategic direction of the company, which includes determining the priorities for product development and allocating the necessary budget resources. They are accountable for ensuring that the product aligns with the company's goals and objectives and that sufficient funding is allocated to support its development and success. Therefore, it is true that executives hold the responsibility for product priorities and budget.Rate this question:
-
- 33.
Documentation writers are responsible for documenting the requirements as use cases.
-
True
-
False
Correct Answer
A. FalseExplanation
Documentation writers are responsible for documenting various aspects of a project, including requirements, but they are not specifically responsible for documenting requirements as use cases. Use cases are a specific technique used in requirements gathering and analysis, and can be created by business analysts or other stakeholders involved in the project. Therefore, the given statement is false.Rate this question:
-
- 34.
System analysts prioritize marketable features, write user manuals, and regress reproducible bugs.
-
True
-
False
Correct Answer
A. FalseExplanation
System analysts do not prioritize marketable features, write user manuals, or regress reproducible bugs. They are primarily responsible for analyzing and designing information systems to meet the needs of an organization. Their role involves gathering requirements, creating system specifications, and working with developers to ensure the successful implementation of the system.Rate this question:
-
- 35.
Which of the following artifacts are (is) expected from a Product Manager?
-
BRD
-
Incident
-
Task
-
Test case
-
Marketable Feature
Correct Answer(s)
A. BRD
A. Marketable FeatureExplanation
A Product Manager is responsible for various tasks related to product development and management. One of the key artifacts expected from a Product Manager is a Business Requirements Document (BRD), which outlines the business needs, goals, and requirements for the product. This document helps the team understand the scope and objectives of the product. Additionally, a Product Manager is also expected to deliver Marketable Features, which are the functionalities or characteristics of the product that can be marketed and sold to customers. These features are essential for attracting and retaining customers, and ultimately driving business growth.Rate this question:
-
- 36.
Which of the following statements are (is) True?
-
Doc managers are accountable for the doc plan
-
Product managers are responsible for the staffing plan
-
Dev managers are accountable for the release notes and contents
-
QA managers are accountable for the final regression
-
Portfolio project managers are responsible for the release schedule
Correct Answer(s)
A. Doc managers are accountable for the doc plan
A. Dev managers are accountable for the release notes and contents
A. QA managers are accountable for the final regression -
- 37.
Who would you expect to be responsible for a SCRUM team’s daily update?
-
Dev manager
-
Portfolio project manager
-
SCRUM master
-
Developer
Correct Answer
A. SCRUM masterExplanation
The SCRUM master is responsible for a SCRUM team's daily update. The SCRUM master is a facilitator and coach for the team, ensuring that the SCRUM framework is followed and that the team is able to work efficiently and effectively. They are responsible for organizing and leading daily stand-up meetings, where team members provide updates on their progress, discuss any obstacles or challenges they are facing, and collaborate on the next steps. The SCRUM master also works closely with the product owner and stakeholders to ensure that the team's work aligns with the project goals and priorities.Rate this question:
-
- 38.
Which of the following are the responsibilities of a SCRUM master?
-
Create the test plan
-
Host the sprint retrospective
-
Facilitate sprint planning
-
Prioritize the use cases
-
Provide weekly plan updates
Correct Answer(s)
A. Host the sprint retrospective
A. Facilitate sprint planning
A. Provide weekly plan updatesExplanation
The responsibilities of a SCRUM master include hosting the sprint retrospective, facilitating sprint planning, and providing weekly plan updates. The sprint retrospective is a meeting where the team reflects on the previous sprint and identifies areas for improvement. The SCRUM master plays a key role in facilitating this meeting. Similarly, the SCRUM master is responsible for facilitating sprint planning, which involves determining the work to be done in the upcoming sprint. Additionally, the SCRUM master provides weekly plan updates to keep the team informed about the progress and any changes in the plan.Rate this question:
-
- 39.
In which of the following phases are Use Cases discussed by the SA with the SCRUM team?
-
Product Approval
-
Sprint planning
-
Release planning
-
Retrospective
-
Beta
Correct Answer(s)
A. Sprint planning
A. Release planningExplanation
During the Sprint planning phase, the SA (Scrum Master) discusses the Use Cases with the SCRUM team. This is the phase where the team plans the work to be done in the upcoming sprint, and the Use Cases play a crucial role in understanding the requirements and defining the scope of the sprint. Similarly, in the Release planning phase, the SA also discusses the Use Cases with the team to plan for the overall release. Both these phases involve collaborative discussions and decision-making regarding the Use Cases, ensuring that the team has a clear understanding of the user requirements and can deliver the desired functionality.Rate this question:
-
- 40.
As a SCRUM team, which phase allows me to reflect on the sprint and action improvements for the upcoming sprint?
-
Product planning
-
Release planning
-
Sprint execution
-
Sprint retrospective
-
Validation
-
Release retrospective
Correct Answer
A. Sprint retrospectiveExplanation
The correct answer is Sprint retrospective. The sprint retrospective is a phase in SCRUM where the team reflects on the completed sprint and identifies areas for improvement. It allows the team to review what went well and what didn't, and to take actions to improve their processes and outcomes for the upcoming sprint. This phase helps the team continuously learn and adapt, leading to increased efficiency and effectiveness in future sprints.Rate this question:
-
- 41.
As a Scrum Master what do I need to ensure during a sprint planning session?
-
Tasks are created
-
Test plan is created
-
Code is reviewed
-
Tasks are estimated
-
Use cases are signed off
Correct Answer(s)
A. Tasks are created
A. Tasks are estimatedExplanation
During a sprint planning session, as a Scrum Master, you need to ensure that tasks are created and estimated. This is important because it helps the team to have a clear understanding of the work that needs to be done and how much effort is required for each task. By creating and estimating tasks, the team can effectively plan and allocate their resources and time during the sprint.Rate this question:
-
- 42.
At Aptean, every product goes through both validation and beta phases.
-
True
-
False
Correct Answer
A. FalseExplanation
The statement mentions that every product at Aptean goes through both validation and beta phases. However, the correct answer is False, which suggests that not every product at Aptean goes through both validation and beta phases.Rate this question:
-
- 43.
Which of the following statements about sprint execution are true?
-
Burndown chart reflects the progress of tasks
-
Multiple beta builds are released to the customer
-
No documentation is written during this time
-
Test cases should already be documented
-
SA elaborates use cases for the upcoming sprint
Correct Answer(s)
A. Burndown chart reflects the progress of tasks
A. SA elaborates use cases for the upcoming sprintExplanation
During sprint execution, the burndown chart is used to reflect the progress of tasks completed and remaining, allowing the team to track their progress and make necessary adjustments. The SA (Scrum Master or System Analyst) is responsible for elaborating use cases for the upcoming sprint, ensuring that the team has a clear understanding of the requirements and goals for the sprint. However, it is not stated whether multiple beta builds are released to the customer, if any documentation is written during this time, or if test cases should already be documented.Rate this question:
-
- 44.
A product manager is available to provide clarifications during a sprint planning phase.
-
True
-
False
Correct Answer
A. TrueExplanation
During the sprint planning phase, the product manager plays a crucial role in providing clarifications. They are responsible for answering any questions or concerns from the development team regarding the product requirements and goals. By being available, the product manager ensures that the team has a clear understanding of the tasks and can plan and prioritize effectively. This collaboration between the product manager and the development team helps in creating a well-defined and achievable sprint plan. Therefore, the statement "A product manager is available to provide clarifications during a sprint planning phase" is true.Rate this question:
-
- 45.
Regression testing is started only when the code is frozen and the release is feature complete.
-
True
-
False
Correct Answer
A. FalseExplanation
Regression testing is not only started when the code is frozen and the release is feature complete. Regression testing is a type of software testing that is performed to ensure that the existing functionality of the software has not been affected by any new changes or bug fixes. It can be performed at various stages of the software development lifecycle, including during development and after the release. Therefore, the statement that regression testing is only started when the code is frozen and the release is feature complete is incorrect.Rate this question:
-
- 46.
When is the escrow activity done?
-
Release exit
-
Release planning
-
Release retrospective
Correct Answer
A. Release exitExplanation
The escrow activity is done during the Release exit. This means that the escrow process, which involves the release of funds or assets held in escrow, takes place at the end of the release phase. It is a crucial step in ensuring that all contractual obligations have been met and that the release is finalized. The Release exit marks the completion of the release and signifies the transition to the next phase or project.Rate this question:
-
- 47.
Which of the following statements are (is) True ?
-
During pre-planning, Architects, System Analysts (SA), and Development, QA and Doc Managers review the BRD with the PM and provide the level of effort estimates for the MFs
-
Scrum team engages with customers for beta program
-
At the end of a sprint, SA demos Use Case implementation to the PM
-
At Aptean, SCRUM is used for continuous development
Correct Answer(s)
A. During pre-planning, Architects, System Analysts (SA), and Development, QA and Doc Managers review the BRD with the PM and provide the level of effort estimates for the MFs
A. At the end of a sprint, SA demos Use Case implementation to the PMExplanation
During pre-planning, various stakeholders including Architects, System Analysts (SA), and Development, QA and Doc Managers review the Business Requirements Document (BRD) with the Project Manager (PM) and provide effort estimates for the Minimum Features (MFs). This allows for a comprehensive understanding of the project requirements and helps in planning the development process. Additionally, at the end of a sprint, the System Analyst (SA) demonstrates the implementation of the Use Cases to the Project Manager (PM), ensuring that the developed features align with the desired functionality.Rate this question:
-
- 48.
During the Product Approval phase, the Product Manager, Portfolio Project Manager, Product Development managers meet to review and plan for the Marketable Features to be developed in the upcoming year.
-
True
-
False
Correct Answer
A. TrueExplanation
During the Product Approval phase, key stakeholders such as the Product Manager, Portfolio Project Manager, and Product Development managers come together to assess and strategize the development of Marketable Features for the upcoming year. This meeting allows them to review the proposed features, prioritize them, and plan their implementation. Therefore, the statement "True" accurately reflects the purpose and activities conducted during the Product Approval phase.Rate this question:
-
- 49.
How do you see the sprint burndown for your team?
-
On the TFS team home page
-
Using an Excel report
-
The Scrum Master will show it to you
-
No answer
Correct Answer
A. On the TFS team home pageExplanation
The sprint burndown for the team can be seen on the TFS team home page. This means that the team can access and track the progress of their sprint by simply visiting the TFS team home page. It provides a visual representation of the remaining work and helps the team to understand if they are on track to complete the sprint successfully. Using this feature, the team can monitor their progress and make any necessary adjustments to ensure timely delivery of their work.Rate this question:
-
Quiz Review Timeline (Updated): Mar 21, 2023 +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
-
Current Version
-
Mar 21, 2023Quiz Edited by
ProProfs Editorial Team -
Jul 01, 2014Quiz Created by
Apteantraining2
Back to top