Ep2.0 Final Assessment For Managers

WIP limit refers to the restriction on the number of work items that can be in progress in a particular workflow state. This means that there is a maximum limit set on the number of tasks or activities that can be simultaneously worked on within a specific stage of the workflow. This helps to prevent overloading and bottlenecks, ensuring that the team focuses on completing the current work before taking up new tasks. By implementing WIP limits, teams can improve efficiency, reduce multitasking, and maintain a steady flow of work throughout the workflow process.

The correct answer is 14 hours because it is the shortest amount of time listed.

PDM stands for Product Data Management, which is a system used to manage and control product-related information throughout its lifecycle. LOE (Level of Effort) and Confidence Level are important factors in project management, and PDM provides the necessary tools and features to track and analyze these aspects. PDM allows users to assess the effort required for a particular task or project and determine the level of confidence in its success. Therefore, PDM is the most likely source for providing the Marketable Feature LOE & Confidence Level.

At the beginning of the Portfolio Planning Process, the PPM polls the Product Manager(s) to identify horizontal themes and individual product roadmaps. This is important because it helps the PPM understand the different product strategies and plans that the Product Manager(s) have for their respective products. By identifying horizontal themes, the PPM can look for commonalities or synergies among different products that can be leveraged to optimize the overall portfolio. Additionally, by understanding the individual product roadmaps, the PPM can assess the feasibility and alignment of each product with the overall portfolio goals and objectives.

PSPI stands for Potentially Shippable Product Increment. This means that it is a part of the product that has been completed and is potentially ready to be shipped or delivered to the customer. It signifies that the product increment has met the necessary quality standards and can be potentially released or shipped to the market.

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.

The Project Manager (PM) creates the Business Requirement Document (BRD). The PM is responsible for overseeing the planning, execution, and closing of a project, and part of this role involves gathering and documenting the business requirements for the project. The BRD outlines the objectives, scope, and deliverables of the project, as well as the functional and non-functional requirements. By creating the BRD, the PM ensures that all stakeholders have a clear understanding of the project's goals and requirements, which helps in guiding the project team throughout the project lifecycle.

Use Cases are marked as PM Demo completed after the Sprint demo because the Sprint demo is a crucial milestone in the Agile development process. During the Sprint demo, the development team showcases the completed user stories and features to the product owner and stakeholders. This provides an opportunity for them to review and provide feedback on the functionality and usability of the application. Once the Use Cases have been demonstrated and approved during the Sprint demo, they can be marked as PM Demo completed, indicating that they have met the necessary requirements and are ready for further testing or deployment.

The sprint burndown chart should start by the second day of the sprint. This is because the chart is used to track the progress of the sprint and show how much work is remaining. By starting the chart on the second day, the team will have enough data to accurately represent the work completed and the work remaining. Starting the chart on the first day may not provide an accurate representation as the team may not have started working on the tasks yet. Starting the chart by the last day or by the demo of the sprint would be too late as it would not allow the team to track their progress effectively throughout the sprint.

After the SA presents the functional requirements of the Use Case and the coding and testing approach are determined, the next milestone achieved is UCDC (Use Case Detailed and Complete). This milestone signifies that the use case has been thoroughly analyzed, all the necessary details have been captured, and it is ready for further development and testing.

The role of a technical writer during Sprint development is to update content related to the Use Cases committed to the current sprint. This involves ensuring that any changes or updates made to the Use Cases are accurately reflected in the documentation. By keeping the documentation up to date, the technical writer helps to ensure that all team members have access to the most current and accurate information, which can improve the efficiency and effectiveness of the development process.

Scope variance is measured by calculating the ratio of the number of milestone deliverables (MFs) that have been closed to the total number of milestone deliverables that have been committed. This ratio provides an indication of how well the project is adhering to its planned scope. A higher value indicates that a larger proportion of the committed deliverables have been successfully closed, indicating good scope management. Conversely, a lower value suggests that there may be scope creep or difficulties in completing the planned deliverables.

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.

Sales and marketing collateral and legal documents are prepared during the launch phase. This is because the launch phase is when a product or service is introduced to the market, and it is crucial to have all the necessary materials and documents ready to support the sales and marketing efforts. This includes creating promotional materials, sales presentations, brochures, and legal documents such as contracts and agreements. By preparing these materials during the launch phase, companies can ensure that they have everything they need to effectively promote and sell their product or service.

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.

The correct answer is "Reproduces the issue". After a Service Ticket is created for a Customer, the Support Analyst needs to reproduce the issue reported by the customer. This involves trying to recreate the problem or error that the customer is experiencing. By reproducing the issue, the Support Analyst can verify its existence and gather more information about it, which will help in resolving the problem effectively.

A team is eligible for innovation days when their sprint goals are met. This means that they have successfully completed all the tasks and objectives set for the sprint. Innovation days provide an opportunity for the team to explore new ideas, experiment with different approaches, and work on innovative projects outside of their regular sprint work. By achieving their sprint goals, the team has demonstrated their ability to deliver on their commitments and can now allocate time for creative and innovative endeavors.

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.

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.

Release Planning should be started no later than one month before the targeted start date of the first development sprint. This ensures that there is enough time for the necessary planning and preparation before the actual development work begins. Starting the Release Planning process earlier allows for a more thorough and well-thought-out plan, reducing the risk of delays or issues during the development phase. It also provides enough time for any necessary adjustments or changes to be made based on feedback or new requirements that may arise.

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.

