Monday, August 22, 2016

The Black Sawn


  • First, it is an outlier, as it lies outside the realm of regular expectations, because nothing in the past can convincingly point to its possibility. 
  • Second, it carries an extreme impact
  • Third, in spite of its outlier status, human nature makes us concoct explanations for its occurrence after the fact, making it explainable and predictable.


The Scientific Method as an Ongoing Process


Friday, August 19, 2016

Talent Is Overrated Tips

How the Best Organizations Apply the Principles of Great Performance


  • Understand that each person in the organization is not just doing a job, but is also being stretched and grown.
  • Find ways to develop leaders within their jobs.
  • Encourage their leaders to be active in their communities.
  • Understand the critical roles of teachers and of feedback.
  • Identify promising performers early.
  • Invest significant time, money, and energy in developing people.
  • Make leadership development part of the culture.

Monday, August 15, 2016

Example of an "Open Defects" Graph


Top 10 Risks List About Software Projects


  1. Creeping requirements
  2. Requirements or developer gold-plating
  3. Released software has low quality
  4. Unachievable schedule
  5. Unstable tools delay schedule
  6. High turnover
  7. Friction between developers and customers
  8. Unproductive office space
  9. Unrealistic plan
  10. Low experience team

Planning Checkpoint Review


  1. Name of project's key decision maker 
  2. Vision statement
  3. Business case for the software 
  4. Preliminary effort and schedule goals
  5. Preliminary effort and schedule estimates 
  6. Top 10 Risks List
  7. User Interface Style Guide
  8. Detailed User Interface Prototype
  9. User Manual/Requirements Specification 
  10. Software Quality Assurance Plan 
  11. Detailed Software Development Plan

The Least Sophisticated Software Process


  1. Discuss the software that needs to be written.
  2. Write some code.
  3. Test the code to identify the defects. 
  4. Debug to find root causes of defects. 
  5. Fix the defects.
  6. If the project isn't done yet, return to step 1.

Software Project With and Without a Process

Without

With

Maslow's Software Project Need Hierarchy.


Estimative Variation


Conceptual Phases of a Software Project


Defects on Software Projects


Recommended Bibliography

  • Peopleware do Tom de Marco
  • The Mythical Man Month do Fred Brooks
  • The Psychology of Computer Programming do Gerard Weinberg
  • Thinking, Fast and Slow do prêmio Nobel, Daniel Kahneman
  • Predictably Irrational do Dan Ariely
  • The Upside of Irrationality: The Unexpected Benefits of Defying Logic do Dan Ariely
  • The (Honest) Truth about Dishonesty do Dan Ariely
  • The Lucifer Effect do Philip Zimbardo
  • Talent Is Overrated do Geoffrey Colvin
  • Descartes' Error: Emotion, Reason, and the Human Brain do Antonio Damasio
  • The Black Swan do Nassim Taleb
  • Fooled by Randomness do Nassim Taleb
  • Linked, the New Science of Networks do Albert-László Barabási
  • Six Degrees: The Science of a Connected Age do Duncan Watts
  • Everything Is Obvious: How Common Sense Fails Us do Duncan Watts
  • Sync: How Order Emerges From Chaos In the Universe, Nature, and Daily Life do Steven H. Strogatz
  • Chaos: Making a New Science do James Gleick
  • Nonlinear Dynamics and Chaos do Steven H. Strogatz
  • The (Mis)behavior of Markets do Benoit Mandelbrot
  • After the Gold Rush do Steve McConnell
  • Software Project Survival Guide do Steve McConnell
  • The Virtue of Selfishness de Ayn Rand
  • O Poder do Mito de Joseph Campbell