Showing posts with label Program. Show all posts
Showing posts with label Program. Show all posts

Thursday, April 21, 2016

Silence The Mind To Think Clearly & Deliver Results


#SridharPeddisetty #Agile #Scrum #Motivational #ProjectManagement #Management #AgileBestPractices #Inspirational  
Once there was a farmer who discovered that he had lost his watch in the farm. It was not an ordinary watch because it had sentimental value for him. After searching the hay for a long while, he gave up and sought help of a group of children playing outside the barn. He promised that the person who finds it would be rewarded. Hearing this, the children hurried inside the barn, went through and around the hay but still could not find the watch. Just when the farmer was about to give up looking for his watch, a little boy went up to him and asked to be given another chance.The farmer looked at him and thought, “Why not? After all this kid looks sincere enough.” So the farmer sent the little boy back in the barn. After a while the little boy came out with the watch in his hand. The farmer was happy and surprised and so he asked the boy how he succeeded where the rest had failed. The boy replied, “I did nothing but sit on the ground and listen. In the silence, I heard the ticking of the watch and just looked for it in that direction.”

A peaceful mind can think better than a worked up mind. Using the metaphor, a focused project team more often than not, delivers a project successfully. Project team must remain focused on managing value based project goals and stakeholders instead of simply concentrating on budget and scheduling. Below 5 tips can be used for a project team to remain focused 

#1. Be clear on the project value: Project delivery is not just about achieving agreed scope, schedule or cost but its about delivering value. Its often seen that project team while remaining focused on current work tasks sometimes remain oblivious of the value project is going to achieve at the end. In most cases, statement of work (sow) or proposal is authored by individual(s) who would likely not be responsible for actual execution of the project. So its important for the project team to be always aligned with what would be the end value of project. Project team needs to have a complete ‘buy-in’ into the value for them to appreciate their current work tasks. 

#2. Break plan into achievable milestones: We all understand that for every journey we embark, milestones helps us remain focused. Milestones are the small steps, which leads project team to the ultimate project goal whether it be developing of new product or service. Measurable milestones help the project team remain focused and celebrate their achievements along the journey, which goes a long way for a motivated team. Milestones also help team in executing, checking, planning and acting while keeping tab on quality to ensure alignment with the overall project goal. 

#3. Prioritize impediments mapped with value: In my earlier post Looking At An Impediment From A Value Perspective, I had shared  how when faced with an impediment, enlarge your vision of looking at the impediment from the perspective of delivering value. Matured project teams view the impediments as tasks, which needs to be completed for respective user stories and the tasks could be updated and prioritized for the value. As a Scrum Master or Project Manager, one needs to know how things get done in the organisation and who to speak to when faced with an impediment. 

#4. Separate people from the problem: It is very easy to get overwhelmed with frequent pressures of delivering value and thats when things can get defensive for the team. In my earlier post You Already Have ‘NO', Go For ‘YES’, I had shared how its important to keep emotions under check while delivering and always keeping in mind to respond and not to react.’My side of the boat is not leaking’ attitude does not help so its important to separate people from the problem and be rational in identifying solutions for the impediments or dependencies. 

#5. Look for continuous improvements: In my earlier post Value Stream Mapping As A Process Improvement Tool, I had shared how "Value Stream Mapping” can be applied as a tool for identifying inefficiencies in the processes. Retrospections are also key in identifying opportunities for continuous improvements. Note that singular way of doing retrospections does not necessarily fit culture of all organizations so its very important to customize how the feedback is taken and loop for the continuous improvement is applied.

Summary
Similar to how important it is to allow yourself a few minutes of silence to think sharply, project team needs to be focused for successful delivery of project value. 

Please share your thoughts on how you manage to keep yourself focused. 

Previous posts you might be interested in

Sunday, March 1, 2015

Inside and Outside Project Comparison and Prioritization

