Consultant Frustration Coefficient

Talking to Joey B this evening about creating a tool that would measure how frustrated you may become with wanting to mentor a team on Agile development practices. I am calling this the Consultant Frustration Coefficient.

What you would do is hand out a short questionnaire that would ask varying questions to assess the client’s value system and the staff’s literacy level as it relates to development pragmatic practices.

The result would look something like this:

  • Code: Staff shows a firm understanding of claiming to know OOP however certain frequencies indicate that staff view OOP as COBOL syntax with many function libs. Caution should be taken.
  • Design Patterns: Staff shows understanding of design patterns relating to UML documentation. All indicators are pointing towards an automated code creation and wizard driven setup culture. Caution should be taken.
  • TDD: Staff understands what Unit Testing is but does not understand why they should write test that QA should be writing. They do not want to use open source libraries. Critical deal breaker here! Extreme Caution!
  • Paired Programming: Staff indicators show extreme frustration with one another and would rather work alone in their cubicles on development task. Caution should be taken.
  • CI: Management indicators show reluctance to increased time spent outside of coding and server setup. Good luck getting it passed management. Staff may show resistance. Caution should be taken.
  • Agile: Staff has the probability of buying into it but management value system does not lend itself to embracing agile. Caution, you may be wasting your time.

CFC Rating: This project will pose extreme challenges and frustration for you. But it looks like all of your other opportunities right now so go with it!

Any other categories that we should collect? :-)

About Joe Ocampo

My personal philosophy is simple: "Have a good strategy that sets the environment for success through the enablement of the whole. Be agile but with a mind towards pragmatism. Delegate to the best qualified individuals, but don’t be afraid to involve yourself in all parts of a job. Treat everyone with respect, humility, and with a genuine pursuit towards excellence." Respected business and technical leader with expertise in directing organization towards effective results driven outcomes. Proven ability to perform and communicate from both technical and business perspectives. Strong technical and business acumen developed through experience, education and training. Provides the ability to utilize technology, harness business intelligence and execute strategically by optimizing systems, tools and process. Passionate about building people, companies and software by containing cost, maximizing operational throughput and capitalize on revenue. Looks to leverage the strengths of individuals and grow the organization to their maximum potential by harnessing the power of their collective whole and deliver results. Co-Founder of
This entry was posted in Humor. Bookmark the permalink. Follow any comments here with the RSS feed for this post.

6 Responses to Consultant Frustration Coefficient

  1. You might add some database–related ones such as this:

    Staff does not believe in the use of stored procedures and uses dynamic in–code SQL. [I've declined a project because of this once]
    Staff does not use primary keys, or indexes, or constraints on database tables. [I have a friend suffering though a project like this now]

  2. Jimmy Bogard says:


    Isn’t NHibernate dynamically generated SQL?

    How about this one: “Client believes typed datasets are the ideal data access layer”


    “Ex-developer, now manager still holds sway on technical decisions”

  3. @bogardj:

    Well, what I really meant was SQL statements which are hard–coded in the source code and concatenated with variable values at run–time.

  4. Jimmy Bogard says:


    Ah, I see! So no understanding of SQL injection attacks, fun fun! :)

  5. Donn Felker says:

    Well said… I can’t count how many times I’ve been in this situation. :)

  6. Joe Ocampo says:

    The unfortunate reality is that we are always encountering this. :-)