Hans Samios' Personal Lean-Agile Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools

Trace:
james_tamm_-_want_better_collaboration_dont_be_so_defensive

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
james_tamm_-_want_better_collaboration_dont_be_so_defensive [2015/08/17 09:21] – hpsamiosjames_tamm_-_want_better_collaboration_dont_be_so_defensive [2020/06/02 14:21] (current) – external edit 127.0.0.1
Line 1: Line 1:
-====== Premise ======+====== James Tamm - Want Better Collaboration Dont Be So Defensive ======
  
-In this talk we’ll look at why the technical practices of test-driven development, refactoring, continuous design, clean code and automated testing can help you and your organization be great. This talk is not just for the technical people. Business people need to understand that they cannot have a great product and productive team without technical excellence. 
  
-Technical excellence is more than two week sprints, a burn-down chart and a daily stand-up meeting. The basic rules of Agile or Scrum are not an end in themselves, but rather a staring point based upon principles and practices that allow and encourage teams to adopt, adapt, and refine their craft. Unfortunately, it too often seems that agile is just another micro-management approach. +====== Premise ======
- +
-Extreme Programming, the spur under the saddle that started this wild ride, is based on sound technical practices. Why do so few employ the engineering practices that are designed to support the tight iterative cycles of Agile and Scrum? The founders of Scrum expected you to pull in the engineering practices. They figured that once the continuous improvement cycle revealed the problems of poor product quality, hard to change code, wasted time debugging, long stabilization efforts and the ever growing burden of manual test, you'd hunt for solutions. Come to this session and see why you can't be great without technical excellence. +
- +
-====== Summary ====== +
- +
-  * Content rating (0-no new ideas, 5 - a new ideas/approach, 9-new ideas): 6 some new ways of thinking about things +
-  * Style rating (0-average presentstion, 5 - my level, 9-I learned something about presenting): 4 bitty +
- +
-====== Action / Learning ====== +
- +
-  *  +
- +
-====== Presentation ====== +
- +
-====== Notes ====== +
- +
-Book "the debrief imperative" Murphy +
- +
-Scrum, instead of PDCA people just to A +
- +
-Agile 10 year anniversary in Snobird +
- +
-  - Demand technical excellence +
-  - Promote individual change and lead organizational change +
- +
-Symptom is hardening sprint Does this degrade into a firefight +
- +
-Being good at chasing bugs does not mean technical excellence +
- +
-Propose a marriage of scrum and XP +
- +
-Certified scrum developers 55K vs 300K certified scrum masters +
- +
-How are you spend your time mr developer Coding, testing, debugging +
- +
-Debug later programming vs tdd +
- +
-Longer time it takes discover a bug, increases time to find it in the code. Time to fix is short. +
- +
-We create the bugs. We did it. +
- +
-We have a problem +
- +
-People do what they know I've got 10 years experience - the same year 10 times doesn't count +
- +
-XP +
- +
-Talks about values - simplicity, respect, feedback Practices help Dijkstra - not waste time debugging, should not put defect in +
- +
-If we move test upstream could we get working features to flow +
- +
-Tdd is not so much test first and test together +
- +
-Changes the physics of the mistake. +
- +
-A complex system that works has evolved from a simple system that works +
- +
-Book systems bible - John Gall +
- +
-Why not do automated test at module level. 3 modules means all tests would take 1000 tests Unit test strategy 10 units test per module plus a few of of the interactions +
- +
-Orgs are set up to assuming amount to test is same to create - we know as fixed resources +
- +
-25% defects introduced while changing and fixing code. Means 75% were introduced new code +
- +
-Because systems act up we have to be careful +
- +
-Cannot just what was done in previous iteration, as have to test what we did in the past Unsustainable growth in the untested code gap +
- +
-Tests must be automated Cost of retest is low +
- +
-Tests is not all there technical excellence +
- +
-Two values of software Want to be able to evolve our code +
- +
-Refactoring 3 critical skills Smell bad code and recognize why it is bad Step wise refinement of code. Requires tests. +
- +
-The lawyers are coming Toyota brake problem was caused by single bit flip in the code +
- +
-Why doesn't team use tdd and refactoring +
- +
-Won't work for us +
- +
-Stories are optional until we are late You are all special But it doesn't matter +
- +
-Find a way to get the product shippable +
- +
-It is hard +
- +
-Don't have time compared to what? +
- +
-Michael Dubakov looking at optimize development speed Green help. Red detracts. Yellow could have effect either way +
- +
-No wonder we have any time +
- +
-Tdd is faster than debug later programming +
- +
-Fun - working proactively, getting things done +
- +
-Scrum masters Make sure your team knows about these state of the art practices Support learning, problem solving and continous improvement Make sure org understand what is important Not dogma followers +
- +
-Developers Become expert in your craft Build trust - make your work visible Learn and try things Become advisor to org Become aware of limits of org Pair +
- +
-Managers Stop motivating people +
- +
-Motivating people is hard, demotivating is easy +
- +
-A programmers life Work, home, play, sleep - we always think about code. Title: JamesTamm-WantBetterCollaborationDontBeSoDefensive Timestamp: 2015-08-07 16:02:46 +0000 Created: 2015-08-07 11:16:55 +0000 Last Accessed: 2015-08-07 11:16:55 +0000 Times Accessed: 0 Tags: Metadata: gpslongitude=-77.017185,gpslatitude=38.781725 # Premise+
  
 Jim's keynote will challenge you to look at yourself through self-critical eyes. Entitled "Want Better Collaboration? Don't be so Defensive!", Jim will discuss skills essential for effective collaboration. In particular, he will focus on achieving success even during difficult interactions. He will show how your own defensiveness is a key factor in resolving conflicts and building collaboration. He will share practical tools designed to help you manage your own defensiveness. Jim's keynote will challenge you to look at yourself through self-critical eyes. Entitled "Want Better Collaboration? Don't be so Defensive!", Jim will discuss skills essential for effective collaboration. In particular, he will focus on achieving success even during difficult interactions. He will show how your own defensiveness is a key factor in resolving conflicts and building collaboration. He will share practical tools designed to help you manage your own defensiveness.
Line 121: Line 12:
 ====== Summary ====== ====== Summary ======
  
-  * Content rating (0-no new ideas, 5 - a new ideas/approach, 9-new ideas): +  * Content rating (0-no new ideas, 5 - a new ideas/approach, 9-new ideas): 7 
-  * Style rating (0-average presentstion, 5 - my level, 9-I learned something about presenting):+  * Style rating (0-average presentstion, 5 - my level, 9-I learned something about presenting): 6 
 + 
 +Useful presentation that helped me personally. And well presented with interaction.
  
 ====== Action / Learning ====== ====== Action / Learning ======
  
-  * watch - Ted talk +  * [[http://agilealliance.org/resources/learning-center/keynote-want-better-collaboration-dont-be-so-defensive|Keynote Speech]] 
 +  * [[https://www.youtube.com/watch?v=vjSTNv4gyMM|Watch Tedx Talk if cannot get to original]]
 ====== Presentation ====== ====== Presentation ======
  
Line 210: Line 103:
 Start noticing if in red zone / green zone Look for defensiveness Practice your action plan Start noticing if in red zone / green zone Look for defensiveness Practice your action plan
  
 +{{tag>Collaboration Conference}}
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/james_tamm_-_want_better_collaboration_dont_be_so_defensive.1439828513.txt.gz · Last modified: 2020/06/02 14:27 (external edit)