Download ProjectLibre FRC Tutorial V2

The project will now complete towards the end of November instead of the end of October! The reason
for this is simple: The tasks are defined so that the second round of design is not started until the
marketing study is completed. We have told the software that Task 2 is being done by someone who only
works 20 hours per week and so it recalculated the ending date (remember: Duration * Units = Work) and
adjusted the schedule of the other tasks that depend upon it. Is this new Task 2 completion time a
problem? We won’t know until we assign the resources to the rest of the tasks.
To simplify the tutorial as this software development effort goes through three similar design, code and
test cycles, we will assign team members only to Tasks 1 through 10. As an exercise, you can recreate
the project plan where this tutorial ends, continue assigning people to the second and third development
cycles, and see the schedule effects of bringing other people onto the team.
We will next assign people to Tasks 3 through 10. (Task 1 is still being held off for discussion later on in
this tutorial.) Recall that we have one software architect (TM4), TM3 can program but only functions A,
B, and C, and TM1 can program but at a slow rate. The decision, therefore, of which team member will
do the design task (Task 3) is simple, TM4, and we will make that allocation. We have four programming
tasks, 4 through 7, one involving function D (Task 7) that only TM4 can code so we will allocate TM4 to
that task. Since TM1 is slow, we will assign Task 6 to that person and the other two to TM3. (Making all
assignments at the 100% Units level for now.)
Moving beyond the programmers, TM5 is our test designer and so is assigned Task 8, TM6 executes tests
and so is assigned Task 9 and, finally, TM7 is assigned the user documentation writing in Task 10.
Except for now having the names beside the task’s bars, the Gantt chart remains unchanged:
21