.. Copyright (C) ALbert Mietus; 2023, 2024 .. sidebar:: Workshop & Blog Welcome to the condensed "blog edition" of my workshop `“Using & Writing an Agile SIA”`. |BR| If you're eager for the full experience, don't hesitate to reach out for the complete workshop. .. _AgileSIA: ============ An Agile SIA ============ .. post:: 2024/03/21 :tags: SysEng, Modernize :category: lecture :language: en The **SIA** -- an acronym for *System* (or Software) *Impact Analysis* -- is an often used approach to get insight into the costs, risks, and possibilities of implementing a feature. It should result in a readable document to decide whether it adds value to implement that feature and offer options on how |BR| But is also a document that is repeatedly incorrectly used. The classical SIA isn't very Lean nor Agile; certainly not when it became an (upfront) design document, as often ... |BR| On second thought, a good SIA is lean and agile. A short, up-front *“think ahead”* document makes it possible to postpone details to future sprints and assist the Product Owner in picking the right solution without adding costs. Let’s study how we can write an Agile SIA. One with business value. .. admonition:: *“a Bumper”* is **not any** Bumper (demo) .. image:: ./aBumper.jpg :width: 33% :align: right * In this workshop, we design ‘a bumper’. Or actually: we write the SIA for it. * By using a not-software example, it is easier to *not focus* on the technicalities that shouldn't be in the SIA anyhow * For mechanical engineers: I’m probably oversimplifying and missing relevant details. Sorry about that:-) |BR| I welcome feedback to improve! * The “bumper image” is from a `1967 Citroen 2CV `__, which is cropped and `reused `__ as permitted. Thanks! .. rubric:: Content .. toctree:: :maxdepth: 2 goal/index goal/5chapters demo/index notes/index