Copyright © 2012-2014 by Mark J. Sebern Software Engineering Process I SE 2800

Copyright © 2012-2014 by Mark J. Sebern

Software Engineering

Process ISE 2800


Scrum Overview

(from http://en.wikipedia.org/wiki/File:Scrum_process.svg)


..Scrum Overview

(from http://en.wikipedia.org/wiki/File:Scrum_process.svg)

Review/retrospective


Scrum Roles• Who are these people?

• Product owner

• ScrumMaster

• Development team

• What problems will we have in implementing Scrum roles in this course?



Scrum Roles• Who are these people?

• Product owner

• ScrumMaster

• Development team

• What problems will we have in implementing Scrum roles in this course?


What will be developed, and in what order

Guiding team on creating, following process; removing impediments

5-9 people: determines how to deliver whatproduct owner requests.


Some Role Questions• Is the product owner the only

interface to the stakeholders (users, customers, etc.)?

• How does the ScrumMaster become qualified?

• Who is on the development team?

• Full-time only?

• What about specialists (e.g., testers)?


Scrum Activities

Sprintplanning

Sprint execution

Sprint review

Sprint retrospecti

ve

Daily scrum


Copyright © 2012 by Mark J. Sebern

Product BacklogProduct Backlog Items

(PBIs)• What goes in here?• Who manages these

items?• What is “grooming”?• How are the PBIs

ordered?• How are the PBIs

measured?


Copyright © 2012 by Mark J. Sebern

Sprints

• What is a sprint?• How long does one

last?


Copyright © 2012-2014 Mark J. Sebern

Sprint Planning

• What are these components?

• How does planning work?


PBIs vs Tasks

• Measurement units (story points, hours)?

• Mapping between PBIs and tasks?

• Types of tasks and definition of done

• Design, code, review, test, etc.


Checkpoint



Sprint Execution (1)

• Doing the work!

• Performing the identified tasks

• Tracking progress (more later . . .)

• Adapting to emergent knowledge

• (Re)allocating team effort as needed



Sprint Execution (2)• What is the daily scrum?

• "Stand-up" meeting (< 15 minutes)

• 3 questions answered by each member:

• What have I accomplished (since last)?

• What do I plan to have done (by next)?

• What is keeping me from progressing?



Sprint Execution (3)

• What is “done”?

• Potentially shippable product increment

• How about “done done”?

• How does this interact with work breakdown (task definition)?



Sprint Execution (4):

Inspect and Adapt• Sprint review

• Focus on the product (includes feedback)

• Sprint retrospective

• Focus on process (process/practice improvement)


Review

• Scrum process• Roles• Product owner, Scrummaster, Developers

• Product backlog, sprint backlog• Sprint execution• Potentially shippable product increment – done

work• Review• Retrospective


Documents

Copyright © 2012-2014 by Mark J. Sebern Software Engineering Process I SE 2800