Product Development Management - IAR061 Flashcards
What are the three basic goals with project portfolio management? Describe one method or tool per each that you can use in order to achieve these goals respectively?
Maximize value of portfolio
Net present value
Expected commercial value
Opting pricing theory
Scoring models
A strong link to strategy
Top down - e.g Strategic buckets
Bottom up - e.g Scoring models with strategic parameters
Achieving a balanced portfolio
Bubble diagrams
Portfolio maps
Histograms
Pie charts
5 Different ways to source needed technology
Internal R&D
Outsourcing
Licensing
Alliances
Aquisition
5 Different ways to source needed technology - What does companies use?
In the industry today, internal R&D is quite common because they want to keep control of the development process. They also want to keep knowledge and technology available to the company. Outsourcing R&D is however also common nowadays, and is also increasing by some companies, to be able to focus on their own projects and decrease development cost, often used in the software industry. Acquisition is common when the development process is rapid and technology is of crucial importance, then companies acquire knowledge from other firms.
Dominant Design
A dominant design is the one design that has won allegiance on the market . It´s a design that meets the requirements of most classes of users and where numerous of features are implicit. Most of the surviving competitors on the market will produce products that conform, or look very similar to the dominant design.
The process of a dominant design begins in the early invention stage where various designs are approached to create a new innovation, this is called the fluid stage. There is considerable uncertainty about the technology and its market. Firms experiment with different product designs at this stage. Then the new design is competing with other designs on the market where a dominant design then exceeds its competitors. The market converges towards the dominant design. After the dominant emerges the specific phase begins, where firms focus on improvements to the design and manufacturing efficiency.
Dilemmas and “trade-offs” in R&D Management
Competitors are ahead
Facing the dilemma of catching up with competitors who are already ahead and maybe have established a market or technology advantage
Cutting development cycle time
In order to respond to a rapidly changing market a company might want to shorten the development time and get a faster time to market. The dilemma is to still meet the quality demands and requirements but cutting a development process.
Projects budget can´t be held
Due to different factors, maybe delays or development issues, the project’s budget cant be held and the company faces a problem, whether to allocate more resources into the project or relocate or similar.
Short term vs Long term goals
Short term thinking may be beneficial due to instant financial impacts and success but may hinder long term innovation and future competitiveness. However the company may stay competitive for a longer while if they plan long term, but will not get immediate results.
Competitors are ahead
Traditionally functionally organized structures have a tendency to develop barriers to the necessary cooperation and integrations between functions. Discuss the underlying reasons for the existence of these barriers.
Competence
Culture
Organization affiliation
Status
Time pressure
Information availability
Geographical distance
Goals
Commonly used mechanisms that organizations use in order to overcome these barriers?
Organizational mechanisms: Up/down in the organization
Hierarchical authority: Setting clear organizational rules which describe who is in charge of what and who to answer to.
Rules, programs and procedures: Organizing and defining frameworks, tools, methods and procedures to work according to
Planning and goals: A clear planning of the project and clearly set-up goals that people from different functions can interpret on and work towards.
Narrowing span of control: In order to reduce uncertainty the span of control should be narrowed down. Less people directly below a manager -> Lower uncertainty and narrower span of control.
Lateral mechanisms: Between functions
Direct contact: Enhance the cross functional integration by direct contract between functions. Face-to-face contact on a daily basis instead of email.
Liaison rules: Setting up rules that apply to liaisons from different functions when working in cross-functional project teams.
Integration of roles: Enhancing cross-functional integration with integration roles from different functions: Roles that implies working within different areas creates ambidextrous roles that manage communication between departments and that becomes multilingual.
Task forces: Focused problem solving work groups that melades people from different functions
Cross functional teams: When property managed, projects carried out using CFTS can be done more effectively and efficiently CFTs involve people from different functions and encourage people to be involved in the project from the beginning and to communicate with all the other people (functions) within the team.
Matrix design: Designing matrixes (House of quality, pugh, gantt and so on) makes people from different functions intersect and constitute with their respective knowledge and perspective.
Platforms can be many things. Discuss three other views (except for components) of what a platform is, and the benefits to gain from each of these three views
Processes
In this context, the platform represents well established processes, workflows or procedures that a range of products or product families share and requires to design and manufacture or
assemble the product.
The benefits is that the processes etc are standardized which makes for an efficient development and production process
People & relations
The view here is that the platform consists of a network of people within or/and outside the organization. The products/projects are designed or managed by a standard group of people or by the same manufacturing people. The platform of the product is the people and their relationships.
The benefits is that the constant collaboration nurtures relations and creates easy knowledge transfers within the network
Knowledge & skills
The set of skills and knowledge that has been involved in developing a certain product or managing a project. The common platform is the knowledge shared which could have been obtained through similar training, education, mentorships etc. Design “know-hows” technology applications and production techniques, testing methods.
The benefits could be that it supports ongoing learning and developments, it also gives the product a competitive edge with a well established educated knowledge platform.
Stage-Gate Process
The stage gate process involves dividing the process into distinct stages, each having their own goals, deliverables and criterias for advancement. The gates act as decision points where the project is reviewed and evaluated whether the criterias are met and the project can move on to the next stage.
In the gate there are three parts:
Inputs - A prescribed list of deliverables that the project leader must present to the gate
Criteria - A set of hurdles, criterias or questions that the project is judged upon
Outputs - The decision to GO/KILL/HOLD/RECYCLE within an approved action plan.
The project receives funding allocated to the different stages, this means that the project receives funding based on successful progression. The underlying thinking for the process set up is to fund the project gradually as the project delivers and fulfills stated targets at different stages. The project leader is the one who should report at the gate meeting.
What does “Success Assured/verified concept” mean within the “Lean development thinking”?
All relevant knowledge gaps should have been closed, in the knowledge values stream, before you embark on a development project, the project value stream. Hence the uncertainty has been reduced to an acceptable level.
Elaborated
The lean principles aim to minimize waste, improve efficiency and increase success in product development.
Before initiating a development project, it is essential to ensure that all relevant knowledge gaps have been addressed and closed.
The primary goal of the “Success Assured/Verified Concept” is to reduce uncertainty to an acceptable level. In product development, uncertainty arises from factors like market dynamics, technology, customer needs, and competitive forces. By addressing knowledge gaps, you can reduce uncertainty and increase the likelihood of project success.
Mechanistic structure
A mechanistic structure is an organizational structure that is design so that individuals and functions behave in a predictable way and can be held accountable for their actions
Mechanistic structures have high formalization and standardization
Its good for operational efficiency and reliability
Minimizes variation
But may stifle creativity
A rigid and tightly controlled structure
High specialisation
Rigid departmentalization
Clear chain of command
Narrow span of control
High formalization
Centralized
Limited information network
Organic Structure
Flexibility and Adaptability: Organic structures are designed to be more flexible and adaptable to changing circumstances, both internal and external.
Low Formalization and Standardization: Unlike mechanistic structures, organic structures have lower levels of formalization and standardization.
Highly flexible and adaptable structure
Cross functional teams
Cross hierarchical teams
Free flow of information
Wide spans of control
Less formalization
Decentralisation
Encouraging creativity.
May cause low consistency and low reliability.
What is an “Analytical prototype?”
One key method/tool used in R&D is prototypes, however prototypes can be many different things. An analytical prototype represents the product in a non-tangible, usually mathematical manner for analysis. It’s a non physical form of prototype and can be used to perform mathematical simulations and analysis.
In “Lean product development” there is a clear distinction between the “knowledge value stream” and the “product value stream”. What does this mean, what is the difference between these two?
The knowledge value stream
To capture and reuse knowledge (markets, customers, technologies, product and manufacturing capabilities). The Knowledge Value Stream represents the systematic process of capturing, creating, organizing, and reusing knowledge and information critical to the success of a product development project
Gathering knowledge about customer needs, preferences, and market trends
Keeping up-to-date with the latest technologies
Understanding the product’s specifications, features, and design
Knowledge about the organization’s manufacturing capabilities
Product value stream
The Product Value Stream, on the other hand, is focused on the flow of tasks, activities, people, and equipment directly related to creating the actual product. It involves the practical steps needed to develop, design, and manufacture the product, resulting in tangible outputs. Here are key characteristics of the Product Value Stream:
Design and Development: This stream encompasses tasks related to creating product specifications, drawings, and bills of materials (BOM).
Manufacturing Process: It involves defining the manufacturing process
Resource Allocation: Determining the allocation of human resources, equipment, and facilities to carry out the product development tasks.
The product value stream deals with physical, tangible tasks and activities while the knowledge value stream deals with knowledge about the process/products etc.
What is SCRUM?
SCRUM is a framework used in agile project management and is widely used in the software development industry.
It includes sprints where the project is divided into fixed length time periods, typically lasting a few weeks, each sprint is a mini project with its own deliverables and goals.
The team has a scrum master which is the project leader and a development team working together to complete the work within each sprint