20 Common Logical Fallacies – Don’t Be a Victim!

The 20 Most Common Logical Fallacies

  1. Appeal to ignorance – Thinking a claim is true (or false) because it can’t be proven true (or false).
  2. Ad hominem – Making a personal attack against the person saying the argument, rather than directly addressing the issue.
  3. Strawman fallacy – Misrepresenting or exaggerating another person’s argument to make it easier to attack.
  4. Bandwagon fallacy – Thinking an argument must be true because it’s popular.
  5. Naturalistic fallacy – Believing something is good or beneficial just because it’s natural.
  6. Cherry picking – Only choosing a few examples that support your argument, rather than looking at the full picture.
  7. False dilemma – Thinking there are only two possibilities when there may be other alternatives you haven’t considered.
  8. Begging the question – Making an argument that something is true by repeating the same thing in different words.
  9. Appeal to tradition – Believing something is right just because it’s been done around for a really long time.
  10. Appeal to emotions – Trying to persuade someone by manipulating their emotions – such as fear, anger, or ridicule – rather than making a rational case.
  11. Shifting the burden of proof – Thinking instead of proving your claim is true, the other person has to prove it’s false.
  12. Appeal to authority – Believing just because an authority or “expert” believes something than it must be true.
  13. Red herring – When you change the subject to a topic that’s easier to attack.
  14. Slippery slope – Taking an argument to an exaggerated extreme. “If we let A happen, then Z will happen.”
  15. Correlation proves causation – Believing that just because two things happen at the same time, that one must have caused the other.
  16. Anecdotal evidence – Thinking that just because something applies toyou that it must be true for most people.
  17. Equivocation – Using two different meanings of a word to prove your argument.
  18. Non sequitur – Implying a logical connection between two things that doesn’t exist. “It doesn’t follow…”
  19. Ecological fallacy – Making an assumption about a specific person based on general tendencies within a group they belong to.
  20. Fallacy fallacy – Thinking just because a claim follows a logical fallacy that it must be false.

[Read more…]

Agile For All adds three new members to the team

gI_86400_petergreen-agileforall-announcement

Peter playing his trumpet!

In case you missed the press release, Peter Green, Adobe Systems Agile Transformation Leader, will join our Agile For All team on March 16th. I am personally excited about Peter’s amazing contributions to the Agile community and his enterprise level experience. I’m also excited to say that Peter isn’t the only one joining the team! See below for more details on all of the exciting news.

For those of you that don’t know him, Peter led a grass roots Agile transformation at Adobe from 2005 to 2015, starting with his own team, Adobe Audition. His influence includes the teams behind such software flagships as Photoshop, Acrobat [Read more…]

Be an Expert in a Year – Growing the Agile Way

The guys over at Expert Table Tennis had a great idea. What would it take to become an expert?

Dedication? Heart? Perseverance?

The Expert in a Year Challenge took part during 2014 and followed the progress of novice table tennis player Sam Priestley, as he attempted to go from beginner to expert in just one year and break into the top 250 players in England.

Sam (the subject of the experiment) has been playing recreational ‘ping-pong’ in his kitchen with his flatmates for a few months. He then decided to buy himself a table tennis robot to practice with. He then, with the help of his friend Ben Larcombe, started a challenge…

You can find the whole story here.

What I find most fascinating about this story is the fact that there is almost a universal truth in all of this: As we increase investment in experience, we will become (over time) more productive and efficient. 

This is at the heart of what we do here at Agile for All.

Agile for All Consulting Philosophy

  • Training – to start the agile adoption by setting up the framework which will be used. We like to teach Scrum as the basis, but we include many ideas from other agile processes and lean thinking.
  • Coaching – to cement the training into a permanently changed way of thinking and doing things.
  • Practice – continuously reinforcing the training with correct practices which lead to high quality results.
  • Patience – remembering that change takes time and also requires a settling of ideas into solid and repeatable patterns for the organization.

The practice and patience is where the organization is taking on all of the “hard work” in the sense that they must invest time in experience “being Agile” rather than just “doing Agile.”

I find, that one of the most powerful conversations I often have with people from all levels of an organization is around the art of possibility. Vision casting the (very much real) potential of the company to do great and extraordinary things.

It takes time, dedication, perseverance, and heart. The heart… that’s where we start.

Agile and Scrum training the Agile For All way