We understand the needs of a Project Management Office (PMO) to help drive IT efficiency, cut costs and improve the quality of project delivery in terms of time and budget. In my earlier blog 7 Questions to Ask Before Establishing a Project Management Office (PMO), I shared three types of roles a PMO plays in an organization in terms of supporting, controlling or directing. A PMO can boost productivity while ensuring that priority projects get the most attention, but it is important to perform the right comparisons between projects to prioritize them. The PMO should not be comparing 'inside' of a project in terms of which department/business unit the project belongs to with 'outside' of another project in terms of goals it's achieving. While reviewing projects, the PMO should go over the project charter or SOW, which includes:

  • High-level scope of the project 
  • Goals and objectives 
  • Cost 
  • Schedule
  • Critical measures
  • Potential gains
  • Risks
  • Assumptions
  • Issues
  • Dependencies
  • Constraints
  • Identification of key stakeholders
  • Project's impact on the entire organization

Use a common basis for comparing projects while prioritizing them. One way of prioritizing projects is to group them in terms of:

  • Business critical, strategic objectives or initiatives of the organization
  • Business unit/department critical (one or multiple)
  • Business unit/department need (one or multiple)
  • Internal process improvements or exploring long-term growth by adopting new technologies and/or business models 

Note that the above mentioned grouping of priorities can change according to the strategic goals of an organization. After grouping priorities, there might be a potential need to do project sequencing for execution within each prioritized group. Harold R. Kerzner in his Project Management - Best Practices: Achieving Global Excellence book shares key decision criteria for project sequencing, which includes:

  • Strategic priority
  • Window of opportunity
  • Project interdependencies
  • Resource availability

Share your thoughts on how you compare and prioritize projects within your organization.
Inside and Outside Project Comparison and Prioritization was originally posted under Prokarma blog on Feb 26th 2015.

Wednesday, January 28, 2015

Are You Providing 'Right' Status of Your Project, Program or Portfolio?



A class teacher was posing questions to her second grade students as part of an assessment. She asked Tom, "Can you tell me a name of an animal that starts with the letter 'e'?" Tom replied "Elephant". The teacher asked him again but this time to name an animal that starts with letter ’t’ and Tom replied "Two Elephants". The teacher asked him the same question again and this time Tom responded "Ten elephants". Annoyed, the teacher asked him to name an animal that starts with letter ‘m’ and Tom replied "Mother elephant". By now, the teacher was getting very angry and repeated the same question. With a calm demeanor Tom responded "Maybe an elephant".
Syntactically it can be argued that Tom was giving the ‘right’ answers but they were technically wrong and certainly not the answers the teacher was expecting. Similarly, when stakeholders are asking for the ‘status' of a project, most often they are looking for how, when and at what cost (business value) the project will be delivered. The status report should not be just about status of scheduling, cost or scope but should be more of a report on business value. It is important to understand respective stakeholders objectives regarding the project, program or portfolio and the status report should be targeted accordingly. A dashboard summarizing the status on business value with respective links to elaborate on the specific status of scope, schedule and cost can be shared.
For instance, while executing Agile based projects it is important to understand the overall business value of the project. To understand business value it is important to first identify key stakeholders, respective goals, how to measure the goals and understand the relationship between various value drivers. Prioritized business value can then be mapped to respective themes or milestones, which helps in quantifying the requirements of overall business value while breaking them down in terms of incremental value. Overall status of the project can then be measured for each theme while sharing supporting status on:

  • Velocity (actual vs. planned)
  • Story Points (accepted vs. planned)
  • Number of Defects 
  • Percentage of Unit Test Coverage
  • Number of Test Cases
  • Number of Test Cases automated
  • Percentage of New Test Cases Added
  • Percentage of New Test Cases Automated

In my earlier post on 10 Ground Rules on the Right Metrics for Your Business, I discussed on how to select the right metrics. These posts can be used as guidelines for selecting metrics, which can then be included in future status reports showing progress on the business value of a project,  program or portfolio.
In summary, a good status report is an effective communication and transparency tool, which shares the progress on the business value of a project or a program or a portfolio mapped with objectives. What are your thoughts on providing the right status?

