Specification as Programming: How to Talk to your AI Collaborator

If prompts are ephemeral specifications, and specifications are persistent prompts, then specification is the new programming.

This workshop explores a radical shift in how we think about AI-assisted development. Instead of writing code and hoping AI helps, we focus upstream: crafting specifications so precise that code generation becomes almost mechanical.

Through focused exercises, you'll learn:

• Specification structures that AI can execute reliably.
• Techniques for systematic requirement drilling (from vague intent to executable spec).
• How to use AI itself to help elicit and refine specifications.

This isn't about abandoning coding skills—it's about playing to each party's strengths. LLMs generate code fast, but are myopic and quickly get out of their depth. Humans are slower at producing curly brackets, but far better at navigating complexity, ambiguity, and long-running contexts. The leverage shifts to defining what should be built, precisely—and letting AI handle the implementation.

Go to Session

Garbage In, Quality Out? Mastering Agile Product and Portfolio Management in Embedded Systems Development

In the embedded systems industry, technical prowess often takes center stage. Yet, in my observation, many projects falter not because of engineering challenges, but due to shortcomings in product and portfolio management. This talk examines how these crucial aspects have become a significant vulnerability in numerous embedded systems projects.

We'll look at common pitfalls in product and portfolio management, their ripple effects throughout project lifecycles, and practical strategies to address these issues. The discussion will cover implementing agile methodologies tailored for embedded systems, aligning product vision with market demands, and harmonizing portfolio decisions with broader corporate strategies.

Drawing from real-world examples, we'll explore how effective management practices can steer challenging projects towards successful outcomes. Attendees will gain insights into transforming potential project pitfalls into opportunities for delivering quality embedded systems, even when faced with difficult starting conditions.

Go to Session

Scaling Agile Development in Large-Scale Embedded Projects

This presentation dives into the nuances of applying agile methodologies in the complex and demanding field of large-scale embedded systems. This talk is specifically tailored to address the multifaceted challenges that professionals face when scaling agile practices in large-scale projects, ranging from the technical (what does a multi-team embedded CI/CD pipeline look like?) to issues of team structure and product architecture.

The first part of the presentation lays the groundwork by exploring the fundamental principles of agile development and the common challenges encountered when scaling these methodologies in large-scale projects. It sets the stage for a deeper exploration into the specific challenges and solutions pertinent to embedded systems development, a field characterized by its unique blend of hardware and software integration, functional safety issues, and often complex regulatory requirements.

The talk then transitions to a focused discussion on the integration of agile practices in embedded systems. This includes an examination of how DevOps, as one of the many strategies in agile development, can be effectively implemented in such environments. The aim here is to provide attendees with actionable insights and strategies that are specifically tailored to the unique environment of embedded systems.

Lastly, we lead the conversation back to the agile mantra of focusing on value – which is easier said than done. The talk introduces the concept of value streams to understand who takes part in value creation, and how, and extends it to value loops – explicitly closing feedback loops to enable pursuit of value.

The attendants should gain understanding of the challenges of scaling agile to larger endeavors, and what to pay attention to in order to be successful.

Key Topics:

1. Overview of Scaling Agile Development: Understanding the foundational principles and common challenges in scaling agile processes in large-scale projects.
2. Scaling Agile in Embedded Systems: Delving into the specific challenges and considerations unique to embedded systems development, including hardware-software integration and compliance with safety standards.
3. It’s Called Conway’s Law, not Conway’s Suggestion: On the pitfalls an intricacies interaction between architecture and team structure in larger product organizations.
4. Role of DevOps in Agile Embedded Systems: Discussing how DevOps principles can enhance agile methodologies in embedded systems, as one of the many strategies employed.
5. Value, Value Streams, and Value Loops: Re-focusing the conversation to what actually counts: creating value for the users, as quickly and reliably as we can.
6. Real-World Case Studies: Analyzing successful applications of agile methodologies, including DevOps, in large-scale embedded system projects, providing practical examples of implementation and outcomes.

Go to Session

Live Q&A - Scaling Agile Development in Large-Scale Embedded Projects

Live Q&A with Luca Ingianni for the talk titled Scaling Agile Development in Large-Scale Embedded Projects

Go to Session

How to do Embedded Development in an Agile Way

Agile: what is it, and what isn't it -- you might think that this topic would be settled by now, but the debate seems to be increasing if anything.  I've encountered many doubts about whether agile makes sense for embedded in the first place, and how to apply its principles.

So in this talk I'll try to summarise how to understand agile, and how to apply it in the embedded domain.

• What's the mindset and philosophy behind Agile (I promise, it's not sprints)
• Should you be using agile in the first place?
• How can you possibly apply it in physical products?
• How does it work in regulated, i.e. safety-critical contexts?
• How can you convince your coworkers, your managers -- and perhaps even yourself, to give it a try?
• Where should I start, and who do I need to ask for permission?

I'll also try to address the most frequent doubts, criticisms and especially misunderstandings of agile, particularly as applied to embedded systems.

Go to Session