Clearly Specifying Quality

December 29, 2002 by · Comment
Filed under: Process, Quality 

One of the most difficult things to do in software development (if observation of projects across the industry is any indication) is clearly specifying the system needs from the quality perspective. Functional specifications are often incorrectly labeled as the complete specification for the system, or attempts at specifying the quality side degrade to untestable statements such as “The system shall be user-friendly.” Worse yet, attempts to simply reuse quality specifications from existing systems can result in serious consequences from under-specification, or unachievable goals from over-specification of quality. Read more

Steady Focus at a Higher Level

December 1, 2002 by · Comment
Filed under: Leadership, Quality 

I attended a panel discussion last week where the topic was how Dell has managed to overtake Compaq, and stay on top in such volatile times. There were many reasons offered up from the panel, and indeed, to stay atop any sector of the technology field one would have to excel in several areas simultaneously. While doing nothing innovative on the product front, Michael Dell has continued from the days in his Texas Dorm room to excel in both customer intimacy and business excellence. Read more

  • Search by Topic

  • What’s Happening

    January, 2018 – A workshop series to help you develop resilience in the workplace and in your life!

    Next open enrolment sessions start soon – contact us to get involved!

  • On The Road Again

    Jim frequently travels across Western Canada for engagements, and welcomes opportunities to meet, run a workshop, Diagnostic or Lunch and Learn session.

    Contact Jim if you would like to connect around any of the upcoming dates:

    • January 17-19 – Calgary, AB
    • February 6-8, 2018 – Lethbridge, AB
    • February 10-11, 2018 – Edmonton, AB
    • February 21-23, 2018 – Edmonton, AB
    • March 7-9, 2018 – Saskatoon, SK
  • What People are Saying

    If your desire is to effect change or have more influence on a software team, you could either stumble around in the dark for a few years, experimenting with different techniques, or you could buy, read, and apply the techniques in this book. This choice, of course, is up to you.

    — Matt Heusser