Engineering Process Certification Assessment

REA stands for Requests for Engineering Assistance and Request for Engineering Assistance. This acronym is commonly used in the engineering field to refer to the process of seeking help or support in engineering-related matters. The use of both variations of the acronym suggests that either form can be used interchangeably to convey the same meaning.

If a use case is not finished at the end of the sprint, the best course of action would be to move it to the next sprint by changing the iteration path. This allows the unfinished use case to be carried forward and prioritized in the next sprint, ensuring that it is completed in a timely manner. Closing it and raising another use case would create unnecessary duplication and confusion, while leaving it alone would result in the use case being neglected and potentially forgotten.

The SCRUM master is responsible for a SCRUM team's daily update. The SCRUM master is a facilitator and coach for the team, ensuring that the SCRUM framework is followed and that the team is able to work efficiently and effectively. They are responsible for organizing and leading daily stand-up meetings, where team members provide updates on their progress, discuss any obstacles or challenges they are facing, and collaborate on the next steps. The SCRUM master also works closely with the product owner and stakeholders to ensure that the team's work aligns with the project goals and priorities.

The typical methodology used in our Sustaining Engineering teams is Kanban. Kanban is a visual project management system that helps teams to visualize their work, limit work in progress, and improve overall efficiency. It allows teams to track and prioritize tasks, and ensures that work flows smoothly through the different stages of the process. Kanban is known for its flexibility and adaptability, making it a popular choice for teams working on sustaining engineering projects.

If you have no task to book your time against, the best option would be to add a new task. This allows you to allocate your time and ensure that you are productive. By adding a new task, you can effectively manage your time and prioritize your workload. This also helps in maintaining a structured schedule and avoiding any wasted time.

When working on a task with another team member at the same time, creating a new task for your work is the appropriate action to take. This allows both team members to track their individual progress and time spent on the task separately. By creating a new task, each team member can accurately record their own contributions and avoid any confusion or overlap in time tracking.

System analysts do not prioritize marketable features, write user manuals, or regress reproducible bugs. They are primarily responsible for analyzing and designing information systems to meet the needs of an organization. Their role involves gathering requirements, creating system specifications, and working with developers to ensure the successful implementation of the system.

The sprint burndown for the team can be seen on the TFS team home page. This means that the team can access and track the progress of their sprint by simply visiting the TFS team home page. It provides a visual representation of the remaining work and helps the team to understand if they are on track to complete the sprint successfully. Using this feature, the team can monitor their progress and make any necessary adjustments to ensure timely delivery of their work.

The reason we are asking all products to use this standard TFS structure is because the consolidated reporting we need relies on knowing what is stored where in TFS. This implies that having a standardized structure will allow for easier and more accurate reporting, as the data will be organized in a consistent manner. It is not simply because Microsoft recommends it or because management told us to, but rather because it is necessary for the specific reporting requirements.

At the end of the sprint, it is important to update tasks that are not closed and/or tasks with remaining hours. This is because these tasks may not have been completed within the sprint and need to be carried forward or reassigned to the next sprint. By updating these tasks, the team can have an accurate understanding of the progress made and plan accordingly for the next sprint.

In TFS, the type of work item used to represent a defect is called a "Bug". This work item is specifically designed to track and manage software defects, allowing teams to effectively identify, prioritize, and resolve any issues or flaws in the software development process. By using the "Bug" work item type, teams can ensure that defects are properly documented, assigned, and resolved in a systematic manner.

The correct answer is "In 1 release." This means that a marketable feature should be delivered within a single release of a product or software. A release typically refers to a version or update that is made available to users. By delivering the feature in one release, it ensures that it is complete and ready for use by customers or clients. This approach allows for better planning and management of development efforts, as well as providing a clear timeline for when the feature will be available to users.

Under "Approved Process Guidance Documents," you can find documents that provide information about the Aptean Engineering Processes and guide you on what you should do on a daily basis. These documents likely outline the standard procedures, best practices, and recommended actions to follow in order to ensure efficient and effective engineering processes within the organization.

