Perhaps some of you recall our post on project commitment. We have a continuation of that story now that is revealing.  In that post we saw how not communicating clearly about actions that could possibly happen or actions that were not even remotely possible can put our project at risk.  In that post, we show […]

When I was but a young engineer, I was developing an embedded product for a small organization whose product line went all over the world.  Partially through the development of the product, a new permutation became needed. The owner of the company, also an Engineer that at one time did work for NASA, asked me […]

Like the Ishikawa Diagram, the Histogram can serve us well.  The histogram allows us to visualize the trends based upon a category.  It is a graphical distribution of data, in the example below we see the distribution of the duration to prepare an incoming vehicle to be a suitable device to put under test out […]

Continuing with our communications theme and agile methods, we discuss the question, “what did you do yesterday?”  This simple question places a check in a few project management boxes starting with the mechanism for the control of the output – specifically the feedback portion of our project control system.  Learning what happened yesterday (coupled with […]

Another beneficial attribute of Agile, particularly Scrum, is the daily sprint meeting. In this very short and focused meeting that includes the immediate project team and as needed the sponsor, we will learn much about the state of our project. The questions three that are up for discourse are: What did you do yesterday? What […]

We like this saying: The problem is solved by the person feeling the pain; we see much merit in it and believe it to be an axiom. We have touched upon this a bit in our blog on sponges. We see areas where one part of the company or development process makes due or improvises […]

The customer is the receiver of the output; the customer can be an internal end customer or an intermediary to the next “chain” of events on the way to the final customer. Ultimately, we are aligning our actions (Suppliers, Inputs, Processes, and Outputs) in a way that provides the biggest benefits for our final customer. […]

To go on further with the output discussion, we need to make sure we have an understanding of indicators.  Indicators inform us what is going on. My stomach growling is a pretty good indicator that I am hungry, and sweating while mowing the lawn is a good indicator I will need a refreshing beverage upon […]

How do we know when our output is successful?  Well, when the customer takes acquisition can be the first tangible evidence for many organizations the output is “good”.  So we know what we mean by good, I provide a brief list: capabilities of the output can be deployed suitable quality (Key Product Characteristics are met) […]

Our organization’s structure can confound what constitutes and output.  Consider the company that is structured as a “functional” organization, the output from one group will typically go to another group in the system.  This organization structure is sometimes referred to as “silo” since each part of the company, group or department is segregated by expertise.  This has […]