Scrum 101 Pt 1

Scrum is a(n)

• agile process that allows us to focus on delivering the highest business value in the shortest time

• a agile process that focus on custom and culture vs. needs of customer

• methodology that is about minimizing complexity

• the standard way of accomplishing a goal

Scrum allows us to

• rapidly and repeatedly inspect actual working software every 2 weeks

• stay the course with little interaction with customer until product completion

• self-organize to determine the best way to deliver the highest priority features

• adapt to the constant changes by customers communicating with developers

Every 2 weeks - 1 month

• anyone can see real working software and decide to release it as is or continue to enhance it for another sprint

• will have a retrospective meeting

• will have a scrum meeting

• will have a sprint planning meeting to confirm priorities for backlog

What are the characteristics of scrum?

• Self-organizing teams

• Product progresses in a series of month-long "sprints"

• Requirements are captured as items in a list of "producer backlog"

• No specific engineering practices prescribed

• Uses generative rules to create an agile environment for delivering projects

The total story points delivered over a sprint

• Velocity

• Sprint

• User Stories

• Planning Poker

Planning Poker

• Team reviews each story then everyone shows their card with story points

• draw a line on the wall from smallest to largest; team silently determines values

• Review the story through buckets to determine how complex it is

• Example:

  Light=1

  Medium=2

  High=3

  Complex =4

Complexity Buckets

• Team reviews each story then everyone shows their card with story points

• draw a line on the wall from smallest to largest; team silently determines values

• Review the story through buckets to determine how complex it is

• Example:

  Light=1

  Medium=2

  High=3

  Complex =4

Affinity Sizing

• Team reviews each story then everyone shows their card with story points

• draw a line on the wall from smallest to largest; team silently determines values

• Review the story through buckets to determine how complex it is

• Example:

  Light=1

  Medium=2

  High=3

  Complex =4

User Interface

• What the user sees on his/her end.

• What the developer sees on his/her end.

• What the Product Manager sees.

• What the Project Owner sees on his/her end.

Pulling of data; Source the data

• Data/Integration

• Data Sourcing

• Data Extraction

• Testing Intergration