We all need to learn from the past, but what do you do if you weren’t part of that history? Virtually no project exists in isolation. It is always building on something that was done before, preparing for something to be done in the future, or both. New and younger project managers may not know that context.
Connect In Person
The 3rd annual PMI Talent & Technology Virtual Symposium will equip participants with the skills to address current challenges and the roadmap to guide them through the constant change of the future. Our lineup of speakers will examine the ways in which project professionals have responded to crisis and share lessons to evolve beyond it.
We start the new decade with a bang as we present the 13th edition of our annual virtual conference and exhibition! Whether you’re a seasoned PM or new to the field, PMXPO provides an excellent opportunity to learn, network, earn PDUs and broaden your perspective on project management. This year’s show is headlined by keynote speaker Cara Brookins, a bestselling author who rebuilt her broken family by building her own house watching “how-to” videos on YouTube.
Love project scheduling? Or just want to learn what’s new in the world of project scheduling? Attend the PMI Scheduling Conference – exclusively for PMI Members. Learn the latest in scheduling best practices not available anywhere outside of PMI. We’ll share tips and tools from real-life projects and programs.
The purpose of this presentation is to summarize and share the strategies, planning, and execution lessons learned from a large scaled Windows 7 to Windows 10 migration project at a large Health Care provider organization. The author will share the challenges presented, and the tactics and techniques developed and implemented by his team to complete the project on schedule and on budget. This is not an instruction guide on how to plan and execute a Windows 10 migration project. This presentation simply shares their lessons learned and best practices with the hope that the audience can harvest one or more point to apply in any future desktop operating system migration project.
Agile, for many a silver bullet, worked pretty well for software development teams with most of them being the first attempt to have a structured approach. Bringing some order to chaos was beneficial, and the results were in some cases spectacular. Most, if not all Agile frameworks were developed by software engineers and for software engineers. Apart from a couple of frameworks, like Disciplined Agile and SAFe that combine Agile with traditional Lean practices used in manufacturing, most Agile frameworks were developed for small teams (less than 10) and a start-up culture. In real life, Agile does fail, more often than we think and far more often than we learn in the training courses. Agile became the victim of its success with some organizations trying to use Agile as a remedy for core issues like lack of vision, lack of decision or even lack of skills. Contrary to public opinion, Agile and self-organization require more skills and discipline than command and control. To be Agile, an Organization must be Agile at all levels not only at the team level. Agile is based on trust; verbal agreements should be enough. There is no need of sign-offs and approvals for each and every activity. But that's a risk when there are multiple parties involved, especially when commercial agreements are made between entities. This webinar is a collection of real life projects that had to balance Agility with traditional practices. In most cases, the solution was the return to following a plan. For each example there will be an assessment of the causes that lead to failure, what the organization could've done better, and lessons learned that could prevent such issues.
Advance Your Career
Per the Agile Business Consortium, business agility allows businesses to adapt quickly to market changes; respond rapidly and flexibly to customer demands; adapt and lead change in a productive and cost-effective way without compromising quality; and continuously be at a competitive advantage. The primary reason for moving to Agile is to achieve faster business value and keep you ahead of the competition. Agile is built for change - fundamentally, it is about creating Business Agility. It enables the enterprise to deliver projects more efficiently, with relentless focus on business value and providing the highest return on investment. Whether it is a software project, a new service offering or a new product, Agile’s twelve principles and three pillars (transparency, inspection, adaptation) are designed to reduce money spent on undesirable or unusable features which were built based on outdated requirements.
What must we do to bring about a Change initiative as smoothly as possible? Communicate! Communicate! Communicate! How much, and for how long do we do this? Until we get sick and tired of the sound of our own voice – then we take a deep breath and a drink of water and we start all over again. Communication isn’t something that stops and starts; it’s a constant activity before, during and after any Change initiative.
Save Time With Tools + Templates
This Excel workbook provides eight logs and registers to help your project. It includes a Changes Log, a Lessons Learned Log, an Assumptions-Constraints Log, an Issues Log, a Risk Register (with accompanying risk guide and list), a Customer Promise Log, a Project Task Tracker, and an RFI Tracker. It's perfect for new and seasoned PMs alike.
This Excel workbook contains a wealth of templates to help you during your project. It includes a project checklist, charter, budget sheet, risk log, scope change log, project team register, communication reference chart, lessons learned register and more.
This log helps you collate both the positive and negative experiences throughout the life cycle of any software development project. The main purpose of this template is to collect, share, learn and improve from the real-time experiences you encounter during the project.
We all know we are supposed to do a “lessons learned” exercise as part of our projects. Some of us even take the time to go through the motions. The challenge is that lessons learned rarely get paid attention to, and organizational practices rarely change as a result. If we really want to learn from our projects, we need to change how we think about lessons learned.
Learn From Others
The COVID-19 pandemic has prompted a global project. In this article, the author looks at the comprehensive application of project management principles during this crisis.
Project issues will plague even the best-run projects. The project manager must have a strategy to deal with issues, but it is just as important for the practitioner to support the team and control the narrative. Here are four suggestions that project managers can use when conducting issue management.
As ProjectManagement.com celebrates its 20th anniversary, Joe Wynne—a contributor since our very first year—shares a sampling of his PM journal entries from two decades ago!
As ProjectManagement.com celebrates its 20th anniversary, Mark Mullaly—who has been a contributor since our very first year—shares insights that he would most want his younger self to know, appreciate and learn from.
As ProjectManagement.com celebrates its 20th anniversary, author Michael Wood--who has contributed since our very first year--looks back at his introduction to the site, and how it has evolved.
ProjectManagement.com is 20 years old! To celebrate this milestone, we look back at 20 lessons our subject matter experts have shared over the last two decades—one for each year!
As one of the core technical components of the PMI Talent Triangle®, lifecycle management walks us through various project phases before it finally culminates with the termination phase. What is the best way to manage this when project closure is abrupt?
Project management techniques help to establish order and clear lines of responsibility and can be invaluable tools for successful implementation of due diligence efforts. The application of a WBS and a project schedule remove the potential bias of a “done deal” mentality and focus the effort to develop an informed opinion.
Managing projects in a desert environment during the hot summer period presents unique challenges. The author shares his experience and lessons learned from three major oil and gas projects in the Middle East. Tips for managing projects in a similar environment are presented to assist other project managers.
You don’t have to be a seasoned project manager to have a negative view of the lessons-learned process. But is it really such a waste of time? New PMs especially should carry out lessons learned as often as they can. Here are some ways to do that...
Ask a Question