PPM, which stands for Portfolio Project Management, initiates the Portfolio Planning process. PPM is a management approach that helps organizations prioritize and manage their projects and programs in alignment with their strategic objectives. It involves identifying, evaluating, and selecting the right projects to include in the portfolio based on their potential benefits, risks, and resource requirements. PPM also ensures that the selected projects are effectively executed and monitored to achieve the desired outcomes and maximize the return on investment.

The role of the Lead QA Engineer during Release Planning is to determine the Test strategy and Test planning approach for the release. This involves identifying the overall approach and methods that will be used for testing during the release, as well as determining the specific test plans and procedures that will be followed. The Lead QA Engineer is responsible for ensuring that the testing process is well-defined and effective in identifying and resolving any issues or bugs before the release.

A single team working on multiple releases is not supported because it can lead to a lack of focus and prioritization. Each release typically requires dedicated attention and resources to ensure its success. When a team is spread too thin across multiple releases, it can result in delays, quality issues, and a higher risk of failure for all the releases. It is more efficient and effective to have separate teams dedicated to each release, allowing them to focus on delivering the best possible outcome for their specific release.

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.

The product backlog can be found at any level. This means that it is not restricted to a specific level within the project or organization. The product backlog is a dynamic and constantly evolving list of requirements, features, and enhancements for the product. It serves as a single source of truth for the development team and stakeholders to prioritize and plan the work. Regardless of whether it is at the project level, team level, or organization level, the product backlog remains an essential tool for managing and delivering the product.

A System Analyst provides Acceptance Criteria for Feature Use Cases. System Analysts are responsible for analyzing, designing, and documenting system requirements, including acceptance criteria. They work closely with stakeholders, such as product managers and development teams, to understand the needs and expectations for a feature. Based on this understanding, they define the acceptance criteria, which outline the conditions that must be met for a feature to be considered complete and satisfactory. By providing the acceptance criteria, System Analysts ensure that the feature meets the desired functionality and quality standards.

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.

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.

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.

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.

Level 4 in the iteration tree structure contains the current work list of Bugs and Tasks in progress for SE teams. This suggests that there are multiple levels in the iteration tree structure, and Level 4 is where the work list is located. The question does not provide further information about the iteration tree structure or the specific roles and responsibilities of each level.

The correct answer is Collect, Analyze, Balance, Approve. In the Aptean Annual Roadmap Process, the first phase is to collect information and data relevant to the roadmap. The next phase is to analyze the collected information and data to identify trends, patterns, and opportunities. Once the analysis is done, the next phase is to balance the roadmap by prioritizing and aligning the initiatives and projects based on strategic goals and resources. Finally, the approved roadmap is the last phase in which the roadmap is reviewed and approved by relevant stakeholders.

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.

A product roadmap captures both the market problem and the proposed solution. It outlines the strategic direction of a product, including its goals, features, and timeline. It helps align the team and stakeholders on the product vision and provides a high-level overview of how the product will address the market problem. A product roadmap is a visual representation of the product strategy and serves as a guide for product development and decision-making.

We check for Release Schedule variance during the Launch phase. This is the stage where the final product or service is released to the market or the intended users. It is essential to monitor the release schedule at this stage to ensure that the product is launched according to the planned timeline. By checking for variance, any delays or deviations from the schedule can be identified and addressed promptly, minimizing any potential negative impacts on the project or the organization.

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.

After the Solution Architect (SA) accepts a Use Case, the state of the Use Case is considered "Resolved." This means that the SA has reviewed and acknowledged the Use Case, and any issues or problems associated with it have been addressed or resolved. The Use Case is now ready to proceed to the next stage of development or implementation.

not-available-via-ai

During release planning, the feature development team, SA (Solution Architect), and PDM (Product Development Manager) review requirements and determine the Release Execution Plan. This means that these key stakeholders come together to assess the requirements and create a plan for how the release will be executed. This ensures that everyone is on the same page and understands what needs to be done for a successful release.

At the end of a sprint, either the SA or PDM demos the Use Case implementation to the PM (Project Manager). This allows the SA or PDM to showcase the work that has been done during the sprint and gather feedback from the PM. This helps in ensuring that the project is progressing as planned and any necessary adjustments can be made.

The maximum number of levels allowed in the iteration tree structure is 6.

Vista reviews the portfolio plan during the Vista Roadmap session. This suggests that the Vista Roadmap session is a specific event or meeting where the portfolio plan is discussed and evaluated. It is likely that the Vista Roadmap session is a dedicated time for stakeholders to come together and assess the portfolio plan, making decisions and adjustments as necessary. The other options, such as the Aptean Roadmap presentation, Annual Roadmap process kickoff, and Investment allocation meeting, do not specifically mention the portfolio plan or indicate that it is reviewed during those events.

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."

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.

The correct answer is "After all Test Cases are executed." This means that an MF (Module Functionality) is marked ready for SIT (System Integration Testing) only after all the test cases have been executed. This implies that all the planned tests have been performed on the module to ensure its functionality and performance. The execution of test cases is a crucial step in the testing process, as it helps identify any defects or issues in the module before it is deemed ready for integration testing.

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.

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.

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.

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.

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.

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.

The State of an Incident is set to closed when the developer provides the necessary information to Support. This means that the developer has gathered all the relevant information and documentation required to resolve the incident and has provided it to the Support team. Once this information is received, the incident can be considered resolved and closed. The other criteria mentioned in the question, such as customer satisfaction and support step creation, may be important in the overall incident resolution process, but they are not specifically mentioned as the trigger for closing the incident.