Value, Scope and Change Requests
Change requests are part of any development project. Change requests are sometimes necessary as we learn by building and doing the work. In my experience, change requests often are born from requirements we thought we understood, only to learn by working with the product or system that we really did not have enough understanding to be able to record this in the form of specifications. We think we are making things better when we spend an abundance of time documenting the requirements, at least those requirements about which there is uncertainty. That is not to say this is not a worthwhile endeavor, we have been in product development long enough to know there are downsides to delivering a product that has no associated documentation. The testing and manufacturing portions of the work will make use of these requirements documentation and the errant or lack of documentation makes the work of these areas and more difficult … Continue reading
Business is predicated on providing value to the customer, but it does not end there. The business itself needs to see value in the work, so this is really a value chain that is only as strong as the weakest link. If the value to the customer is too low or not existing, no customers will purchase the product. If the value to the business from the product is too low, there will be no investment
What is value
Value is the difference between the utility received and the cost for things.
Value = Utility – Cost
Value = Benefit – Cost
The utility may be customer dependent, but this must be understood, as this will drive the subsequent work. Not knowing what the customer values, clouds how we approach the work. We will write more about the conundrum later. It suffices to say no value to the customer means no value to the business, … Continue reading
My first job out of university was with a small product development and manufacturing company. The company developed their own embedded products for sale all over the world. I do not know how this collection of technicians and engineers ended up as a tight or as close when it came to work. The group was a collection of characters. The other electrical engineer, we will call Flicky (we had secret names for each of the team members). There was one technician we referred to occasionally as IR because of the unfortunate anagram is name made. There was a mechanical designer we referred to as BWI, I will explain that later. There was another assembler / technician we referred to as Wal.
Games with the Team
When it came to the electrical or embedded product idea generation and development, I can recall a game we played. We would read the specifications together, asking questions where we could of the sales … Continue reading
Queuing theory is the study of waiting lines and is associated with business in determining resources needed to achieve service business throughput objectives, but it does not just apply to services and material handling.
Queuing Theory and Billable Hours
I have worked at companies that had a target for billable hours, that well in the 90%. That is, 90% or more of the hours the employee worked, had to be assigned to specific project work. The organization treated the time an employee was at work and available to work on specific projects, at nearly 100%, so for example, in a 40-hour work week, it was expected that 36 hours or greater were dedicated to specific project activities. This was recorded in the project schedule.
Queuing Theory and Product Development
The impact of queues on product development and knowledge management in general is explained well in this Harvard Business Review article a snippet of which is found below:Continue reading
Poor Process or Poor Execution
I have used both conventional approaches to projects, as well as agile. In fact, i have used some of the agile techniques in conventional projects with success. I know, anecdotal but perhaps an interesting anecdote.
Conventional projects have had considerable high failure reported (Standish Group Studies for example). The problem become, why these conventional projects fail. For example, I have been on projects where the project manager is seldom seen, where conventional project processes are ignored or executed poorly. There can be many reasons for failure, poor process, poor execution or poor strategy, can end in the same failure. It is like a play in football, if the offense executes it well, we may get a touchdown. If we have not play, or execute a good play poorly, we might fail in both cases.
So the question becomes what is the root cause of the failure? For example, I wonder how the strategy was selected for … Continue reading
What does not work -duration
Besides wasting time planning out many months into the future as if we could see and control that far ahead, there have been studies over the years that have established an inverse correlation between the length of time a project runs and project success rate. Perhaps this does not sound so odd, given the more tasks we have or the more work we must do, the greater the risks. Consider a product and the opportunities for failure, the more parts, the more opportunities for failure or more failure points.
There is no silver bullet when it comes to product development. However, there are some things that studies tell us what does not work.
First, the planning and long-term project or treating the job like we know the details 6 months to 3 years in the future. There are studies from the Standish group that illustrates the project s longer than 6 months in duration have … Continue reading
(Lexington, NC, September 28, 2018) – Cognitive biases are always at work, playing dirty tricks behind our perceptions. Jon M. Quigley, Founder and Principal, Value Transformation, will address this issue in his latest presentation, “Things that Secretly Sabotage your Project and Team” to be held on Thursday, October 4, 2018 from 07:00 pm to 07:50 pm at Turbine Hall, Winston-Salem, North Carolina.
Project managers and teams of all organizations have experienced this common conundrum: their team members are capable, intelligent and well equipped, yet do things that appear to make no sense. The signs of bias at work here are hard to see, but that is most likely the case.
In his talk, Jon Quigley will reveal how cognitive bias impacts work, the most common biases we are likely to be affected by, and how they influence selection of strategies, team development, and other areas. The takeaway from the session will include ways to transform a group of … Continue reading