Estimation of client’s future needs and requests for website development
After a website is launched, our clients often realize that they would need “something slightly different” or “more functions” (large reports, interactive visualizations, internal sections for authorized users, e-learning, surveys etc.). When we develop a new website for our client who already approached us before, we try to estimate requests that might appear in near future, based on our previous experience with the particular client and/or in similar projects. This often saves time and efforts of developers and coders, because a specific modality or module is available at the website from the very beginning.
website development, design, client, request, modification
Our clients (both internal and external) often come with an initial request for a website, but their needs for functions often grow soon after the website is launched. When they return with an initial request for another website, it is useful to predict what they will need and in what aspect they website will be modified and extended in near future and include this in the development phase.
a project manager with good mental health and empathy
generic: high level abstract best practice, metalevel category (e.g. manage architectures)
Medicine/Healthcare, Education (Technology enhanced learning), Data science (analysis & visualisation), Software engineering
In which projects do/did you use this practice?
Prostaforum, NSC e-learning
6–10 years of experiences
|1. How do you rate the potential benefit for your projects?||4|
|2. How often are you using that practice?||3|
|3. What is the effort to introduce the practice in your project upfront?||3|
|4. What is the effort to apply the best practice in your project daily basis?||2|
Questions 1, 3 and 4 (1 = Low, 5 = High)
Question 2 (1 = Never, 5 = Always)