html5-img
1 / 16

XP at HP

XP at HP. David Facer Tim Collinson April 2013. Careful what you ask for…. After years of traditional SCRUM, what happens when we go XP?. How we practiced SCRum. Standup Storymapping (aka backlog grooming) Well-formed User Stories Sprint Planning Scrum of Scrums Sprint Review

bob
Télécharger la présentation

XP at HP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. XP at HP David Facer Tim Collinson April 2013

  2. Careful what you ask for…

  3. After years of traditional SCRUM, what happens when we go XP?

  4. How we practiced SCRum Standup Storymapping (aka backlog grooming) Well-formed User Stories Sprint Planning Scrum of Scrums Sprint Review Retrospective Release Planning High-level Planning

  5. The Ceremonies we liked Standup  Storymapping (aka backlog grooming)  Well-formed User Stories  Sprint Planning  Scrum of Scrums    Sprint Review  Retrospective  High-level Planning  Release Planning   

  6. Some things we already did: Unit Tests Pair Programming Continuous Integration Story Mapping

  7. So we took the 1st Chance: New Project RoR (very nice for TDD) Outside of SoS, Release Planning, etc. –this was a risk that we planned to address Would have DevOps responsibility

  8. How we practice XP Standup – slightly modified Storymapping (aka backlog grooming) Well-formed User Stories and… XP Stories (kinda like tasks, but not) Iteration Planning Continual Review Retrospective High-level Planning

  9. How we practice XP (technically) RoR Pairing TDD GIT Jenkins Chef/Capistrano/Rake

  10. Example SCRUM user story: Actor: As an agent Use: I need to be able to efficiently change my password So what: So that I can get logged in and get to work and stay in compliance with my schedule. As an agent, I need to be able to efficiently change my password, so that I can get logged in and get to work and stay in compliance.

  11. Example XP storiEs: Agent sees link/button to change password System suggests to agent to change password Agent can ignore password suggestion Agent sees change password dialog Agent sees link to modal password rules Agent can enter old password Agent can enter new password + confirm Agent can submit new password Agent is returned to login

  12. Strategy & tactic: Tactical decision making at the tactical level Strategic decision making at the strategic level Increasingly you’re driven much like TDD, as in MDD Strategy & Vision must be crisp And if all else fails, the “13 feet” rule

  13. Cons • Can lose sight of the big picture • No more caffeine-fueled, ninja-like innovation • No good way to pull all-nighters Dave’s TOP Three: Pros Confidence: TDD, CI, DevOps, frequent release Traction & Velocity: stories completed daily Way fewer “ceremonies”

  14. Cons • Organizational misunderstanding • Not a great “fit” for all temperaments • Demands “normal” working hours Tim’s TOP Three: Pros Small, digestible stories We push frequently & consistently Way fewer “ceremonies”

  15. Outcomes: Nearly doubled velocity Reduced QA consumption to nearly zero Engagement is tangibly improved Software quality is noticeably improved

  16. Questions? David Facer

More Related