Ep2.0 Final Assessment For Managers
-
What is the typical methodology used in our Sustaining Engineering teams?
-
Agile
-
Sustenance
-
Scrum
-
Kanban
-
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.
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:
-
- 3.
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:
- 4.
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:
-
- 5.
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:
-
- 6.
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:
-
- 7.
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:
-
- 8.
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:
-
- 9.
By when should you create tasks for Use Cases, planned for the sprint?
-
By the end of the Sprint
-
By the end of the Sprint planning session
-
By the end of DHQA
-
By the end of the mid-sprint review
Correct Answer
A. By the end of the Sprint planning sessionExplanation
Tasks for Use Cases should be created by the end of the Sprint planning session. This is because the Sprint planning session is where the team determines which Use Cases will be included in the upcoming sprint. Creating tasks for these Use Cases at the end of the session ensures that the team has a clear plan and understanding of what needs to be done for each Use Case before the sprint begins.Rate this question:
-
- 10.
A Marketable Feature must be delivered in:
-
One sprint
-
One release
-
One Hot Fix
-
One iteration
Correct Answer
A. One releaseExplanation
A marketable feature refers to a feature that is ready to be released to the market and can generate value for the customers. Delivering a marketable feature in one sprint may not be feasible as it may require more time for development, testing, and refinement. Similarly, delivering it in one hot fix or one iteration may not be appropriate as these are typically used for addressing specific issues or making small adjustments. Therefore, delivering a marketable feature in one release, which includes multiple sprints and iterations, allows for thorough development, testing, and refinement to ensure that the feature meets the market's requirements and expectations.Rate this question:
-
- 11.
What does the DHQA milestone indicate?
-
Indicates that QA has completed test case authoring
-
Indicates that the Use Case is ready for QA testing
-
Indicates that Regression QA has signed off on the build
-
Indicates that the MF is ready for end-to-end testing
Correct Answer
A. Indicates that the Use Case is ready for QA testingExplanation
The DHQA milestone indicates that the Use Case is ready for QA testing. This means that the quality assurance team can begin testing the functionality and performance of the Use Case to ensure that it meets the required standards and specifications. The completion of test case authoring is not necessarily indicated by the DHQA milestone, as it only signifies the readiness for testing. The milestone does not indicate that Regression QA has signed off on the build or that the MF is ready for end-to-end testing.Rate this question:
-
- 12.
What can you find under "Development Model" wiki?
-
Agile manifesto, principles, and practices
-
Dashboards and metrics for Vista group of companies
-
Information about Aptean Engineering Processes
Correct Answer
A. Information about Aptean Engineering ProcessesExplanation
Under the "Development Model" wiki, you can find information about Aptean Engineering Processes. This suggests that the wiki provides details and documentation specifically related to the engineering processes followed by Aptean, a software company. It may include information about their development methodologies, best practices, project management approaches, and other relevant processes that Aptean follows in their software development lifecycle.Rate this question:
-
- 13.
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:
-
- 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 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:
-
- 16.
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:
-
- 17.
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:
-
- 18.
What is the typical duration of Portfolio Planning Process?
-
12 weeks
-
9 weeks
-
8 weeks
-
7 weeks
Correct Answer
A. 12 weeksExplanation
The typical duration of the Portfolio Planning Process is 12 weeks. This process involves the evaluation and selection of projects or investments to be included in a portfolio based on their alignment with strategic objectives and their potential for delivering value. It includes activities such as project prioritization, resource allocation, risk assessment, and financial analysis. The 12-week duration allows for a thorough and comprehensive assessment of the available options and ensures sufficient time for decision-making and planning.Rate this question:
-
- 19.
Who approves any open issues at the end of the UAT phase?
-
Project Manager
-
Product Manager
-
Portfolio Project Manager
-
Product Development Manager
Correct Answer
A. Product ManagerExplanation
The Product Manager is responsible for approving any open issues at the end of the User Acceptance Testing (UAT) phase. This is because the Product Manager is in charge of overseeing the development and delivery of the product, ensuring that it meets the required specifications and quality standards. They have a deep understanding of the product and its features, making them the most appropriate person to assess and approve any remaining issues before the product is finalized and released.Rate this question:
-
- 20.
During Portfolio Planning, 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 portfolio planning, it is common for the product manager, portfolio project manager, and product development managers to come together and evaluate the marketable features that will be prioritized for development in the upcoming year. This collaborative meeting allows for a comprehensive review of the product portfolio and ensures that the chosen features align with the overall product strategy and market demand. Therefore, the statement "True" accurately reflects this practice.Rate this question:
-
- 21.
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:
-
- 22.
Who does the UAT testing?
-
Market Analysts and Professional Services
-
Solution Consultant, QA managers and System Analyst
-
Customers and Project Managers
-
Executives and Portfolio project Managers
Correct Answer
A. Solution Consultant, QA managers and System AnalystExplanation
The UAT testing is typically performed by Solution Consultants, QA managers, and System Analysts. These individuals have the necessary expertise and knowledge to ensure that the software or solution being tested meets the requirements and specifications set by the customer or end-user. They are responsible for identifying any issues or bugs and providing feedback to improve the product before it is released to the customers. Market Analysts and Professional Services, Customers and Project Managers, as well as Executives and Portfolio Project Managers, may have other roles in the software development process but are not directly involved in UAT testing.Rate this question:
-
- 23.
By the mid-sprint review, the expectation is that:
-
All test cases have been executed
-
2-3 builds have been provided to Regression QA
-
50% of Use Cases have been handed off for QA testing
-
10% of MFs are design complete
Correct Answer
A. 50% of Use Cases have been handed off for QA testingExplanation
By the mid-sprint review, it is expected that 50% of the Use Cases have been handed off for QA testing. This means that half of the Use Cases, which are scenarios or interactions between the user and the system, have been passed on to the Quality Assurance team for testing. This indicates progress in the development process and shows that a significant portion of the Use Cases have been deemed ready for testing.Rate this question:
-
- 24.
The entry criteria for Release Planning is ( are)
-
Detailed Use Cases with acceptance criteria
-
Test strategy, development approach, and non-functional performance requirements
-
Product roadmap, approved budget and staffing forecast
-
BRDs attached to Use Cases in TFS
Correct Answer
A. Product roadmap, approved budget and staffing forecastExplanation
The entry criteria for Release Planning includes having a product roadmap, an approved budget, and a staffing forecast. These elements are essential for effective release planning as they provide a clear direction for the product, ensure that there are sufficient resources allocated, and help in making informed decisions about the release timeline and scope. The detailed use cases with acceptance criteria, test strategy, development approach, and non-functional performance requirements are also important for release planning, but they are not specifically mentioned as entry criteria in this question. The BRDs attached to use cases in TFS is not mentioned as an entry criteria for release planning.Rate this question:
-
- 25.
What is the output of Validation Process group?
-
Release execution plan
-
Completed features
-
Product Roadmap
-
Release Candidate/Gold build
Correct Answer
A. Release Candidate/Gold buildExplanation
The output of the Validation Process group is the Release Candidate/Gold build. This means that after going through the validation process, the team has identified and resolved any issues or bugs, resulting in a stable and final version of the product that is ready for release. The Release Candidate/Gold build is the culmination of the validation process and signifies that the product is of high quality and meets all the necessary requirements for deployment.Rate this question:
-
- 26.
What is the objective of Portfolio Planning?
-
To determine investments with the desired ROI as captured in the Product Roadmap
-
To determine staffing plans that will meet market analyst reports on trends
-
To identify themes for bi-weekly investment
-
To enhance cloud competence to fulfill business plans
Correct Answer
A. To determine investments with the desired ROI as captured in the Product RoadmapExplanation
The objective of Portfolio Planning is to determine investments with the desired ROI as captured in the Product Roadmap. This means that the purpose of portfolio planning is to identify and prioritize investment opportunities that have the potential to provide a good return on investment. By aligning investments with the product roadmap, organizations can ensure that they are investing in projects and initiatives that will contribute to their overall business goals and objectives. This helps to optimize resource allocation and maximize the value generated from the portfolio of investments.Rate this question:
-
- 27.
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:
-
- 28.
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:
-
- 29.
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:
-
- 30.
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:
-
- 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 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:
-
- 32.
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:
-
- 33.
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:
-
- 34.
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:
-
- 35.
Why do we track the burndown?
-
To measure the business value delivered
-
To see whether a particular team member is optimally assigned to tasks
-
To check that the team is in control of their workload
-
No answer
Correct Answer
A. To check that the team is in control of their workloadExplanation
The reason why we track the burndown is to check that the team is in control of their workload. By monitoring the burndown chart, we can see the progress of the team's work and compare it to the planned work. This allows us to identify any potential issues or delays in the project and take necessary actions to ensure that the team stays on track and meets their deadlines. It helps in maintaining transparency and accountability within the team and ensures that everyone is aware of their responsibilities and the overall progress of the project.Rate this question:
-
- 36.
Which milestone indicates that the SA has completed the presentation of Use case requirements?
-
Use Case Design Completed
-
Developer Hand-off to QA
-
Ready for FIT
-
Ready for UAT
Correct Answer
A. Use Case Design CompletedExplanation
The milestone that indicates that the SA has completed the presentation of Use case requirements is "Use Case Design Completed". This milestone suggests that the SA has finished the process of designing the use cases and presenting them, indicating that the requirements have been thoroughly defined and documented. It signifies that the SA is ready to move forward with the next steps in the project.Rate this question:
-
- 37.
How soon should I turnaround a request for engineering assistance?
-
Within 4 weekdays
-
Within 3 working days
-
Within 10 working days
-
Within 7 days
Correct Answer
A. Within 3 working daysExplanation
The correct answer is "Within 3 working days." This means that the person should aim to provide engineering assistance within three business days. Weekends and holidays are not included in the count. This timeframe ensures a prompt response to the request and allows for efficient problem-solving and support.Rate this question:
-
- 38.
Identify an entry criteria for sprint development
-
Tasks created and estimated
-
Use Cases coded and unit tested
-
Product roadmap attached
-
Marketable Features Ready for FIT
Correct Answer
A. Tasks created and estimatedExplanation
The entry criteria for sprint development is that tasks are created and estimated. This means that before starting a sprint, the team must have a clear understanding of the tasks that need to be completed and how long each task will take. This allows for effective planning and allocation of resources during the sprint.Rate this question:
-
- 39.
Who recommends technical solutions for the proposed solutions to market problems?
-
Product Developer
-
Product Development Manager
-
Product Architect
-
Portfolio Project Manager
Correct Answer
A. Product ArchitectExplanation
The Product Architect is responsible for recommending technical solutions for proposed solutions to market problems. They have a deep understanding of the product's architecture and design, and they use their expertise to evaluate different options and propose the most suitable technical solutions. The Product Architect collaborates with other stakeholders such as the Product Developer, Product Development Manager, and Portfolio Project Manager to ensure that the recommended technical solutions align with the overall product strategy and goals.Rate this question:
-
- 40.
What does the "S" in "SE Team" denote?
-
Solutions
-
Sustenance
-
Service
-
Sustaining
Correct Answer
A. SustainingExplanation
The "S" in "SE Team" denotes "Sustaining". This means that the team is responsible for maintaining and supporting the existing systems or products. They ensure that everything is running smoothly and address any issues or problems that arise.Rate this question:
-
- 41.
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:
-
- 42.
In which phase, the final certification of Documentation is done?
-
FIT
-
SIT
-
UAT
-
Launch
Correct Answer
A. SITExplanation
In the Software Integration Testing (SIT) phase, the final certification of documentation is done. This phase involves integrating different modules of the software and testing their interactions to ensure that they work together as expected. During this phase, the documentation is reviewed and verified to ensure that it accurately reflects the integrated software system. This final certification of documentation is crucial as it ensures that the documentation is up-to-date and aligns with the integrated software, providing accurate information to users and stakeholders.Rate this question:
-
- 43.
Which of these is an activity from the Launch process group?
-
Escrow of software and documentation
-
Final regression testing
-
Drafting the Release Readiness Checklist
-
Synchronized sprint demo
Correct Answer
A. Escrow of software and documentationExplanation
The activity of escrow of software and documentation is part of the Launch process group. Escrow refers to the process of depositing software and related documentation with a third-party escrow agent, who holds it in trust until certain conditions are met. This activity is typically done during the Launch process group to ensure that the software and documentation are protected and accessible to the appropriate parties, such as the end-users or stakeholders.Rate this question:
-
- 44.
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:
-
- 45.
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:
-
- 46.
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:
-
- 47.
A Use Case should be small enough to be delivered in:
-
1 month
-
2 weeks
-
1 day
-
1 week
Correct Answer
A. 1 weekExplanation
A use case should be small enough to be delivered in 1 week. This is because use cases are meant to represent specific functionalities or interactions within a system, and it is important to break them down into manageable units of work. A use case that takes longer than a week to deliver may indicate that it is too complex or encompasses too many functionalities, which can make it more difficult to plan, develop, and test effectively. By keeping use cases small and focused, it allows for better productivity, collaboration, and iteration within the development process.Rate this question:
-
- 48.
Identify an expectation from synchronized sprints
-
All Scrum teams start their sprint on the first working day of the month
-
All Scrum teams create and update tasks throughout the sprint
-
All Scrum teams specify their capacity as 7 hours per day
-
All Scrum teams synchronize their sprint burndowns
Correct Answer
A. All Scrum teams start their sprint on the first working day of the monthExplanation
The expectation from synchronized sprints is that all Scrum teams start their sprint on the first working day of the month. This means that all teams within an organization are aligned and begin their sprints simultaneously, allowing for better coordination and collaboration. By starting at the same time, teams can synchronize their efforts, share progress, and address any dependencies or issues that may arise during the sprint. This helps in maintaining a consistent rhythm and enables the organization to track and monitor the progress of multiple teams effectively.Rate this question:
-
- 49.
What is the role of a developer during Portfolio Planning?
-
Work with the Product Architect to evolve technical solutions for the BRD proposals
-
Work with the QA manager to design test plans
-
Provide confidence level and level of effort for Marketable Features
-
Work with System Analyst to write the BRD
Correct Answer
A. Work with the Product Architect to evolve technical solutions for the BRD proposalsExplanation
During portfolio planning, a developer works with the Product Architect to evolve technical solutions for the BRD proposals. This means that the developer is responsible for collaborating with the Product Architect to come up with innovative and feasible technical solutions that align with the business requirements. This involves understanding the technical aspects of the proposals and suggesting improvements or modifications to ensure that the proposed solutions are viable and effective. The developer's role is crucial in ensuring that the technical aspects of the portfolio planning are well-thought-out and aligned with the overall objectives of the organization.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