A Scrum Master is not directly responsible for the quality of a release. The Scrum Master's main role is to facilitate the Scrum process and ensure that the team is following the Agile principles and practices. The responsibility for the quality of a release lies with the entire Scrum team, including the Product Owner, Development Team, and stakeholders. The Scrum Master may support the team in identifying and addressing quality issues, but they do not have sole responsibility for it.

Executives are responsible for the product priorities and budget because they hold the highest level of authority and decision-making power within an organization. As leaders, executives are responsible for setting the overall strategic direction of the company, which includes determining the priorities for product development and allocating the necessary budget resources. They are accountable for ensuring that the product aligns with the company's goals and objectives and that sufficient funding is allocated to support its development and success. Therefore, it is true that executives hold the responsibility for product priorities and budget.

The correct answer is Sprint retrospective. The sprint retrospective is a phase in SCRUM where the team reflects on the completed sprint and identifies areas for improvement. It allows the team to review what went well and what didn't, and to take actions to improve their processes and outcomes for the upcoming sprint. This phase helps the team continuously learn and adapt, leading to increased efficiency and effectiveness in future sprints.

Teams which follow Scrum and work in sprints track their progress using a burndown chart. In Scrum, sprints are time-boxed iterations where teams work on a set of tasks to deliver a potentially shippable product increment. The burndown chart is a visual representation of the remaining work over time in a sprint. It helps the team to track their progress, identify any deviations from the planned work, and make necessary adjustments to meet the sprint goal. Therefore, teams that do not follow Scrum or work in sprints may not use a burndown chart to track their progress.

Entering time on tasks at least once per day and whenever a task is completed ensures accurate tracking and documentation of the time spent on each task. This practice allows for better project management, as it provides real-time updates on task progress and helps identify any potential delays or bottlenecks. Additionally, entering time regularly ensures that the time spent on each task is recorded promptly and accurately, reducing the chances of forgetting or misrepresenting the actual effort put into the task.

During the sprint planning phase, the product manager plays a crucial role in providing clarifications. They are responsible for answering any questions or concerns from the development team regarding the product requirements and goals. By being available, the product manager ensures that the team has a clear understanding of the tasks and can plan and prioritize effectively. This collaboration between the product manager and the development team helps in creating a well-defined and achievable sprint plan. Therefore, the statement "A product manager is available to provide clarifications during a sprint planning phase" is true.

During the Product Approval phase, key stakeholders such as the Product Manager, Portfolio Project Manager, and Product Development managers come together to assess and strategize the development of Marketable Features for the upcoming year. This meeting allows them to review the proposed features, prioritize them, and plan their implementation. Therefore, the statement "True" accurately reflects the purpose and activities conducted during the Product Approval phase.

Use Cases should be stack ranked against one another, within the same marketable feature. This means that when prioritizing Use Cases, they should be ranked in order of importance and value within a specific feature that is marketable to customers. By stack ranking the Use Cases, it helps to determine which ones should be implemented first based on their significance and impact on the product. This allows for efficient planning and development of features that align with the overall goals and objectives of the product.

A task is not user-focused. Unlike user stories, which are focused on the end user's needs and requirements, a task is a more detailed and specific piece of work that needs to be completed to accomplish a user story. It is typically a lower-level work item that is part of the implementation process and is not directly related to the user's perspective.

Stack ranking is a process of evaluating and ranking items based on their importance or priority. In this question, the options are "Marketable Feature," "BRD," "Use Case," and "Task." The correct answer is "BRD" because a BRD (Business Requirements Document) is not typically stack ranked. A BRD is a document that outlines the business requirements for a project or product, and it is used as a reference for the development process. However, it is not directly ranked or prioritized like marketable features, use cases, or tasks.

In TFS (Team Foundation Server), each team has a Home Page. This means that all teams in TFS have their own individual Home Page. This allows each team to have a dedicated space where they can access and manage their project-related information, such as tasks, backlog, and progress. Having separate Home Pages for each team helps in organizing and streamlining the work within TFS, ensuring that each team has a centralized location to collaborate and track their specific project requirements and goals.

