Skip to main content

David A. Koontz

A little about David in ObjectThink*
As a polymorphic instance OOConsultant, davidKoontz has taken on many roles for various instances of TechnologyCompany. Much of davidKoontz time in the CPU has been spent within the methods objectOrientedProgramming(), objectModeling(), agileCoaching(), xpPractices()... 
Before he became a CollegeStudent his father brought home an instance of the AppleComputer which had a BasicProgramFactory on which he taught himself to program, but not in ObjectThink.  As a CollegeStudent object his first association with ComputerClasswas in the fortranClass. The PunchCardRoom instances became a sink for much of his processing time. He was overjoyed at the ability of SophemoreClassStudent instances to work on the GreenScreen instances in the ComputerLab.
He received an instance of MechanicalEngineeringDegree from the universityOfNorthCarolinaAtCharlotte, having spent a good part of his educational hours in a one-to-many association with the ComputerLab.
* Inspired by About the Author section in Scott Ambler's The Object Primer.

After working in many roles and organizations searching for a great company culture David practices skills in mechanical engineering and software development as applied to engineering problems.  As the 1980s turned into the 90s the personal computer revolution had made it's initial mark in companies David found his computer skills out weighing the mechanical engineering skills, and the environment was much cleaner than the steel fabrication factory.  Teaching CAD/CAM and mentoring engineers in design and computer programming to manufacture for automations and production/assembly was an interesting role. David worked in the education industry for a while, returning to the University to work with Project Mosaic.  

Then into the contract and project world of professional developer as a software engineer.  Trying to find a company culture that understood design and the creative process of building software.

Later in life David moves into the Agile Software Development movement (circa 2004).
David is an Agile Transition Guide for organizations wishing to explore and discover their unique path to Lean/Agile software development. Previously a software engineer with 20+ years developing software solutions within a variety of industries. David uses his experience in group dynamics, systems thinking and the power of the Agile philosophy to unleash a team’s full potential. He enjoys mentoring individuals and coaching teams. David believes in empowering the team with self-organization, setting them on the path to achieve the team's purpose and providing them the proper intrinsic motivation to move the team along the productivity curve toward ultra performance. David has experience teaching Scrum and XP practices to multiple groups that evolved into Agile teams delivering quality software and value to customers.

David's Resume is available for download.

Most Popular on Agile Complexification Inverter

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?



Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, then yo…

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.

Introduction

Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

Do You Put “CSM” After Your Name?

I’ve noticed a new trend—people have been gaining titles. When I was younger, only doctors had initials (like MD) after their names. I always figured that was because society held doctors, and sometime priests (OFM) in such high regard that we wanted to point out their higher learning. I hope it was to encourage others to apply themselves in school and become doctors also. Could it have been boastful?

The Wikipedia describes these “post-nominal initials”:
Post-nominal letters, also called post-nominal initials, are letters placed after the name of a person to indicate that the individual holds a position, educational degree, accreditation, office, or honor. An individual may use several different sets of post-nominal letters. The order in which these are listed after a name is based on the order of precedence and category of the order. That’s good enough for me.
So I ask you: is the use of CSM or CSP an appropriate use of post-nominal initials?
If your not an agilista, you may wonder …

Situational Leadership II Model & Theory

Have you ever been in a situation where you thought the technique needed to move forward was one thing, yet the person leading (your leader) assumed something else was what was needed?  Did you feel misaligned, unheard, marginalized?  Would you believe that 54% of all leaders only use ONE style of leadership - regardless of the situation?  Does that one style of leading work well for the many levels of development we see on a team?

Perhaps your team should investigate one of the most widely used leadership models in the world ("used to train over 5 million managers in the world’s most respected organizations").  And it's not just for the leaders.  The training is most effective when everyone receives the training and uses the model.  The use of a ubiquitous language on your team is a collaboration accelerator.  When everyone is using the same mental model, speaking the same vernacular hours of frustration and discussion may be curtailed, and alignment achieved, outcomes …

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…