Posts tagged Modernize

An Agile SIA

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
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 …
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.

Read more ...

Applying BDD & TDD in legacy



As I described in Introducing BDD & TDD, understanding the common goals of Behavior & Test Driven Development and defining your specific needs is the first and most critical step to start using this essential discipline.
Whenever the goal is to use new tools, it is simple: purchase them, shop for some hands-on training, and you are done.

Our ambition is different: we want to become Agile and Lean.
Then, it depends on the starting point too. B&TDD in greenfield development is relatively simple: start writing your tests and code!

However, starting with B&TDD in (Modern) Embedded Software can be more challenging due to the existing and often extensive codebase that was developed before the emergence of B&TDD.
Then, the question ‘How to start?’ is more like ’How to get out of the waterfall?’

Read more ...