Re: Hello
"Frédéric Lambert" <[email protected]> Fri, 1 Dec 2006 17:28:22 +0100
| Newsgroups | gmane.comp.kde.kplato |
|---|---|
| Message-ID | <[email protected]> |
--===============2122429092== Content-Type: multipart/alternative; boundary="----=_Part_2551_30954368.1164990502944" ------=_Part_2551_30954368.1164990502944 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello ! Here is the new list of our choosen functionalities : - Bugs corrections - Improvments of the graphical interface : new buttons, short cuts etc... - List of the remaining task for each resource, and the list of the past task (in order to print) - Pert : Enter the task List in order to calculate some indicators like : - Stroke of each task : earlier start, later start, earlier end, later end... - critical way - Charts to display Budgeted Cost of Work Scheduled vs. Budgeted Cost of Work Performed (Schedule Variance); and Budgeted Cost of Work Performed vs Actual Cost of Work Performed (Cost Variance). - Export to Kspread (Kspread PLugin) If you have another ideas, just tell us :) Best Regards ! KPlato French Team ;-) 2006/11/17, Jim Sabatke <[email protected]>: > > Dag Andersen wrote: > > Fredag 17 november 2006 10:00 skrev Jim Sabatke: > >> Dag Andersen wrote: > >>> Mandag 13 november 2006 19:49 skrev Jim Sabatke: > >>> (...) > >>> > >>>> Even GANTT charts have limited use IMHO. The best charting available > is > >>>> to display Budgeted Cost of Work Scheduled vs. Budgeted Cost of Work > >>>> Performed (Schedule Variance); and Budgeted Cost of Work Performed > vs. > >>>> Actual Cost of Work Performed (Cost Variance). > >>>> > >>>> Those two graphs will give the project team and executives a very > good > >>>> view of how the project is actually proceeding. > >>> How many datapoints do you think we typically need to plot? > >>> I'm asking because it would be nice to use kchart for this but there > is a > >>> practical limit to how much data it can handle. > >>> > >>>> Estimated Cost and Time of Completion are also useful. > >>>> > >>>> Jim > >>> (...) > >> You actually don't need that many data points. The graphs show > >> incremental progress, so depending on the size of the project, daily or > >> weekly data points are sufficient. The idea is that there should be > >> enough data points to accurately convey the real status of the project. > > Diplomatic :) > > I'm playing a little bit with kchart and I'd say *much* more than 20 > values > > (per curve) and we get into problems. First with text along the x-axis > (one > > text per value), then with performance. It's made to resize to it's > window, > > (no scrolling) so the largest chart would be a full screen one. We can > always > > put it in a scrollview though, if needed, put then performance comes > into > > play. Hmm, it's not an exact sience... > > > > OTOH whats the granularity of the performance data? We used to enter > data > > weekly for projects of 3 months to approx a year, so it would be hard to > show > > accurate data for smaller intervals. > >> Jim > >> _______________________________________________ > >> kplato mailing list > >> [email protected] > >> https://mail.kde.org/mailman/listinfo/kplato > > > > I think that weekly data points are pretty much ideal. That's the > granularity I usually used when I was using CA Superproject (now > defunct), which, btw, would have made a good model to copy for kplato. > > Jim > _______________________________________________ > kplato mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/kplato > ------=_Part_2551_30954368.1164990502944 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline <p>Hello !</p> <p>Here is the new list of our choosen functionalities :</p> <p><br> - Bugs corrections</p> <p> - Improvments of the graphical interface : new buttons, short cuts etc...</p> <p> - List of the remaining task for each resource, and the list of the past task (in order to print)</p> <p> - Pert : Enter the task List in order to calculate some indicators like :<br> - Stroke of each task : earlier start, later start, earlier end, later end...<br> - critical way</p> <p> - Charts to display Budgeted Cost of Work Scheduled vs. Budgeted Cost of Work Performed (Schedule Variance);<br> and Budgeted Cost of Work Performed vs Actual Cost of Work Performed (Cost Variance).</p> <p> - Export to Kspread (Kspread PLugin)</p> <p><br>If you have another ideas, just tell us :)</p> <p>Best Regards !<br></p> <div>KPlato French Team ;-)<br><br> </div> <div><span class="gmail_quote">2006/11/17, Jim Sabatke <<a href="mailto:[email protected]">[email protected]</a>>:</span> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Dag Andersen wrote:<br>> Fredag 17 november 2006 10:00 skrev Jim Sabatke:<br>>> Dag Andersen wrote: <br>>>> Mandag 13 november 2006 19:49 skrev Jim Sabatke:<br>>>> (...)<br>>>><br>>>>> Even GANTT charts have limited use IMHO. The best charting available is<br>>>>> to display Budgeted Cost of Work Scheduled vs. Budgeted Cost of Work <br>>>>> Performed (Schedule Variance); and Budgeted Cost of Work Performed vs.<br>>>>> Actual Cost of Work Performed (Cost Variance).<br>>>>><br>>>>> Those two graphs will give the project team and executives a very good <br>>>>> view of how the project is actually proceeding.<br>>>> How many datapoints do you think we typically need to plot?<br>>>> I'm asking because it would be nice to use kchart for this but there is a <br>>>> practical limit to how much data it can handle.<br>>>><br>>>>> Estimated Cost and Time of Completion are also useful.<br>>>>><br>>>>> Jim<br>>>> (...) <br>>> You actually don't need that many data points. The graphs show<br>>> incremental progress, so depending on the size of the project, daily or<br>>> weekly data points are sufficient. The idea is that there should be <br>>> enough data points to accurately convey the real status of the project.<br>> Diplomatic :)<br>> I'm playing a little bit with kchart and I'd say *much* more than 20 values<br>> (per curve) and we get into problems. First with text along the x-axis (one <br>> text per value), then with performance. It's made to resize to it's window,<br>> (no scrolling) so the largest chart would be a full screen one. We can always<br>> put it in a scrollview though, if needed, put then performance comes into <br>> play. Hmm, it's not an exact sience...<br>><br>> OTOH whats the granularity of the performance data? We used to enter data<br>> weekly for projects of 3 months to approx a year, so it would be hard to show <br>> accurate data for smaller intervals.<br>>> Jim<br>>> _______________________________________________<br>>> kplato mailing list<br>>> <a href="mailto:[email protected]">[email protected]</a><br>>> <a href="https://mail.kde.org/mailman/listinfo/kplato">https://mail.kde.org/mailman/listinfo/kplato</a><br>><br><br>I think that weekly data points are pretty much ideal. That's the<br>granularity I usually used when I was using CA Superproject (now <br>defunct), which, btw, would have made a good model to copy for kplato.<br><br>Jim<br>_______________________________________________<br>kplato mailing list<br><a href="mailto:[email protected]">[email protected]</a><br><a href="https://mail.kde.org/mailman/listinfo/kplato"> https://mail.kde.org/mailman/listinfo/kplato</a><br></blockquote></div><br> ------=_Part_2551_30954368.1164990502944-- --===============2122429092== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kplato mailing list [email protected] https://mail.kde.org/mailman/listinfo/kplato --===============2122429092==--