Are You Providing the 'Right' Status of Your Project, Program or Portfolio? was originally posted under Prokarma blog on Jan 27th 2015.

Comments: Some comments to the blog post are shared in google+  under https://plus.google.com/u/0/+JakeRahnerS/posts/62Es4z7rpm3

Tuesday, January 6, 2015

7 Questions to Ask Before Establishing a PMO


According to the definition in Project Management Institute (PMI) PMBOK Fifth Edition, the Project Management Office (PMO) is a management structure that standardizes the project related governance processes and facilitates the sharing of resources, methodologies, tools and techniques. The responsibilities of a PMO can range from providing project management support functions to actually being responsible for the direct management of one or more projects.
PMO is also applicable to program and portfolio management offices. By definition, program is a group of related projects managed in a coordinated way to obtain benefits and control not available from managing them individually and portfolio is a collection of components (i.e. projects, programs, portfolios and other work such as maintenance and related ongoing operations) that are grouped together to facilitate the effective management of that work in order to meet the strategic business objectives. 
The PMO is established within an organization based on its strategic objective, in which it could play supporting, controlling or directive roles. 

  1. In a supporting role the PMO is more consultative in nature. The goal is to provide templates, best practices, training, and a knowledge base including lessons learned from previous portfolios, programs or projects. The PMO's primary role is more as a document control center with a low level of control.
  2. In a controlling role the PMO is more focused on auditing. This ensures portfolios, programs or projects are following recommended methodologies, best practices, standards, processes, etc. The PMO's primary role is to maintain compliance across portfolios, programs or projects with a moderate level of control.     
  3. In a directive role the PMO is more management focused. Involved in the organization's portfolios, programs and projects, the PMO's primary role is identifying, prioritizing, authorizing, and managing with a high level of control.

So before establishing a PMO, it is very important to understand your organizations strategic goals. The following set of questions will help serve as guidelines

Question #1

What is the mission of the PMO?
Is the mission of the PMO to provide consulting services to projects, programs and portfolios running across an organization and/or to provide standards, processes, templates and also be responsible for auditing on a regular basis while flagging the projects, programs and portfolios that are not meeting their objectives and/or directly manage projects, program and portfolios while forming a governance framework.

Question #2

What are the roles and responsibilities of the PMO?
A well defined RACI matrix across organization will help determine the tolerance and maturity of organization to adapt to one of the supporting, controlling or directive PMO types.

Question #3

What would be the KPIs for a PMO?
How the PMO will be measured is important. Determine the type of PMO that needs to be established and set appropriate metrics accordingly. 

Question #4

What would be the 30-60-90 day implementation action plan to establish the PMO?
A step by step action plan of 30-60-90 days will help create short, mid and long-term goals for the PMO and help determine the PMO type as well.

Question #5

What is the governance model for the PMO? 
Managing and controlling the PMO for a longer period will depend on the governance model defined for the PMO. In turn, the governance model will help in understanding the type of PMO needed. 

Question #6

What is the availability of qualified personnel to staff the PMO?
Establishing a PMO is heavily dependent on finding qualified personnel and a key factor to be considered in determining the type of PMO.

Question #7

Where does the PMO fit in the organizational hierarchy? 
Understanding where the PMO will fit in the organizations' hierarchy will help establish innovators, early adopters, early majority, late majority and laggards. This will also help in planning the roll out of PMO in 30-60-90 cycles. 
Please share your thoughts on how you would establish PMO in your organization.

7 Questions to Ask Before Establishing a PMO was originally posted under Prokarma blog on Jan 6th 2015. 

Saturday, December 20, 2014

Top 20 Tips for Project Managers


