Articles about Process from iwebforyou: practical, plain-language guidance on websites, SaaS platforms and cloud for you.
This category is about the way a website project runs. Every iwebforyou project goes through five stages, counted down from T-5 to T-0, the day the site goes live, and no stage begins before you have approved the previous one. Each stage has a defined result, an approval point and a risk it removes. Changes outside the agreed scope are written down and assessed, never applied informally, so that cost and time stay visible to everyone. At handover you receive full ownership, access details and documentation. The same discipline applies to platforms: requirements are written down before any code, and technology is chosen after them. Articles in this category explain these steps in plain language, what each approval means for you and what we ask from your side in time and decisions. Read them before a project starts, so that you know what to expect at each point.
2 articles
Before any code is written, a platform needs its purpose, users, rules, limits, data and the checks that show it works, all in writing. That way the build answers the questions your business really has.
Read the articleIn test-driven development (TDD), you first write a test that fails, then the code that passes it, and finally you improve the code. This way every feature of a SaaS platform has its check from the start. Most tests are small and fast, while a few check the whole in the browser.
Read the articleSend a project request, or check your current website for free. We read every message ourselves.