Agile and Lean Development for Hardware

Revision as of 01:37, 1 March 2012 by Clarman (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Overview

1 day

This practical, information-packed seminar summarizes practices, organizational design ideas, and experiences related to applying agile and lean principles and practices in hardware or hardware and embedded software development, including related FPGAs. It primarily draws on experience from PCB development done with elements of Scrum, agile principlies practices, Kanban method, and lean principles and practices.


Methods of Education

Discussion, presentation, Q&A, memory recall exercises


Audience

Managers and hands-on engineers in the development of hardware (PCBs, ...), FPGAs, board-level software, and drivers.


Level

Introductory: This course introduces concepts and techniques that the attendee will not apply during the session.


Prerequisites

course Agile, Lean, and Iterative Development: Management Overview or equivalent


Participants must read (available online), before the course:


And these chapters, available in paper print or online at Safari. These following chapters are from Scaling Lean & Agile Development: Thinking and Organizational Tools for Scrum (Larman & Vodde).

  • Chapter 2: Systems Thinking
  • Chapter 4: Queuing Theory
  • Chapter 8: Teams


NOTE! Your company may have an online Safari account that you can use to read the book chapters online free. Please ask your colleagues if you have a Safari account.


Topics

  • team organization: for example, how should thermal design, layout, and mechanical work together?
  • multilearning
  • release planning in agile hardware development
  • practices that do and do not apply from Scrum and other agile methods
  • WIP management
  • the implications of queuing theory for hardware development project management
  • Kanban method
  • obeya
  • lean development: principles and practices
  • stop and fix culture
  • reduction of special-cause and common-cause variability
  • kaizen
  • set-based concurrent development
  • decomposing hardware development into smaller steps: PCB example
  • splitting large hardware requirements
  • expressing requirements with 'stories'
  • adaptive iterative planning
  • "definition of done" in hardware Sprints
  • Product Owner and ScrumMaster
  • Product Backlog in hardware development: PCB example
  • burndown charts and visual management
  • test-driven development
  • "continuous" integration
  • and more!


Maximum Participants

35


Environment - Room, Tools, Texts

Read this: Course Environment - Presentation Oriented