![\"\"](\"https:\/\/twproject.com\/support\/wp-content\/uploads\/linux-expert.png\")
<\/p>\nIn Twproject you can create your\u00a0projects assigning skills instead of resources. This is very useful during project plan phase.<\/p>\n
Consider now this use case:<\/p>\n
– handling projects open now with real people<\/p>\n
– modeling future projects with assignments by skills<\/p>\n
Having both in the same system makes it possible for example to share project tree creation and maintenance between planning project managers and production project managers.<\/p>\n
We assume below that we start from a future project.<\/p>\n
We created departments and teams, with people in teams. Each department team has a manager.<\/p>\n
Suppose we have an IT department with 3 Linux experts.<\/p>\n
We need to create a new resource without login that represents that.<\/p>\n
Example:<\/p>\n
<\/p>\n
This resource should not have a login, and should be put in the team where it belongs to (IT in this case).<\/p>\n
The crucial point is the resource capacity<\/strong> \u2013 working hours per day, which actually is the potential output of the team for such skill. In this case we have 3 Linux experts in the team, who can dedicate 5 hours out of 8 (3 are taken by say \u201cBusiness As Usual\u201d), so the potential output is 3*5 hours of \u201cLinux Expertise\u201d per day. Notice that this holds only for planning projects, as in the day to day operations load is not given by such simple availability but you have to use the operator load where are taken into account open assignments but also worklog inserted which progressively frees the team members from the assigned hours.<\/p>\n So we suppose to have a future project called \u201cSigaro\u201d, the idea being that at this moment we know skills required and can only predict effort. We surely now know the core structure, and we even have some milestones. All this can be set in Twproject.<\/p>\n Created the Gantt\/tree structure, we assign the \u201cLinux Expert\u201d skill with an estimated effort of 80 hours.<\/p>\n The operator load function is now already effective and useful, and can handle a skill \u201cbooked\u201d in several future projects, giving you a report of the state of commitment:<\/p>\n More future projects you will have, more useful it will become.<\/p>\n What happens when the time comes that the project has to be started? First generate a \u201csnapshot\u201d of the project, which will be the project as planned.<\/p>\n You will add assignments for real people: you will assign a project manager, resources with the skill\u2019 skills (sorry J), and the skill\u2019 assignment can remain, as it does not record workload and worklog accumulation is not done for resources without a login.<\/p>\n Notice that the worklogs you will be inserting will subtract from the operator load.<\/p>\n The last point is important because this way you can check in the same operator load page the load of both \u201creal\u201d operators and of skills. As you have in the team both the skills and the real operators, by clicking \u201coperator load\u201d on the team you will see a load \/ availability overview.<\/p>\n That\u2019s it.<\/p>\n","protected":false},"excerpt":{"rendered":" In Twproject you can create your\u00a0projects assigning skills instead of resources. This is very useful during project plan phase. Consider now this use case: – handling projects open now with real people – modeling future projects with assignments by skills Having both in the same system makes it possible for example to share project tree […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":2412,"menu_order":2,"comment_status":"closed","ping_status":"open","template":"","meta":{"footnotes":""},"class_list":["post-3022","page","type-page","status-publish","hentry"],"yoast_head":"\nFuture project<\/h2>\n
![\"\"](\"https:\/\/twproject.com\/support\/wp-content\/uploads\/wl-di-lux.png\")
<\/p>\nRunning project<\/h2>\n