Scrum A Breathtakingly Brief And Agile Introduction

ChrisSims, Hillary Louise Johnson: Scrum A Breathtakingly Brief And Agile Introduction ASIN:B007P5N8D4

about Scrum

== Excerpts ==

What is Scrum?

Roles Scrum recognizes only three distinct roles: product owner, scrum master, and team member

Product Owner

One way that the product owner maximizes ROI is by directing the team toward the most valuable work,

make sure the team fully understands the requirements.

Scrum Master

The scrum master acts as a coach, guiding the team to ever-higher levels of cohesiveness, self-organization, and performance. While a team’s deliverable is the product, a scrum master’s deliverable is a high-performing, self-organizing team.

This is a peer position on the team,

Team Member

So, how many team members should a scrum team have? The common rule of thumb is seven, plus or minus two.

Scrum Artifacts

The Product Back Log

Sprint Backlog

all the stories that the team has committed to delivering this sprint and their associated tasks.

Burn Chart-s

Task Board

Definition of Done

The Sprint Cycle

The sprint cycle is the foundational rhythm of the scrum process.

As of this writing, it is common for scrum teams to work in sprints that last two weeks, and many teams are starting to work in one-week sprints.

The table that follows maps out the various meetings you would schedule during a one-week sprint.

Sprint Planning Meeting

Part One: “What will we do?”

One by one, in priority order, the product owner presents the stories he would like the team to complete

This process repeats for each story, until the team feels that they can’t commit to any more work.

Part 2: “How will we do it?”

Daily Scrum (Stand Up Meeting)

no more than 15 minutes.

the team needn’t solve problems in the meeting: simply surfacing the issues and deciding which team members will address them is usually sufficient.

Story Time

discussing and improving the stories

not the stories in the current sprint--those stories are now in the sprint backlog.

one hour per week,

team works with the product owner

Define and Refine Acceptance Criteria

Story Sizing (Estimating)

Story Splitting

As of this writing, the story time meeting isn’t an “official” scrum meeting.

Sprint Review

main event of this meeting: demonstrating the stories that did get done.

feedback and ideas,

This meeting is not a decision-making meeting.

one-half to one hour

RetroSpective

one to two hours

Abnormal Sprint Termination (When Good Sprints Go Bad) *