Mix & Match
by Cyndee Miller
It was almost like watching rival cliques at school, die-hard agilistas matching wits with waterfall purists. The drama was always quite civil, mostly limited to snobbish comments dismissing the merits of the rival approach.
But lately — and frankly, I never thought I’d say this — they’re learning to play nice.
Some of this comes down to organizations not willing to take sides. They’re simply letting the best approach win.
“Most companies are becoming more results-oriented and less methodologically dogmatic,” said Bryan Berthot, PMI-ACP, PMP, project manager, AT&T Entertainment Group in a recent article on PMI.org. “They empower their project teams to choose their preferred project management framework — as long as they deliver results.”
Forget the preconceived notions. Teams are using whatever they need for the project at hand.
Check out the numbers in PMI’s 2017 Pulse of the Profession: While plenty of project professionals said they relied on agile or waterfall for recent projects, 20 percent used hybrid. And 23 percent relied on something other than agile, hybrid or plan-driven approaches, which could be a further blend or customization of approaches.
Social networking king and Silicon Valley mainstay LinkedIn seems like a natural for all agile, all the time. But when the company launched an overhaul of its website, the project leaders decided to go hybrid.
Mind you, this is a company steeped in sprints and fast-track developments, and now it’s adopting an agile/waterfall hybrid approach. The rationale? Allow project managers to incorporate user and stakeholder feedback — while retaining a sense of urgency.
“This hybrid approach enabled us to define requirements at the beginning of the project and provided the needed flexibility and transparency to adapt to the fast-changing requirements,” Ranjit Dhaman, PMP, senior staff technical program manager at the company, told PM Network. “We were building a foundation for future product innovation, and a quick turnaround time was needed to keep up the pace with daily product releases.”
It’s not just agile teams adopting waterfall ways, of course.
French tire-maker Michelin says it’s developing an agile approach to project, program and portfolio management.
“We believe that agility could also be used in multiple ways — in everything we do,” Philippe Husser, senior partner, progress direction, said in PMI’s latest Pulse of the Profession. “The world is changing very quickly around us, so much so that we cannot afford anymore to have projects taking two to five years to deliver because, during this time, the initial requirements have changed.”
The company now has project managers, along with a steering committee and project sponsor, select the best approach for each project together.
It’s just like those fine ladies of En Vogue would say: Free your mind and the rest will follow.
What’s happening on your projects? Do you and your teams gravitate toward one approach? Or are you doing whatever you need to do?
by Cyndee Miller
Agile is the punk rock of project management. After years of living on the fringe, it’s officially gone mainstream—much to the joy of some and the utter dismay of others.
Like punk, it was built around a call to disrupt the status quo.
When a group of software programmers wrote the agile manifesto 16 years ago, the big goal was to embrace change: “to be aware of changes to the product under development, the needs and wishes of the users, the competition, the market and the technology,” Andy Hunt, a co-author of the agile manifesto, told PM Network last year.
While that purpose still holds true, the agile club is no longer limited to software developers, startup leaders and waterfall haters. An HPE survey showed agile’s ascendancy from anti-establishment to mainstream really took off in the past five years, with a significant adoption inflection point occurring around 2010. And check out the current numbers: Ninety-four percent of the survey respondents in the latest VersionOne State of Agile survey said their organizations practiced agile. PMI recently partnered with Agile Alliance on an Agile Practice Guide.
Some of this comes down to the business world’s obsession with digital transformation, which 42 percent of execs say they’ve begun, according to a 2017 Gartner survey. As Jason Bloomberg, president of Intellyx, wrote: Companies are increasingly going agile “to successfully navigate the disruptive waters that threaten to drown them.”
Take South Africa’s Standard Bank. Facing competition from a rapidly expanding fintech sector, this 155-year-old bastion of financial service embarked on a multiyear digital transformation—with a shift to agile software dev at the center, according to McKinsey.
Not everyone, however, was onboard. I know, shocker, right? To change hearts and minds, the company’s CTO and his team held town hall meetings to explain their logic and set targets for the transition, gave teams autonomy to make decisions on how to go about their day-to-day functions, and co-located team members for better collaboration.
So far, so good. In early agile engagements, Standard Bank reported productivity increases of up to 50 percent and unit-cost reductions of up to 70 percent per function point.
But for some, agile’s entrance into the mainstream has given rise to a new challenge: the dilution of the very term. Mr. Hunt told PM Network the word has become “sloganized” and is “meaningless at best, jingoist at worst.”
In that same article, Jordi Teixido, PMP, COO at Strands, Barcelona, Spain, said: “Agile is wonderful when you’re really iterating and collaborating, but it’s also a refuge for mediocre practitioners who are unable to document or express their requirements or forecast what they want to build. If you don’t follow the rules of the game in waterfall, everyone knows it. But in agile, that’s harder to tell from the outside—and because of that, some people use agile on projects that would be far better under waterfall.”
What do you think? Is your organization using more agile? And do companies have a grasp on what the term really means?
3 Tips to Enhance Your Leadership IQ
Education and Training,
Human Aspects of PM,
Reflections on the PM Life,
Categories: Benefits Realization, Best Practices, Career Help, Change Management, Communication, Communication, Complexity, Education and Training, Ethics, Facilitation, Human Aspects of PM, Human Resources, Innovation, Innovation, Leadership, Leadership, Lessons Learned, Lessons Learned, Mentoring, Program Management, Project Delivery, Project Failure, Project Planning, Project Requirements, Reflections on the PM Life, Risk Management, Roundtable, Social Responsibility, Stakeholder, Strategy, Talent Management, Teams
By Peter Tarhanidis
The boards I serve have common opportunities and challenges revolving around promoting a brand, balancing the operating budget and growing capital. Yet, while flawless leadership is expected, in actuality it is difficult to sustain.
As I reflected on why many organizations were challenged around execution, I realized that executives must improve their leadership intelligence around three key factors to enable success:
In my experience as a mentor and leadership coach, these tips can help align decision-making, leader accountability and stakeholder engagement to the needs of the customers, and improve the overall culture of the organization. As a result, the brand will come to life.
How have you improved your leadership intelligence?
by Dave Wakeman
Project managers, first and foremast, are often considered as communicators. Early on, when I first received my Project Management Professional (PMP®) certification, I remember someone telling me that 90 percent of a project manager’s job was communicating.
The thing about communicating is that in too many instances we consider it to be about talking at or to people. But how much time do we really spend listening—far and away the most important part.
Listening should be one of your strongest strategic allies. It enables you to get on-the-ground information, allows you to tap into experts, and helps you to see the real role and value that the project can play in your organization.
Here are a few ideas on how to make listening a bigger part of your communication strategy.
1. Be open and engaged to the feedback of your stakeholders. It’s easy to say that you are open to conversations and that feedback is something you want, but are you actually following through in a meaningful way with your stakeholders?
If we aren’t careful, it’s entirely possible that we say we want to hear from people. But in practice, we rush them, dismiss their concerns and quickly shuffle them off to something else.
You need to be present and open to conversations from your stakeholders and not attempt to end the conversations as quickly as possible. Your colleagues and stakeholders may not be able or willing to get to the point right away due to nerves, the need to come up with a new idea through conversation or some other underlying factor.
2. Ask questions. This goes along with being open and engaged. One of the key skills I have developed over the years as a consultant is the ability to use questions to uncover the real challenges at the heart of a situation.
As a project manager, people will come to you with a conversation that is often built around pain.
“Our project is delayed.”
“Our teams aren’t working well together.”
“We don’t have the budget to complete this task.”
The real issue lies with one question: “Why?”
You must ask the questions that uncover the root causes of the pain that aren’t being spelled out in the conversation.
3. Keep an open mind. As a modern day project manager, you aren’t going to have all the answers. The beauty of the modern project is that everyone has a specialty that they are handling. They have unique experiences that they bring to the project and their point of view is going to be different than anyone else’s.
Your job as a project manager is to harness that expertise and direct it in a manner that enables you and your project to receive the best possible benefit from all these experiences, experts and ideas.
To do that, you need to be open-minded, which means that you have to be careful not to allow your preconceptions overwhelm the information being presented in the conversation. You have to be open to the idea that new information will change the information you already have and the ideas that you have already formed.
If you keep these ideas in mind, you will be a better listener. If you are better at listening, you will likely be a better communicator—and this will make you a better project manager.
How have you developed your listening skills?
BTW, if you like this stuff and the stuff I usually post, I do a Sunday email that talks all about value, connection, and humans. You can get that for free by sending me an email at dave @ davewakeman.com
Maximizing the Value of Agile
By Lynda Bourne
Everyone wants to “go agile.” But far too many organizations seem to think agile is simply a different way of doing project work that will miraculously achieve major efficiencies.
For the approach to achieve its promise, the upper echelons of the organization need to become agile aware and adapt the way projects are initiated, funded and governed so that the project team can optimize their use of agile processes to create value. After all, one size does not fit every situation in an agile world.
I’d like to look at the differences in the management approach that are needed to maximize the value of agile in different situations.
One quick note: Different agile methodologies have different terminology and approaches. For this post, agile is defined as producing an output using a series of relatively short, time-boxed iterations, or sprints, where the work to be accomplished in each sprint is sized to be relatively consistent (e.g., can be accomplished by a team in two weeks), and what is to be done in each sprint is determined during the lead-up to that sprint.
There are three environments where the agile approach can add value:
1. Maintenance environments: In these efforts, the application of agile concepts without the need for project management overheads can be very beneficial. Techniques including small focused teams, short sprints, backlog prioritization, and management. Burn down reporting can show how much maintenance work is facing the teams, the team efficiencies, and the overall backlog trend.
Agile does not need to be embedded in a program or project to be effective. In this situation, the finance and resources (i.e., the agile teams) are the fixed constraints; the organization’s budgeting procedure funds a predetermined level of staffing on an annual basis. The management variable is the amount of work accomplished each month and deals with new and emerging maintenance issues and minor enhancements in a timely manner based on some effective form of prioritization.
2. Contractual or legal obligations: In projects like these, the scope of work is fixed (or at least subject to formal change control) and the management variables are efficiency and cost consequences. In this environment, with adaptation, a whole range of standard project management processes such as earned value can be applied to the oversight of project work and used for management reporting and project control. The agile teams still function in the traditional agile way, sizing the amount of work included in each sprint, producing usable outputs in short intervals and progressively building toward the completed project. The management challenge is achieving the specified scope within the approved time and cost parameters.
3. Projects that lack a defined scope: In these projects, the client often has a vision of what the outcome should achieve, frequently framed in terms of business improvements. In this situation, the project is on a journey to optimize the delivery of as much of the vision as is sensible. The management variables for this type of project include scope, cost and time.
Decisions will have to be made about which parameters are more important—either as an overall consideration or on an element-by-element view of the various components within the project.
a. In some projects, time to market is a key factor, possibly with scope as the second most important factor. And, to a large extent, how much it costs to achieve the necessary scope within the deadline will be a consequence rather than the control. The primary management challenge is delivering the scope required to implement the vision within the time constraint as efficiently as possible.
b. Other projects have the quality of the vision as their primary drive, and the management challenge is to achieve all of the vision for the optimum time and cost outcomes. Decisions on how much and how long can vary depending on progress toward achieving the vision. Obviously, there must be some cost and time constraints. And a key conversation with the client has to be around the value proposition of still achieving their vision based on cost information to date, with the possibility of adapting the vision based on learned experience as the project proceeds.
c. Lastly, in some projects where the available funds are limited, the challenge for management is to achieve as much of the vision as possible within the defined funding limit, frequently with time as an additional limitation imposed by the funding cycle or the market. To maximize value, the client needs to be fully engaged in the decision-making process around scope inclusions, deferrals, and exclusions.
Once you understand the agile framework you’re operating within, the real challenge is making sure your clients and other senior stakeholders also understand that an agile approach to project delivery requires very different governance and decision-making processes. Organizational agility starts at the top by setting the right challenges for the agile teams within the right funding model. The next step is to use appropriate assurance functions to make sure agile teams are delivering what’s needed to create value—old-fashioned budgeting processes are unlikely to be appropriate.
How do you go about engaging your senior stakeholders in this type of conversation?