Have you ever heard this before at work? Can you do me a favor? As I was leaving a work place one day, I overheard a gentleman on the phone talking to what certainly sounded like a co-worker. Upon termination of the call he was tetchy. He started with, “nothing is too difficult for the […]
After we have identified the objective and the preferred delivery mechanisms we will set about building the training. We will consult subject matter experts, and put material together. That material will include: Develop Training Material Course Objective and Description Rubric Lesson plan (including formative assessment questions) Presentation, application exercises and practice material Student material (perhaps […]
In our previous post we discussed training needs tied to the organization’s objectives. In that work, we uncovered the scope of the needed training to address specific areas for improvement with very specific metrics identified. The discussion and subsequent research of the objectives also provided us with input to help ascertain the best delivery mechanism. […]
Training development follows similar set of processes or activities as product development. First and foremost we must know what we are trying to achieve. What is our scope? What is our ultimate objective? Those same steps we use to evoke the requirements or our product targets for our training requirements. The objectives of our training […]
I have been brought back to this topic many times over the past few months. Hits production is sort of like “hitting the fan.” We release our product after development and then put our fingers in our ears hoping to not hear the metaphoric explosion at the plant. It is no wonder. We have the […]
The team works toward an objective of developing and releasing software according to a schedule. The delivery date comes, and the team has not achieved the objective. The project manager is at a loss for words. What happened? The team then informs the project manager – “we always said the time was tight”. The team […]
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 […]
The daily sprint meeting has connections to our risk management as well. We have seen from the previous posting the fact we are having the meeting daily can hasten our project’s (system’s) ability to respond. The sprint master is now asking about the obstacles or impediments to achieving the objectives of the sprint. Impediments and […]