You can break down Software to its building elements as we did before, and you’ll get something like this:
Seems fine. What about their dependencies?
We can proceed as before, and identify and add dependencies for these as well, but isn’t that too much detail? Instead, we can have a simple list of items, to make sure we won’t forget any of them, and to be able to measure progress, and let the people who are supposed to do it determine in which sequence to work. This makes sense, especially because these small items don’t impact anything outside their parent deliverable.
P3pper doesn’t force you to schedule the whole plan, and you can decide to leave the details of some parts to improvisation. Let’s do that next!