Download - Scrum Gathering Shanghai - April 2010

Transcript
Page 1: Scrum Gathering Shanghai - April 2010

Scrum & XP Scrum Gathering, Shanghai

Page 2: Scrum Gathering Shanghai - April 2010

Scrumology.com

Scrum and XP

• Title: Scrum and XP: Myths, truths and how to do it.

• Description: Scrum and Extreme Programming are two common Agile frameworks. You may have heard that Scrum is equivalent to XP without technical practices. Or, perhaps you have heard that Scrum is only a project management framework. The presentation intents to explore the truth in these matters and to discuss how to effectively integrate the XP technical practices within the Scrum framework.

Page 3: Scrum Gathering Shanghai - April 2010

The Speaker

Kane Marhttp://Scrumology.com

Working with ...

http://OutSofting.com - Scrum Training - Scrum Coaching

Page 4: Scrum Gathering Shanghai - April 2010

Scrumology.com

Common Myths about Scrum and Extreme Programming (XP)

•Myth: Scrum is just a management process

•Myth: Scrum is XP without Technical practices

•Myth: Scrum and XP are mutually exclusive

Page 5: Scrum Gathering Shanghai - April 2010

Scrum Practices

Page 6: Scrum Gathering Shanghai - April 2010

Scrumology.com

Scrum Practices

• Scrum Teams (and their associated roles): ScrumMaster, Product Owner and Team

• Time-Boxes: Release Planning Meeting, Sprint Planning Meeting, Sprint, Daily Scrum, Sprint Review, and Sprint Retrospective

• Artifacts: Product Backlog, Sprint Backlog, Release Burndown, and Sprint Burndown

• Reference http://www.scrum.org/storage/scrumguides/Scrum%20Guide.pdf

Page 7: Scrum Gathering Shanghai - April 2010

Reference: http://www.scrum.org/storage/scrumguides/Scrum%20Guide.pdf

Page 8: Scrum Gathering Shanghai - April 2010

Extreme Programming Practices

Page 9: Scrum Gathering Shanghai - April 2010

Scrumology.com

Extreme Programming Practices

• Feedback: Pair Programming, Planning Game, Test Driven Development, Whole Team, Customer Tests

• Continuous Process: Continuous Integration, Design Improvement (Refactoring), Small Release

• Shared Understanding: Coding Standard, Collective Code Ownership, Simple Design, System Metaphor

• Programmer welfare: Sustainable Pace

• Reference: K. Beck, Extreme Programming Explained: Embrace Change. Boston: Addison-Wesley, 1999.

Page 10: Scrum Gathering Shanghai - April 2010

Reference: http://www.XProgramming.com

Page 11: Scrum Gathering Shanghai - April 2010

Reference: http://www.XProgramming.com

Page 12: Scrum Gathering Shanghai - April 2010

Some differences of Scrum and XP

• Scrum is agnostic with regard to technical practices

• The Scrum model for Roles and Responsibilities is better defined

• The Scrum Timeboxes (meetings) are better defined

• Scrum explicitly lists Scrum artifacts: Product Backlog, Sprint Backlog, Release Burndown, and Sprint Burndown

Page 13: Scrum Gathering Shanghai - April 2010

Some differences of Scrum and XP

• The XP model for technical practices is better defined

• The XP model for a Continuous Process is better defined

• XP introduces concepts that make delivering “an increment of potentially shippable code” possible

Page 14: Scrum Gathering Shanghai - April 2010

Scrumology.com

Scrum + XP

What would happen if we take the best of Scrum and combine it with the best of Extreme Programming?

Page 15: Scrum Gathering Shanghai - April 2010

Scrumology.com

XP@Scrum and XBreed

• XP@Scrum - Ken Schwaber’s initial ideas of combining Scrum and XP

• XBreed - Mike Beedle’s ideas about combining Scrum and XP

Page 16: Scrum Gathering Shanghai - April 2010

Scrum + XP

Page 17: Scrum Gathering Shanghai - April 2010

Scrum + XP

Page 18: Scrum Gathering Shanghai - April 2010

Scrumology.com

Combining Scrum & XP

• Try ... all of Scrum

• Try ... the key XP technical practices: Continuous Integration, Test Driven Development, Refactoring

• Try ... some key XP concepts including Simple Design, Common Code Ownership and Small Releases

Page 19: Scrum Gathering Shanghai - April 2010

Scrumology.com

Combining Scrum & XP

• Avoid ... mandating that all XP technical practices be adopter. Rather, educate teams on the different practices and allow them to decide when and how to adopt them.

• Avoid ... unrealistic expectations. Rather, recognize that this is a paradigm shift in how teams write and deliver software, and expect that this will take time.

• Avoid ... adopting Scrum without changing technical practices. Rather, recognize the limitations of existing technical practices and educate teams in the XP technical practices and their implications.

Page 20: Scrum Gathering Shanghai - April 2010

Scrumology.com

A Quote

“Most high performance teams use Scrum and XP together.”

Page 21: Scrum Gathering Shanghai - April 2010

Higher Performance

• By using XP Technical practices we can deliver high quality software at the end of every Sprint

• And, it’s only when we can deliver high quality software on a regular basis that we can know the true rate at which we can deliver functionality to the business

• Combining Scrum and XP is a powerful way of taking your team to the next level

Page 22: Scrum Gathering Shanghai - April 2010

Build something beautiful and inspiring!

Page 23: Scrum Gathering Shanghai - April 2010

Scrumology.com

References

• http://www.controlchaos.com/about/xp.php

• http://www.scrum.org/storage/scrumguides/Scrum%20Guide.pdf

• http://www.XProgramming.com

• K. Beck, Extreme Programming Explained: Embrace Change. Boston: Addison-Wesley, 1999.

• K. Schwaber and M. Beedle, Agile Software Development with Scrum

Page 24: Scrum Gathering Shanghai - April 2010

Photo Credits

http://www.flickr.com/photos/tprzechlewski/http://www.flickr.com/photos/26629142@N03/ http://www.flickr.com/photos/jesuspresley/

http://www.flickr.com/photos/ahmadzamri/http://www.flickr.com/photos/tprzechlewski/ http://www.flickr.com/photos/morton/

http://www.flickr.com/photos/dfletcher/http://www.flickr.com/photos/caspermoller/ http://www.flickr.com/photos/marc_smith/ http://www.flickr.com/photos/giovannijl-s_photohut/