PMI Global is looking for participants to pilot test our upcoming eLearning offering – the Citizen Developer Practitioner Course and Micro-credential. This will include 4-5 hours to complete the course and a 60-minute exam. The pilot test will begin on 22 March, and you will have three weeks to complete the course and exam. After completion, you will be required to provide feedback on your experience.

In this course, you will learn how to:
• Determine if your problem can be solved with a Citizen Development process
• Effectively brainstorm solutions
• Evaluate the challenges that your app must overcome
• Gather the data and resources you will need
• Bring your project to fruition

Participants will receive the product for a greatly discounted price of $99 (Actual price : $249) and earn both a digital micro-credential badge and a minimum of 6 PDUs.
PMI Global will be in touch on 18 March to inform those who have been selected. As there are limited spots available, not all who apply will be able to participate. Those not selected will be provided with a discount code to take the course once it has been launched.

PARTICIPATE IN THE PILOT

Offer valid for a limited time. Cannot be combined with any other offer. Discount is applied to the full price. Other conditions may apply. For details on terms and conditions, visit PMI.org/terms.

Agile is getting a lot of great press lately as we see companies like Amazon thriving by leveraging the concepts. But we also see push back from other business leaders on why Agile won’t work for them, or companies that have tried going Agile but are not seeing the expected improvements. Instead of realizing Agile as an all or nothing idea, we should analyze each of the Agile principles, taking a pragmatic approach to leveraging Agile within our own organizations.

This focused segmentation on each Agile principle is key since no individual practice will provide a competitive advantage. If something is easy to replicate, everyone will do it. Also, what organizations do is not simple – each one is completing a complex combination of different tasks to create customer value.

That leads me to this – The secret sauce of Agile is: It’s a framework built on strong principles you adjust to fit your organization. The goal is to make the right adjustments while not losing the underlying strengths that Agile brings.

To do that successfully, you need to understand each of the principles in depth. The four key Agile principles we have identified are:

BREAKING PROJECTS INTO SMALLER BITES

CONNECTING WITH CUSTOMERS

LEVERAGING THE POWER OF TEAMS

BUILDING IN CONTINUAL LEARNING

Join me over the next few posts, as we delve into each one of the principles throughout this Agile blog series. Today, we start with: Breaking Projects into Small Bites.

Smaller Bites

The first principle is breaking projects and initiatives into smaller bites, following the old adage that the way to eat an elephant is one bite at a time. As we think about how to break up projects, we need to also answer:

If you think about construction, where traditional project management comes from, these questions are fairly easy to answer. If you are looking at building a new bridge, for example, to see if there is value, it’s easy to see what those who would use the bridge are doing today, and if they are willing to pay for a replacement. This answers the first two questions, so then the real focus is on how we do it. Since this isn’t the first bridge that’s been built, we can get a reasonable idea and estimates from previous projects to help us answer the last question. If we found ourselves without previous information, we would need to experiment. That’s much harder on these types of projects since there may not be an easy way to break the project up into smaller bites. We could start with a rope bridge, but chances are it’s not going to add any value till we have a four-lane highway ready to use, thus failing the first question.

Construction projects are not the only ones that may provide this complication. IT infrastructure or software upgrade projects are often similar and are quite a bit different from software projects – which is where Agile came from. Software projects are far more unique and have their own conditions to be considered. You see similar issues in marketing, educational design, business process changes, or any project where we don’t have a good, previous solution to copy.

The problem with these types of projects is:

Even with this complexity, there is some good news. Unlike construction projects, these projects are easier to break up into experiments where we can test our assumptions and reduce the risk to the organization. The key is to focus on breaking the project up into the right pieces, that will help answer these questions as quickly as possible.

How to Break Projects Into Small Pieces

Let’s talk about how to break that elephant up with a real-life example. A company I worked with had a hypothesis that they were paying generous benefits but employees weren’t seeing that value since they didn’t know what those benefits cost. For the three questions, the hypothesis was:

How will this project deliver value to the customer?

If employees knew the cost of their benefits, they would be more satisfied

How will it deliver value to the organization?

Satisfied employees would provide more value to the organization (in this case reduced turnover)

How do we do it, including how long will it take, or how much will it cost?

We have access to the benefit information and can present it in the right format to make it easy for employees to understand.

Looking at how to break this project up, we would want to:

Present employees an example of a current benefit to see if this increases satisfaction. If possible, we probably want to start with the biggest benefit.

We don’t have time to wait for turnover, but we still need to measure satisfaction, perhaps with a questionnaire, targeting a group of employees that have the most turnover.

