Scrum #1

Scrum is:

1. Lightweight 2. Simple to understand 3. Difficult to master

Scrum framework consists of

Scrum Teams and their associated roles, events, artifacts, and rules.

Who should decide who will be the Scrum Master for a new Scrum Team?

The Development Team and the Product Owner -- thescrummaster.co.uk -- (Because Scrum Team is self-organize??)

The Scrum Master serves the Development Team in several ways, including:

1. (Coach self-organize)Coaching the Development Team in self-organization and cross-functionality; 2. (Help product value)Helping the Development Team to create high-value products; 3. (Impediment)Removing impediments to the Development Team's progress; 4. (Facilitate)Facilitating Scrum events as requested or needed; and, 5. (Coach org environments)Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood.

What happens when a Sprint is cancelled?

1. (Review Done)Any completed and "Done" Product Backlog items are reviewed. 2. (PO accept potentially releasable)If part of the work is potentially releasable, the Product Owner typically accepts it. 3. (Re-est and put back incomplete)All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog.

How does Definition of "Done" help the Scrum Team?

1. ASSESS: Assess when work is complete on the product Increment 2. ESTIMATE: Guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning 3. TRANSPARENCY: Ensures artifact transparency

The purpose of the Sprint Retrospective is to:

1. DONE: Inspect how the last Sprint went with regards to people, relationships, process, and tools; 2. IMPROVEMENTS, POTENTIAL IMPROVEMENTS: Identify and order the major items that went well and potential improvements; and, 3. PLAN IMPROVEMENTS: Create a plan for implementing improvements to the way the Scrum Team does its work.

Competency: Developing & Delivering Products Professionally

1. Emergent Software Development 2. Managing Technical Risk 3. Continuous Quality 4. Continuous Integration 5. Continuous Delivery 6. Optimizing Flow

Competency: Understanding and Applying the Scrum Framework

1. Empiricism 2. Scrum Values 3. Roles 4. Events 5. Artifacts 6. Done 7. Scaling

Competency: Evolving the Agile Organization

1. Organizational Design & Culture 2. Portfolio Planning 3. Evidence Based Management™

Scrum Artifacts

1. Product Backlog 2. Sprint Backlog 3. Increment

The input to the Sprint Planning

1. Product Backlog, 2. the latest product Increment, 3. projected capacity of the Development Team during the Sprint, 4. and past performance of the Development Team.

What are the three most applicable characteristics of the Product Owner?

1. Product Value Maximizer 2. Lead Facilitator of Key Stakeholder Involvement 3. Product Marketplace Expert

The purpose of the Sprint Review is...

1. Scrum Team and stakeholders collaborate about what was done 2. Attendees collaborate on the next things that could be done to optimize value (In other words, to inspect the Increment and adapt the Product Backlog)

Competency: Developing People and Teams

1. Self-Organizing Teams 2. Facilitation 3. Leadership Styles 4. Coaching & Mentoring 5. Teaching

What is the role of Management in Scrum?

1. Support the Product Owner with insights and information into high value product and system capabilities. 2. Support the Scrum Master to cause organizational change that fosters empiricism, self-organization, bottom-up intelligence, and intelligent release of software. -- Scrum Open --

Sprint Backlog

1. The set of Product Backlog items selected for the Sprint, plus 2. A plan for delivering the product Increment and realizing the Sprint Goal

Scrum Competencies

1. Understanding and Applying the Scrum Framework 2. Developing People and Teams 3. Managing Products with Agility 4. Developing & Delivering Products Professionally 5. Evolving the Agile Organization

Sprint Planning answers the following:

1. What can be delivered in the Increment resulting from the upcoming Sprint? 2. How will the work needed to deliver the Increment be achieved?

Product Backlog refinement

1. add detail, 2. estimate, and 3. order (to items in the Product Backlog)

Rules of Scrum

1. bind together the roles, events, and artifacts, 2. governing the relationships and interaction between them.

The team model in Scrum is designed to optimize

1. flexibility 2. creativity 3. productivity

Daily Scrum Meeting Time Boxed

15 minutes for one month sprint

Sprint Retrospective Time Boxed

3 hours for one month sprint

Development Team Size

3-9

Sprint Planning Time Boxed

8 hours for one month sprint

What is the essence of Scrum?

A *small team* of people that is highly *flexible* and *adaptive*

Product Backlog

A single list of features prioritized by business value

When many Development Teams are working on a single product, what best describes the definition of "Done?"

All Development Teams must have a definition of "Done" that makes their combined work potentially releasable.

3C of User Stories

Card Conversation Confirmation https://hocvienagile.com/agipedia/user-story/

Required participant for Daily Scrum

Development Team

Scrum framework is founded on

Empiricism

Only the Product Owner should update the Product Backlog without delegating to anyone?

