Lean and Agile practices for hardware product development and engineering
Apply the relatively new Agile Way of Working to areas beyond software and learn how to harness the power of Agile/Lean methodologies to develop hardware products and products involving both software and hardware.
In the Agile for Hardware training, you will learn how to use the newest Lean/Agile methodologies to drastically reduce your time to market, acquire flexibility and respond to changes in requirements and markets with ease. You will also learn how to improve the quality of your products, ignite innovation, achieve predictability, boost close collaboration among technical and business people and increase employee engagement and satisfaction.
The training combines theory with real world cases to help the participants find out how they can apply the principles and methods in their own context.
During this two-day course you will learn about:
- The principles of Agile and Lean
- Responding to Change
- Fast Learning
- Waste Reduction
- Build in Quality
- Continuous Improvement
- Incremental and iterative product development, Kanban and Scrum
- Learning how to apply them in non-software contexts.
- Product agnostic
- Designing for Agility
- Modular Product Architecture
- Set-Based Design
- Model-Bases System Engineering
- eXtreme Manufacturing
- Hardware MVP development
- Lean-Agile Project Management
- Working with external vendors and suppliers
- How to partner up with external and internal vendors and suppliers to develop complex products and solutions in an Lean-Agile manner
- Agility and compliance and audits
- Meeting regulatory and industry standards and delivering high-assurance systems
- Agile quality assurance
- Scaling up agility and managing complexity
- Developing complex systems that need numerous teams to cooperate.
- Implementing Lean Portfolio Management to harmonize the organization’s strategy, initiatives and teams.
- Enabling the organization to apply Lean/Agile forecasting and capacity management to deliver with highest possible throughput.
Attendees who pass the certification exam will receive:
Certification for Certified Hardware Agilist (CHA) bestowed by Blinklane.
About the trainers – Agile for Hardware
Ali Hajou has experienced the advantages of iterative product development that include the development of hardware and software components in the pharmaceutical industry, the semiconductor industry, and more. Ali helped them find their own Agile Way of Working, as ‘the standard practices’ do not always apply ‘right out-the-box’.
Davar Azarmi is a multidisciplinary professional with more than 16 years of experience in variety of IT and business roles. He is proficient in areas such as strategic management, IT management, change management, software engineering, lean and agile methodologies and data analytics. He has supported a microchip producer to adapt Agile way of working at scale. As a result, they improved their quality and time to market drastically and managed their budgets and resources better.
Watch an Aftermovie of the last Agile for Hardware 2019 conference by clicking below. Follow the website for announcements: www.agilehardware.eu
Each course day starts around 9:00 and ends at 17:00 hours, including lunch and intermission.
- Lean/Agile Fundamentals
- Designing for Agility
- Hardware MVP development
- Agile Project Management
- Working with External Vendors and Suppliers
- Lean/Agile and Compliance
- Scaling Up Agility and Adding Complexity
No prior knowledge of Agile is required.
This course is intended for people who are involved in developing hardware products and products that combine both software and hardware. It includes, but is not limited to:
Referred industries include, but are not limited to:
- Period 2 days
- Maximum number of participants:18
- Level:Awareness, Foundation, Advanced
- Lunch included:Yes
- Payment methods:Invoice, iDEAL, CreditCard
Graham Brackley - Rating: 8/10
Practical exercises for key points were very good. Learning objectives could be a little clearer defined perhaps and key features such as points instead of time units justified to help understanding/onboarding. Where Agile works, where it doesn't work so well. A clear method to develop costing and time needed when a project with unique features is being bid or started.
Auke Anema - Rating: 8/10
During the course the other course takers had some questions on certain subjects with applying the material on hardware projects. But then again the majority of the course can be used for running hardware projects
Désirée Queren - Rating: 7/10
It's very good to have expierences shared with exemplary companies. This was done good, of course considering that there are not soo many companies available yet specifically in hardware. There were different procedures on how to implement or transform or up to which degree changes could be implemented, especially considering early start of transformation vs later. This is a very helpful approach. Regarding managing external partners as well as budgeting the topics were covered very briefly only, of course also recommending literature. Of course this will be company dependent, but it would be great if there are more specific examples on how this could be achieved as a total. So not to only focus on the development (R&D) part only, but to consider the full business.
Scott Bogner - Rating: 9/10
Overall it was great! There was a lot of data packed in the two days and I felt a bit overloaded the last hour or two of the last day.
Ben Ferguson - Rating: 9/10
Overall excellent course. Very densely packed however, so by the end of the second day, could kind of tell that people were starting to struggle a bit. Maybe did need to be that densely packed just to get all the info in. Feedback that we already talked a bit about during the course was surrounding the exercises - it did put quite a bit of pressure on one person that the value mapping was based around. Could a pre-defined example be used - so all people can concentrate on learning the agile concepts rather than having to think up the detail to put on the post-its? Pros and cons are clearly there as we discussed. But worth recording somewhere. Some examples were used to try to help describe concepts (experience from NXP or ASML or whoever) which at certain times were good - but sometimes didn't quite hit the mark and maybe went into too specific details or too specific people even which made it almost harder to understand what was trying to be explained without the full picture that you guys have. Discussions which arose were all pretty good.