Documentation writers are responsible for documenting various aspects of a project, including requirements, but they are not specifically responsible for documenting requirements as use cases. Use cases are a specific technique used in requirements gathering and analysis, and can be created by business analysts or other stakeholders involved in the project. Therefore, the given statement is false.

The escrow activity is done during the Release exit. This means that the escrow process, which involves the release of funds or assets held in escrow, takes place at the end of the release phase. It is a crucial step in ensuring that all contractual obligations have been met and that the release is finalized. The Release exit marks the completion of the release and signifies the transition to the next phase or project.

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

A characteristic of a Kanban team is having a continuous inflow of work. Kanban is a lean methodology that focuses on visualizing and managing work in progress. It emphasizes a "pull" approach, where work is pulled into the system based on the team's capacity and the availability of resources. This ensures a steady flow of work and prevents overloading the team. Holding a weekly standup meeting is not specifically a characteristic of a Kanban team, as it is a common practice in many agile methodologies. The statement about Aptean SE is unrelated to the characteristics of a Kanban team.

The System Analyst is primarily responsible for creating use cases. Use cases are a way to capture and describe the interactions between users and a system. They outline the steps and actions that a user takes to achieve a specific goal. Use cases help to define the functionality of a system and ensure that it meets the needs and requirements of the users. They are an important tool in the analysis and design phase of software development.

A developer is responsible for coding, code review, and unit testing. Coding involves writing the actual program or software using programming languages. Code review is the process of examining the written code to ensure it meets quality standards and follows best practices. Unit testing involves testing individual components or units of code to ensure they function correctly.

A Product Manager is responsible for various tasks related to product development and management. One of the key artifacts expected from a Product Manager is a Business Requirements Document (BRD), which outlines the business needs, goals, and requirements for the product. This document helps the team understand the scope and objectives of the product. Additionally, a Product Manager is also expected to deliver Marketable Features, which are the functionalities or characteristics of the product that can be marketed and sold to customers. These features are essential for attracting and retaining customers, and ultimately driving business growth.

The "S" in "SE Team" denotes Sustaining.

Enhancement is a bug type in TFS that is not counted in the SE Defect Backlog because it refers to the addition of new features or improvements to existing functionality. While defects and bugs are typically focused on fixing issues or problems, enhancements are about enhancing the product's capabilities. Therefore, enhancements are categorized separately and are not considered as part of the defect backlog.

The team is responsible for progress on the burndown. In Scrum, the team collectively takes ownership of delivering the product increment. The burndown chart is a tool used to track the progress of work during a sprint, and it is the responsibility of the team to update and maintain the chart. The team collaboratively works together to complete the planned work and ensures that the burndown is accurate and reflects the progress made towards the sprint goal. The Scrum Master or Team Leader may support and facilitate the team's progress, but ultimately, it is the team's responsibility.

A QA member is responsible for conducting various types of tests to ensure the quality of the software. Acceptance tests are performed to validate if the software meets the requirements and expectations of the stakeholders. Use case test cycle involves testing the software's functionality based on different use cases. Integration tests are conducted to check the interaction and compatibility of various components of the software. Therefore, the responsibility of a QA member includes performing acceptance tests, use case test cycle, and integration tests.

In IBOP/Pivotal, a change request is used to represent a defect. This suggests that when a defect is identified, it is categorized as a change request rather than a separate entity like a defect or bug. This implies that the process for addressing and resolving defects in IBOP/Pivotal involves submitting a change request to make the necessary changes to fix the defect.

The product backlog can be found at any level. This means that it can be accessed and utilized by anyone involved in the product development process, regardless of their role or position. The product backlog serves as a dynamic, prioritized list of features, enhancements, and bug fixes that need to be implemented in the product. It is continuously updated and refined throughout the project, allowing the team to adapt and respond to changing requirements and priorities. This flexibility and accessibility make the product backlog an essential tool for effective Agile development.

