Ep2.0 Final Assessment For Managers
-
What does the "S" in "SE Team" denote?
-
Solutions
-
Sustenance
-
Service
-
Sustaining
-
The EP2.0 Final Assessment for Managers evaluates knowledge in sustaining engineering with a focus on methodologies like Kanban, tool usage in IBOP\/Pivotal and TFS, and understanding of specific acronyms like REA. Essential for engineering managers to ensure continuous improvement and effective defect management.
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 workflow management system that helps teams to visualize their work, limit work in progress, and focus on completing tasks before starting new ones. It allows teams to have a clear overview of the tasks at hand, prioritize them, and allocate resources accordingly. Kanban promotes continuous improvement and ensures a smooth flow of work, making it an effective methodology for sustaining engineering teams.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 capacity and demand. This means that as soon as a task is completed, a new one is pulled into the team's workflow, ensuring a continuous flow of work. This helps to optimize efficiency and avoid bottlenecks in the process.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. A change request is a formal proposal to modify a system in order to correct a defect or enhance its functionality. It is a request for a change to be made to the system, usually submitted by a user or tester who has identified a problem or issue. Therefore, in this context, a change request is the entity used to represent a 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
The correct answer is "Bug". In TFS (Team Foundation Server), a bug work item is used to represent a defect. This work item is specifically designed to track and manage defects in software development projects. It allows teams to capture and prioritize bugs, assign them to team members, track their status, and monitor their resolution progress. Using the bug work item in TFS helps ensure that defects are properly documented, addressed, 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
The acronym REA stands for Requests for Engineering Assistance and Request for Engineering Assistance. This means that both options are correct and can be used interchangeably to refer to the same thing.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 helps in assessing the effectiveness of an SE team by tracking the number of defects resolved and the overall progress made. Secondly, it aids in determining how much work should be done each week by analyzing the backlog and setting realistic goals. Lastly, it allows evaluating the work remaining, which helps in prioritizing tasks and allocating resources effectively. Therefore, all of the given options are valid 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. This means that when tracking software defects in TFS, enhancements are not considered as bugs and are not included in the backlog specifically for defects. Instead, enhancements are typically tracked separately in a different backlog or prioritization system, as they represent improvements or new features rather than actual defects or issues in the software.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 then reviewed by the Portfolio Planning Team and assigned to a release. The details of these features are captured in the Doc plan. The SCRUM team also reviews 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 given answer is "Created by the Portfolio Project Manager." This statement is false because BRDs (Business Requirements Documents) are not created by the Portfolio Project Manager. BRDs are typically created by business analysts or product managers who work closely with stakeholders to gather and document the requirements for a project. The BRD assists in feature development throughout the project, includes the position of competitors, and may have one or many MFs (Mandatory Features) associated with it.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 or value within a specific marketable feature. This allows for effective planning and development of the product or system.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 because it is a low-level work item that is typically focused on the technical aspects of a project rather than the user experience. Tasks are usually more granular and specific than user stories, which are typically used to capture user requirements and needs. Therefore, the statement that a task is user-focused is false.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 assignment or activity that needs to be completed. In this case, updating a user manual requires a series of tasks such as reviewing the existing content, making necessary changes, and ensuring the document is up to date. Tracking these tasks helps the Documentation member keep a record of the progress and ensures that all the necessary updates are made to the 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 represent interactions between users and a system, outlining the steps involved in achieving a specific goal. They help to identify and define system requirements, functionalities, and user interactions, ensuring that the system meets the needs of the users. Use cases are important in the development process as they provide a clear understanding of how the system should function and how users will interact with it.Rate this question:
-
- 15.
Which of the following are (is) NOT stack ranked?
-
Marketable Feature
-
BRD
-
Use Case
-
Task
Correct Answer
A. BRDExplanation
The Business Requirements Document (BRD) is not stack ranked because it is a document that outlines the business requirements for a project or product. Stack ranking is a process used to prioritize and rank items based on their importance or value. Marketable Feature, Use Case, and Task are all items that can be prioritized and ranked based on their value or importance, but a BRD is not an item that can be stack ranked in the same way.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 at the top. In this case, the item with the highest priority is indicated by the number 0, as it is at the top of the stack.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
A marketable feature should be delivered in one release because a release typically represents a complete and stable version of a product that can be made available to customers. Releasing a marketable feature in a single release ensures that it is fully developed, tested, and ready for use by customers. It also allows for better planning and coordination of resources and timelines, as the feature can be bundled with other related updates and improvements in the release. Delivering a marketable feature across multiple sprints or quarters may lead to delays, confusion, and a fragmented user experience.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 helps in achieving clearer objectives. When tasks are broken down into smaller, manageable chunks, it becomes easier to understand what needs to be done and how to achieve it. This also leads to less confusion as team members have a clear understanding of their responsibilities and can work towards completing their tasks more efficiently. Additionally, shorter duration tasks allow for more accurate estimates as it is easier to estimate the time and effort required for smaller tasks compared to larger ones.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, tasks that are not closed and/or have remaining hours must be updated. This is because these tasks are still in progress and need to be tracked and managed accordingly. By updating these tasks, the team can have a clear understanding of their status and make necessary adjustments for the next sprint or project planning.Rate this question:
-
- 20.
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), every team has a home page. This means that each team within an organization will have its own dedicated home page in TFS. Therefore, the correct answer is "All teams, one for each team."Rate this question:
-
- 21.
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 various types of information. It includes the sprint burndown for Scrum teams, which provides a visual representation of the team's progress in completing tasks during the sprint. It also displays metrics relevant to the team, which could be key performance indicators or other data that helps track the team's performance. Additionally, the Home Page provides information about builds, which could be updates on the status of software builds or deployments. Overall, the Home Page serves as a centralized hub for important information related to the team's progress and performance.Rate this question:
-
- 22.
How often should you enter time on tasks?
-
At least once per day and whenever a task is completed.
-
All the time.
-
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. By entering time regularly, it becomes easier to analyze productivity, allocate resources, and evaluate project progress. Additionally, entering time whenever a task is completed ensures that the time spent on each task is accurately recorded and prevents any potential delays or errors in tracking. This approach allows for efficient time management and helps in making informed decisions based on accurate time data.Rate this question:
-
- 23.
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 is to add a new task. This allows you to allocate your time and stay organized. By adding a new task, you can ensure that your time is accounted for and that you have a clear plan for what needs to be done. This approach helps to maintain productivity and prevents any time from being wasted.Rate this question:
-
- 24.
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 field for Remaining indicates the amount of work left to be done on the task. The field for State indicates the current status or progress of the task. The field for Completed indicates whether the task has been finished or not. By setting these fields, you can effectively track and manage the progress of the task and ensure that it is completed in a timely manner.Rate this question:
-
- 25.
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 clarifying accountability and ensures that the task is assigned to the right person. Additionally, setting the "State" field is crucial as it allows tracking the progress of the task and provides visibility into whether it is in progress, completed, or on hold. By setting these two fields, the team can effectively manage and monitor the task throughout its lifecycle.Rate this question:
-
- 26.
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, it is important to create a new task for your work. This ensures that both team members can track their individual progress and time spent on the task separately. By creating a new task, it avoids confusion and allows for better organization and accountability within the team.Rate this question:
-
- 27.
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 code for software or applications. Code review involves examining the code written by oneself or others to ensure it meets quality standards and best practices. Unit testing involves testing individual components or units of code to ensure they function correctly. These activities are all part of the development process and are essential for creating high-quality software.Rate this question:
-
- 28.
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 tests to ensure the quality of a product. Acceptance tests are performed to verify if the product meets the specified requirements. Use case test cycle involves testing the product's functionality based on different use cases. Integration tests are conducted to check the interaction between various components of the product. Therefore, a QA member is responsible for conducting acceptance tests, use case test cycle, and integration tests to ensure the quality of the product.Rate this question:
-
- 29.
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 primary responsibility of a Scrum Master is to facilitate the Scrum process and ensure that the Scrum team is following the principles and practices of Scrum. The Scrum Master is responsible for removing any obstacles or impediments that may hinder the team's progress. The quality of a release is a collective responsibility of the entire Scrum team, including the product owner, development team, and stakeholders.Rate this question:
-
- 30.
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 decision-making authority within an organization. As leaders, executives are responsible for setting strategic goals and objectives, which includes determining the priorities of the products or services the company will offer. They also have the authority to allocate financial resources and determine the budget for these products. This responsibility ensures that the company's resources are effectively utilized and aligned with the overall business strategy.Rate this question:
-
- 31.
Documentation writers are responsible for documenting the requirements as use cases.
-
True
-
False
Correct Answer
A. FalseExplanation
Documentation writers are responsible for documenting the requirements, but they are not specifically responsible for documenting them as use cases. Use cases are a specific technique used to capture and describe functional requirements, and while documentation writers may use use cases as part of their documentation process, it is not their sole responsibility to document requirements in this format. Therefore, the correct answer is false.Rate this question:
-
- 32.
System analysts prioritize marketable features, write user manuals, and regress reproducible bugs.
-
True
-
False
Correct Answer
A. FalseExplanation
The statement is false because system analysts are responsible for analyzing and designing computer systems to meet the needs of users, not prioritizing marketable features. They also document system requirements, create technical specifications, and work with developers to implement the system. While they may assist in writing user manuals and identifying and fixing bugs, it is not their primary role.Rate this question:
-
- 33.
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 defining and driving the product strategy and vision. They are expected to create a Business Requirements Document (BRD) which outlines the functional and non-functional requirements of the product. Additionally, they are also expected to deliver marketable features, which are the key functionalities that add value to the product and attract customers. Therefore, both BRD and marketable features are artifacts that are expected from a Product Manager.Rate this question:
-
- 34.
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 correct answer is the SCRUM master. The SCRUM master is responsible for facilitating the daily updates of the SCRUM team. They ensure that the team members are following the SCRUM framework and help remove any obstacles or impediments that may hinder the team's progress. The SCRUM master also helps to enforce the daily SCRUM meetings and ensures that the team is working together efficiently and effectively towards their goals.Rate this question:
-
- 35.
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. Facilitating sprint planning involves guiding the team in determining the goals and tasks for the upcoming sprint. Providing weekly plan updates involves communicating the progress and status of the project to stakeholders. These responsibilities are important for the SCRUM master to ensure effective teamwork, continuous improvement, and transparency in the project.Rate this question:
-
- 36.
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 time when the team decides which use cases will be included in the upcoming sprint and how they will be implemented. Similarly, in the release planning phase, the SA also discusses the use cases with the team to determine the scope and timeline for the release. Therefore, both sprint planning and release planning phases involve discussions and considerations related to use cases.Rate this question:
-
- 37.
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 that allows the team to reflect on the completed sprint and identify areas for improvement. During this phase, the team discusses what went well, what didn't go well, and what actions can be taken to improve the upcoming sprint. It is a crucial part of the SCRUM framework as it promotes continuous improvement and helps the team to deliver better results in each sprint.Rate this question:
-
- 38.
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, it is important to ensure that tasks are created and estimated. This is necessary to break down the user stories into smaller, manageable tasks that can be assigned to the development team. By estimating the tasks, the team can have a better understanding of the effort required for each task and plan the sprint accordingly. This helps in setting realistic goals and ensuring that the team can complete the planned work within the sprint timeframe.Rate this question:
-
- 39.
At Aptean, every product goes through both validation and beta phases.
-
True
-
False
Correct Answer
A. FalseExplanation
At Aptean, not every product goes through both validation and beta phases.Rate this question:
-
- 40.
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. It helps the team to visualize and track the remaining work. Additionally, the SA (Scrum Master or Systems Analyst) is responsible for elaborating use cases for the upcoming sprint. This involves analyzing and refining the user stories and requirements to ensure they are well-defined and ready for implementation.Rate this question:
-
- 41.
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. This is because the product manager has a deep understanding of the product requirements and can provide valuable insights and explanations to the development team. By being available during this phase, the product manager ensures that the team has a clear understanding of the goals and objectives for the sprint, leading to more effective planning and execution of tasks.Rate this question:
-
- 42.
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 limited to being started only when the code is frozen and the release is feature complete. It is a type of testing that is performed throughout the software development lifecycle, including during the development phase. Regression testing aims to ensure that previously developed and tested software still performs correctly after changes and modifications have been made to the code. Therefore, it is not necessary for the code to be frozen or the release to be feature complete for regression testing to be initiated.Rate this question:
-
- 43.
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 when a release of a product or service is completed, the escrow activity takes place. Escrow refers to the process of depositing something of value, such as source code or documentation, with a third party for safekeeping. In the context of software development, escrow is often used to ensure that the source code of a software product is accessible and can be used by the client or customer in case the development company goes out of business or fails to provide ongoing support. Therefore, the escrow activity is typically conducted at the end of a release to ensure the safekeeping and accessibility of the source code.Rate this question:
-
- 44.
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 a team can be seen on the TFS team home page. This is a feature in TFS (Team Foundation Server) that provides a visual representation of the team's progress in completing work during a sprint. It helps the team track the remaining work and identify any potential issues or delays. By regularly checking the sprint burndown on the TFS team home page, team members can stay informed about the progress and make necessary adjustments to meet their sprint goals.Rate this question:
-
- 45.
Which teams track their progress using a burndown chart?
-
It varies depending on management decision
-
All teams
-
Teams which follow Scrum and work in sprints
Correct Answer
A. Teams which follow Scrum and work in sprintsExplanation
Teams which follow Scrum and work in sprints track their progress using a burndown chart. In Scrum, work is divided into short iterations called sprints, and the progress of the team is visualized using a burndown chart. This chart shows the amount of work remaining over time, allowing the team to track their progress and make adjustments as needed. Other teams may use different methods to track their progress, but specifically in the context of Scrum and sprint-based work, the burndown chart is commonly used.Rate this question:
-
- 46.
What should you avoid during a sprint?
-
Burndown is under the ideal line
-
Remaining work is flat for a long period of time
-
Burndown is over the ideal line
-
Remaining work goes up and down in spikes
-
The sprint is nearly finished and there is a lot of work remaining
Correct Answer(s)
A. Remaining work is flat for a long period of time
A. Remaining work goes up and down in spikes
A. The sprint is nearly finished and there is a lot of work remainingExplanation
During a sprint, it is important to avoid situations where the remaining work is flat for a long period of time or goes up and down in spikes. This indicates a lack of progress or inconsistent progress, which can hinder the team's ability to meet their sprint goals. Additionally, if the sprint is nearly finished and there is still a lot of work remaining, it suggests that the team may not be able to complete the planned work within the sprint timebox.Rate this question:
-
- 47.
Who is responsible for progress on the burndown?
-
The Scrum Master or Team Leader
-
The Systems Analyst
-
The team
-
No answer
Correct Answer
A. The teamExplanation
The team is responsible for progress on the burndown. In Scrum, the team collectively takes ownership of the project and is accountable for delivering the work. The team is responsible for updating the burndown chart daily, tracking the progress, and adjusting their work accordingly to meet the sprint goal. The Scrum Master or Team Leader may facilitate the process and support the team, but the ultimate responsibility lies with the team members themselves.Rate this question:
-
- 48.
Why are we asking all products to use this standard TFS structure?
-
Because this is the way Microsoft recommends.
-
Because the consolidated reporting we need, relies on knowing what is stored where in TFS.
-
Because management told us to.
-
No answer
Correct Answer
A. Because the consolidated reporting we need, relies on knowing what is stored where in TFS.Explanation
We are asking all products to use this standard TFS structure because the consolidated reporting we need relies on knowing what is stored where in TFS. By having a standardized structure, it becomes easier to track and analyze data stored in TFS, which is crucial for generating accurate and meaningful reports.Rate this question:
-
- 49.
What is the maximum number of levels allowed in the iteration tree structure?
-
6
-
5
-
There is no maximum
Correct Answer
A. 6Explanation
The maximum number of levels allowed in the iteration tree structure is 6.Rate this question:
-
Quiz Review Timeline (Updated): Mar 20, 2023 +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
-
Current Version
-
Mar 20, 2023Quiz Edited by
ProProfs Editorial Team -
Aug 19, 2014Quiz Created by
Apteantraining2
Back to top