Categories
-
Recent Posts
Tag Archives: derived requirements
Decisions have consequences!
My wife and I recently returned from 12 days in Hawaii where we celebrated 40 years of marriage. I was very disciplined to avoid doing any real work during that time, rather concentrated on enjoying the sensory overload that the … Continue reading
Posted in Decision Concepts
Tagged consequences, decisions, derived requirements, implementation tasks, opportunities, risks
Leave a comment
A 3V Traceability Model
I’ve written numerous posts on decision-to-requirements traceability based on the fact that decisions are the creators and consumers of requirements. Consistent with this, I use a 3V (or 3-Vee) model of traceability that is best represented by a 3-D model … Continue reading
Posted in Decision Concepts, Decision Driven Product Development
Tagged continuous improvement, decision analysis, derived requirements, design decisions, learning cycles, learning organizations, modeling, product development, requirements analysis, requirements derivation, requirements management, requirements traceability, systems engineering, test planning, trade study, V-model, Vee-model, verification
Leave a comment
Decision Driven® Information Architecture
Many of my previous posts have described the relationships among various types of knowledge: decisions, criteria, alternatives, requirements, risks, plans, etc. There’s method (actually science) to my madness; here’s the Decision Driven® Information Architecture that I believe illustrates how decisions … Continue reading
Posted in Decision Concepts, Decision Driven Innovation, Decision Driven Product Development, Decision Driven Strategy
Tagged alternatives, analysis tasks, criteria, decision, decision context, decision data, derived requirements, implementation tasks, information architecture, information model, issues, knowledge management, models, opportunities, opportunity growth, performance estimates, product development, requirements, risk mitigation, risks, strategy, systems engineering, traceability
Leave a comment
Failure to manage decision consequences
Everyone believes that decisions have consequences, but many fail to proactively manage them. You can make a great decision, select a great alternative and still fail during execution. Here are a few examples of common “failure to follow-through” decision faults: Next … Continue reading
All requirements are derived requirements
Every requirement that you will ever face can be traced to an upstream decision; all requirements are derived requirements. I used to offer students in my Decision Driven® Design workshops a large cash prize if they could name a requirement that … Continue reading
Accelerating new product development
There’s no quick fix for accelerating the development of a new product. That’s because your organization has a baseline (existing, current) capability for product development that is comprised of a mix of existing solutions, people, process/methods, tools and knowledge assets. If … Continue reading
Posted in Decision Concepts, Decision Driven Product Development
Tagged acceleration, capability roadmap, decision quality, decision rationale, derived requirements, forward engineering, learning cycles, massively parallel thinking, new product development, NPD, platform, platform engineering, product development, product functions, reuse, reverse engineering, scalability, time to market
Leave a comment
Managing decision interactions
A Decision Breakdown Structure (DBS) for any complex strategy, system or project is a way to decompose the situation into well-framed, loosely-coupled, bite-sized and manageable “thought packages“. Each decision “node” within this structure is a well-framed “fundamental question or issue that demands … Continue reading
Posted in Decision Concepts, Decision Driven Innovation, Decision Driven Product Development, Decision Driven Strategy
Tagged constraints, criteria, critical path, cross-constraints, decision dependencies, decision interactions, decision network, decision tree, derived requirements, lean processes, lean thinking, NPV, pareto's law, problem domain, project management, roadmaps, solution space, strategy, systems engineering, thinking breakdown structure, traceability, trade space
1 Comment
Control requirements volatility with decision baselines
Requirements volatility is one of the classical problems encountered in systems engineering and new product development. Changes in requirements that occur or are discovered after the design has started can lead to costly delays, rework, project cancellation or even failures … Continue reading
Posted in Decision Concepts, Decision Driven Innovation, Decision Driven Product Development, Decision Driven Strategy
Tagged constraints, decision baseline, decision network, decision pattern, decisions, derived requirements, product development, requirements, requirements baseline, requirements volatility, root cause analysis, systems engineering, traceability
Leave a comment
Decisions bridge innovation and execution
I’m kicking back this afternoon watching the Masters tournament. I’ve already seen 4 or 5 commercials from IBM poking fun at an overemphasis on innovation techniques (talking) at the expense of execution (doing). I’m sure this rings true to anyone who … Continue reading
Posted in Decision Concepts, Decision Driven Innovation
Tagged alternative, criteria, decision, decision network, derived requirements, evaluation, execution, implementation, innovation, out-of-the-box thinking, project plan, risk mitigation, task, thinking breakdown structure, work breakdown structure
Leave a comment
Decision Driven® Solutions Blog 