MVP for PMI Agile Exam Flashcards

With the PMI Agile Certified Practitioner (ACP) exam celebrating its first month in the wild, I am sure you are already seeing a lot of study aids and prep courses being offered.  Full disclosure, I do offer ACP prep courses and I also offer PMI Agile Exam flashcards.   Wait, did you read that correctly?  Yes, you did.  I want to ensure there is a source of relevant study material available to the masses so I created the PMI Agile Flashcards website and have an iPhone app (that needs to be submitted to Apple for approval). As a co-lead for the PMI ACP support team, we are tasked with creating a knowledge base of relevant information for the ACP exam.  Think of it as a Wikipedia for the PMI-ACP but within the PMI.org website.  Though that's all well and good, creating a glossary for both trainers and certification aspirants is not a study aid.  I still see the need for things like study guides and exam prep tools.  I think back when I was preparing for the PMP.  Reading the PMBOK Guide was a wealth of information but I needed something to put it into context.  It wasn't until I read Rita Mulcahey's book that it all made sense to me.  I also created a deck of flashcards for myself to help me prepare for the PMP exam.

Fast forward to today, for those of you who are looking for a study guide for the ACP, Mike Griffiths (the other PMI ACP support team co-lead) has just completed his ACP Exam prep book. I am releasing my Minimum Viable Product (MVP) for my PMI ACP Exam Flashcards. If that combination worked for me to prepare for the PMP, I hope it works for you for the ACP.

If you are wondering what I mean by MVP, I got the term from the Eric Ries book The Lean Startup.  I knew that I needed to get something out there now, get feedback from customers, and iterate the product.  The good news is, I know the questions and answers on the flashcards are relevant to the exam.  All I needed was to get something out there that people could use.

My MVP

1. The first 75 flashcards loaded

I have loaded 75 flashcards into the database.  I know they are all relevant because I took (and passed) the ACP exam and because I have been involved during the certification development and am now involved to support it.  I've been involved in the Agile and PMI communities for a while now.  I want good quality prep materials made available to people. I don't want them to just pass the exam.  I want them to learn something.

2. All flashcards map to one of the six domains

• Value Driven Delivery

• Stakeholder Engagement

• Boosting Team Performance Practices

• Adaptive Planning

• Problem Detection and Resolution

• Continuous Improvement (Product, Process, People)

3. All flashcards map to the two areas you will be graded on

• Tools and Techniques

• Knowledge and Skills

4. 20 free flashcards to view without login

I figure you'll know if this product has value for you within 20 flashcards.  After that, you'll probably want to create a login so you can keep track of your progress.

5. 20 free flashcards with progress tracking with login

So, you created a free account.  You'll now be able to visualize your progress as you go.  By navigating to the progress screen, you'll be able to navigate back to cards that you got incorrect or skipped earlier.  Since you're still using a free account, you'll have access to 20 flashcards.

6. Access to all flashcards with paid account

This is where we wrap it all together.  The goal is to have a few hundred flashcards in the system.  You can get started now with the first 75.  As the database grows, random flashcards will appear as "unviewed".  Just check your status before you begin and you know where you stand.

What is next?

• Add more flashcards

• Make some changes in the User Interface to make it easier to navigate

• Get feedback from customers

• Refine the product or pivot

• Get the iOS and Android versions completed

Note: A few of the links are Amazon affiliate links.

PMI Agile Contact Hours versus PMI-ACP PDUs

I get asked on a regular basis what the difference between a contact hour and a PDU is. When people come to my PMI-ACP exam prep class, they qualify to claim 21 Agile contact hours.  If they currently have another PMI credential, they could choose to apply those 21 hours as a PDU.

PMI Agile Contact Hours

When completing your PMI-ACP application, you are required to report (among other things) your "Agile" education. They will be referred to and measured as contact hours. To qualify to sit for the ACP exam, you need 21 contact hours.

 Professional Development Units (PDUs)

PDUs can only be applied if you have a PMI credential.  If you try to claim a PDU and you don't have a credential, PMI will politely either tell you don't have permission to that area of the website (where you claim the PDU) or they will send you a friendly email. The image below is only viewable if you have at least one PMI credential.

Hope this brief overview helps. If you have any questions, please leave a comment below.

Optimize the Whole

I know we talk about self-organized and empowered teams being at the heart of agile practices.  But sometime I see that focus from individuals and teams going a little too far.  Sometimes people forget about the big picture.  I believe everything we do needs to map back to organizational visions and goals.  If you can't do that, what you are doing is wasteful.  For some organizations, everything needs to map back to increasing profits or lowering costs.  But we have to be careful not to fall into the "local optimum" trap.

A local optimum of a combinatorial optimization problem is a solution that is optimal (either maximal or minimal) within a neighboring set of solutions. This is in contrast to a global optimum, which is the optimal solution among all possible solutions. (Thank you Wikipedia)

You can read more about local optimums in the late Eli Goldratt's book, The Goal.  To the layman, you should consider activities and efforts that will benefit the organization or process flow as a whole, not necessarily what is best for you or your team.  I know it sounds counter-intuitive but hear me out.

