Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Agile Doesn't Have to Stink

Agile Doesn't Have to Stink

Justin Carmony

May 08, 2015
Tweet

More Decks by Justin Carmony

Other Decks in Technology

Transcript

  1. Agile Doesn't
    Have to Stink
    Justin Carmony - OpenWest 2015
    @JustinCarmony

    View Slide

  2. • Director of Development

    @ Deseret Digital Media
    • Utah PHP Usergroup

    President
    • I Make (and Break)

    Web Stuff (~10 years)
    • @JustinCarmony

    [email protected]
    Hi • Director of Development

    @ Deseret Digital Media
    • Utah PHP Usergroup

    President
    • I Make (and Break)

    Web Stuff (~10 years)
    • @JustinCarmony

    [email protected]

    View Slide

  3. This

    Presentation
    • Slides Posted Online
    • Feel free to ask on-topic
    question during presentation
    • Q&A Session At the End
    • Feel free to ask me any
    questions afterwards

    View Slide

  4. • You’ve Heard of Agile
    • You Know the Basic Structure
    of Scrum
    • You’ve tried to do Agile in
    some fashion with some team.
    Assumptions for this Presentation
    Planning
    Estimation
    2 Week Sprint
    Daily Standups
    Review & Retrospectives

    View Slide

  5. Let’s Take a Poll
    Developers? Product Owners? Project Managers?
    Scrum Master? Management?

    View Slide

  6. I’m A Developer

    View Slide

  7. Lets Get This
    Out of The Way

    View Slide

  8. Agile Sucks!

    View Slide

  9. Yes

    View Slide

  10. Yes
    , It Can

    View Slide

  11. Yes, It Can
    But It Doesn’t Have To!

    View Slide

  12. Lets Talk About
    Why

    View Slide

  13. ag·ile [aj-uhl, -ahyl]
    quick and well-coordinated in movement; lithe: an
    agile leap.
    active; lively: an agile person.
    marked by an ability to think quickly; mentally acute
    or aware: She's 95 and still very agile.
    1.
    2.
    3.

    View Slide

  14. ag·ile [aj-uhl, -ahyl]
    quick and well-coordinated in movement; lithe: an
    agile leap.
    active; lively: an agile person.
    marked by an ability to think quickly; mentally acute
    or aware: She's 95 and still very agile.
    1.
    2.
    3.
    4. A marketing word for any Development Tool,
    Training, or Processes recently released.

    View Slide

  15. Terrible Word

    View Slide

  16. View Slide

  17. View Slide

  18. Who uses Agile Processes?

    View Slide

  19. We’re Agile!

    View Slide

  20. What does Agile Mean?

    View Slide

  21. View Slide

  22. Actually…
    Welll…
    Uhhh….
    I guess…
    Hmm…
    Derp…

    View Slide

  23. View Slide

  24. View Slide

  25. View Slide

  26. Story Time

    View Slide

  27. View Slide

  28. Project Manager
    Work List
    Developers
    Tickets
    Guessing
    Hours
    Team Meeting

    View Slide

  29. Project Manager
    Work List
    Developers
    Tickets
    Guessing
    Hours
    Team Meeting
    Product Owner + Scrum Master
    Backlog
    Scrum Team
    Stories
    Estimating
    Story Points
    Sprint Planning

    View Slide

  30. View Slide

  31. View Slide

  32. View Slide

  33. It Was Frustrating

    View Slide

  34. Why Agile?

    View Slide

  35. Our Team is More Efficient!
    We Do Agile Because…
    We Make a Better Product!
    We Release On Schedule!

    View Slide

  36. Our Team is More Efficient!
    We Do Agile Because…
    We Make a Better Product!
    We Release On Schedule!

    View Slide

  37. Fundamentally
    Agile is About…

    View Slide

  38. Better Decisions

    View Slide

  39. Agile Is Not
    Just a Process

    View Slide

  40. Agile is a Decision
    Making Framework

    View Slide

  41. Quick Agile Test

    View Slide

  42. Have You Changed How You Make
    Decisions?

    View Slide

  43. • Have you changed how make decisions about:
    • What you work on “Today”
    • Features, Bugs, & Priorities
    • Releases & Deadlines
    • Planning for the Future
    Decision Making

    View Slide

  44. Re-learning Agile

    View Slide

  45. Reality In; Decisions Out
    R.I.D.O

    View Slide

  46. Reality

    View Slide

  47. Week 1 Week 2 Week 3 Week 4 Week 5
    Week 6 Week 7 Week 8 Week 9 Week 10
    Time
    Progress

    View Slide

  48. Week 1 Week 2 Week 3 Week 4 Week 5
    Week 6 Week 7 Week 8 Week 9 Week 10
    Time
    Work Finished

    View Slide

  49. Week 1 Week 2 Week 3 Week 4 Week 5
    Week 6 Week 7 Week 8 Week 9 Week 10
    Time
    Work Finished

    View Slide

  50. Week 1 Week 2 Week 3 Week 4 Week 5
    Week 6 Week 7 Week 8 Week 9 Week 10
    Time
    Work Finished

    View Slide

  51. View Slide

  52. Insanity!

    View Slide

  53. Goal:
    Honest Assessment
    of Reality

    View Slide

  54. What is Reality?
    Things we can Control Things we cannot Control
    The Past
    Deadlines
    Features
    Bugs
    Feature Scope
    Sick & Personal Leave
    Work Emergencies
    How Long Things Take
    ???
    What To Code
    Etc, etc, etc
    What to Fix
    Actions for Right Now
    Re-evaluate Scope
    Etc, etc, etc
    Etc, etc, etc

    View Slide

  55. Decisions

    View Slide

  56. Make Decisions that
    Manage Risk

    View Slide

  57. Complexity
    Critical

    View Slide

  58. Complexity
    Critical

    View Slide

  59. Complexity
    Critical

    View Slide

  60. Complexity
    Critical

    View Slide

  61. Complexity
    Critical

    View Slide

  62. Improving Parts
    of your Process

    View Slide

  63. Team Roles

    View Slide

  64. Project
    Manager
    Owns the Process
    Owns the Product
    Owns Development

    View Slide

  65. Project
    Manager
    Owns the Process
    Owns the Product
    Owns Development
    Hard to assess reality for all 3 things

    View Slide

  66. Scrum
    Master
    Owns the Process
    Owns the Product
    Owns Development
    Product
    Owner
    Dev
    Lead

    View Slide

  67. Scrum
    Master
    Product
    Owner
    Dev
    Lead
    Reality Decisions

    View Slide

  68. Share Common Goal
    Individual Responsibilities

    View Slide

  69. Meetings

    View Slide

  70. Meetings Suck!

    View Slide

  71. Keep Them Simple!
    Keep Them Short!

    View Slide

  72. Review
    Retro
    Estimation
    Planning
    2.5 Hours

    View Slide

  73. Retrospectives

    View Slide

  74. MOST IMPORTANT
    PART OF OUR PROCESS!

    View Slide

  75. 1.What went well?
    2.What do we want to Change?
    3.How are we going to Change It?
    Retrospectives
    Reality In
    Decisions Out

    View Slide

  76. Document It!

    View Slide

  77. • Added 0 point option to Pivotal for for simple tasks that were falling
    in the cracks before.
    • More consistent with standups. Starting & ending on time.
    • Gathered good feedback from stakeholders
    • Having a UI that we can demonstrate with helps communicate to
    stakeholders
    What Went Well

    View Slide

  78. Disrupted several times by AdOps “Emergencies” that could have been
    avoided with early communication.
    What To Change & How
    Problem
    Solution
    Designate point person (product manager) for all requests to come
    through. Proactively coordinate with AdOps before Sprints start.

    View Slide

  79. Pivotal & GitHub Notifications are being too noisy in the HipChat Room.
    What To Change & How
    Problem
    Solution
    Create new HipChat room for All Notifications and only post critical
    notifications in the main room.

    View Slide

  80. With Remote Developers visit, we didn’t have enough on boarding work
    for new Junior Dev.
    What To Change & How
    Problem
    Solution
    Tag “easy” items regularly to have a clean backlog of on boarding tasks.

    View Slide

  81. Several DN stories planned had CMS dependencies that weren’t
    finished
    What To Change & How
    Problem
    Solution
    Use “dependency” label in both DN & CMS backlogs
    Review CMS backlog before finalizing each sprint plan

    View Slide

  82. Review Your
    Retrospective Items!

    View Slide

  83. • Safe Communication Environment
    • Focus on the Future
    • Look for Small, Manageable Changes
    • Focus on You before Others - “What can I improve”
    Making Retrospectives Effective

    View Slide

  84. Estimation

    View Slide

  85. It’s Not Precise!
    It’s Not Accurate!

    View Slide

  86. View Slide

  87. View Slide

  88. View Slide

  89. View Slide

  90. View Slide

  91. Releasing

    View Slide

  92. Complexity
    Critical

    View Slide

  93. Complexity
    Critical

    View Slide

  94. View Slide

  95. • Don’t Over Analyze for perfect Precision!
    • Focus on Identifying Complexities.
    • Opportunity for Product Owners & Devs to clear up Ambiguity and
    define a more clear scope.
    • You will get better over time. There will always be stories that will be
    greatly over or under estimated.
    Estimation
    Reality In Decisions Out

    View Slide

  96. View Slide

  97. Planning

    View Slide

  98. • Planning goes smoothly when:
    • You Product Backlog / Icebox is Well Defined
    • Broken into manageable stories & estimated
    • End of planning ensure:
    • Goals are set and stories are prioritized
    • Everyone knows what they will be doing next
    Planning

    View Slide

  99. Stand Ups

    View Slide

  100. • Focus on the spirit of the meeting, not the rules.
    • Make sure to identify three areas:
    • What happened Previous Day
    • What they will work on Today
    • Anything Blocking.
    • Opportunity for Decisions! Keep an eye on Goals!
    Making Stand Ups Effective
    Reality In
    Decisions Out
    Reality In

    View Slide

  101. Final Thoughts

    View Slide

  102. Everyone Has a Process

    View Slide

  103. Be Strategic About It

    View Slide

  104. Spirit Over the Rule

    View Slide

  105. Always Look for
    Ways to Improve

    View Slide

  106. Questions?

    View Slide

  107. Thank You
    Twitter: @JustinCarmony
    Email: [email protected]
    Web: justincarmony.com
    Please Leave Feedback: https://joind.in/10884

    View Slide