|
|
| Line 5: |
Line 5: |
|
| |
|
| This tutorial is written using kplato release 0.9.84 working on a kubuntu installation 10.10 with KDE 4.5.1. Language used is english. | | This tutorial is written using kplato release 0.9.84 working on a kubuntu installation 10.10 with KDE 4.5.1. Language used is english. |
|
| |
| = Executing and controlling =
| |
| It's time to start our project. After certain time we collect the informations needed as completion percentage, worked hours, expenses.
| |
|
| |
|
| |
| == Gantt chart ==
| |
| Now, as we have the baseline, we have prepared all the data needed for the next step which is controlling the working process! Before this, we have to check if everything is right. Looking at the gantt chart we can see a big picture about our project and therefore be able to visually view if there are some errors.
| |
|
| |
| So, have a look at the Gantt in "views->gantt", should be like this
| |
|
| |
|
| |
| <center>[[Image:kplato_gantt1.png|800px]]</center>
| |
|
| |
|
| |
| You can also configure the Gantt view to show scheduling errors!
| |
|
| |
|
| |
| If everything look right, we can proceed forward.
| |
|
| |
| == Project performance chart ==
| |
| At this point the project performance chart, show the baseline and the state before start. Should be like this:
| |
|
| |
|
| |
| <center>[[Image:kplato_ppc.png|800px]]</center>
| |
|
| |
|
| |
| Where BCWS means Budgeted Cost Work Scheduled, BCWP means Budgeted Cost Work Performed, ACWP means Actual Cost Work Performed. All these are considered as effort and costs. PI are the Performance Indexes, where CPI is the Cost Performance Index and SPI is the Schedule Performance Index.
| |
|
| |
|
| |
| '''''CPI is equal to BCWP/ACWP. When this index is below 1, means that you are over budget as ACWP is major than BCWP. If the index is over 1, means that the costs are under budget'''''
| |
|
| |
| '''''SPI is equal to BCWP/BCWS. When this index is below 1, means that you are behind schedule. A value greater than 1 means that you are ahead of schedule.'''''
| |
|
| |
| == Task performance chart ==
| |
| On the "task performance chart" we can analyse deeply each task or group of tasks with the same index as before.
| |
|
| |
| This is really useful in long and complicated project.
| |
|
| |
|
| |
| <center>[[Image:kplato_tpc.png|800px]]</center>
| |
|
| |
| == Task status ==
| |
| In the "task status view", you can check the actual situation of the project. Can be used as a daily check!
| |
|
| |
|
| |
| <center>[[Image:kplato_task_stat1.png|800px]]</center>
| |
|
| |
|
| |
| Is it time to simulate some work now!
| |
|
| |
| So, let's start to enter some value, right clicking on the activity in the "next period" mec design and choose "progress" from the menu that appear. This will appear!
| |
|
| |
|
| |
| <center>[[Image:kplato_task_stat3.png|800px]]</center>
| |
|
| |
| In this task progress window, we can choose to define the starting date of the task. Click on the Started button on the upper right corner of the window and choose the date.
| |
|
| |
| Than we choose to add a completion percentage for the task, clicking on the add entry in the tab completion. Than click on the %complete field and move the cursor that appear up to 20%. On the field at the right you can insert the effort used, in this case we will insert 32.
| |
|
| |
| Note that the edit mode must be set to 'Per task' (default is 'Calculate Effort'). The final window will be like this one:
| |
|
| |
|
| |
| <center>[[Image:kplato_task_stat4.png|500px]]</center>
| |
|
| |
|
| |
| now we do the same for the second task that can be started, the "ele design". But for this task we choose the edit mode as "per resource" and compile the relative tab with 5 hours per day on tue, wed and thu. The result will be like below:
| |
|
| |
|
| |
| <center>[[Image:kplato_task_stat5.png|500px]]</center>
| |
|
| |
|
| |
| Than we move briefly to the task execution view and choose the "orders" task and insert the progression using the "calculate effort" edit mode. Choosing the data we started and the % complete to 10%, the effort will be calculated automatically and the result should be like below:
| |
|
| |
|
| |
| <center>[[Image:kplato_task_stat6.png|500px]]</center>
| |
|
| |
| than moving to the task status menu we'll find the following:
| |
|
| |
|
| |
| <center>[[Image:kplato_task_stat8.png|800px]]</center>
| |
|
| |
| == Task execution ==
| |
| In the task execution we can have a general view of the things going on.
| |
|
| |
| '''''Note that BCWS are referred to Today!'''''
| |
|
| |
| <center>[[Image:kplato_task_exec1.png|800px]]</center>
| |
|
| |
|
| |
| Is a reasonable view to have a general check!
| |
|
| |
| == Gantt ==
| |
| The gantt menu is a typical gantt diagram where you can have a clear picture about the sequence and the duration of the project. With our example, will be like this.
| |
|
| |
|
| |
| <center>[[Image:kplato_gantt2.png|800px]]</center>
| |
|
| |
|
| |
| To have a better view of the gantt diagram, it's possible to work on the zoom. This can be done right clicking on the upper part of the diagram where there are the months and days. This menù will appear:
| |
|
| |
|
| |
| <center>[[Image:kplato_gantt3.png|500px]]</center>
| |
|
| |
|
| |
| With this menu it's possible to change the scale or the zoom in/out. Most useful could be the "zoom..." selection that can zoom in or out by a small menu. Try it!!
| |
|
| |
| == Milestone gantt ==
| |
| Milestone gantt is a part of the gantt diagram with a filter only to the milestones. In this project we do not have any, so the window will be blank!
| |
|
| |
|
| |
| <center>[[Image:kplato_mgantt.png|800px]]</center>
| |
|
| |
| == Resource assignment ==
| |
| The resource assignment view let's you check which resource is used in which day, how many hours and for what.
| |
|
| |
|
| |
| <center>[[Image:kplato_res_ass1.png|800px]]</center>
| |
|
| |
|
| |
| on the right window, between brackets are the hours of availability while just before the brackets the hours used for that resource.
| |
|
| |
| == Resource assignment gantt ==
| |
| The resource assignment gantt is a gantt diagram with the resource data. Can be useful to visualise the working period of the resources as well as quickly check about some availability to anticipate some tasks!
| |
|
| |
|
| |
| <center>[[Image:kplato_res_ass2.png|800px]]</center>
| |
|
| |
|
| |
| In this view we can see that the first resource is fully used for the first 3 days as in the main row related to the resource is written 1.0, this means 100%. than on the sub rows of the resource we can see the tasks and the time spent for each task.
| |
|
| |
| == Cost breakdown ==
| |
| The cost breakdown view represent the result of the accounting of the various tasks cost, generated according the cost assignment in the task and the cost breakdown structure that we decided at the beginning of the job.
| |
|
| |
|
| |
| <center>[[Image:kplato_cb1.png|800px]]</center>
| |
|
| |
|
| |
| On the left windows, in the total column, between brackets there's the total sum for the project according the task, while just before the brackets is the actual total expenses.
| |
|
| |
| == Reports ==
| |
| Reports are still in a early stage but you can choose to export as pdf some views, which can be good as the report!
| |
|
| |
| [[Category:Tutorials]]
| |
| [[Category:Office]]
| |
