Previous month:
November 2017
Next month:
January 2018

Government Lessons in People Over Process

CubicleMy first opportunity to create and run a large agile team did not start well. Having had good successes with small to medium sized agile teams I was keen to unleash the benefits on a bigger scale. I was working for IBM at the time and was able to persuade my account manager to pitch the approach on one of our government projects. A clean-sheet development opportunity with a smart team and engaged business group – what could go wrong? As it turns out, plenty due to my ill-advised approach.

It was the early 90’s and we were trialling techniques that would later become the agile approach DSDM (Dynamic Systems Development Method). Taking ideas like James Martin’s RAD (Rapid Application Development) and active user involvement from Enid Mumford’s Participative Design Approach, we had already dramatically reduced development time and improved acceptance rates on several projects. I was convinced collocated teams with short iterations of build/feedback cycles were the future. We were all set for a big client success and who better than the British Government for good publicity! My enthusiasm was about to be tested.

I was given a full rein of the project, or as I would later realize, just enough rope to hang myself with. Having struggled to get dedicated business input on previous projects I commandeered a large boardroom to collocate the development team and business subject matter experts (SMEs). It was awesome, everyone was together in one room and we had direct access to the business representatives for requirements elicitation, clarification, and demo feedback. We were working hard and getting lots of features built but the business representatives hated it.

At first, I thought they hated me. I think that is a common mistake, we internalize changes in behaviour as attacks or criticisms of ourselves. What have I done? What did I say to upset them? - all of them! I recall wanting to write on my internal project status report to the IBM PMO that “the business is revolting”. However, that is what occurred, starting as cordial and helpful, the business SMEs became less helpful, then uncooperative, and finally hostile. I had a revolt on my hands that I did not understand.

This was my first introduction to organizational change. Luckily for me, I had access to many people in IBM smarter and more experienced than I was. I was given a book called “How to Manage Change Effectively: Approaches, Methods, and Case Examples” by Donald Kirkpatrick that changed my career. In it Kirkpatrick outlines circumstances where people will resist change. These include:

  1. When people sense loss in: security, pride and satisfaction, freedom, responsibility, authority, good working conditions, and/or status
  2. It creates more problems than it is worth
  3. Extra efforts are not being rewarded
  4. Lack of respect for those initiating the change
  5. The change initiative and its implications are misunderstood
  6. Belief that the change does not make sense for the organization
  7. Change is misdirected, current state or alternatives are better
  8. A low tolerance for change in our lives
  9. When change violates a principle or commitment that the organization must stand by
  10. Exclusion from the change initiative
  11. Changes viewed as criticism of how things were done in the past
  12. The change effort occurs at a bad time, other issues or problems are also being handled

Something I was not aware of at the time is how the career development process works within the government. The most junior new hires work in open-plan cubical offices. Then as you get a promotion you get moved to bigger cubicles with higher walls that are more like mini-offices. Next, you get promoted to a real office, then an office with a window, and eventually a corner office. In short, your workspace defines your status, responsibility and authority.

By bringing these business representatives into a shared boardroom to work on the project I had unwittingly generated change resistance scenarios 1-3 and probably triggered many others also. Making them sit and work together like the most junior recruits had caused a loss of good working conditions, status, freedom, pride, satisfaction, and perceived authority. A bad idea when hoping to develop a productive working relationship with someone.

Luckily for me the Kirkpatrick book also lists circumstances when people do accept change, which unsurprisingly are the opposite conditions and include:

  1. When change is seen as a personal gain: in security, money, authority, status or prestige, responsibility, working conditions, or achievement
  2. Provides a new challenge and reduces boredom
  3. Opportunities to influence the change initiative
  4. Timing: the time is right for organizational change
  5. Source of the change initiative is liked and respected
  6. The approach of the change and how it is implemented appeals to us

So, equipped with these ideas we changed our approach. Instead of the business SMEs being collocated with us they returned to their fancy corner offices, long lunch breaks, and afternoons spent reading the newspaper - none of which they could do when they all sat together. Instead, we reserved their mornings for questions, review sessions, and demonstrations. This was better received because their morning calendars were blocked with important project meetings, but we rarely called on all of them at once unless it was for a business demo.

Now they had their offices back, a little more free time, and were engaged in a more respectful way. The team were sceptical at first. However, it really is much better to have one hour of someone who is cheerful, engaged, and helpful than eight hours of someone who is bitter, obstinate and causing issues. The project went much smoother after these changes and it taught me an important lesson in never trying to introduce a process or practice without considering the people elements first.

We completed the project early, largely due to the input and hard work during acceptance testing of the business SMEs, and IBM got their successful case study. I learned to temper my enthusiasm and consider other stakeholders who will undoubtedly have a different view of the project than myself. Individuals and interaction are indeed more important than processes and tools, even if they are your own pet agile processes and tools.

[I first wrote this article for the Government themed November issue of, available to subscribers Here]

PMI-ACP Training Partner Program

RMC TPP ImageWhen I travel I often meet people who say they used my books or other training materials to help them pass their PMI-ACP exam. Plus, I’m also asked by others how to get permission to use my book as the basis for their own PMI-ACP training courses.

So, I am excited to announce the new PMI-ACP Training Partner Program from RMC Learning Solutions. For an introductory low price of $500 per year you receive:

  1. Use of a slide deck (290 slides) from our PMI-ACP® Exam Prep, Second Edition book

