Scrum depuis les tranchées

6acd3df818349485f3942b5c6d16247a?s=47 Youri Ackx
October 31, 2013

Scrum depuis les tranchées

Petit guide des bonnes (et des moins bonnes) pratiques. Journée Agile 2013 à Louvain-la-Neuve. Version HTML5 en ligne :


Youri Ackx

October 31, 2013


  1. 1.


    LESS GOOD) PRACTICES Journée Agile 2013 — Youri Ackx @YouriAckx
  2. 5.

    PRELIMINARY NOTES Any resemblance to real persons, living or dead…

    May contain unorthodox opinions or XP fragments YMMV
  3. 7.

    HUMAN FACTOR “Build projects around motivated individuals. Give them the

    environment and support they need, and trust them to get the job done.” — Manifesto for Agile Software Development
  4. 9.
  5. 10.

    COACH Hire a Scrum coach Avoid forming bad habits Avoid

    wasting time figuring things out "Moral authority" A few sessions will already do you good
  6. 11.

    SEAT THE TEAM TOGETHER “Just get the team together. Even

    if you have to personally threaten each individual, carry all their gear, and wipe up their old coffee stains. If there is no space for the team, make space. Somewhere. Even if you have to place the team in the basement. Move tables around, bribe the office manager, do whatever it takes. Just get the team together.” — Henrik Knieberg
  7. 12.

    SEAT THE TEAM TOGETHER Basement might be too remote from

    life Central location is better specially for new teams
  8. 13.

    BOARD Wall board vs Atlassian Pros and cons Prefer simple

    wall board by default 80" wall touch screen wins
  9. 18.
  10. 20.

    DON'T Think in technical terms Think user stories first User

    actually needed to tell the bank to adjust a warranty
  11. 21.

    “The sales marks the deal as closed and the sales

    support team receives a notification”
  12. 22.

    As a _____ , in order to _____ , I

    _____ + How to Demo In the previous example we actually had 2 stories
  13. 23.

    BE VISUAL Please review those 250+ pages specs vs visual

    model Paper, pen, post-its, PowerPoint Prototypes, mockups, wireframes
  14. 24.

    PROBLEM SEDIMENTATION No need to fix everything right now →

    Parking Don't let issues drag Don't let tech debt build up
  15. 25.
  16. 26.

    THE VERSATILE TEAM MYTH Might work with senior developers With

    junior: no so good Not convinced it makes sense How I understand it
  17. 27.

    THE RELUCTANT ONE It's up to you to keep him…

    or drop him Do not underweight the power of disturbance when pondering
  18. 28.
  19. 29.

    BOARD OVERBOOKING One more for the road! No team commitment

    You can always add some if stories run out
  20. 30.

    END OF SPRINT EFFECT Artificial, not business related … But

    forces you to wrap up Refrain the urge to score at all cost
  21. 31.

    SUPPORT Increase "slack" time percentage (Aubry) How to deal w/

    support volatility? Tracking is painful (and has a cost) Impact on sprint
  22. 33.

    “In real life, you can’t always sprint. You need to

    rest between sprints. If you always sprint, you are in effect just jogging.” — Henrik Knieberg
  23. 39.