In recent weeks, I’ve come across the same theme again and again in projects: customer and provider agree to get started quickly, specifications exist only rudimentarily, after all, they trust each other and want to reach a (very roughly) defined goal quickly and together. Details are arranged “on call”…
Then two things happen:
𝟭) 𝗱𝗲𝗿 𝗞𝘂𝗻𝗱𝗲 𝗵𝗮𝘁 𝘂𝗻𝘁𝗲𝗿𝘀𝗰𝗵𝗮̈𝘁𝘇𝘁, 𝘄𝗮𝘀 𝗲𝘀 𝗯𝗲𝗱𝗲𝘂𝘁𝗲𝘁, 𝗜𝗧-𝗣𝗿𝗼𝗷𝗲𝗸𝘁𝗲 𝘂𝗺𝘇𝘂𝘀𝗲𝘁𝘇𝗲𝗻 𝘂𝗻𝗱 𝘄𝗲𝗹𝗰𝗵𝗲 𝗠𝗶𝘁𝘄𝗶𝗿𝗸𝘂𝗻𝗴𝘀𝗽𝗳𝗹𝗶𝗰𝗵𝘁𝗲𝗻 𝗲𝗿 𝗵𝗮𝘁.
𝟮) 𝗱𝗲𝗿 𝗔𝗻𝗯𝗶𝗲𝘁𝗲𝗿 𝘄𝗶𝗿𝗱 𝗺𝗶𝘁 𝗪𝘂̈𝗻𝘀𝗰𝗵𝗲𝗻 𝗸𝗼𝗻𝗳𝗿𝗼𝗻𝘁𝗶𝗲𝗿𝘁, 𝗱𝗶𝗲 𝘃𝗼𝗿𝗮𝗯 𝗻𝗶𝗰𝗵𝘁 𝗯𝗲𝗸𝗮𝗻𝗻𝘁 𝘄𝗮𝗿𝗲𝗻 𝘂𝗻𝗱 𝗺𝗼̈𝗰𝗵𝘁𝗲 𝗳𝘂̈𝗿 𝗱𝗲𝗿𝗲𝗻 𝗨𝗺𝘀𝗲𝘁𝘇𝘂𝗻𝗴 𝗯𝗲𝘇𝗮𝗵𝗹𝘁 𝘄𝗲𝗿𝗱𝗲𝗻.
This is often peppered with a process model that has been agreed as “extremely agile” (at least that sounds modern). This suggests rapid progress and short paths, but in reality only leads much more quickly to discussions about what is included in the “standard” and what are additional requirements.
At this point at the latest, you wish you had defined a little more in advance and recorded it in writing. In extreme cases, third parties/experts have to be called in to mediate or assist in court.
𝗗𝗮𝗵𝗲𝗿 𝗺𝗲𝗶𝗻𝗲 𝗘𝗺𝗽𝗳𝗲𝗵𝗹𝘂𝗻𝗴: 𝗤𝘂𝗮𝗹𝗶𝘁𝗮̈𝘁 𝗺𝘂𝘀𝘀𝘀 𝗴𝗮𝗻𝘇 𝗮𝗺 𝗔𝗻𝗳𝗮𝗻𝗴 𝗯𝗲𝗴𝗶𝗻𝗻𝗲𝗻. 𝗡𝘂𝗿, 𝘄𝗲𝗻𝗻 𝗦𝗶𝗲 𝗜𝗵𝗿𝗲 𝗔𝗻𝗳𝗼𝗿𝗱𝗲𝗿𝘂𝗻𝗴𝗲𝗻 𝗴𝗲𝗻𝗮𝘂 𝗸𝗲𝗻𝗻𝗲𝗻 𝘂𝗻𝗱 𝗳𝗲𝘀𝘁𝗵𝗮𝗹𝘁𝗲𝗻, 𝗵𝗮𝗯𝗲𝗻 𝗦𝗶𝗲 𝗲𝗶𝗻 𝗸𝗹𝗮𝗿 𝗱𝗲𝗳𝗶𝗻𝗶𝗲𝗿𝘁𝗲𝘀 𝗣𝗿𝗼𝗷𝗲𝗸𝘁𝘇𝗶𝗲𝗹.
Simply starting to run can be dangerous.
#informatikersindcool#qualitätamanfang
