Classic mistakes in product development
Requirements Managament & Stakeholders
Hidden or implicit requirements
Lack of stakeholder pain analysis
no systematic structure
No systematic documentation
Lack of functional coverage through use cases
No common notation
Lack of a synergetic model of the solution portfolio
Redundancies due to a lack of modularity or re-use
Highly complex dependencies
No systematic best practices
Lack of methodical competence- everyone does everything
Leadership
Micro-management
Projection of personal wishes as targets
Missing empathy
Drawers instead of individual promoting
Fixed mindset
No systemic mindset
No systematic best practices
Top Down mentality
Blame instead of learning
Lack of responsibility
System Architecture
No digital visualization, lack of a system model
Redundant Documents and graphics
No visual complexity management
Inconsistent or unavailable modelling
Lack of synergy management
No common notation
Immature separation of of layers (logical, physical, functional, etc.)
No systematic best practices
Process, Planning & Estimation
No estimation methodology
Lack of availability of historical figures based on experience
No tracking of risks and assumptions in estimates
Unrealistic planning driven by wishful thinking
No uncertainties buffers
No lifecycle view
Late prototypes being industrialized
Delayed process compliance
Quick wins before sustainability
No systematic best practices
Lack of explicit commitment
Finden Sie sich hier wieder?
Sustainable Product Engineering bringt Sie weiter.