We need to test if we can get access to the data and test different ways to show the information to make sure it is easy to understand

As you lay out what you want to learn, it gets easier to understand how to break the project into the right pieces.

Value of Breaking Projects into Smaller Pieces

So whether you’re agile or not, let’s talk about the benefits of this approach:

As an organization – testing the value of ideas early lets you focus on the good ones. It also helps to uncover big technical risks quickly so you get a picture of the real effort projects will take. Finally, delivering the projects quickly, and in small increments lets you deliver value faster, speeding return on investment.

As a customer – teams are already testing on real customers today; all of them when they release. Smaller testing means you get to see what approach a team is considering early, provide meaningful input on finding the best approach, and only a small group of customers is impacted.

As a team – testing early means you waste less time on bad ideas. It’s demoralizing to put your heart into a project and then not find out till the end it didn’t deliver the value you expected.

By taking this approach, Agile is pushing an empirical tactic, pressing you to think like a scientist, understand what ideas are really theories, and find ways to test the theories early.

As you look at getting this same value with your own projects, think about the three questions around organizational value, customer value, and the approach. If you have good evidence to support your ideas, it may be more similar to the construction

project example, and focusing on how to efficiently put the project in place could be the best approach. But, if there are a lot of assumptions like we described above, it’s worth the time to set up a quick experiment and validate them.

On our next post, I’ll be reviewing the second principle, Connecting with Customers.

The Power of Teams

As kids, I think everyone of us wanted to be superheroes. Teams give us that ability – they turn ordinary people into top performers. In his book Scrum Twice the Work in Half the Time – Sutherland explains the difference between your best and worst individual performers is 10 times. That means the best performers get 10 times more done than the worst. That sounds impressive, until you hear the difference between the worst and best teams is 2,000 times (2,000 times better starts to sound and feel a lot like a superhero).

Part of the difference might be in existing team structure. Most of the time, we think about teams as individuals working on similar items with a manager directing traffic. That’s not a team. And, it won’t provide the advantage of leveraging the intelligence of the group. In his book Turn the Ship Around, Marquette talks about how, traditionally in a submarine, you have one captain thinking for the 140 crew. Marquette discusses how he got each individual to think for themselves. By doing that, he outperformed every other submarine in the US fleet. It was easy for him to see that no other captain, however smart they may be, is going to be as smart as 140 people.

For those who have worked in a solid team, it’s a great experience.  However, teams need the right elements to be successful. An example I like to share is a research project called Aristotle looking at successful teams that Google conducted. They started with an assumption that great teams would be made of great individuals, but couldn’t find any correlation. What they did find were five key elements that did correlate with team performance:

Psychological Safety

Can we take risks without feeling insecure or embarrassed?

Dependability

Can we count on each other to do high quality work and meet commitments?

Structure and Clarity

Are the goals, roles, and plans on the team clear?

Work Meaning

Does our work provide us with an individual sense of purpose?

Work Impact

Do we believe the work we’re doing matters?

If you’re looking for structure, Scrum, the most popular Agile framework, provides teams a simple approach on how to plan, touch base regularly, review work against plans, and implement regular retrospectives to identify and make needed adjustments.

Benefits of Teams

There are so many benefits to high functioning teams, but one of the most valuable is innovation. New ideas often come from leveraging existing ideas in a new way. When you present a problem to a group, each person comes with a different perspective, a lifetime of different experiences, and the more diverse your team is, the more diverse those experiences will be. Great ideas come from one person seeing the problem in a different way, and then others in the group building on those ideas till at the end you have a completely new solution.  This means:

As an organization – innovation is the lifeblood of any good company. It is the ultimate source of competitive advantage. It is why companies like Google and Amazon are so hard to compete with.

As a customer – it gives you the best product at the best price. Customers are so tired of hearing the word “or.” Would you like quality or would you like a price you can afford?  Innovation gives you the ability to give customers “and.” Toyota did this in the 50’s, providing the quality of a Mercedes for the cost of a Ford, gaining a decade of competitive advantage.

As a team – we talked about a key part of successful teams is meaning and impact. There is a joy of going home (or logging off our computer in our home office) at the end of the day knowing that, as a team, you did the impossible and the world is better because of it. Innovation makes the impossible possible, and it’s fun getting to do it.

You don’t have to be Agile to improve what your teams are doing today.  Look at the Google Aristotle aspects of a team and think about how you make groups more like teams.  Wherever you are today, leveraging the genius of the entire organization will help you be far more effective, with a side effect of much happier employees.

In the last part of our Agile Series, we’ll take a look at Continual Learning.

