In production or project planning the scheduling of backlog items is an essential task. It is important to keep an overview of all work to be done and to include the items step by step in the planning board. In a previous blog post we have already discussed different backlog visualizations. Now, we will see how our Visual Scheduling Widget can help you to perform the handling of backlogs by using Gantt charts.
This post will give you an answer and explain the different options each view offers. This approach of the two views with their respective strengths is of course not limited to the VSW alone, but is intended as food for thought for all developers who have to create an HTML5 Gantt chart.
A few months ago, I presented our Model for Resource Planning HTML5 Gantt Charts in a two-part blog post. Now that we have successfully realized many more projects in the meanwhile it is time to give you an update.
During the last years we gained a lot of experience in developing HTML5 Gantt charts. It boiled down to a generalized model for resource planning, that is now basis of our Visual Scheduling Widget. How this model looks like, I started to explain in my previous blog post, when I described the data model and its' different types of objects we think are relevant to visualize resources and their activities.
In this post I explain how to map the members of this data model to interactive graphical representations. So the second (and last 😉) part of my series of blog posts about our generalized model for HTML5 Gantt Charts refers to the concept of mapping.
Some time ago, I reported on the way NETRONIC helps its customers develop web applications for scheduling or resource planning by offering custom tailored, interactive HTML5 Gantt charts. Since then, things have evolved outstandingly. My update on this is the following blog post about our new generalized model for resource planning that is today the basis of our Visual Scheduling Widget.
First of all, I have to clarify that this blog post is not(!) about progress bars as we all know well from installing software or from downloading files. But this post is about the visualization of progress as we are used to see for instance in production planning or project management software systems.
I want to demonstrate the difference between a "classic" progress bar and a forecast oriented visualizaton of progress. The second is a new approach that has been currently implemented in our latest Gantt chart application we developed with our NETRONIC Web Application Framework and the feedback from the users was enthusiastic.