Panel

Live Q&A & Panel Discussion - Agile Track

Watch Now

52:34

EOC 2025

Panel

Live Q&A & Panel Discussion - Agile Track

52:34 EOC 2025

Live Q&A & Panel Discussion - Agile Track

52:34

Live Q&A and Panel Discussion with speakers presenting in the Agile track.

1 / 5

Please log in or create an account to test your knowledge and see the answers.

According to the panel, what is the main organizational challenge when adopting Agile in embedded teams?

A Agile can be implemented in isolation; teams only need to change their internal rituals.

B Adopting Agile mostly requires buying new tools and automation to be effective.

C Changing to Agile inevitably impacts customers, colleagues, and the rest of the organization and must be considered.

D The primary barrier is that embedded engineers lack programming skills for Agile.

E Agile adoption only fails when teams refuse to use Scrum exactly as prescribed.

What practical value-stream technique did the panel recommend to find where development work is getting delayed?

A Count the number of Git commits per developer to identify slow contributors.

B Map the development steps and the queues between them, and look for where queues build up.

C Increase sprint length to allow more work to complete before handoff.

D Focus solely on retrospectives to identify delays after each sprint.

E Track only story points completed per sprint to find bottlenecks.

When implementing hardware-in-the-loop (HIL) CI for multiple embedded products, which approach did the panel recommend?

A Create a bespoke, top-to-bottom test framework for each product platform individually.

B Install CI agents directly on the target embedded hardware to run tests in place.

C Use modular HAL layers and reusable infrastructure so tests can generalize across platforms.

D Avoid early-stage generic testing and wait for final-unit testing to ensure accuracy.

E Only test on virtualized simulations; real hardware testing is unnecessary.

How did the panel characterize the relationship between Agile and Scrum for embedded teams?

A Scrum and Agile are identical; teams must follow Scrum precisely to be Agile.

B Agile is best avoided in embedded contexts; Scrum is the only applicable method.

C Scrum is a prescriptive starting point, but Agile is broader—teams should adapt practices to their context.

D Agile forbids any upfront architecture; everything must be fully emergent during sprints.

E Using Scrum mechanically (ceremonies only) guarantees successful Agile adoption.

With AI/agentic tools becoming part of development, what concrete change did panelists say embedded teams must make?

A Trust AI outputs without human checks to speed up development.

B Remove CI and manual review since AI will generate correct code.

C Strengthen continuous integration and add verification checks so AI outputs are validated rather than accepted blindly.

D Only use public large models without integrating private code context to avoid overfitting.

E Replace architectural constraints with prompt engineering alone, ignoring existing architecture.

Formatting help

italics	surround text with asterisks
bold	surround text with two asterisks
hyperlink	[hyperlink](https://example.com) or just a bare URL
code	surround text with `backticks`
~~strikethrough~~	surround text with ~~two tilde characters~~
quote	prefix with >

Upvotes Newest Oldest

No comments or questions yet. Be the first to start the conversation!

Partners & Sponsors

CodeSecure

atym

embedd.it

IAR

Become a Sponsor