Connecting with Customers

I had this epiphany when I came to Agile. As a solution architect I had been spending a lot of time getting sign-offs from customers to make sure we had the right solution before we started the project.

The problem is solutions are like art. Often customers don’t know what they want till they see it. Further, they may not even know what the underlying problem is. What they do know, is what is they don’t like what they have today.

While customers are not experts at understanding how to take a problem apart and find an answer, your solution team is, but, your solution team may not know what is most important to the customer. Worse, they often think they know and move forward to test that theory by delivering a finished product – that’s an expensive experiment!

The epiphany I had was: Take the customers who understand where their pain points are and know a good solution when they see it; put them together with teams who are experts at root cause analysis and developing innovative ideas and you create the perfect environment for innovative solutions that meet customer needs.

How to Connect with Customers

Whether you are developing software solutions, creating marketing campaigns, developing education curriculums, or changing a business process, chances are you are trying to think of the right solution for your customers. However, if you have ever delivered a finished project and the customer says “Oh, now I know what I want,” – this is the strong an indication that there’s an opportunity to improve.

Here are some steps to make this actionable:

Continual Learning

It’s cliché that the world is moving quickly. A key element of this change is companies, many whom are your competitors, continually looking for better ways to serve customers. Just ask Sears, Kmart, or Toys R Us and they’ll tell you – If you’re not finding a better way, someone will.

The problem is our current structures are not built for learning – they are built for control. Hierarchies are built to increase efficiency and stability in the organization, not leverage great ideas. We need to change this. We need to build companies of entrepreneurs, where experimentation and innovation are an integral part of what we do. We want good ideas to get the same attention, no matter where they originate.

How to do we foster continual learning into our organizations

Before you even start, one of the first things to consider is understanding what is the clear goal of what you want when you are finished. Do you want more efficiency, do you want more customer value, do you want more sales, do you want more revenue, more profits? As we discussed in Part 3 – Teams are amazing idea engines – set them loose on a problem and they will come up with incredible results, but you have to start with pointing them towards the right problem. As a leadership team – it’s your responsibility to understand where you want innovation in your organization and what is going to make a difference, so your teams can focus on how to get you there.

The next thing you need is the right environment. Looking back again at Part 3 the Power of Teams, we mentioned psychological safety is important. But, that isn’t just safety within the team. Ironically, for the team to succeed they also need to be able to fail. With innovation, people need to feel safe in the organization as a whole, knowing that ideas may not work every time, but when they do, it will be worth it.

You also need an idea meritocracy. Often when you start a new team, members come in wanting to know what their tasks are and when they are due. They know they are usually asked to leave their brain at the door and just do the tasks as asked. What a waste of good people! Teams need to know that great ideas can come from anywhere or anyone. It shouldn’t matter if you are in accounting, you might have a great idea for operations. Operations might have a great idea for sales. You may see great ideas come from facilities, customer service, or accounting. We need to be able to judge ideas on merit, not rank or role.

This next part is a little more controversial since it has to do with money. To entice entrepreneurs, you need to be able to share rewards for great ideas. To find the best way to serve customers, you need to measure the value the team is delivering to them. Taking that one step further – as teams deliver great value, there should be some direct rewards, sharing the value of those ideas that made it possible.

It’s rewarding to see the value customers are getting but if organizations don’t share a portion of the benefits, team members may end up feeling cynical that they’re doing a great job, but the owners are the only ones seeing rewards. Nucor Steal pays employees 75% of market wages, but with bonuses they can make 125%.  At Google, employees can make as much as 300% more than someone in the same role, based on the value of their contributions.  Haier, a Chinese appliance company, has broken departments into small mini companies where employees are encouraged to think of new revenue streams and there can be significant rewards when those ideas payoff.

Beyond the right environment, the last element is room to process and digest thoughts. Agile is the only methodology I’ve seen that does continual improvement effectively. The reason is that there is time built into every iteration to take a step back, discuss where to improve, and build those tasks into the next iteration.  We all know that improvement is important, but we’re not scheduling time to do it.

In one of the departments I managed, I thought I was doing a great job delegating and communicating with my team till we had our first retro. I was surprised to learn that wasn’t the case. Over the course of a year, we were able to eliminate, automate, and delegate my administrative overhead from 20 hours a week to 4. It left me a lot more time to focus on strategic value and the team was much happier with the growth they were seeing. You have opportunities, but you won’t know where those opportunities to grow are, or what is possible, until you take time to ask.

Benefits of Continual Learning