You've probably seen this local optimum in action in one way or the other.  If you have a process flow, it's happened.  With a traditional waterfall application development flow, have you ever had a development team deliver features without any concern of the impact to their QA counterparts or others downstream in the process?  The release is dependent on the other teams but what do they care?  They were very efficient at getting their work done.

Have you ever had that boss who was utterly obsessed with keeping everyone "100%" busy rather then being focused on ensuring the greatest amount of value flowed through the system in the shortest possible time?  Both instances are bringing attention to practices that happen and we just accept them.  One example is focusing too much on the localized efficiency. The other focuses too much on utilization.

My Freeway Analogy

When I get on the freeway, I don't care that I can go the speed limit for 5 miles out of my 50 mile commute (localized efficiency).  I really don't care how many cars the freeway can hold (utilization).  What I care about is that I can go as fast as I can for my overall commute.  That should be the goal.

I'll close with one of my favorite quotes by Eli Goldratt

A system of local optimums is not an optimum system at all

I'm curious if others out there can give me some more examples of local optimums and how they addressed them.  How did you optimize the whole?

Image Source: Awesome DC

PMI Agile CoP Strategic Planning Day 1

The first full day of the PMI Agile Community of Practice strategic planning session just wrapped up.  It's been an amazing day.  We discussed how we could help Project Management Practitioners, PMI Members, CoP Volunteers, and Agile Leaders. Topics ranged from increasing awareness of Agile, to the PMI-ACP, and a PMI-ACP Glossary. Though we all come from all over the country, different organizations, and different backgrounds, we have at least one thing in common.  We all have a passion for Agile.

Because the PMI-ACP certification is transitioning to an operational stage, myself and a few others focused deeply on what we wanted to see happen in 2012.  First, you'll be seeing the PMI-ACP v1.1 coming January 31.  You should see PMI-ACP v1.2 out the end of the second quarter.  I'll save the real good stuff for subsequent posts.  Until then, goodnight from Miami.

The Future of Agile & PMI

During my session at the AgileDC conference, I talked about the past, present, and future of Agile. I drew a parallel between the adoption curve of Agile and Geoffrey Moore's adoption curve of technology.  Even before the Agile Manifesto was penned, there were Innovators introducing agile practices and mindsets.  In the last ten years, the early adopters and visionaries have taken Agile to the next step of market acceptance.  I'll admit, I only started using agile practices about 6 years ago.  During that time, as acceptance of Agile has grown, the Agile "mantra" has been relatively consistant.  I like to use the word mantra because Agile really does create a transformation.  If the values and principles of the Manifest resonate with you, you become an adopter, a proponent, and a member of a community.

The Agile community is a self-organized group of like-minded people and market adoption has been very organic.  So, back to my session at AgileDC.  I wanted to make a point of saying that Agilists do what they do because something resonates within them.  What we are doing, as Agilists, feels like it aligns with why we do it.  We want to deliver more value.  We want more interactions and collaborations. We respond to change.

Now, let's look at the Project Management community, specifically that group related to the Project Management Institute.  The primary difference between the PMI community and the Agile community is Project Managers don't appear to be joined by a common cause.  Rather, they are joined by a common certification. PMI's goal is

“Serve practitioners and organizations with standards that describe good practices, globally recognized credentials that certify project management expertise, and resources for professional development, networking and community.“

While I was doing research for my AgileDC session, I came across an interesting fact.  What Project Managers (associated with PMI) are doing does not align with why they are doing it.  Scan the blogoshere and you'll find less content about how to become a better project manager and more about how to pass the Project Management Professional (PMP®) exam.  Though the graph above about Agile Adoption is subjective, the graph below is not.

Something happened in February 2008.  It was the last time there were more members of PMI than there were PMPs. (260,458 vs. 259,694) Since then, the gap has widened to 366,854 PMI members and over 466,163 PMPs.  Project managers, associated with PMI, find more value in a certification than they do being a member of a community.  But can you blame them?  Job listings require certifications or accreditations.  Hiring managers search for acronyms and not people.  The simple truth is some are pursuing the mastery of performance-based objectives versus learning-based objectives (ie. getting a passing score on an exam versus getting better at a craft).  Since credential holders don't have to be a member of the community to maintain their PMP status, they dropped their memberships.  If not for the fact that I could not be a member of the PMI Agile Community of Practice without being a member of PMI, I would probably have ended my membership as well.  But, that alone is enough for me to stay.

The Agile Community of Practice (CoP) and it's leadership are self-organized.  I get a different vibe from them than I do others associated with PMI.  It's less about how do I maintain my certification and more about how can we help others.  It is my hope that as the Agile CoP grows, its servant leadership and passion will spread to other areas of PMI.

With the PMI-ACP certification, I'm very curious how this will impact the Agile community and the PMI community.  When I did my last PMI-ACP prep class, 66% of my learners were PMPs and 33% of the class was not associated with PMI at all.  Will the PMI-ACP just be another group of letters to appear in a hiring manager's keyword search or will it become more than that?  I truly hope it is the latter.

