Lightning Talk: The businesscase for architecture - Niek Van Raaij

./resources/talk-the-businesscase-for-architecture-niek-van-ra.resources/screenshot.png

arch, devops, secutiry

Level 1: too vague ./resources/talk-the-businesscase-for-architecture-niek-van-ra.resources/screenshot.1.png hard business case vague

-–

Level 2: missing why ./resources/talk-the-businesscase-for-architecture-niek-van-ra.resources/screenshot.2.png what would we do with that 10% now free? still have to pay “and fire 10% of developers” would be a business case ./resources/talk-the-businesscase-for-architecture-niek-van-ra.resources/screenshot.3.png

-– How to do write better business cases ./resources/talk-the-businesscase-for-architecture-niek-van-ra.resources/screenshot.4.png ./resources/talk-the-businesscase-for-architecture-niek-van-ra.resources/screenshot.5.png

./resources/talk-the-businesscase-for-architecture-niek-van-ra.resources/screenshot.6.png “reduce rollback time by 10%” how much is the lost revenue of a 10 minute downtime? now 10% less

./resources/talk-the-businesscase-for-architecture-niek-van-ra.resources/screenshot.7.png “pick up the first most valuable” but also “communicate the goal”