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
