Input output , tool and techniques for PMP exam preparation
Subrat Shankar NathSenior Consultant| Capgemini Technology ServicesThane, Maharashtra, India
In perspective to PMP exam preparation, how important one to know all Input-output and tool and techniques? Does it require to have them all in the memory to clear the exam?
Just to clarify, I am not asking about 49 processes, belong 10 knowledge areas and 5 Process groups. I have understood them well, I don't need any technique or trick to memorise them.
I am only struggling with Input-Output Process and Tools and Techniques and find it hard to understand it.
Thanks for the suggestions and helping me with it.
I was crazy enough to memorize the ITTO's but it's not necessary. Just examine the process flows (the maps are in the PMBOK) and how the processes and input/output documents interact, and eventually you will see patterns, commonalities and frequencies.
...
1 reply by Subrat Shankar Nath
May 16, 2018 8:49 AM
Subrat Shankar Nath
...
Hi Sante,
Thanks for the swift reply.
I am getting crazy to understand or find any patterns in ITTO's. Please, do you mind, sharing me patterns or commonalities have to discover or perhaps any blog which can help me? It will help me to understand and get a grip on it.
Saving Changes...
Subrat Shankar NathSenior Consultant| Capgemini Technology ServicesThane, Maharashtra, India
May 16, 2018 8:42 AM
Replying to Sante Delle-Vergini, PhD
...
I was crazy enough to memorize the ITTO's but it's not necessary. Just examine the process flows (the maps are in the PMBOK) and how the processes and input/output documents interact, and eventually you will see patterns, commonalities and frequencies.
Hi Sante,
Thanks for the swift reply.
I am getting crazy to understand or find any patterns in ITTO's. Please, do you mind, sharing me patterns or commonalities have to discover or perhaps any blog which can help me? It will help me to understand and get a grip on it.
...
1 reply by Sante Delle-Vergini, PhD
May 16, 2018 5:23 PM
Sante Delle-Vergini, PhD
...
Hi Subrat, it' not something that can be explained: patterns or commonalities for 100's of ITTO's. One example is that when examining the flow diagrams, you will see that, for example, update project documents, OPA's and EEF's appear quite a lot, and more importantly why, and this will eliminate many of the ITTO's. The penny drops for people at different times, but the only way for that to happen is study the flow diagrams and ask yourself "why is the ITTO here", see where that process comes from, and where it's going to, and why the ITTO is associated with it.
Saving Changes...
Dinah YoungProject Manager / Software Asset Manager| Prince William CountySpringfield, Va, United States
Some people memorize them. I am not good at memorizing anything.
So as I read through the Inputs, I think why is that an input. I make sure that I understand the purpose of each input. I get to the point where it is obvious that "x" needs to be an input to the process. It is more of a learning technique.
I do the same with the outputs.
Now the tools take a bit more thought process and sometimes you just need to memorize them. Saving Changes...
Anish AbrahamPrivacy Program Manager| University of WashingtonAuburn, Wa, United States
As Sante mentioned, I found the Data Flow Diagram of every process very helpful to understand the ITTOs. In PMBOK you will find a DFD at the beginning of each process. It shows where does the input for the current process come from and which processes do the outputs go into. Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
You need to understand them fully and the logic behind them and this way no matter what, you will always answer any question based on an in depth understanding rather than memorization because in most cases, the questions are not straight forward. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Exam questions are situationatonal questions so in my personal opinon to memorize ITTOs has no sense. Saving Changes...
I agree with Sergio, there is no point in memorizing and remember that in end of the day the PMBOK is accessible in real life.
You need to understand the process not memorize it. The logical flow is important. Saving Changes...
Like others, I don't believe in memorizing ITTOs, understand the why it is an ITTOs for something. If required you will know what makes sense. Saving Changes...
I am getting crazy to understand or find any patterns in ITTO's. Please, do you mind, sharing me patterns or commonalities have to discover or perhaps any blog which can help me? It will help me to understand and get a grip on it.
Hi Subrat, it' not something that can be explained: patterns or commonalities for 100's of ITTO's. One example is that when examining the flow diagrams, you will see that, for example, update project documents, OPA's and EEF's appear quite a lot, and more importantly why, and this will eliminate many of the ITTO's. The penny drops for people at different times, but the only way for that to happen is study the flow diagrams and ask yourself "why is the ITTO here", see where that process comes from, and where it's going to, and why the ITTO is associated with it.
...
1 reply by Michael Brian
May 16, 2018 6:26 PM
Michael Brian
...
This is some good advice and it's most likely the route I will go once I get up to ITTOS.
I actually created a mind map chart of the 10 knowledge areas and their processes to not only see how it flows, but to also notice which processes are duplicated through each knowledge area or what steps are similar. From what I gather, each area starts with developing a plan, taking a course or few courses of actions and ending with a result of control and monitoring what is going on.
Love can sweep you off your feet and carry you along in a way you've never known before. But the ride always ends, and you end up feeling lonely and bitter. Wait. It's not love I'm describing. I'm thinking of a monorail.
Community Champion
