Agile preso

464 views

Published on

Few topics have garnered more scorn and skepticism from the top-level executives of software or Web development companies than agile. Whether at a dev shop, agency, or company, large or small, selling agile development to The Man is often a daunting task. Have no fear! In this discussion you will learn all the tips, tricks and techniques needed to help your boss see why agile methodologies and practices not only make the design and development teams better and happier (read: more efficient), but how they can save time and money (read: add to the bottom line). Using the language of the business owner, we will cover both new and familiar topics including agile estimation, creating and using an inception deck, user stories, iteration planning and the burn-down chart, agile communication, business driven development, and visual workspaces. As a bonus we will share ideas for paying down your technical debt, setting up continuous integration, and how to develop an agile ROI model based on the real-life work of area software professionals. Best of all, you?ll learn how to show and not just tell The Brass these concepts without ever using the word agile.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
464
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Agile preso

    1. 1. Agile is NOT a 4 Letter Word How I Got My Boss Over the Waterfall and Into the 21st Century
    2. 2. My name is Ben and I’m a recovering Waterfallic...
    3. 3. While there is value in the items on the right, we value the items on the left more. Individuals and interactions over processes and tools Working soft ware over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
    4. 4. My Boss listening to me explain agile
    5. 5. Anatomy of a Perfect Client
    6. 6. Let’s seeif we can hit your target velocity.
    7. 7. Anatomy of a Perfect Client
    8. 8. S.H.I.E.L.D.wants to see yourburndown chart.
    9. 9. Anatomy of a Perfect ClientTheir project isimportant AND theyhave time for you. Committed
    10. 10. Anatomy of a Perfect ClientEager to learn andtrusts you to do thejob, and/or has in-house expertise. Collaborative
    11. 11. Anatomy of a Perfect ClientAnswers their phone,responds to email andwill meet with youearly and oftenthroughout a project. Responsive
    12. 12. Anatomy of a Perfect ClientCares about gettingto done, not meetinga (often arbitrary)deadline. Understanding
    13. 13. Anatomy of a Perfect ClientActs as an advocatefor your team,removing obstaclesand handling internalcommunications. Supportive
    14. 14. Anatomy of aApproaches projects Perfect Clientas risk/reward andrecognizes thatchanging course canbe more importantthan staying the Adaptablecourse.
    15. 15. My reaction
    16. 16. That’s great, but most ofmy clients aren’t like that They usually don’t know any better They are scared of the unknown They need a reason to trust you Or... They really are a bad client
    17. 17. ?uestimation
    18. 18. Estimation Exercise Temperature - Degrees Celsius/Fahrenheit Latitude - # Degrees + (NSEW) Area or Length - Square Miles/KM Money - US Dollars Time - Year AD/BC Volume - Cubic Miles/KM/Ft/Meters or Gallons/Liters Weight - Pounds/English Tons/Kilograms/Metric Tons
    19. 19. EstimationLook for something to count Available Sooner Rather than Later Requirements User Stories Indicators of Relative SizeAdd Variance, not PaddingAcceptable Risk
    20. 20. Minimum Safe Assurance
    21. 21. Inception Deck You Have To Go Deeper
    22. 22. Test Driven Development Less Bugs = Less Waste ROI FormulaIndustry Average # Bugs/#Lines of Code /Reduction of Latent Bugs
    23. 23. Paired Programming Two Heads are Better than One ROI Formula Decrease in idle time + Increase in coding efficiency (reduced errors)- Reduction of individual productivity (15%)
    24. 24. Iterative DeliverySomething Delivered, Something Gained ROI % increase in project size - YOY + Decrease in Rework (%)
    25. 25. Employee Morale The Morale of the Story ROI FormulaCost of replacing an employee + Paying for putting up with
    26. 26. Motivate
    27. 27. Motivate
    28. 28. Ingredients for SuccessCommitment from MGMTAgile Coach/Boot CampFail Fast, NOT Fail LastTools and Practices Continuos Integration, DVCS, Code Coverage SOLID Programming (Katas) Custom Agile
    29. 29. ResourcesUncle Bob - ButUncleBob.comClean Code: A Handbook of AgileSoft ware Craftsmanship – Robert C.MartinSeven Languages in Seven Weeks –Bruce A. TateSoft ware Estimation: Demystifying theBlack Art – Steve McConnellThe Agile Samurai – JonathonRasmusson
    30. 30. About.me/Sirius_B T: @Sirius_BBlog: w3rdofmouth.com

    ×