What is the role of the Scrum Master during Sprint Execution?
- Assign tasks to team members
- Facilitate the Scrum events, remove impediments, and coach the team
- Manage the product backlog
- Review and approve user stories
The Scrum Master's role during Sprint Execution is to facilitate the Scrum events, such as the Daily Stand-up, Sprint Review, and Sprint Retrospective. They also remove impediments that are blocking the team's progress, coach team members on Scrum practices, and ensure that the Scrum framework is followed effectively.
How does the Scrum Team handle changes to the Sprint scope once the Sprint has started?
- Changes are approved by the Scrum Master only
- Changes are automatically rejected to maintain the stability of the sprint
- Changes are escalated to senior management for approval
- Changes are negotiated with the Product Owner and may be added to the Sprint backlog if feasible
The Scrum Team handles changes to the Sprint scope by negotiating them with the Product Owner. If the changes are deemed feasible and align with the sprint goal, they may be added to the Sprint backlog with the approval of the Product Owner. It's essential to maintain transparency and collaboration between the team and the Product Owner to ensure that changes do not disrupt the sprint's progress unnecessarily.
The "blocks" issue link type is typically used to indicate that one issue _______ another.
- Blocks
- Depends on
- Relates to
- Requires
In JIRA, the "blocks" link type is used to indicate that one issue is blocking another, meaning that the resolution of the blocked issue depends on the resolution of the blocking issue.
When designing workflows, it's important to keep them _______ to avoid unnecessary complexity.
- Complicated
- Flexible
- Linear
- Simple
It's crucial to keep workflows simple to ensure clarity and ease of use. Complex workflows can lead to confusion and inefficiency.
In Scrum, what is the typical duration of a sprint?
- 1 month
- 2 weeks
- 3 weeks
- 4 weeks
In Scrum, the typical duration of a sprint is 2 weeks. However, this can vary depending on the specific needs and preferences of the team. Shorter sprints promote more frequent feedback and adaptability, while longer sprints may be suitable for larger, more complex projects.
Scenario: Your organization is transitioning to Agile, and some team members are resistant to change. How would you address this resistance and promote Agile adoption?
- Assign Blame
- Ignore the Resistance
- Impose Agile Practices
- Provide Training and Education
Providing training and education is crucial to address resistance to change by helping team members understand the benefits and principles of Agile methodologies. Ignoring the resistance or imposing Agile practices forcefully can lead to further resistance and hinder the transition process. Assigning blame is counterproductive and does not address the underlying issues causing resistance.
What scripting language is commonly used for advanced automation in JIRA?
- Groovy
- JavaScript
- Python
- Ruby
Groovy is commonly used for advanced automation in JIRA. It offers powerful scripting capabilities and is supported by JIRA for customizing workflows, automating tasks, and developing plugins.
The Product Owner has identified a critical change in priorities and wants to add a high-priority item to the current Sprint. What action should the Scrum Team take?
- Evaluate the impact on the Sprint Goal and discuss with the Product Owner
- Immediately incorporate the new item into the Sprint backlog
- Refuse to accommodate the change as it disrupts the Sprint plan
- Schedule a separate meeting to discuss the change
When the Product Owner identifies a critical change in priorities during a Sprint, the Scrum Team should evaluate the impact on the Sprint Goal and discuss it with the Product Owner. This ensures transparency and alignment with the Sprint Goal, enabling the team to make informed decisions about adjusting the Sprint backlog. Rushing to incorporate the new item without considering its impact can lead to scope creep and jeopardize Sprint commitments.
Scenario: Your team uses JIRA for managing IT support requests. You want to create a workflow that ensures every issue is assigned to the right support team based on the type of request. Which JIRA feature would you use to implement this workflow?
- Assignee
- Components
- Custom Fields
- Issue Types
Custom Fields allow you to capture additional information on issues beyond the default fields provided by JIRA. By creating a custom field for "Support Team" and configuring it to appear on the appropriate screens, you can ensure that every issue is assigned to the right support team based on the type of request. This ensures efficient routing of IT support requests to the appropriate teams.
In a JIRA workflow, what is a "resolution"?
- A field that indicates why an issue is closed
- A status assigned to an issue
- An action taken on an issue to move it forward
- The final step in the workflow
In JIRA, "resolution" refers to the reason why an issue is closed. It helps in tracking the outcomes of issues, such as "Fixed," "Won't Fix," "Duplicate," etc., providing clarity on the status of the issue. It's a crucial part of workflow management, aiding in reporting and understanding the resolution of various issues.