Take a moment to consider the last time you were in any sort of training environment. Were the tables set up “classroom style” so everyone faced forward in rows? Did the instructor read a lot of PowerPoint slides? Perhaps the room was even dark so everyone could see the PowerPoint better. Maybe you were lucky and you even had a workbook that was 500 pages long to go along with the training! <please feel free to gag at this point> Yes, we’ve all been there, and it’s horrible. It is one reason why many adults avoid any sort of educational opportunities – it’s just too horrible to ponder going through that again!

Well, people in our courses experience something completely different from what happens in a normal classroom. That didn’t happen by accident. [Read more…]

Life Change Starts with Clarity

Clarity starts with understanding YOU first... then the problem.

Clarity starts with understanding YOU first… then the problem.

There are moments where each one of us have wished for significant life change – this could be related to our current circumstances, our jobs, our vocations, our relationships, and even something about ourselves.

Our constant desire for improvement and life change is a natural consequence of being human as all of us desperately want to see forward momentum and progress. We want to see that “breakthrough” because there’s something within all of us that speaks to us deeply about how things today are not as good as they possibly could be.

As a result we’re willing to put ourselves at risk, to try new things and new relationships for the hope and the chance of obtaining that which we do not have yet but believe that we can have soon. That’s why the “self-help” and “self-improvement” industry is a billion dollar industry – in 2008 it was estimate that it would scale beyond $11 billion (and that was 4 years ago)!

Despite the changing economic tidal waves which we’ve all experienced the market is continuing to expand and grow. Although I’m not a fan of everything that I see sitting out on the shelves at your local Barnes and Noble I do encounter occasional gems that remind me why I love the industry that I’m a part of.

[Read more…]

Organizational Commitment: Pig & Chicken – Part 2

agile-safari-pig-and-chicken-part2

Many people really don’t like the original cartoon (See & read Pig & Chicken part 1). When I decided to do three strips on the Pig & Chicken, I knew there would be a lot of ‘concern’, but based on where I want to go, I made the decision that it had to be done. [Read more…]

Interesting Articles to Spark Ideas

I come across many articles that I think would be great to pass on to others. Most of them I try to post to Twitter, Linked In, or Google Plus (occasionally FaceBook). The issue with that approach is that they are lost to the social media wind. Knowledge baseThere are many book marking tools and ways to save links, but I’m going to give this idea a shot and see what happens. My idea is quite simple, I’m just going to add articles to this article. I’m going to put the date I added them and anytime I add a new one, I’ll update the post so it gets sent out again to subscribers (again only if there is a new article). Let me know what you think — I’d love to hear any thoughts, pro or con! [Read more…]

Why Project Retrospectives Are Challenging

Project retrospectives are challenging. I spoke a bit about this in lessons learned vs. project retrospectives. You might look at a merger, acquisition, implementation of a new ERP system, or even a major upgrade of an ERP or CRM system. These are non-reoccurring events. A retrospective of this type is quite different from a typical agile retrospective, primarily because on this type of project, people will change and the project will not repeat (the definition of a project is that it is a unique endeavor). At issue here is the fact that if the people will not be the same and the project does not reoccur – then they can’t come up with actions they will apply right away based on what they learned. Ideas for change often just end up in a spreadsheet, a book shelf, or some electronic tool. A big book of “lessons learned” that sits on the shelf gathering dust does not provide much, if any, value. [Read more…]

The Value of Planning Together

Yes! I love hearing great stories like this from our clients and students!

Yes! I love hearing great stories like this from our clients and students!

If you’ve taken part in any of our Scrum classes, then you know we highly value the power of face-to-face communication. The emergent power of real-time collaboration allows us to uncover one of the most detrimental nuances of the work we do in software development: ASSUMPTION.

We begin with the idea from the Agile Manifesto (principle #5), which reminds us that,

“The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.”

To be clear, at the end of the day, we can all readily agree that “the most efficient and effective method” … … IS face to face… so how do we deal with this in the real world? (And yes, I live there too…) [Read more…]

Agile Commitment — Classic Pig & Chicken (Part 1)

The Pig & Chicken is a cartoon that many in the agile community are familiar with. I know some will see it and ask, why is this one being rehashed (I know this because I reviewed it with a few people and they asked). Some will be quite annoyed, since many “strongly dislike” the cartoon (which is fine – please add your comments!). So, for anyone reading this and thinking any of those things, please read on. I’d like to say “don’t worry, I have a plan”, but only you can judge for yourself how it pans out!

agile-safari-pig-and-chicken-part1

What Is The Pig & Chicken Cartoon?

For readers who are not familiar with agile (or any agile folks who have not seen the cartoon), the ideas is that the pigs are the team (or Scrum Team). The chickens are everyone else. [Read more…]