Note: These slides are an outline of our book. Our Training Partners use them as supplemental, reference slides as they develop their own course.  You can use some, or all, of these slides in your course.

  1. One Instructor License for the PM FASTrack® PMI-ACP® Exam Simulation Software – v2 (Downloadable exam simulator. This is a $199 value)

Note:  This exclusive Instructor License allows you to use pre-configured exams to focus on/test a specific knowledge area.  The Instructor License is not available outside of RMC and our Training Partners.

  1. Discounts of 35-55% off the List Price of selected RMC LS products you order at one time

Note: This enables you to include our training materials in the price of your course. It also includes discounts on my brand-new PMI-ACP Exam Workbook.

Maybe you already use one of my books for teaching PMI-ACP courses, or maybe you are looking for slides on which to base a course? Either way, getting professional materials aligned to the PMI-ACP exam content outline is much easier than building them all yourself. Also, you can rest assured that the permissions are all in order and everything will be updated as the exam changes.

If you would like to learn more about this program and take advantage of savings of 35-55%, please contact Marcie McCarthy at

Got Your CSM, Now What?

Credential QuestionPerhaps, like 500,000+ other people, you have some form of Certified Scrum Master (CSM) credential and are looking to distinguish yourself and continue your learning journey. Of course, learning is not tied to credentials, many people are anti-certification and that is an understandable choice. I encourage lifelong learning separate from credentials. However, for credential seekers, this article explores some common credential pathways beyond the CSM.

I want to disclose upfront that I have been involved with the development of ICAgile, PMI-ACP, and DSDM Leadership credentials so I likely have some bias and preferences. However, my goal here is not to recommend specific credentials but instead to explain options and environmental factors to consider, helping people make their own choice based on their own situation.

Also, because there are so many credentials available I will undoubtedly miss out many credentials in this discussion, maybe including your favorite or your company’s. This is not meant to be an exhaustive catalogue of agile credentials rather a thinking or discussion tool for getting the research process started. 

How Did You Get Here?

When people ask me what credentials to get next, I ask how they got where they are now. Did they move from software development into a Scrum Master role? Were they previously a PMP certified project manager who took a CSM class to learn a little about Scrum? The answers to questions like these and the next one: “Where Do You Want to Go?” help ground and orient the decision-making process. If we don’t know where we are to begin with, then a map is unlikely to be helpful.

Where Do You Want to Go?

Credentials may be obtained to help secure a new job or promotion. People also seek them to demonstrate understanding of certain topics, and just for personal achievement. All of these motives are valid and help drive the choice of where to go next. If you are pursuing job opportunities then you should research what hiring managers are looking for. Are they asking for PMP, CSP or PMI-ACP credentials? If so then we are narrowing our choices down.

Alternatively, if you are pursuing a credential more for personal learning, then the curriculum is likely more important than recognition by hiring managers. Maybe there is an online program that very few people have ever heard of but it’s a great fit for your learning objectives. If so, be more influenced by content and quality rather than recognition and opportunity.

This sounds basic, but I’m surprised by how many people pursue credentials just because their colleagues did and they don’t want to be left behind, or it was the next course suggested in their company’s training roadmap. Credentials should be for you. Asking questions like: Do you want to strengthen your current role? Do you want to change roles? Do you want to stay at your current organization? All these issues factor into the next steps to take.

Directions from Here

There are a few obvious directions from CSM that include Down Deeper, Upwards and Outwards. By Down Deeper I mean going deeper into Scrum with an Advanced Certified Scrum Master (A-CSM), Certified Scrum Practitioner (CSP), or Professional Scrum Master (PSM) credential. These are good options if you want to demonstrate a further commitment and understanding focussed just on Scrum.

Upwards refers to scaling Scrum for large projects, programs, and enterprise transformations. There are several popular Scaling frameworks available including SAFe, Nexus and LeSS. All offer training paths and credentials if that is the direction you want to pursue.

The Outwards direction means broader than just Scrum. Due to the popularity of Scrum people sometimes forget there is a rich wealth of complementary approaches outside of it. Lean, Kanban, Leadership, and Emotional Intelligence are all topics that agile teams can benefit from. Certifications like the PMI-ACP and the ICAgile suite of credentials provide coverage and demonstrate knowledge of these topics. Also, I class Disciplined Agile Delivery (DAD) here rather than a scaling framework since it is more pragmatic and deals with more than just agile and scaling.

How to Decide: Personal and Environmental Factors?

So, knowing how we got here and a little more about where to go next and why, we can start to create some pathways.  Shown below is a sample flowchart for someone interested in pursuing agile approaches further and wondering what to consider next.

Flow Chart

However, maybe you are not interested in agile and want to pursue risk management further. That is fine, use these personal and environmental factors to create your own framework. Maybe a PMI-RMP (Risk Management Professional) credential fits the bill? My point is that with a wide variety of experiences, goals, motivations and credentials to choose from there will be a huge array of possible decision trees like this.

The purpose of this article is not to recommend a single path for the half a million CSM’s in the workforce, rather explain a framework for evaluating your options. Don’t be pressured by peers or corporate training roadmaps, instead honestly evaluate why you may want to obtain a new credential and then which would best fit your development goals.

[I first wrote this article for here]