Successfully reported this slideshow.
Your SlideShare is downloading. ×

Key Concepts for Project Mgmt

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Loading in …3
×

Check these out next

1 of 14 Ad

Key Concepts for Project Mgmt

Download to read offline

Compilation of key concepts for Time Management and Project Scheduling & Project Mgmt

Learn more tips & techniques at www.pmpwisdom.blogspot.com

Register for a free webinar at

https://pmpwisdom.blogspot.com/p/webinar.html

Compilation of key concepts for Time Management and Project Scheduling & Project Mgmt

Learn more tips & techniques at www.pmpwisdom.blogspot.com

Register for a free webinar at

https://pmpwisdom.blogspot.com/p/webinar.html

Advertisement
Advertisement

More Related Content

Slideshows for you (20)

Viewers also liked (20)

Advertisement

Similar to Key Concepts for Project Mgmt (20)

More from Jaiveer Singh (16)

Advertisement

Recently uploaded (20)

Key Concepts for Project Mgmt

  1. 1. Key Concepts of Project Management  Brief overview using easy to understand analogies Compiled By: Jaiveer Singh, PMP
  2. 2. Project Feasibility - Illusion or Reality
  3. 3. Scheduling is Modeling
  4. 4. Progressive Elaboration – Moving From the Unknown to the Known Progressive elaboration, is defined by PMBOK*as “continuously improving and detailing a plan as more detailed and specific information and more accurate estimates become available as the project progresses, and thereby producing more accurate and complete plans that result from the successive iterations of the planning process”.
  5. 5. Understand Project Landscape
  6. 6. Identify Project Hidden Challenges The Tip of the Ice Berg
  7. 7. Few Common Project Challenges
  8. 8. Panoramic Project Planning How many times have you heard about looking at the “big picture”? Taking in the full panorama of the landscape during a project planning phase could not only help you plan a better project, but it could flush out some key details that could be lurking just off camera, especially the ones that may not have hit you until just before “Go Live”. 8
  9. 9. Understand Project Activities Network
  10. 10. The Living Project Schedule • Project planning isn’t just an activity for the start of the project--the project plan must be a living, evolving document that is updated and changed on a regular basis. 10
  11. 11. Project Planning for Beginners • The good project manager involves their team in project planning...the great one teaches them how. 11
  12. 12. Identify & Mitigate Risks • Hidden traps often come from surprising sources, resulting in project delays or funding shortfalls. It is critical to identify all the risks up front, establish mitigation strategies and allocate ample time and budget to overcome any hurdles. How? Through effective planning, of course! 12
  13. 13. Project Diagnosis Pulse check: Assess the burn rate. Are you eating up budget faster than you anticipated? What is the new estimated total cost? Blood pressure: Perform a risk assessment, in terms of what could happen between now and the go live date to cause a significant incident. Various frameworks exist for this assessment. The Six Sigma FMEA (Failure Mode and Effect Analysis) template can be modified to suit your needs here, giving you an objective framework for assessing all possible places where your solution could fail, and steering your future corrective actions toward those that have both the highest likelihood of occurrence and greatest criticality. Temperature: Create a heat sheet (red yellow green) with respect to key milestones. This should be part of your regular status report, along with some basic trending. 13
  14. 14. Compiled by: A practitioner of Analytics, Productivity, Information Modelling, Enterprise ProjectProgramPortfolio Management & Execution Management. Jaiveer Singh, PMP Project Management Trainer focusing on MS Excel, MS Project and MS EPM product to improve productivity of management community. @ singhjaiveer Working as Project/Program & Portfolio manager for large IT projects http://www.slideshare.net/Jaiveer www.singhjaiveer.blogspot.com www.project-management-practice.blogspot.com

Editor's Notes

  • Scope Delivery Feasibility
  • Rolling Wave Planning We can see more clearly what is in close proximity, but looking further ahead our vision becomes less clear. Depending upon the project - its length and complexity - we may be able to plan as much as a few weeks or even a few months in advance with a fair amount of clarity. Rolling Wave Planning is a multi-step, intermittent process like waves - because we cannot provide the details very far out in our planning. A detailed, well-defined WBS is created for that period of clarity, and only milestones are highlighted for the rest of the project. Progressive Elaboration is what happens in rolling wave planning process. Progressive Elaboration means that over time we elaborate the work packages in greater detail. Progressive Elaboration refers to the fact that as the weeks and months pass we have planned to provide that missing, more elaborated detail for the work packages as they now appear on the horizon. Generally in development projects the scope progressively elaborates, this poses a great risk to schedule/cost as the estimation is usually done during the start of the project and not all elaborations are considered as changes.
  • Get to the depth of issues to understand their impact
  • Obtain a thorough patient history : Skilled medical diagnosticians may not rely solely on the patient’s recollection. In some cases they need to interview family and friends to obtain information on subtle symptoms. When trying to diagnose failing projects, they shouldn’t don’t rely solely on direct interviews of the project team. A multi-perspective view of the situation is needed: Have a closed-door session with the project sponsor : Find out what the key issues are with the project and begin to explore areas where a rescoping might help bring things back on track. Find out what kind of scope reductions are likely to be accepted by the business, and which might require significant salesmanship or a fierce battle. Understand the organization’s politics so that you can factor them into your corrective action plan. Talk to the project stakeholders about their original expectations, their current concerns, and any difficulties they may be experiencing with the project team. Create comfortable communication channels with all members of the project team , and dig deeper than project plans, status reports and issues logs. Find out what is causing project anxiety within the team. There are often valuable clues here. Be sure to probe any areas that are glossed over or brushed aside quickly. Take the project’s vital signs : Pulse check : Assess the burn rate. Are you eating up budget faster than you anticipated? What is the new estimated total cost? Blood pressure : Perform a risk assessment, in terms of what could happen between now and the go live date to cause a significant incident. Various frameworks exist for this assessment. The Six Sigma FMEA (Failure Mode and Effect Analysis) template can be modified to suit your needs here, giving you an objective framework for assessing all possible places where your solution could fail, and steering your future corrective actions toward those that have both the highest likelihood of occurrence and greatest criticality. Temperature : Create a heat sheet (red yellow green) with respect to key milestones. This should be part of your regular status report, along with some basic trending. Other specialized diagnostic tests as needed - Assess the scope (original and current), review the technology strategy, development strategy, testing strategy, release strategy and change management strategies. http://www.pmhut.com/rescuing-a-project-diagnosis

×