We recently had the honor of speaking with Ori Schibi, author of the book “Managing Stakeholder Expectations for Project Success” Ori will also be a speaker at the PMI Global Congress 2014 - North America, delivering "The Role of the Business Analyst in Managing Stakeholder Expectations " So you kind of get the feeling that he knows what to expect from stakeholders.
Although most of Ori's answers imply an increase in the scope of the BA role and what appears to be additional work volume - he beleives deeply that enhancing the collaboration between the PM and the BA will allow both roles to achieve more effective results with improved efficiently – resulting in less work for each overall.
Q1. How important is the role of the BA in managing stakeholder expectations? Are there ways of increasing or decreasing that importance? (Perhaps by making their power/lack of power to alter scope clear?)
The role of the BA in managing stakeholder expectations is important and can be substantial, even though this aspect of the BA’s role is often overlooked. In fact, there is a strong need for an increase in the BA’s role in managing expectations. There are multiple areas that are inherent to the BA’s role and the knowledge that the BA brings to the table that can provide significant value to the effort of managing stakeholder expectations. The areas of potential contribution span all throughout the project:
1. Take part in performing project complexity and readiness assessments to identify early areas of deficiency or concern
2. Take a more active role in providing information for the Project Charter, utilizing the BA’s knowledge of the business case and other early project-related due diligence activities
3. Establish clear boundaries with the PM on who does what (in the areas of risk, quality, transitioning requirements and scope management, communication, issue management and reporting)
4. Provide the PM with a “package” of background documentation, access information, and existing resources that are applicable to the project
5. Take an active role in managing issues and assumptions
6. Establish guidelines for prioritization and urgency (cross-project and within the project)
7. Jointly (with the PM) define project success criteria and trade-offs that factor in both project and business objectives
8. Help the PM articulate the cost-benefit and impact of actions, decisions or delays
9. Jointly build a set of Health Measures that serve as early indicators to stakeholders of trends and warning signs before performance issues surface
Q2. What are the top 3 ways Project Managers could work with stakeholders to improve stakeholder communications?
1. Focus (i.e. invest time and energy) in building trust, developing a rapport and establishing healthy working relationships with at least a representation of the key stakeholders (partially by utilizing the BA’s familiarity and existing relationships with stakeholders)
2. Establish a Team Contract that outlines a set of ground rules to set expectations and serve as a code of conduct for communication within the team and with external stakeholders. This Team Contract should address three areas:
a. General communication
b. Emails and messaging
c. Meetings and teleconferences
3. Create a Delegation and Escalation system that will free up some of the PM’s time to handle “strategic” aspects of the project (e.g. resource management, cross-project dependencies and business risks), specifically:
a. An “internal” system (within the project team) of delegation and areas of ownership that builds a system of support for BAs and team members to handle an agreed upon set of ongoing “mechanical” responsibilities of the project (e.g. schedule management and certain aspects of reporting)
b. A combined internal and external set of clear escalation procedures for risks, reporting, issues and controls to reduce “noise” in the system.
Q3. What role does the BA play in managing risk? Are they more able to identify risks than the Project Manager?
The BA has the organizational and product knowledge, as well as exposure to project related processes and activities that enables the BA to make an even greater contribution to managing risk than even the PM.
The BA’s involvement in risk management should focus on three categories, depending on the project’s needs and on the BA’s level of experience:
a. Requirements management (i.e. the process) related risks – with the central role the BA plays in the requirements process, he/she needs to (and often does) lead the effort of managing risks related to and around the requirements process, and incorporate all remaining risks into the overall project risks considerations. These are mainly risks that may impact the project success criteria.
b. Requirements and scope (i.e. the product) related risks – the BA needs to capture and introduce into the project risk management process all of the risks related to the actual requirements; i.e. risks that may impact the ability of the project to deliver product and project success. Since the PM has no clear context and visibility into the requirements, the BA is perfectly suited for integrating the requirements related risks into the project.
2. Project risks – beyond the familiarity with the product, the BA is also closely involved with project-related processes, team coherence and performance, roles and responsibilities, and has visibility of other issues, assumptions and constraints. Having this additional set of eyes involved in and interacting with the day-to-day project work can be handy in providing the PM with alerts and help the process of managing by exception.
3. Context for business/operational risk – with the PM typically focusing on project risks (surrounding the project success criteria), many of the PM’s decisions may be “good for the project”, yet at times be misaligned with business objectives and/or existing operational issues, or ones that may be triggered by project decisions (e.g. reducing the testing time to achieve schedule milestones, which may increase the risk for defects and other post implementation issues). In this case the BA can serve as the “voice of reason”, resulting in better likelihood to address both project and business related risks and considerations.
Q4. What role does the BA play in managing quality? How is that best clarified in the requirements they produce (both written and verbally communicated)?
The BA should, along with the PM, own quality. The BA is the most applicable person to lead the effort to pursue quality and in turn ensure that the PM maintains a focus on quality. Quality is the key to achieve a combination of product quality, project success and customer satisfaction – and the BA has the most applicable knowledge of these areas.
The way to achieve quality is by integrating all relevant considerations into the project decision making process. Working with the PM, the BA should provide an impact assessment of actions and decision on the product and on any downstream areas – with a focus on business value and post project impact.
More specifically, the BA should lead the enhancement of the quality assurance role (e.g. audits, reviews, process analysis), lead the way in producing project health measure indications, and incorporate cost of quality analysis to ensure impact is expressed in terms and values that resonate with stakeholder needs.
The BA plays an important role in producing quality through the requirements. With over 40% of project defects traced back to the requirements, owning the quality starts with producing requirements that are SMART-CUT (Specific, Measurable, Attainable, Realistic and Time-bound; Clear/Complete, Unambiguous and Traceable). Applying the notion that “quality needs to be designed into the product and not inspected into it” makes it the BA’s role to take quality seriously from day one and ensure that no requirement makes it into the project if it’s not ready to go. Further, it is the BA’s responsibility to ensure that the requirements “hand-off” is done properly so that each requirement is appropriately represented in the project scope, as well as in subsequent planning.
Conceptually, the BA should deal with, if not own, all of the “invisible” aspects of quality, i.e. those parts of the quality iceberg that is under water. These “invisible” aspects are the hidden costs organizations incur as a result of poor quality; these costs are difficult to track and account for, as they are spread over time, beyond the project end date, and over multiple cost centres – depending on the areas impacted.
Q5. Could you tell us a bit about your book? Perhaps give us three things that our members might find most useful about it?
1. “Managing Stakeholder Expectations for Project Success”is a pioneer in providing an integrated approach to managing stakeholder expectations, by offering a broad context for the area of stakeholder engagement. The book reviews and considers everything that the PM needs to do in order to effectively manage stakeholder expectations; and ultimately deliver project success. With that, the book introduces a comprehensive Team Contract that allows the PM to “own” project communication and effectively addresses common issues that often plague projects’ and teams’ performance in a meaningful and constructive way.
2. The book focuses on what the PM needs to do and to focus on and how the PM should to utilize his/her time to maximize the value produced by working smarter, not harder. It clearly articulates common challenges and problems and provides simple and straight forward approaches to address them, establish environments that foster collaboration, overcome barriers and continuously keep an eye on project success criteria and their alignment to business objectives.
3. The book is intended not only for PMs, but also for BAs (to enhance the BA’s ability to add value to stakeholder expectations management) and for Project Sponsors (to clarify the mandate they need to provide PMs so the job gets done). In addition to being relevant for the three leading non-technical roles in a project, the book is also a first to introduce a detailed breakdown of what project integration entails, along with full consideration and impact of dependencies and project trade-offs. Additional concepts that contribute to the reader’s ability to apply critical thinking include time management, and a mechanism to determine urgency and prioritization.
My upcoming book (no title yet) deals with how to enhance and streamline the relationship, touchpoints and collaboration between the PM and the BA and is due to be published in the Fall of 2015.
Ori Schibi (MBA, PMP, PRINCE2 Practitioner), is a visionary leader, communicator, connector, and devoted husband and father. With 24 years’ experience, he offers practical and unique ways to effectively manage projects and people. Ori is the President of PM Konnectors (www.pmkonnectors.com, a Toronto, Canada based Consulting firm specializing in program/project management / recovery, PMOs, cost of quality measurements, process streamlining and improvement, PM/BA skills assessments and communication management. Ori is the author of the book “Managing Stakeholder Expectations for Project Success” (J. Ross, 2013; www.ManagingStakeholderExpectations.com).
Managing a Portfolio of Accidental PMs
How do you steer a portfolio managed by a "mostly accidental" group of Project Managers?
PPM Software is becoming more "accidental-friendly" and Brightwork is a great example of that. Recently we spoke with Eamonn McGuiness, CEO of Brightwork to get his perspective on how to best manage those who consider PM a role they play rather than a profession. Here are his responses to our questions...
Eamonn: Oh man, only three words… you’re breaking my heart! But if I have to give just three, they would be:
Projects, Success, Easy.
Hopefully you can see how those go together to create the BrightWork vision.
Dave: What type of business and/or end-user is Brightwork MOST useful for? (e.g. - Small Business vs. Large, PM Mature/Not PM Mature, Line of Business Projects/IT Projects, Professional PM/PM as a role, Industry, Large/Complex One-offs vs. highly repeatable small projects)
Eamonn: These classifications are very good, so let me talk a little bit about these in relation to BrightWork.
So to summarize the answer, the real strength of BrightWork is that we specialize in the mix of project management scenarios.
Dave: How would you compare Brightwork to Microsoft's Standard Sharepoint offering? How does it compare in terms of both collaboration and PPM/EPM functionality? In terms of price?
Eamonn: When you think of SharePoint you think collaboration. It does just what the name says – it is a place to bring your team together to work, share and collaborate. But for those organizations that want to go a step further using SharePoint to manage projects and across portfolios, they will note that there are boundaries to the out-of-the-box project management functionality.
Microsoft has built SharePoint as a platform that is designed to be extended. So where SharePoint is collaboration, BrightWork adds project and portfolio management functionality, such as:
SharePoint has a free version, called SharePoint Foundation and there is also a version that you can pay for called SharePoint Server. Now SharePoint itself does not include PPM, but that functionality can be obtained through licensing a third party tool such as BrightWork on premise, or in the cloud paying per user per month. BrightWork pricing can be found on our website.
Dave: Does the Brightwork Portfolio Management offering work best in a loosely structured or tightly structured environment?
Eamonn: BrightWork is uniquely qualified to fit a mixed structure environment, so let me explain that. We have developed a really simple framework for project and portfolio management on SharePoint that allows organizations to start in where they are ready, and then add more process as needed, or use some combination of the two.
Here is a really simple spectrum we like to share. Across the top of the diagram it goes from left to right, starting with a little bit of project management, to a lot on the right. Then down left hand side, you see we have four workloads such as managing projects, managing portfolios, managing demand and managing work. Then we said well, you could manage projects with a little bit of project management or a lot, so we built templates for each. You can manage portfolios with a little bit of project management or a lot, and we built templates for those too. So all combinations of work and process are built into the product as SharePoint templates.
It’s a very simple approach that we encourage our customers to use and adapt to their own situation. For example, they might have several routine projects in a Project Lite template, a few complex projects using the Structured template, and then you manage across all those projects with a semi-structured Project Office.
Dave: How do your best practices templates work? Are they based on proven methods and how does one decide if a particular template might work for them?
Eamonn: The idea behind the templates is that they allow you put in whatever project management practices you desire and give that to the project team as a starting point. You give the people a SharePoint site that is a set of rail tracks to guide project managers and teams. It is a very pragmatic approach to getting started.
The SharePoint templates are based on project management best practices, and are intended to give organizations a fast starting point to manage their project work. The templates enable teams to get started quickly with the amount of process that is necessary for the project at hand. The choice of which template to start with is governed by two main factors. One is the amount of project management that the project needs to be successful and secondly, the amount of project management that the team is capable of absorbing. The templates are also designed to help you to evolve your project management maturity to where you want it to be.
Dave: What percentage of your portal customers customize the application to integrate with their internal systems? What are the drivers behind that decision?
Eamonn: This would not be the primary concern for the majority of our customers. Most of them are more concerned with getting project management up and running really well, as opposed to integrating with financial, budgeting or other internal systems right off the bat. That type of integration would typically occur in a later iteration.
Dave: You talk about having a structured approach to implementation and rollout. In your mind, what are the three most important factors when rolling out any sort of Project or Portfolio Management toolset?
Eamonn: I think you might expect me to call out factors like: a commitment to project management, the aptitude of project management resources and the availability of training. And those are three factors that are very important to the process.
But at BrightWork we like to use a quote from the ancient Greek philosopher Aristotle, and that is: “That which we learn to do, we learn by doing.” So the best way to get good at project management, is to practice project management. With that in mind, here is our approach:
1. Start quick – with the amount of project management your team needs and is able for, and get some quick wins.
2. Stay relevant – decide the amount of project management you aspire to achieve, and then gradually build up to it bit by bit as needed.
3. Evolve at pace – make the deployment process a series of projects itself, in which you deliver an amount of project management quickly, get feedback from the team, and build that into the next iteration.
Risk Management: A Process or a Way of Life?
Situation: You organization needs to take risk management a lot more seriously.
We recently spoke with Loren Padelford, Executive Vice President & General Manager at Active Risk. The folks at Active Risk talk a lot about establishing an "Active Risk Culture" at your organization - really making risk management a way of life, rather than a set of sterile processes. As a concept that sounds interesting, but how does it really work? Loren offers some clarification in his responses below.
How much difference can having a "Risk-Aware Culture" have on a business? Can you compare it to simply having Risk Management processes in place or even just using general policies to manage risk?
The difference between risk awareness and simple risk management is immense. In a risk-aware culture, risk is part of everyone’s daily activity. Most firms would argue that they have a risk management “process” or “policy” in place, but a risk-aware culture means that risk is analyzed to a granular level - where it has the most impact. This means that every single person within an organization, from the CEO to the finance department to the newest project manager, not only understands their risks, but implements and uses risk management on a daily basis. If everyone understands that their role has a component of risk management involved and that risk management needs to be practiced every day, than the organization’s ability to understand its risk at a more in-depth, mature level, increases.
We’re seeing and research is showing that organizations with higher levels of risk maturity have improved in profitability, enterprise value, and opportunity generation.”
Q. Could you describe how a Risk Aware Culture is established? What are the top 3 (must do) components of the process?
Establishing a risk-aware culture can be a relatively simple process if the organization, on an individual level and as a whole, is committed. Having executive level support is number one. Having the CEO involved in the process and actively understanding his or her own role as a risk manager is a must. Without senior level support and daily involvement, risk is seen as optional and a risk-aware culture will not be achieved.
Secondly, an effective risk management process must be goal-focused. In order to draw employees into the process, each individual in an organization needs to establish tangible goals that they want to achieve through risk management. Risk needs to be a valuable process to the people who do it every day and setting goals will show them how effective risk management is in helping them achieve their goals more quickly.
Finally, organizations must be careful not to over-complicate its risk management. In order for risk to take hold in a culture and become engrained in everyday activity, it must consist of simple tools and remain focused on the risk that really matters to each individual’s goals and objectives.
Q. How "Risk Mature" does your organization have to be to establish this sort of culture? Are there pre-requisites to keep in mind?
Because risk is an ongoing process, there is absolutely no threshold for risk maturity. Organizations that want to become more risk mature simply need to focus on the three attributes mentioned above – executive support, setting goals and keeping the process simple. If an organization achieves these things, they will find themselves in a position where the company starts to pull in risk awareness naturally, instead of finding it pushed onto them.
Q. When is it inappropriate to establish this sort of culture? In which industries is it more difficult?
Because every industry encounters risk on a daily basis, it is never inappropriate to establish a risk culture.
Additionally, every industry has a certain requirement to take risks in order to create opportunity. Of course, all industries have their particular challenges and some are more complicated than others, but there is never a time and place when risk is an inappropriate process to engage as a core component of a company’s strategy.
Q. Given your company's deep experience in fostering effective Risk Aware cultures, could you tell us what this takes from a staffing and a tool perspective?
From a staffing perspective, the organization must have executive-level support. I cannot stress this point enough: the Chief Executive Officer must also serve as the Chief Risk Officer. They will be the educator of risk throughout the organization and translators of the goals and objectives of the business. They are not only imperative to the success of the process, but they are the cultural enablers bringing risk to an organization-wide level.
Without the right tools, it’s nearly impossible to execute risk management well. Organizations should look for tools, like Active Risk’s ARM solution, that provide a centralized hub for all risk information, so that the defined Chief Risk Officer is able to own the risk management process. This tool should integrate seamlessly into existing systems and processes, and have the ability to be personalized to each user’s needs.
The most successful organizations are the ones who have taken the approach of giving individuals high power and highly capable, yet simple to use tools to support risk management as a daily activity in business. These are the organizations that reap the rewards of a risk-aware culture.
About Loren Padelford
Loren is responsible for all customer-facing activities at Active Risk including sales, marketing, services, partners and customer success.
Loren has a broad track record of success in technology, advertising and business services. Prior to joining Active Risk, Loren was Vice President of Strategic Alliances and Global Sales Director for Dyadem International, a leading enterprise HSE software provider. Loren was a key member of the leadership team and instrumental in the growth of the business, which led to the acquisition of Dyadem by IHS (NYSE:IHS) in April of 2011. Prior to Dyadem, Loren was National Sales Manager at Recall Corp, Sr. Director of Sales & Account Management at advertising firm Uthink and started his career selling photocopiers with Ricoh Corp.
Loren holds an MBA in Marketing from the University of Liverpool Management School, a Bachelors of Psychology from the University of Guelph and is a Certified Sales Professional.
Another Supportive Community
Situation: You are a user of Daptiv's products and need a little help from time to time.
Q. Tell us a little bit about this new community you are starting. What are it's goals and what do you see as the immediate benefits to your user base? What will be the benefits for Power Users who are consistently active on the site?
The Daptiv community was conceptualized with the aim to foster product innovation and streamline the whole process of knowledge sharing through mutual collaboration. This new platform gives all its users an opportunity to collaborate directly with Daptiv peers and employees to receive timely responses to product related queries and leverage the community’s knowledge of best practices.
A highly user friendly and intuitive platform, it makes it easy for all the users to access the training courses and refer to knowledge based posts to advance expertise in Daptiv PPM whenever in need. The Greenhouse’ feature of the platform allows customers to share ideas and vote on new and innovative features for Daptiv’s product roadmap. It’s like an interactive knowledge house which is just a click away from its users. Active users and contributors will be abreast with the latest in technology, product and capabilities.
Q. How is this similar to or different from the MS Project 2010 Community or MPUG?
The Daptiv community includes a couple of unique capabilities. First, the platform is an evolved version of our Greenhouse community that was launched back in 2008 and enables customers to propose ideas and collaborate with our product team. Second, we include a library of Daptiv PPM applications and reports, which enable users to download best practice components and use them immediately in Daptiv PPM. This is addition to our blogs, videos, forums and knowledge base.
Q. Will Daptiv employee participants be pre-selected, or any anyone at the company participate?
Just like a community, this new platform is open to all of Daptiv’s users and customers. It’s an open development platform and a community of contributors. The community not only encourages exchange of knowledge, but also allows Daptiv to stay in closer contact with clients and partners.
Q. Do you see Daptiv partners playing a role in this?
Absolutely! Daptiv partners are an integral part of this community. Our partners tailor to an array of sectors and we value the know-how that they bring in. This is a collaborative community where ideas, experiences and best practices are exchanged for better results. We are eager to listen in and drive Daptiv’s innovation process by creating a closer, more intimate dialogue with our customers.
Q. How do you see members of the community working together?
We have designed the Daptiv Community to become the ultimate go-to resource to help customers with their PPM questions and deliver value for their businesses. We see this platform as a breeding ground for new ideas, seamless engagement and reliability.
Q. In terms of long-term vision, what do you see this evolving into over the next few years? Do you see the scope of this extending beyond Daptiv-specific best practices to more general PPM advice?
The basic premise of this community is to evolve constantly by adapting to the changing environment. Conversations are made in real world environment through open dialogue via discussion forums and an updated knowledge base.
Over the years, this community aims to serve as a one-stop entry point where both customers and employees pitch new ideas and initiate discussions with like-minded peers. Our vision is that this is the first place PPM practitioners from our user community come to ask questions, share best practices and connect with peers.
Recently, we spent some time with Jim Highsmith, an Executive Consultant at Thoughtworks and one of the fathers of Agile - and asked him a few questions about the state of Agile today. We also talked a bit about how he sees the movement evolving going forward. He gave us some very interesting tips and best practices that all of our members should be aware of. This is definitely a “must-read”. Jim will also be conducting a webinar on Aug 22, 2012, 8am PDT, Dispelling Myths About Scaling Agile Projects. If you are available, the webinar will be a great opportunity to interact wth JIm more directly and ask specific questions about your specific Agile challenges.
Q. Let’s start off with an update on you. We all know about your involvement with the Agile Manifesto a decade ago. Could you bring us up to speed on how you feel Agile has evolved and your current focus within the space?
There are three areas that I think have evolved over the last 10 years or are evolving now.
1. A move from Project Team to Organizations. The first is a change in who drives these efforts from project teams to organizations. During the first 4-5 years things were project team oriented. Someone within an organization, usually with permission, would conduct a Agile “rogue project” really on a team-by-team basis. In the last 4-5 five years you have, CIOs, CTOs, Directors of Product Development, VPs of Engineering – those kinds of people –saying “we want to transform major parts of our organization” and making [Agile] more of a combination of bottom up and top down. All of this with much larger organizations getting into Agile over the last five years.
2. A move from engineering and team practices to management practices. In parallel, we’re seeing a move from engineering, engineering practices and team practices to something that is more focused on management and management practices. This is something that is really just getting underway in the last few years, where management and executives have taken a look at this and said, “What do we need to do to make our organizations more Agile?” (as opposed to just making our software engineering practices more Agile) This sort of change from an engineering to a management focus is further demonstrated by the Project Management Institute getting into Agile and Agile certification; not everyone in the Agile community is happy with this, but at least it shows that there is a lot of interest within the project management community as well as within the technical community.
3. A move from Agile development to continuous innovation.The last thing that I would talk about is Agile Development moving from strictly development to continuous delivery and deployment. So your software, in addition to being developed on a short cycle, is being released on a very short cycle in those situations where it makes the most sense. So you have a situation where you are automating that last mile. On the front end of that, the exploratory or discovery phase, the lean startup movement has provided some practices and philosophy around getting starting faster with product inception and product requirements. Agile development to continuous innovation.
I’ve been focused on the management side of these changes, which I call adaptive leadership:
Q. Could you expand a bit on what it means to be Agile?
In fact, I just wrote a blog posting yesterday entitled “What is Agility?”. To me there are two aspects of Agility:
1. The ability to create or respond to change in order to profit in a turbulent business environment. So it’s not just responding to change, but the ability to create change in innovative ways to challenge competitors.
2. The ability to balance flexibility and stability. A lot of people think that agility promotes sort of a lack of structure. But really, if you don't have any structure at all you just kind of go off into chaos. So you really do need structure. The really critical management capability here is to decide how much structure you need and balancing that with the flexibility that you need to respond to the marketplace. Traditional approaches have come down on the side of more structure, more process and more standards, and have really restricted our ability to innovate because we don't have that flexibility, adaptability and learning ability that we need to be competitive.
Q. When trying to understand the limits of Agile practices, most people focus on project size. Yet you talk more about complexity and uncertainty, which are related but not as easy to get your head around. Generally speaking, what is the best way for practitioners to think about these two attributes of programs and projects and how each of them should affect their approach? Any thoughts on this specific to planning?
I think that there’s sort of a myth in the community around project size. Part of this comes from the early Agile work that focused more on small teams and small projects. So the idea was that Agile worked well on small projects, but didn’t scale well to larger projects – but there are plenty of examples now of Agile working well in very large projects and large organizations.
You should really think about this is terms of a few key questions that Agile helps answer:
So there are a lot of reasons that we want to be able to apply Agile as we scale. So we want to scale Agile, but what are some of the things that we need to do to make that happen? That’s where complexity and uncertainty come into play. Complexity and uncertainty are two dimensions that we need to think about. The complexity dimension is the one that we are most familiar with; team size, distribution, domain knowledge, computational complexity all play into overall complexity. Common uncertainty factors can include the newness of the technology you are using, business and marketing uncertainty, new/emerging product requirements. You can have any combination of high and low complexity and uncertainty on any given project, but the general strategy for scaling projects are as follows:
Obviously, the more difficult projects are the ones that have high complexity and high uncertainty. With those kinds of projects you usually have a smaller subset with high uncertainty that you can deal with separately. I think the real message here is that you have to adapt and use some more traditional strategies and some Agile strategies as appropriate. Often you end up using an Agile strategy overall and incorporate traditional elements into it as needed.
Q. A key challenge for organizations that we often hear about is marrying Agile projects with more traditional Project Portfolio Management efforts. The clear goal is to gain the benefits of Agile approaches while attempting to maximize and manage return on investment. Do you have any thoughts, guidance or best practices that you could share in this area?
I think in terms of exploration (certainty) factors with my projects along two dimensions: technology and requirements. If the technology is very familiar to me, the technology exploration factor is low. If the technology is new, the exploration factor is high. The same is true for the project’s requirements. If I have an exploration factor 10 project, things are pretty uncertain. If I’m dealing with a factor of 1, things are pretty certain. Most PPM approaches standardize/homogenize projects, making them seem equally predictable – which doesn't make any sense. For example, to expect predictability within +/-10% of time or cost on a exploration factor 10 project just isn’t reasonable.
So we need to change governance structures and govern different types of projects based on different criteria. With projects that have a low exploration factor, we can use more traditional portfolio measures like scope, schedule and cost. With higher exploration factor projects, we have to ask:
Then the other things like cost and scope become constraints – not drivers. So you have to either run two different types of portfolio management systems or one governance process that combines both traditional systems and Agile. One of the things that I’ve seen lately is continuous monitoring and management of the portfolio, using sort of a Kanban approach. It’s very similar to a traditional approach in some ways, but all of the actions are continuous.
Q. Uncertainty is something that every company is dealing with today. It’s a key concern for every executive. Moving Agile up the food chain, are there steps that can be taken to make a traditional PPM process more adaptive and perhaps more effective that are usually well received by the executive team? Are there ways of coaching executives to make them more Agile-friendly and ultimately more effective in a world that is filled with uncertainty?
The transition is more a management transition than it is a project or portfolio management transition. There is more of a realization now that managers themselves need to learn to be more adaptive. In the past, we’ve seen the attitude that the development teams need to be more Agile and adaptive, but managers thought, “It doesn't really impact me.” I think people are struggling with changes in the marketplace. For example, Amazon fought for years against applying state taxes to Internet sales. Now they’ve changed strategies entirely because they are moving toward same-day delivery. That’s an industry-wide disruption and an example of management thinking in a more Agile way. So that’s how the mindset changes.
The “doing” side of it really involves creating a continuous stream of value:
The “being” side of that (management behaviors) has to do with creating an innovative culture:
With a plan-do mindset, I plan out everything that I want to do – then I do it. With an envision-explore mindset, I envision where I want to go and how I might get there. With envision-explore, I'm creating an innovative culture. With plan-do, you’re really not.
So in terms of dealing with uncertainty, the things that I just talked about help you deliver a continuous stream of value, while creating an innovative culture.
Q. Following the theme of uncertainty, what are your thoughts on planning in an uncertain environment?
I think planning is definitely something you do, but really you’re “speculating”. In my book, I actually replace the word “planning” with “speculating”, because that’s what you’re really doing in a highly uncertain environment.
When a lot of people think about planning, they think about a Microsoft Project plan with 6,000 tasks and someone is going through and checking them off as they are completed. I think that kind of plan isn’t really appropriate in a rapidly changing environment.
What is appropriate is a higher level of planning where you are dealing with shorter periods of time and you’re dealing with larger chunks of work. Again, you would plan an exploration factor 10 project differently than you would plan an exploration factor 5 project. If it’s a 10, you might just run an iteration at a time with a broad goal in mind and a few constraints – then run a series of experimentations on it until you figure out what it's all about. With a 5, you might be able to lay out a reasonably detailed plan for three or six months.
Another key difference between traditional an Agile planning is what you are actually tracking. Traditional planning tends to be task or activity based. In Agile planning, you are doing a product breakdown. So you’re tracking pieces of the product that have value to the customer versus activities where their value is less clear.
Q. Organizational effectiveness has also been a popular theme in recent years. At various levels you see Agile, Lean and even Six Sigma playing roles in helping organizations produce more with less. Do you see these disciplines becoming more integrated or even somewhat merging at some point in the future? How do you see them complementing or detracting from one another?
The ones that I see complementing each other are more the Agile and Lean – particularly the Lean startup movement. The idea of doing less and focusing on high-value stuff is really a complement to Agile.
I haven’t had as much experience with Six Sigma, but it’s more about operational efficiency. There may be places where you want to be more operationally efficient. Then it’s a matter of creating a balance.
Organizations have to think about:
Q. Organizational effectiveness often means standardization. Many large organizations struggle to "standardize" their teams. What are your thoughts on this type of standardization?
I think it depends on whether your focal point is responsiveness or efficiency. If your focus is on becoming more efficient, then standardization probably helps with that. Unfortunately, that drive toward standardization often operates against the ability to be more adaptable, flexible or responsive. The more standard you get, the less flexibility you have. In many large organizations, this drive to be standard encompasses too many things. There may be some areas where standardization is appropriate, but “teams” is not one of them. You need diversity and a set of guidelines, but not much in terms of standardization.
Q. Customer value is obviously critical, but maximizing it sometimes feels in conflict with getting things done. If you had one piece of advice for those trying to maximize value in a tough environment, what would that be?
I would go back to two of the four things that I think adaptive leaders need to do:
One of the things traditional approaches assume is that you’re successful if you’ve delivered all of the scope in whatever you’ve defined. There have been studies that say that 60% of all software developed is rarely or never used. So the measure really needs to be, “Have I delivered value to the customer today?” not “Have I delivered everything in scope?” Then you might ask the question, “What offers value now?” Then you can grow that value over time.
So the Lean idea of doing more with less, combined with an Agile approach, really produces more meaningful results.