Monitoring the Defect Backlog provides several benefits. Firstly, it allows for assessing the effectiveness of the SE team by tracking the number of defects resolved and the rate at which they are resolved. Secondly, it helps in determining how much work to do each week by identifying the number of defects that need to be addressed. Lastly, it enables evaluating the work remaining by keeping track of the number of open defects. Therefore, all of the given options are benefits of monitoring the Defect Backlog.

The statement "Created by the Portfolio Project Manager" is false because BRDs (Business Requirements Documents) are typically created by business analysts or product managers, not by portfolio project managers. BRDs assist in feature development throughout the project, include the position of competitors, and may have one or many MFs (Market Factors) associated with them.

The responsibilities of a SCRUM master include hosting the sprint retrospective, facilitating sprint planning, and providing weekly plan updates. The sprint retrospective is a meeting where the team reflects on the previous sprint and identifies areas for improvement. The SCRUM master plays a key role in facilitating this meeting. Similarly, the SCRUM master is responsible for facilitating sprint planning, which involves determining the work to be done in the upcoming sprint. Additionally, the SCRUM master provides weekly plan updates to keep the team informed about the progress and any changes in the plan.

The burndown chart is used to track the progress of a team's work during a sprint or project. By monitoring the burndown, we can assess whether the team is able to effectively manage their workload. If the chart shows a steady decrease in the remaining work, it indicates that the team is on track and in control of their workload. On the other hand, if the chart shows a slow or stagnant decrease, it may indicate that the team is struggling to keep up with their tasks and may need to adjust their approach or seek additional resources.

The stack rank indicates the priority of the items, with the highest priority being indicated by the number 0.

A single team working on multiple releases is not supported because it can lead to resource constraints and a lack of focus. Each release requires dedicated time and effort to ensure its success, and dividing a team's attention among multiple releases can result in lower quality work and missed deadlines. It is more efficient and effective to have separate teams working on different releases, allowing them to fully focus on their specific goals and deliverables.

A Documentation member tracks work done to update a user manual in a Task. A Task is a specific activity or assignment that needs to be completed as part of a larger project. In this case, updating a user manual would be a specific task assigned to the Documentation member. The other options, Marketable Feature, BRD (Business Requirements Document), and Use Case, do not specifically refer to tracking work done to update a user manual.

Tasks should be of a lesser duration because it allows for clearer objectives. When tasks are broken down into smaller, manageable chunks, it becomes easier to define what needs to be accomplished and how to measure success. Additionally, shorter tasks lead to less confusion as team members have a clear understanding of what needs to be done. It also enables more accurate estimates as it is easier to estimate the time and effort required for shorter tasks. Assigning tasks to one person also helps in ensuring accountability and clarity in responsibilities.

The statement mentions that every product at Aptean goes through both validation and beta phases. However, the correct answer is False, which suggests that not every product at Aptean goes through both validation and beta phases.

Regression testing is not only started when the code is frozen and the release is feature complete. Regression testing is a type of software testing that is performed to ensure that the existing functionality of the software has not been affected by any new changes or bug fixes. It can be performed at various stages of the software development lifecycle, including during development and after the release. Therefore, the statement that regression testing is only started when the code is frozen and the release is feature complete is incorrect.

During pre-planning, various stakeholders including Architects, System Analysts (SA), and Development, QA and Doc Managers review the Business Requirements Document (BRD) with the Project Manager (PM) and provide effort estimates for the Minimum Features (MFs). This allows for a comprehensive understanding of the project requirements and helps in planning the development process. Additionally, at the end of a sprint, the System Analyst (SA) demonstrates the implementation of the Use Cases to the Project Manager (PM), ensuring that the developed features align with the desired functionality.

When completing a task, you should set the fields for Remaining, State, and Completed. The "Remaining" field indicates the amount of work left to be done on the task. The "State" field represents the current status or progress of the task. The "Completed" field indicates whether the task has been finished or not. By setting these fields, you can track the progress and completion of the task accurately.

The current work list of Bugs and Tasks in progress is stored at level 4. This suggests that there are different levels or tiers within the SE teams' work structure, and level 4 is where the Bugs and Tasks in progress are managed and tracked.