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

2. Copyright © 2012-2014 by Mark J. Sebern Scrum Overview (from http://en.wikipedia.org/wiki/File:Scrum_process.svg)

3. Copyright © 2012-2014 by Mark J. Sebern..Scrum Overview (from http://en.wikipedia.org/wiki/File:Scrum_process.svg) Review/retrospective

4. Copyright © 2012-2014 by Mark J. Sebern Scrum Roles Who are these people? Product owner ScrumMaster Development team What problems will we have in implementing Scrum roles in this course? Review/retrospective

5. Copyright © 2012-2014 by Mark J. Sebern Scrum Roles Who are these people? Product owner ScrumMaster Development team What problems will we have in implementing Scrum roles in this course? Review/retrospective What will be developed, and in what order Guiding team on creating, following process; removing impediments 5-9 people: determines how to deliver what product owner requests.

6. Copyright © 2012-2014 by Mark J. Sebern 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)?

7. Copyright © 2012-2014 by Mark J. Sebern Scrum Activities Sprint planning Sprint execution Sprint review Sprint retrospective Daily scrum

8. Copyright © 2012-2014 by Mark J. SebernCopyright © 2012 by Mark J. Sebern Product Backlog Product Backlog Items (PBIs) What goes in here? Who manages these items? What is “grooming”? How are the PBIs ordered? How are the PBIs measured?

9. Copyright © 2012-2014 by Mark J. SebernCopyright © 2012 by Mark J. Sebern Sprints What is a sprint? How long does one last?

10. Copyright © 2012-2014 by Mark J. SebernCopyright © 2012-2014 Mark J. Sebern Sprint Planning What are these components? How does planning work?

11. Copyright © 2012-2014 by Mark J. Sebern 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.

12. Copyright © 2012-2014 by Mark J. Sebern Checkpoint

13. Copyright © 2012-2014 by Mark J. Sebern Sprint Execution (1) Doing the work! Performing the identified tasks Tracking progress (more later...) Adapting to emergent knowledge (Re)allocating team effort as needed

14. Copyright © 2012-2014 by Mark J. Sebern 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?

15. Copyright © 2012-2014 by Mark J. Sebern Sprint Execution (3) What is “done”? Potentially shippable product increment How about “done done”? How does this interact with work breakdown (task definition)?

16. Copyright © 2012-2014 by Mark J. Sebern Sprint Execution (4): Inspect and Adapt Sprint review Focus on the product (includes feedback) Sprint retrospective Focus on process (process/practice improvement)

17. Copyright © 2012-2014 by Mark J. Sebern Review Scrum process Roles Product owner, Scrummaster, Developers Product backlog, sprint backlog Sprint execution Potentially shippable product increment – done work Review Retrospective Review/retrospective