In my last post A Better Path Forward For Federal Programs , I discussed how the Program Management Improvement Accountability Act empowers the Office of Management and Budget to create a program and project management strategy for the U.S. federal government.
The legislation also requires the heads of several U.S. government agencies—including the Departments of Agriculture, Department of Labor, Department of Commerce, Department of Energy and Department of Education—to designate one senior team member to serve as its program management improvement officer. In this role, the senior team member will be responsible for implementing program management policies established by the agency and developing a strategy for enhancing the role of program managers within the agency.
The program management improvement officer also has another set of responsibilities that I find particularly interesting. The law says the project management improvement officer must develop a strategy for enhancing the role of program managers within the agency. This includes expanding training and educational opportunities for program managers. This portion of the legislation creates a formal process for program managers to strengthen their existing competencies and allows project managers to develop into program managers (I once wrote a post on this topic).
Given the complexities inherent to contemporary program management, professional development initiatives will successfully prepare program managers for progressively larger delivery responsibilities. In addition, they will create an opportunity to centralize lessons learned on existing delivery programs for even more effective future program management.
Admittedly, when I first heard of this legislation, I was somewhat doubtful of its ability to influence program management results. However, after diving into the details, I’ve become an advocate. I’m excited about the new standard it will set for federal program delivery—and the prospects it holds for building similar program management capabilities in the private sector.
We may jest about the effectiveness of government regulations, policies and practices—but this legislation has the potential to significantly boost program management innovation in the public sector.
Do you believe the Program Management Improvement Accountability Act will spur program delivery improvements in your workplace?
By Kevin Korterud
Program management made news in December (though perhaps not front-page headlines) when the United States Senate unanimously approved the Program Management Improvement Accountability Act. The legislation enacted a number of initiatives for improving federal program delivery, which has suffered from past budget, schedule and quality challenges.
While government legislation is not necessarily my weekend reading of choice, I recently spent time reviewing the new law. It quickly became apparent to me that, although targeted at improving the delivery of U.S. federal programs, it includes many considerations that are universally relevant to program delivery, even if you’re working in the private sector.
As part of the legislation, the deputy director of management at the Office of Management and Budget has been tasked with several new functions related to program and project management. Let’s take a look at two that I find particularly exciting and relevant to program managers around the world.
1. Chart A Strategic Course
Executives often tell me they don’t know where to start when it comes to improving program delivery. There are typically so many interrelated issues that it’s difficult to determine which actions would have the greatest impact on delivery results.
Other disciplines, such as technology architecture, business change management and customer satisfaction, typically work from some sort of strategic or transformational roadmap. The roadmaps identify common issues, solution strategies and transformational initiatives that drive success for that discipline.
The new federal legislation requires the deputy director of management to “establish a 5-year strategic plan for program and project management.” A program management maturity roadmap will provide a common vision around necessary improvements. And given the size and complexity of federal programs, it will also help teams avoid repeating prior delivery missteps, and enhance the performance of program management processes.
2. Lay a Solid Foundation
Early in my project and program management career, it was common for companies to have a homogenous, centralized employee workforce with strong business and technical domain knowledge that was built over many years. Today, the landscape of program delivery is much more fragmented and fragile.
Global delivery centers, various delivery approaches (waterfall vs. agile), business leaders that rotate every few years, contractors that play a larger role in delivery and emerging technologies are all components that complicate program delivery. It is a wonder that program delivery is ever successful!
The new federal legislation says the deputy director must also, “oversee implementation of program and project management for the standards, policies, and guidelines…” The creation of program management standards, policies and guidelines will serve as a foundation to harmonize the discordant realities of modern program delivery. By establishing unified rules, boundaries, practices and performance metrics that drive a cohesive approach, the inherent complexities of today’s programs can be successfully addressed.
What elements of the Program Management Improvement Accountability Act do you find most intriguing? I look forward to discussing.
The 3 Things That Transcend All Project Approaches
Human Aspects of PM,
New to Project Management,
Categories: Agile, Best Practices, Change Management, Communication, Complexity, Facilitation, Generational PM, Government, Human Aspects of PM, Innovation, IT, Leadership, Lessons Learned, Mentoring, New to Project Management, PMOs, Program Management, Project Delivery, Project Failure, Stakeholder, Strategy, Talent Management, Teams
by Dave Wakeman
Recently I had the chance to engage with Microsoft’s social media team about some of the issues I have been covering here. Their team brought up a question you may have asked as well: How do you differentiate between “digital” project management and project management?
It’s an interesting question, because I firmly believe all projects should be delivered within a very similar framework. The framework enables you to make wise decisions and understand the project’s goals and objectives.
I understand that there are many types of project management philosophies: waterfall, agile, etc. Each of these methods has pros and cons. Of course, you should use the method you are most comfortable with and that gives you the greatest likelihood of success.
But regardless of which project management approach you employ, there are three things all practitioners should remember at the outset of every project to move forward with confidence.
Every project needs a clear objective. Even if you aren’t 100-percent certain what the “completed” project is going to look like, you can still have an idea of what you want the project’s initial iteration to achieve. This allows you to begin work with a direction and not just a group of tasks.
So, even if you only have one potential outcome you want to achieve, starting there is better than just saying, “Let’s do these activities and hope something comes out of it.”
Frameworks enable valuable conversations. I love talking about decision-making frameworks for both organizations and teams. They’re valuable not because they limit thought processes, but because they enable you to make decisions based on what you’re attempting to achieve.
Instead of looking at the framework as a checklist, think of it as a conversation you’re having with your project and your team. This conversation enables you to keep moving your project toward its goal.
During the execution phase, it can give you the chance to check the deliverable against your original goals and the current state of the project within the organization. Just never allow the framework to put you in a position where you feel like you absolutely have to do something that doesn’t make sense.
Strong communication is the bedrock. To go back to the question from Microsoft’s social media team about digital vs. regular project management: the key concept isn’t the field or areas that a project takes place in.
No matter what kind of project you’re working on and in which sector you’re in, the critical skill for project success is your ability to communicate effectively with all the project stakeholders.
This skill transcends any specific industry. As many of us have learned, it may constitute about 90 percent of a project manager’s job. You can put this into practice in any project by taking a moment to write down your key stakeholders and the information you need to get across to them. Then put time in your calendar to help make sure you are effective in delivering your communications.
In the end, I don’t think there should be much differentiation between “digital” projects or any other kind of projects. All projects benefit from having a set of goals and ideas that guide them. By trying to distinguish between different project classifications, we lose sight of the real key to success in project management: teamwork and communication.
What do you think?
By the way, I've started a brand new weekly newsletter that focuses on strategy, value, and performance. Make sure you never miss it! Sign up here or send me an email at email@example.com!
By Wanda Curlee
Transitioning from the military into the civilian workforce can be difficult. If you’re interested in project management, however, you may find that you have valuable skills and experience. When I was introduced to project management years after I finished my service in the U.S. Navy, one of my first thoughts was: I’ve done this before.
Still, it can be hard to know how to start a civilian career as a project manager. Here’s some food for thought.
First, think about tasks you did in the military, whether it was organizing a 5K race or walk for the base, preparing for deployment, returning from deployment, or staging a change of command or retirement ceremony. Just like in project management, all these tasks had a definite beginning and end. Even if the event had been held before, each time was unique. For all of these tasks, a team helped you implement your project.
As you delve into project management as a possible career, I suggest reviewing Project Management Institute’s A Guide to the Project Management Body of Knowledge (PMBOK® Guide). You may discover your military experience directly relates to the project management knowledge areas it details:
Integration management is making sure that processes and project management activities occur when they should. In other words, you would not finish the planning for the change of command ceremony when you are just starting the project. Tasks can happen in parallel and can jump from process to process, but need to occur in an orderly fashion.
Scope management is about making sure the project doesn’t expand beyond what was agreed upon with the project sponsor. For example, you are leading the team that ensures all heavy equipment arrives back at the base after deployment. Your scope is the heavy equipment, not the laptops and desktop computers. Scope change may not be bad, but it has to be monitored.
Cost management can be tricky for military personnel because some types of military projects—such as returning a unit home from overseas deployment—don’t always have clear budgets. But many, such as organizing a dinner or race, do. If you handled smaller projects such as these, you had a finite amount of money—and you knew it would not be fun to have to ask your superiors for more.
Quality management is straightforward in a military context. Anyone who has served as junior officer or senior enlisted officer has made sure the team followed the rules and made good judgment calls.
Human resource management is a no-brainer for officers and senior enlisted officers: they know how to lead teams. (By the way, one of my pet peeves is how PMI refers to human resource “management” rather than leadership.)
Communications management is another no-brainer. Without communication in the military, no one would survive. On a project, communication is formal and informal, and both types need to be documented.
Risk management is understanding what about the environment or team might derail the project. In my day, we commonly referred to this as “operational planning.”
Procurement management is what you need to buy for the project. You might not have had experience with this in the military, but if you have been given a budget, you may have dealt with various vendors to determine the best deal to implement your project.
Stakeholder management is the process of leading the individuals who have a stake in the project, and dealing with any concerns they may have. This is all about knowing people, including their likes, wants and agendas, and managing those.
If any of this piques your interest, consider pursuing a project management certification to develop your skills and signal them to potential employers. In the civilian world, the most globally known one is PMI’s Project Management Professional (PMP)® credential. (A list of PMI’s registered education providers is here.)
If you hope to work for the civilian side of the U.S. military, check out the Defense Acquisition University (DAU). Anyone with a current U.S. military affiliation is eligible for free DAU courses and certifications, which aim to develop the U.S. Department of Defense’s acquisition (aka procurement/contract) management workforce.
Beyond certifications, many universities and companies offer project management certificates and degrees. Not all of these programs are well respected, so make sure to examine their curricula closely before signing up and/or get to know their reputation through online research. (A directory of accredited university programs around the world is here.)
LinkedIn groups can also help you transition into civilian project management and deepen your project management knowledge. (I recommend the Gr8MilitaryPM group.)
Finally, keep in mind that as a transitioning service member, many free or low-cost training options may be available to you. For example, in the United States, funds for training and certification exam reimbursement are available to military veterans through the Department of Veterans Affairs and the G.I. Bill.
If you’re in the Northern Hemisphere right now, you may be dealing with inclement winter weather. That in turn means your local public officials are dealing with how to communicate during a crisis. Project practitioners can learn from them.
Late last month in New York, New Jersey and the New England region in the United States, officials were tasked with preparing citizens for a snowstorm called “historic” before it arrived—but which ultimately spared New York City and neighboring New Jersey. New York City Mayor Bill de Blasio had to defend the decisionto shut down the city’s subway system due to snow for the first time in its 110-year history.
Similarly, project managers must be aware of the downsides involved with communicating risks on fast-changing projects to stakeholders. If flagged risks don’t materialize, we might find ourselves unable to gain cooperation at a later date.
Here are three communication rules of thumb, each corresponding to a project stage, to keep in mind when you have imperfect information about a project with constantly changing variables—but still must address stakeholders.
1. Plan ahead: One of the first rules of crisis management is to be fully prepared for a crisis.In New York City last month, we saw de Blasio and Gov. Andrew Cuomo get out early and explain that the forecast indicated the storm could be the largest in the city’s history. Only 6 inches of snow ended up falling, but the city’s leadership did have a good plan and did effectively prepare the population for the storm.
What can practitioners take away from this? Depending on the type of project you are running, take a few moments to think about how you are going to communicate with your team in case of a problem or uncontrollable event occurring, even if it’s just laying out the steps you need to take on the back of an envelope.
2. Have a clear message:When you are communicating in a variable or crisis situation for your project, you need to have a consistent message, even if you are delivering imperfect or changing information.
Think about how the U.S. National Weather Service issues “advisories,” “warnings” and “watches.” Although some people can be confused by these terms, the service’s definitions of them are distinct.
As a project manager, you may want to put your stakeholder messages into three categories: best case, worst case and most likely case, for example. Choose whichever categories work for your project and clearly define them. Bottom line: Confidently communicate what you know and how it will impact the project and your stakeholders.
3. Review and adapt: Like all good project managers, you likely review best practices at the end of your project. If the project involved communicating in crisis—whether related to weather or a different kind of variable circumstance—it’s especially important to take a few moments at the end to review what worked and what didn’t.
Like the planning and messaging stages noted above, the review doesn’t need to be highly complex. These questions can elicit communications lessons learned:
• How well did my plan allow me to begin communicating early in the crisis?
• Was my message easy for all stakeholders to understand?
• What about my communication delivery methods worked? What didn’t work?
• Did stakeholders respond to my message in the way that I wanted?
These are just three approaches crisis communications. How have you overcome communication challenges driven by project crises or adverse situations in your organization?