Project managers are responsible for the successful initiation, planning, execution, monitoring, controlling and closure of projects. According to the Project Management Institute (PMI), a project is temporary in that it has a defined timeframe, and therefore defined scope and resources. Also, a project is unique in that it is not a routine operation, but a specific set of operations designed to accomplish a singular goal. Project teams often includes people who don’t usually work together – sometimes from different organizations and across multiple geographies.
Project management is the application of knowledge, skills and techniques to execute projects effectively and efficiently. The following 20 tips (not necessarily in any particular order) are good references while managing a project.

  1. Take good care of your project team and your team will take care of client, which in turn will take care of business
  2. The project is all about delivery and keeping stakeholders (internal/external) informed
  3. At any given point of time a project manager should know what tasks need to be done, who should do it and have an ETA
  4. Always be on top of the RAID (Risks, Assumptions, Issues, & Dependencies) log as RAID is a critical factor for a successful project outcome
  5. No plan is perfect so always have Plan B. Circumstances change frequently so always consider the alternatives
  6. Projects are 90% planning and 10% implementation
  7. Plan, Execute, Review and Adjust
  8. Be adaptable and flexible while thinking outside the box
  9. A good communicator is a good listener. By listening you may learn something new while speaking repeats what you already know
  10. Always remember the 80/20 rule (Pareto Principle), which means by executing 20% of the work you can get 80% of the benefit
  11. Break the whole plan into milestones and scope them accordingly including the development of checklists for each milestone to verify quality as project work incrementally iterates
  12. Understand the dynamics of 'Definition of Ready' and 'Definition of Done'
  13. Design a robust feedback loop to learn lessons along the way and strive to continuously improve
  14. Negotiate achievable commitments by separating people from problems
  15. You cannot manage and improve what you cannot measure
  16. 6 P's of Project Management: Proper Planning Prevents Poor Project Performance (If i had 4 hours to cut down a tree, i would take 3 hours to sharpen the axe)
  17. Get the right people involved including the experts you need and proactively seek guidance 
  18. Trust but always verify. Direct communication is a key for forging trustworthy relationships
  19. Plans are nothing; planning is everything. Planning is a continuous process including progressive elaboration or rolling wave planning
  20. The difference between a good project manager and a great project manager are the leadership skills they possess
What are your top tips for a project manager? Please leave a comment to share your tips.


Top 20 Tips for Project Managers was originally posted under Prokarma blog on Dec 10th 2014

Wednesday, December 17, 2014

10 Ground Rules on the Right Metrics