People talk about an Agile transformation like it is a destination that you get to.  However, Agile is a journey. It’s about building an organization that is continually changing and adapting to better fit the world around it. Continual learning is really one of the key principles to Agile because it builds a truly flexible organization.  That means:

As an organization – you don’t have to worry about driving results. A key job today for leadership is to drive the organization to be more effective. Agile puts in a structure where everyone is focused on being more effective. That means leadership has more time to focus on strategic direction.

As a customer – the company is always growing and adjusting to better fit your needs. Every iteration, they are asking how they can serve you better.

As a team – you get growth. Too many times we think people aren’t satisfied because of money or benefits. But a key reason employees leave a job is because they don’t have an opportunity to grow. Continual learning gives you the opportunity to not just do more, but to be more, increasing the value you add. If you’re with a good company, it also means you get to take the results of some of those ideas home as a well-deserved thank you.

The idea of continual improvement isn’t new. Toyota started quality circles after WWII leading to its popularity in the 1950’s. But, 70 years later, it seems we’re still not doing it well. Most teams meet regularly to discuss status. It’s not hard to add some reflection time to those meetings. You can google fun retrospectives to get some ideas of how to get people thinking more creatively. Whether you borrow the approach from Lean or Agile, building continual improvement will help your company grow.

As we have gone through the four key Agile principles, you’re probably thinking they aren’t new. You’re right, they’re not. Agile is really just a collection of good business practices, and rather than a detailed practice, it’s a combination of good principles that companies should leverage to improve what they do.

As you look at Agile, rather than thinking that’s not for me, or that would never work here, do what Agile did —  Take a bunch of great ideas and make them your own.

How did his journey start? His first “official” Project Manager job began when he joined DHL in November, 2004, but his project management journey actually began many years before. In fact, as a child, " I exhibited the innate traits of successful project managers when in the school recess yard my friends wanted to play football, but I brought a pencil and paper out of the classroom to create plays. Most of the kids didn’t want to plan and simply wanted to play (Sound familiar?). I didn’t realize it at the time, but it was the beginning of honing my skills as a servant leader."

After graduating high school, Keith went to a trade school to study electronics technology, because he had a fascination with figuring out how things work and a knack for troubleshooting problems. He worked his way up through Motorola as a Network Analyst and then joined American Power Conversion (APC) to become a Data Center Operations Manager. Throughout this part of his career, Keith was leading teams by creating plans to implement new networks, build out new data centers and manage daily operations on a 24x7x365 schedule. In essence, "I was performing daily operational tasks while creating and managing informal projects before I even knew of the “Project Manager” profession."

After obtaining his Executive Masters of Business Administration (EMBA) degree, Keith decided to move his family from Rhode Island to Arizona to start a new phase of his career outside of the data center. His peers at Motorola helped him relocate. In 2004, Keith learned about the Project Management Institute’s Project Management Professional (PMP) credentials and realized his IT background and the PMP would allow him to change careers while still being connected to technology, which he loves.

Over the past 17 years, Keith Harrington has intentionally selected and joined various companies to gain experience in transportation and logistics, digital education, financial services, healthcare, hospitality and have for the past 5 years been with a terrific network marketing company, Plexus Worldwide. Throughout the course of this journey, he have honed skills as a Project Manager, Program Manager, Portfolio Manager, ScrumMaster and Executive having successfully developed and currently leads an outstanding team of professionals in an Enterprise Project Management Office (EPMO).

I asked Keith Harrington, what he is pastionate about, and he replied, "mentoring my team members to ensure they have the skills and experience to have a successful career in project, program and portfolio management. I had a very good mentor at Motorola that set me on a successful career path and I want to do the same for everyone I can help." After some reflection he felt his colleagues would describe him as analytical, disciplined, honest, and confident which some could describe as arrogance. His introspective traits struck me as a person who respects other's time which has helped his track record of getting projects done.

He believes in the social good, in November, 2020, he became a proud member of the Cancer Support Community of Arizona’s Board of Directors, which is near and dear to his heart since members of his family are cancer survivors. He has also been a blood donor for the past 37 years and a contributor to the Rhode Island Food Bank and St. Mary’s Food Bank for more than 30 years.

Keith Harrington is a gifted storyteller. When I asked him what was on his bucket list besides adding books to an ecletic library he broke it into two parts. "On a social and spiritual level, I want to make sure my family and people that know me consider me a genuine friend that gave back more than I received. On a physical level, I want to build my dream house to spend my retirement years creating, fabricating and giving back to my community."

If you get a chance to speak with Keith Harrington at a breakfast meeting, you will find him engaging. You might even leave with a bit of wisdom.