by David | Feb 27, 2018 | Architecture Definition, Business or Mission Analysis, Design Definition, Implementation, Stakeholder Needs and Requirements, System Requirements
In a previous post, Frank emphasized the challenges of product development and the importance of pre-planning and having an A-Team involved. We put his assertions to the test over the past 2 months by developing a product that allows a non-hazardous tool to be safely...
by David | Jan 23, 2018 | Business or Mission Analysis, Design Definition, System Requirements
We’ve been busy these past few weeks. In addition to helping customers improve their businesses, we’ve been working on a product development challenge. The challenge involves producing a new system that enables remote control from a hazardous area for a tool...
by David | Nov 28, 2017 | Business or Mission Analysis, Stakeholder Needs and Requirements, System Requirements
A few weeks ago I started the “Assess Your Schedule” series in response to a client who asked me what things I look for when I see a schedule for the first time. This week, for my final post in this series I’m going to talk about cost. Sorry, this is...
by David | Nov 22, 2017 | Business or Mission Analysis, Stakeholder Needs and Requirements, System Requirements
Last week, I talked about the importance of being diligent in breaking down engineering work with a WBS. I get kind of fixated on engineering because it’s at the start of any engineered-to-order system or new product development that I typically deal with. I’ve...
by David | Nov 14, 2017 | Business or Mission Analysis, Stakeholder Needs and Requirements, System Requirements
In last week’s schedule assessment tip, I talked about identifying and being wary of any activities that were longer than a week in duration. This week I’m going to address how I assess engineering work in a schedule. Again, my context is primarily drilling equipment....
by David | Jul 3, 2017 | Integration, System Requirements
As you enjoy your 4th of July holiday celebrations, please pause to consider some thoughts regarding safety. Like most systems engineers, we think of safety as an emergent property. Safety isn’t something you hold in your hands or decree, it’s a result. It results—or...