Metrics are standards of measurement that enable us to evaluate aspects of business crucial to growth. Be it operations, project, program or portfolio, they increase visibility into our performance. Note that if we cannot measure, we cannot improve and with right metrics in place we continuously improve. 
Here are ten ground rules on how to select the right metrics for your business:

  1. Each metric should be informational (tells you what's going on), diagnostic (identifies areas of improvement) or motivational (influences behavior)
  2. Metrics should be easy to gather with existing data points for greater efficiency.
  3. You should not gather metrics for the sake of it. No one who matters will care and you will will quickly train people to ignore the data you compile
  4. Portfolio and Program metrics should measure outcomes, not activity. In the cases of Projects and Operations, metrics should measure output and activities as needed
  5. Create a dashboard for each category of metrics that is easily digestible, accessible and more importantly should be actionable
  6. Be smart about what you measure and make use of the data you gather
  7. Measure everything necessary and nothing more. Stakeholders make better decisions with concise data
  8. Don't cut corners as data integrity is very important in a trustworthy partnership
  9. Use tools to measure. Manual effort more often leads to manipulation and invalid data points 
  10. Metrics should be mapped with client and organizational KPI's
Please let me know if you have additional rules regarding business metrics or would like to comment the ones listed above. 

10 Ground Rules on the Right Metrics for Your Business was originally posted under Prokarma Blog on Oct 14th 2014. 

Saturday, September 6, 2014

Tips to document portfolio management experience for PfMP®



In my previous posts related to Project Management Institute (PMI)’s most recent and coveted Portfolio Management Professional (PfMP)® credential. , I have shared 

and this post is for sharing some tips on how to fill application for PfMP. Note that for obtaining (PfMP)® credential, there are two evaluations that needs to be cleared. 
Evaluation 1—Panel Review: The initial evaluation occurs through an extensive application review during which a panel of portfolio managers will assess your professional experience based on your responses to the Portfolio Management Experience Summaries provided on the application.

Evaluation 2—Multiple-Choice Examination: The next step occurs with the multiple-choice examination in which you will be called upon to demonstrate your competence in both situational and scenario-based questions. 
So its important to fill application with appropriate answers to pass panel review. 
Note that there are lot of folks who actually fail panel review and are given only one more chance to reapply with updated answers 
Following experience summary questions are asked in align with 5 knowledge areas of Portfolio Management (Strategic Management, Governance, Portfolio Performance Management, Portfolio Risk Management and Portfolio Communication Management) and you can select either option A or B for each question to map your answer with
Experience Summary #1: Strategic Alignment
A. Identifying and prioritizing portfolio criteria and evaluating portfolio component priorities based on the organization's strategic goals and objectives
B. Creating and/or updating a high level portfolio roadmap using scenarios that helped the organization to align and operationalize the portfolio in accordance with the organization's strategic goals and objectives

Experience Summary #2: Governance
A. Securing authorization to execute the portfolio through identification and justification of recommendations regarding the portfolio
B. Ensuring effective and efficient portfolio management by implementing and/or optimizing the portfolio management plan including key components applicable to your portfolio 

Experience Summary #3: Portfolio Performance
A. Managing portfolio changes to optimize resource utilization and/or ensure portfolio effectiveness and efficiency
B. Evaluating continuous progress toward the achievement of business or strategic goals through the collection, consolidation, and measurement of portfolio value

Experience Summary #4: Portfolio Risk Management
A. Developing and/or updating the portfolio risk management plan
B. Enabling the organization to capitalize on an opportunity(ies) or manage threat(s) based on portfolio risk management processes, methods, and/or techniques

Experience Summary #5: Communications Management
A. Developing, and/or updating a portfolio communication strategy and plan
B. Engaging stakeholders to set and manage expectations and influence the success of the portfolio

Tips on how to document Portfolio Management Experience Summary
#1. How the Portfolio you managed was aligned with strategic goals of the Organization. Remember that Portfolio is a collection of components (i.e. projects, programs, portfolios and other work such as maintenance and related ongoing operations) that are grouped together to facilitate the effective management of that work in order to meet the strategic business objectives. So need to make sure that when you define your portfolio, it clearly defines components and how they were grouped to align with goals.

#2. Make sure that strategic goals are well defined that are tangible and fits acronym SMART (Specific, Measurable, Achievable, Realistic & Time bound)

#3. Use empirical data such as $ (Money and try putting in USD), # (Number like # of years, # of Projects, Programs or Portfolios) or # of direct reports, # of team members, # of projects), % (percentage of increase in efficiency, growth, revenue increase, scalable)

#4. Use more empirical data and less verbiage. Try using more universally known acronyms like Org, SME, PMI, PMP, PgMP, PfMP, others to save on verbiage

#5. Remember that Portfolio is more strategic in nature than projects, programs or operations so include words like strategy, objectives, benefits, org goals, how your portfolio was aligned with the org goals. Do not use words that would reflect 'how' you managed teams because that would be more Project Mgmt. Use words where it mentions more on 'Why/What' of Portfolio and ‘How’ you did governance management to keep it aligned.

#6. Before filling your application make sure to read Pfmp® Handbook and if possible “The Standard for Portfolio Management” to understand how PMI is defining Portfolio and what standards are being suggested to do Portfolio Management (Strategic Management, Governance, Portfolio Performance Management, Portfolio Risk Management and Portfolio Communication Management). While filling in your application, you would need to clearly define how you used each of the 5 knowledge areas to manage your Portfolio in your answer(s)

#7. Portfolio management includes processes to identify, categorize, monitor, evaluate, select, prioritize, balance, and authorize portfolio components within the portfolio. So explain in your answer(s) what those processes were in your case to work on portfolio components

#8. All Portfolio Components have following common features including                    
  • Be representative of investments made or planned by Organization
  • Be aligned with Org. strategic goals and objectives
  • Grouped together for effective management
  • Have the ability to be quantifiable
  • Can be measured, ranked and prioritized
  • Share and compete for Org. resources
So explain in your answer(s) how your portfolio(s), programs, projects & operations that are possible Portfolio components have above mentioned feature(s)

#9. Portfolios have an organizational scope that changes with the strategic objectives of the organization so explain in your answer(s) what was the scope and how it changed (most often it does) with strategic objectives of org
#10. Portfolio managers continuously monitor changes in the broader internal and external environment so explain in your answer(s) how you were monitoring the changes
#11. Portfolio managers create and maintain necessary processes and communication relative to the aggregate portfolio so explain in your answer(s) how you were communicating and using what processes
#12. Portfolio success is measured in terms of the aggregate investment performance and benefit realization of the portfolio so explain in your answer(s) how they were measured and what was the benefit realization
#13. Portfolio managers monitor strategic changes and aggregate resource allocation, performance results, and risk of the portfolio so explain in your answer(s) how they were monitored including portfolio risks

#14. Portfolio managers may manage or coordinate portfolio management staff, or program and project staff that may have reporting responsibilities into the aggregate portfolio so explain in your answer(s) how as a portfolio manager you were coordinating the portfolio staff

#15. Portfolio Management balances conflicting demands between programs and projects, allocates resources (e.g., people, funding) based on organizational priorities and capacity, and manages so as to achieve the benefits identified.  Explain in your answer(s) how you were balancing conflicting demands

#16. In your answer(s) try including references to Portfolio Charter, Portfolio Strategic Plan, Portfolio Roadmap, PMO, Portfolio Governance, Portfolio Sponsors, Portfolio Risk Management Plan, Portfolio Risk Register, Portfolio Communication Management Plan and how they were used in your Portfolio wherever applicable.

Sample points that could be used in your answer(s)
·       Establishing and maintaining a framework, governance model, and methodology (policies and procedures) for portfolio management to achieve organizational strategies and objectives.
·       Guiding the selection, prioritization, balancing, and termination of portfolio components to ensure the alignment with strategic goals and organizational priorities.
·       Providing key stakeholders with assessment of portfolio component selection, prioritization, and performance, as well as identification of portfolio-level issues and risks that are impacting performance.
·       Measuring and monitoring the value to the organization through portfolio performance metrics and targets.
·       Supporting senior-level decision making by ensuring timely and consistent communication to stakeholders on progress, changes, and impact on portfolio components.

Wednesday, July 16, 2014

My Lessons Learned for (PfMP)® Exam


This post is for sharing my lessons learned while successfully obtaining Project Management Institute (PMI)’s most recent and coveted Portfolio Management Professional (PfMP)® credential.











Journey To Obtain PfMP® Credential 
#1. Submitted PfMP® application on 06/16 and got a mail next day from PMI stating that my (PfMP)® application has been accepted and asked me to proceed to make the payment
---Will be sharing tips on filling PfMP application in a later post---

                                 


#2. Made the payment same day and immediately was notified that my application was selected for auditing
   
                                     

 #3. Got the audit package endorsed by one of my portfolio sponsor & supervisor (COO) and Fedex'ed it to PMI on 06/19. Package reached PMI on 06/24 and same day got the mail stating that i have cleared the audit process and moved to first evaluation, the Panel review
                               


#4. In the handbook it is stated that Panel review takes 10 working days and I was getting impatient as the days passed because it actually took more than 10 working days when finally got the mail on 07/11 stating that I have passed the first Panel review evaluation

                               


#5. Referred my PfMP notes, below reference materials and sample exam references and scheduled for taking the exam on 07/16 (exactly one month after applying), obtaining PfMP® credential. 

                               














Exam Tips
#1. Exam is 4 1/2 hours long so make sure you are mentally preparing yourself to sit for that long and devoting with full concentration. Even though this seems very obvious but professionals who have been managing portfolios would have empathy that in our professional daily life, which is packed with meetings, presentations, submitting/reviewing proposals, training & mentoring resources, one seldom gets an opportunity to sit in front of system for that long and not to mention answering bunch (read 170) of questions while concentrating on which answer(s) to eliminate as more often than not, more than one answer can be applicable. 

#2. One can answer some questions based on their practical Portfolio experience but since not all Portfolios are managed ideally the way it is described in the The Standard for Portfolio Management, its important to think from what is described in the The Standard for Portfolio Management while answering the questions in the exam  

#3. Its important to understand all process groups, knowledge areas, processes & their respective ITTOs (Input, Tools & Techniques and Outputs). Expect some direct questions and some indirect questions on ITTOs. 
---Will be sharing my Study Aid on ITTOs in a separate post---

#4. Expect few questions that are related to analyzing which Portfolio component to select or not to select (NPV, IRR, Weighted Ranking & Scoring, etc.) 

#5. Personally I did not get many questions from A Guide to the Project Management Body of Knowledge (PMBOK) or The Standard for Program Management but understand from other's experiences that folks did see questions referred from the two standards. 

#6. As stated in #1 there are few questions for which more than one answer could be applicable so key is to eliminate the least applicable (or select the most applicable). In my case, answering first few questions made me feel uncomfortable as I was not 100% sure of which is most applicable answer so 'marked' the questions. After marking initial questions, I got into the mode and was able to answer subsequent questions with more ease. Having said that, I did continue marking questions and would have marked ~35% (~60) of my questions.  

#7. Personally I always recommend taking a break to rejuvenate, so after finishing answering 170 questions while marking ~60 of them, I took a break. It took me little less than 2 hours to finish answering 170 questions so i could afford a break. After the break, I went through all 'marked' questions and now could think more clearly. It helped me to change answers to almost ~10 questions and feeling more confident on the answers. This time I took more time to go over 'marked' questions and finally finished my exam in 3 hours time. 

#8. To keep things simple for me, I always rely on notes and tend to joggle down points so that I do not need to strain myself while trying to remember. So in the first 10 minutes, while tutorial was running, used scribbling pad provided to me in prometric center to joggle down all ITTOs mapped with processes & respective KA's

#9.  Its important to understand the difference between Strategic Plan, Portfolio Charter, Portfolio Roadmap, Portfolio Management Plan, Portfolio and Portfolio Process Assets. In practical we do use in our Portfolios all of them in some form but sometimes there are overlaps, so its important to understand how The Standard for Portfolio Management clearly segregates their respective inputs, contents and timing of updates. 

#10. My personal experience about PfMP® exam was that I found it easier than any of my previous exam. This was maybe because I now have a sense of understanding of what PMI recommends in terms of standards and how the layout of questions would be. 



Reference Materials
1. Pfmp® Handbook
2. The Standard for Portfolio Management, Third Edition
3. The Standard for Program Management, Third Edition
4. A Guide to the Project Management Body of Knowledge, Fifth Edition
5. PfMP Examination Content Outline
6. PfMP® Exam Practice Tests and Study Guide 
7. Managing Change In Organizations
8. Business Driven Project Portfolio Management: Conquering the Top 10 Risks
9. Mastering Project Portfolio Management
10. Managing Change in Organizations (PMI Article)
11. Portfolio Risk Management (PMI Article)
12. Agile Processes A Unifying Approach for the Future of Projects (PMI Article)
13. Do's and Don'ts for Portfolio Managers (PMI Article)
14. The Power of Portfolio Management (PMI Article) 
15. Strategic Portfolio Management Governance Financial Discipline
16. Unified Portfolio Management Model Paper
17. Use PfM to maximize IT spending
18. PfM keeps IT aligned with business strategy
19. Portfolio Kanban
20. Priority Systems Glossary 
21. Efficient Frontier 
22. Using project portfolio management to improve business value (IBM Article)
23. Project Selection and Portfolio Management
24. Enterprise Risk Management
25. Project Portfolio Risk Management 

Sample Exam References 
1. PfMP® Exam Practice Tests and Study Guide
2. http://www.pmoadvisory.com/live/pfmp_training/
3. http://www.cheat-test.com/Samples/PfMP-Exam.html