By looking
at the specific activities involved in managing tasks it will become clear that it is an
iterative process that is driven by logic??”something we as developers are meant to be
good at! Demonstrating with the help of an example is the easiest way to learn so let
us consider a hypothetical project to build a wall for our garden.
Wait, we are supposed to be developers. If we are to remain true to our
stereotypes then we would avoid manual labor and possibly even leaving
the office. Instead we would just hire a contractor to build the wall for us
and get back to writing code. However, even if we do take this approach,
does not prevent us from viewing it as a project. Although our contractor
will do most of the work for us, we still need to find good contractors,
hire them, schedule the work, and pay them. Although it is much easier
than the example that follows, we still have a collection of related tasks,
and as such is considered a project.
Having decided to defy convention and build the wall ourselves, let's look at the
activities that allow us to manage our tasks and complete our project:
Task Determination: Obviously we need tasks to manage, and although our
first instinct may be to determine every single possible task at the outset, we
need to remember that this is an iterative process so tasks can (and will) be
added, changed, or removed later on.
Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25