What I Learned From Burning Down My House

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    1 Augustus 1991 20 hour: My sister Karien calls her boyfriend from her holiday.

    I’m answering the phonecall. I’m asking her if my father is around, if she can ask him to come to the phone and she can get a pencil and some paper. My sister wants to know what happens and freks out when I insist she passes my father.

    I tell my father his house burned down. I have to repeat it three times.

    Zelfgenoegzaamheid

    ZelfgenoegzaamheidA feeling of contentment or self-satisfaction , especially when coupled with unawareness of danger or troubleComplancecy embraces the staus quoMy parents were not happy with their houseThey had a very expensive loanRelation was on cruise control

    This is filled with energyFalse Urgency is built on a platform of anxiety and angerMore activity then productivityPassive aggresion

    Too busy driving to take gas??PO /SM Too busy to attend demo’s Sprint reviews?

    Aim for the heart not for the senseGreat leaders win over the hearts and minds of others

    I read 20 to 30 pages a day, not just on software developmentI spend 20% of my income on training and courses.Listen to your customer interfacing employeesShow them don’t tell themGive as much disquiting information to as many peopleMake it clear the blame game will not be toleratedSend people out Bring people in

    Too busy driving to take gas??PO /SM Too busy to attend demo’s Sprint reviews?

    Teh medium is the messageStart meetings on timeAct VS WaitRespond fast, move nowClear the desks (agenda)Be visible urgent

    MESware: 2006 7 am: I got a message on my answering machine from my boss at MESware. The building was caught in a fire from the factory below us. I’m asked not to come to work.I’m calling him. He clearly is down. I’m telling him I’m comming anyway,we’ll figure out a way to work from someone’s home.I warn my wife, don’t count on me to help with our two small kids.I start to dis-assemble my home office.By 10 AM me and 4 college’s are working in one of thems home.We do warn our russian collegaue’s.

    My parents have a better home and are still togetherI learned to ask for helpFire at MESware 2006/02/27  first time there was a teamMan on the moon (Before the russians were winning the race fro SpaceBush used 9/ 11Stop the line

    A NONO is more then a skeptical

    A NONO is more then a skeptical

    A NONO is more then a skeptical

    We are one team we either trust eacher or not

    A sense of urgency will only become more essential

    Favorites, Groups & Events

    What I Learned From Burning Down My House - Presentation Transcript

    1. What I learned from burning my house…
      A Sense of Urgency
      Robin Dymond
      Innovel
      Yves Hanoulle
      PairCoaching.net
    2. About()
      Yves Hanoulle
      Robin Dymond, CST
      Project Coach
      Training, Coaching & Consultancy Services
      on agile & Team practices
      in EMEA.
      Certified Core Trainer
      Trainer, Management Consultant and Coach
      Training, Coaching organizations on Scrum, Agile and Lean.
      Certified Scrum Trainer
    3. You.About()
      Who are you?
      What makes you different?
      What do you know about agile?
      Other info you like to share?
      What would be the successful outcome of this course for you?
    4. Agenda
      • Intro
      • Complacency
      • False sense of Urgency
      • True sense of Urgency
      • Bring the outside in
      • Behave with Urgency every day
      • Find the opportunities in a crises
      • Dealing with NONO’s
      • Keep the urgency up
    5. General vs you vs agile
    6. Intro I: 1991/08/01 19:03
    7. Intro II
    8. Intro III
    9. Notes 1
      What were the ramifications of this devastating fire? For you, for the family? What did you lose? What did it cost?
      How does this accident relate to you? Were you complacent? Was it just an accident? How did it change you?
    10. Complacency
      Wiktionary:
      A feeling of contentment or self-satisfaction , especially when coupled with unawareness of danger or trouble
      Merriam-Webster:
      a feeling of being satisfied with how things are and not wanting to try to make them better : a complacent feeling or condition
    11. Complacency
    12. Complacency
      What is Complacency in Software development?
    13. Complacency
      • Manual build, manual testing
      • Not updating practises/Technology
      • Solo programming
      • Not fixing failing build
      • Complicated proces with # steps without value
      • That’s the way we work here
      • Not changing the organisation
      • Blame the messenger
    14. False Urgency
    15. False Urgency
      What is False Urgency in Software development?
    16. False Urgency
      • Many meetings
      • Heavy process with many approvals
      • Detail estimates for detailed requirements
      • Overtime for months
      • Many more meetings
      • Over assigning work to ensure everyone is 100% active
      • Check the hours instead of the results
      • Micro management
    17. True Urgency
    18. Bring the outside in
    19. Bring the outside in
      What is Bring the outside inin Software development?
    20. Bring the outside in
      • Visit your competitors
      • Learn ideas from other industries (lean)
      • Walk a mile in your customers shoes
      • Use your own software
      • Information Radiators all around the company
    21. Behave with urgency every day
    22. Crisis Coach
    23. Behave with urgency every day
      What is Behave with urgency every day in Software development?
    24. Behave wih urgency every day
      • Prioritized Product backlog
      • Daily Stand up
      • Limiting Work In Progress
      • Removing impediments
      • Sun does not set on a defect
      • Continous improvement
      • Stop the line
      • What’s the bottleneck today?
      • Measure time to market
    25. Find opportunities in a crises
    26. Find opportunities in a crises
      What is Find opportunities in a crises in Software development?
    27. Find opportunities in a crises
      Y2K
      Netscape problems  Mozilla
      Music Piracy  iPod
      Bug  First Unit test then fix
      Building software is hard  automate build
    28. NONO’s
    29. Ignore/co-opt
    30. Fire NONO’s
    31. Keep NONO’s Distracted and Busy
    32. Deal with NONO’s
      What is Keep them busy in Software development?
    33. Keep the NONO’s busy
      wedon’t think this works in agile
    34. Identify the nono
    35. Identify
      How can we identify the nono in Software development?
    36. Identify the nono
      Self-organisation
      Pair-Programming
      Co-located teams
      Make their behavior transparent to everyone
      Use social accountability and peer pressure to align
    37. Keep urgency up
    38. Keep Urgency Up
      How can we Keep the Urgency up in Software development?
    39. Keep Urgency Up
      Retrospectives
      Continuous Improvement
      Stop The Line
      What is the Bottleneck today?
      Customer collaboration
    40. Speed will only increase
    41. Leading Change
      A sense of urgency
      The guiding team
      Visions and strategies
      Communication
      Empowerment
      Short-term wins
      Never letting up
      Making Change stick
    42. Sources
      http://www.librarything.com/catalog.php?view=YvesHanoulle
    43. Free Lifetime support
      Twitter: http://twitter.com/YvesHanoulle
      SlideShare: http://slideshare.net/YvesHanoulle
      Linkedin: www.linkedin.com/in/YvesHanoulle
      Web:www.PairCoaching.net
      Blog: http://PairCoaching.wordpress.com
      Flickr: http://www.Flickr.com/YvesHanoulle
      Books: http://www.librarything.com/catalog.php?view=YvesHanoulle
      Mail : FirstName at Paircoaching dot net
      Mobile: +32 476 43 38 32
      Skype: YvesHanoulle
      Innovel LLC
      Robin Dymond
      rdymond@innovel.net
      www.innovel.net
      www.scrumtraining.com
      Americas: (804) 239-4329
      Europe: +32 489 674 366
    44. Thank you !!

    + Yves HanoulleYves Hanoulle, 2 months ago

    custom

    363 views, 0 favs, 1 embeds more stats

    This presentation is about what I learned from when more

    More info about this presentation

    CC Attribution-ShareAlike LicenseCC Attribution-ShareAlike License

    Go to text version

    • Total Views 363
      • 313 on SlideShare
      • 50 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 0
    Most viewed embeds
    • 50 views on http://paircoaching.wordpress.com

    more

    All embeds
    • 50 views on http://paircoaching.wordpress.com

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories

    Tags

    What's New

    © 2009 SlideShare Inc. All rights reserved.