False (Product Backlog items can be updated at any time by the Product Owner or at the Product Owner's discretion)

During the Daily Scrum, the Development Team must answer the 3 questions

False (The 3 questions is just an example)

Scrum does not allow additional meetings that are not defined in Scrum.

False (just minimize the need for meetings)

The Increment must be released at the end of every Sprint

False The Product Owner decides to release it.

Scrum Values

Focus, Courage, Openness, Commitment, Respect

The formal opportunities for Inspection and Adaptation are

Four Scrum events are formal events for inspection and adaptation. They are Sprint Planning, Daily Scrum, Review and Retrospective.

How frequently should scrum users inspect Scrum artifacts and progress toward a Sprint Goal?

Frequently, but it should not get in the way of the work

INVEST of User Stories

Independent Negotiable Valuable Estimable Small Testable

Sprint length

Limited to one calendar month

How much of the capacity of the Development does usually consumes for Product Backlog refinement?

No more than 10%

A Scrum Team is at the end of a Sprint. The next Sprint starts

Only after the Retrospective event of the current Sprint

Which statement best describes a Product Owner's responsibility?

Optimizing the value of the work the Development Team does.

Who is responsible for the transparency of the product development progress

Product Owner

Who is responsible for measuring the performance of the project?

Product Owner -- unbored.training --

Who decides the duration of the Sprint?

Scrum Team

Who is responsible for formulating a Sprint Goal

Scrum Team

A Product Owner is not available, The next immediate accountability is with

ScrumMaster, who needs to educate Product Owner on his role -- hocvienagile --

During Daily Scrum, this plan is used as a reference to understand the changes in progress.

Sprint Backlog

Condition to proceed sprint

Sprint Goal * cannot proceed without a Sprint Goal * can proceed without complete Sprint Backlog -- hocvienagile.com --

Scrum Events

Sprint Planning Daily Scrum Sprint Review sprint Retrospective

Who is responsible for monitoring progress toward Goals?

The Product Owner

Who is responsible for crafting the Sprint Goal at the Sprint Planning?

The Scrum Team

What provides guidance to the Development Team on why it is building the Increment?

The Sprint Goal

In which meetings the Key Stakeholders are allowed to participate?

The Sprint Review

A Product Owner cannot send a representative (delegate) to the Sprint Review.

True A Product Owner though they are accountable for Product Backlog, they can delegate many of the activities around Product Backlog Management, such writing them, ordering them, etc. However, they cannot delegate their participation in Scrum events.

The Product Owner must attend the Sprint Retrospective?

True The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements

The role of ScrumMaster in Sprint Retrospective is

a peer team member

Scrum Team

a self-organizing team consisting of a Product Owner, Development Team and Scrum Master.

Scrum Pillars

transparency, inspection, and adaptation

Competency: Managing Products with Agility

1. Forecasting & Release Planning 2. Product Vision 3. Product Value 4. Product Backlog Management 5. Business Strategy 6. Stakeholders & Customers

Sprint Review Time Boxed

4 hours for one month sprint

The new Sprint length needs to be agreed upon by

Product Owner The Product Owner needs to ensure that the Sprint length is short enough to limit business risks and also short enough so the team can synchronize the development work with other business events. So it requires the approval of the Product Owner.

Who do the Product Backlog refinement

Product Owner and the Development Team collaborate

A customer wants to communicate something very relevant and important about the product to the Development Team. Who should they talk to?

Product Owner only -- hocvienagile.com --

Who is responsible for managing the progress of work during a Sprint?

The Development Team

increment

The sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints.

You are in a Scrum Team that is in the middle of the Sprint. Your team gets some additional team members. The likely result is:

The team may suffer in its productivity -- hocvienagile.com --

Other people than the Scrum Team can attend the Sprint Planning in order to provide technical or domain advice.

True (The Development Team may also invite other people to attend to provide technical or domain advice.)

The Scrum Master serves the organization in several ways, including:

1. (Lead, coach)Leading and coaching the organization in its Scrum adoption; 2. (Plan implementation)Planning Scrum implementations within the organization; 3. (Help understanding)Helping employees and stakeholders understand and enact Scrum and empirical product development; 4. (Cause change increasing productivity)Causing change that increases the productivity of the Scrum Team; and, 5. (Collaborate other SMs)Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization.

The result of the Sprint Review is

1. (mandatory)a revised Product Backlog that defines 2. (optional)the probable Product Backlog items for the next Sprint.

Product Backlog management

1. EXPRESS: Clearly expressing Product Backlog items; 2. ORDER: Ordering the items in the Product Backlog to best achieve goals and missions; 3. OPTIMIZE: Optimizing the value of the work the Development Team performs; 4. TRANSPARENT: Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the 5. Scrum Team will work on next; and, 5. CLEAR TO DEV TEAM: Ensuring the Development Team understands items in the Product Backlog to the level needed.

Service of Scrum Master in regard to the Daily Scrum?

1. Ensures that the Development Team has the meeting, but the Development Team is responsible for conducting the Daily Scrum. 2. Teaches the Development Team to keep the Daily Scrum within the 15-minute time-box. 3. If others are present at the Daily Scrum, ensures that they do not disrupt the meeting.

The Scrum Master serves the Product Owner in several ways, including:

1. Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible; 2. Finding techniques for effective Product Backlog management; 3. Helping the Scrum Team understand the need for clear and concise Product Backlog items; 4. Understanding product planning in an empirical environment; 5. Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value; 6. Understanding and practicing agility; and, 7. Facilitating Scrum events as requested or needed.