If you are a member of PMI, I strongly recommend that you join the Agile Community of Practice (it's free for PMI members).  The writing is on the wall, people.  It's a sign of things to come.  What if you are a PMP but not a member of PMI?  I think joining the Agile CoP is worth the price of the membership.  Regardless of what happens at PMI, Agile will continue to be an ever-evolving self-organized force.

When PMI Introduced the Elephant – Part 3

This post concludes my 3 part series about when PMI Introduced the Elephant in the Room.  It's the basis of my talk at AgileDC on October 26. The elephant I am referring to is the mainstream adoption of Agile.  In part one of my series, I introduced the idea that Agile was about to cross the chasm.  The chasm I'm referring to is based on the "Technology Life Cycle Adoption Curve" concept from Geoffrey Moore's 1992 book Crossing the Chasm. I see parallels between a technology life cycle adoption curve and a methodology life cycle adoption curve.  Though waterfall may be at the far right, with the laggards and skeptics, I see Agile as being embraced by the innovators and visionaries for the last 10 years.  But within the last view years, the earliest adopters and visionaries started to get traction.  It took real leadership to follow a few "lone nuts" and brave ridicule. There comes a time within the adoption curve that the tipping point occurs.   If the original Agile leaders were the flint, the first followers were the spark that made the fire.  With PMI creating the PMI-ACP certification, there is going to be a lot of fuel on the fire.  After teaching my first PMI-ACP class over the last few days, I asked my students why they were pursuing this certification.  What made it different?  Their answers were both enlightening and similar.  The common answer was that their organizations see the PMI endorsement of Agile methods as the legitimizing of Agile.  Until PMI got involved, Agile practices were "undisciplined ideas from those on the fringe".  Even with the certification being in the pilot stage, it has rapidly become a viable alternative to other processes that just aren't working.  Though Agile isn't for everyone, I find it amazing that so many have not adopted it, merely because it wasn't supported by the status quo.

I'm actually not sure where we are on the adoption curve.  But, from listening to my students, the fear of ridicule is being stripped away.  I do believe we are crossing the chasm.

Watch this 3 minute video.  If you are a version of the shirtless (Agile) dancing guy at your organization, all alone, remember the importance of nurturing your first few followers as equals, making everything clearly about the movement, not you.

Be public. Be easy to follow!

There is no movement without the first follower.

(Link to Video on YouTube)

When PMI Introduced the Elephant - Part 1

Last October I entered the Gaylord National with a little trepidation.  The PMI North American Congress was taking place and I found out that several people I admire in the Agile space were going to be attending and speaking.  Leading up to the major PMI event, I was hearing a lot of chatter about these "heretics" who were going to be presenting.  In Washington DC, the PMP was king and few in the Federal space wanted to hear anything about adaptive planning, continuous elaboration, or focusing on delivering value to the customer.  Project Managers were expected to predict the future, define process and then make damn sure you followed it, regardless if anything ever got delivered.  So, I was very much surprised as I walked through the Gaylord and noticed poster after poster, display after display.  "Are you Agile?" Every Agile session I attended, PMI Vice President of Information Technology, Frank Schettini introduced the speaker and told the audience that he leads the team that is responsible for delivering value to PMI’s members, volunteer leaders, certification holders and staff through innovative and reliable technology solutions. He said that he was a strong supporter of the Agile Community and so was PMI.

Though the audience at one of the first Agile sessions was almost hostile towards the presenters, by the time Michele Sliger gave the final session on the final day, there was buzz in the halls of the Gaylord about how "this Agile thing" had taken the conference by storm.

While I was there at the conference, I was privately asked if I would be willing to assist PMI with the creation of an Agile certification.  I was very apprehensive, at first.  I didn’t want PMI "hijacking" Agile.  I was assured that was not the case.  I discovered those I respected most in the industry were already hard at work, making sure it was done right.

Agile was about to cross the chasm and PMI was going to make sure we made it to the other side.

But first, introductions were in order.

The Gemba Walk

As part of a recent engagement I went to assess and coach a group of Agile teams out in Iowa.  Each morning, we would arrive before the daily stand-ups.  Each morning we walked around, listened in on conversations and got updates from the teams.  We quietly studied their large team boards and then how they interacted with the boards and one another. I would describe this daily stroll as our Gemba Walk.  Gemba is a Japanese term meaning "the real place." In business, it refers to the place where value is created; in our case the gemba was the west side of the building on the 5th floor where the teams were located.

Gemba Walk

In lean manufacturing, the idea of gemba is that the problems are visible, and the best improvement ideas will come from going to the gemba. The gemba walk, much like Management By Walking Around (MBWA), is an activity that takes management to those doing the actual value delivery, to look for waste and opportunities to practice gemba kaizen, or practical shopfloor improvement.  If you are in management and you want to make a real difference, get out of your office and go on a gemba walk.

If you are on a project team, do your managers go on a daily gemba walk?

HT: Wikipedia