Member
2008-11-20, 05:54 AM
Fair enough whpalmer4.
Here is a situation that I often run into that I believe treating the parent items as sub-projects (if we want to label it that) would help.
Often, I am working on projects where I don't know what the next step is. Example.
project: get SNMP traps working with vendor hardware
-set up vendor hardware to send SNMP traps
I start working on that task. But am having problem that I don't know how to deal with. In order to complete this task I find other tasks I can do that will move me forward.
-set up vendor hardware to send SNMP traps
--are SNMP traps being sent from vendor hardware
--is SNMP server set up correctly to catch SNMP traps
These are research steps that I need to complete. And those items are not actionable. This usually turns into:
-set up vendor hardware to send SNMP traps
--are SNMP traps being sent from vendor hardware
---send email to vendor hardware to find out how to verify SNMP traps are being sent
--is SNMP server set up correctly to catch SNMP traps
---contact support to verify how to set up SNMP server to catch traps
Once I have completed those two tasks and verified whether or not they are working I'm back to my original parent.
-set up vendor hardware to send SNMP traps
I then need to brainstorm about what the next troubleshooting task is and create children.
OF becomes part of my troubleshooting process.
One thing I would like to see in the iPhone is the ability to add children to a parent task that move it toward completing.