Agile

Mapping the PMI-ACP Exam

PMI Agile Exam BreakdownSo, word on the street is the PMI Agile (Project Professional Certified Practitioner) Certification pilot will begin in just a few weeks.  For those interested in participating in the pilot or taking the exam in a few more months, PMI was kind enough to provide an examination content outline.  Though it's only 16 pages in length, I started to reorganize the data so people can see what they're up against.  Download the PMI-ACP Exam Matrix.

Here is a breakdown of the exam

Agile Tools and Techniques (50% of Exam) I'll write another post about that later

Agile Knowledge and Skills (50% of Exam) Percentage of Knowledge and Skill Content / % of Exam Level 1 (65% / 33%)  (18 knowledge/skills) Level 2 (25% / 12%) (12 knowledge/skills) Level 3 (10% / 5%) (13 knowledge/skills)

HT: PMI Agile Certification Examination Content Outline

Judgement Day

DeadlineLast night (April 19, 2011) at precisely 8.11pm, Skynet, the giant computer network that controls most of the U.S. weapons, became self aware. Tomorrow it begins its assault on humanity. Tomorrow is to be Judgement Day. Hmmmm.  I'm a big Terminator fan but I've heard this story before.  If memory serves me right, I shouldn't be preparing for the day the machines are set to rise and take over the Earth.  I should be preparing for disappointment.

Space 1999

Remember way back when nuclear waste from Earth was stored on the Moon's far side and it was to explode in a catastrophic accident on September 13, 1999?  It was to knock the Moon out of orbit and send it and the 311 inhabitants of Moonbase Alpha hurtling uncontrollably into space.  It didn't happen!

Millennium Bug

Remember all of those crazy people who were stockpiling gold, food, and water leading up to December 31, 1999?  Sure, I still have a container of TVP somewhere in the basement.  It's now there in the event of a zombie apocalypse.  Butt CNN Money reported that we spent over $500 Billion on Y2K.  Again, nothing really happened!

2001: A Space Odyssey

Some technologies portrayed as common which have not materialized include commonplace civilian space travel, space stations with hotels, moon colonization, suspended animation of humans, and strong artificial intelligence like HAL.  We're getting there, but it hasn't happened.  Arther C. Clarke went on to write three sequel novels: 2010: Odyssey Two2061: Odyssey Three, and 3001: The Final Odyssey. Two out of four have come to pass and we missed the mark.

So, what is my science fiction rambling all about?

Why do we keep making predictions?  Aren't we setting ourselves up for a fall over and over again?  Sure, I'm all about setting goals.  We did get a man on the moon by 1970, as President Kennedy pledged.  But fact or fiction, I just don't see 99% of these predictions as coming true.  Just as I have less and less faith in predicting the completion date and scope of a project before it begins, I'm not going to buy into Judgement Day either.  I'm just trying to manage this cone of uncertainty. Let's just review what happened yesterday, let's see what we're doing today, and then we'll see what we can get done tomorrow.

 

HT: Wikipedia

Drawing from Pictofigo

GLSEC Retrospective

GLSECI'm back from a quick trip to Michigan.  The Great Lakes Software Excellence Conference was taking place and my talk had been accepted.  My talk was titled Breaking the Law of Bureaucracy (I'll upload my deck in a few days) and the topic was Servant-Leadership.  Though I really enjoyed giving my talk, the best part of my visit was all of the people I interacted with.  I finally met Casey DuBois, a guy I've known via email and phone for over a decade.  We used to do business together (long distance) and this meetup was a long time coming.  Next, I met several people from Atomic Object and drank a bunch of their coffee.  Later, I met the organizers, sponsors, and other speakers who made the conference happen.  And to think that was just Friday. Saturday went by way too fast.  Everything ran very smoothly. I gave my talk, we played Simon Says and Red Light Green Light, and I even had an opportunity to meet Ben Lichtenwalner from ModernServantLeader.com. If I could have done anything more, it would have been attend more of the sessions.  The speakers and content were top notch.

It was really exciting to talk to a few local startups from the Grand Rapids area and to hear about a local incubator called Momentum. It made me realize the importance of local incubators and helping startups succeed.  These startups have solid ideas!  I'd write about them now but I want to have standalone posts for them.

So, I'm going to keep this short.

Thank you to Grand Rapids for a truly awesome experience.  A very special thank you to Mr. Casey DuBois for his amazing hospitality.

Judging an Agile Book

I'm in Grand Rapids, Michigan, to speak at the Great Lakes Software Excellence Conference.  If you ever imagined what an "Agile" company looked like, I think I am looking at it right now.  I'm blogging today from Atomic Object.  The exterior of the 100 year-old building is very unassuming.  Upon entering the building, I'm greeted by several dogs.  Yes, like in man's-best-friend dogs.  They give me the once-over and allowed me to pass.  I walk past a wall with mountain bikes and walk upstairs to discover a truly Agile workspace.

The floors are a light wood and the workspace is wide open.  There is plenty of natural light.  In the middle of the room is a functioning stop light.  It's exactly what I thought it was.  It's an information radiator to indicate if the build is broken or not.  Fortunately, the light is green.  I'm now sipping on a freshly brewed cup of black coffee and enjoying web access.  There are almost as many whiteboards as there are approachable friendly people.

I know you should not judge a book by its cover.  But, if I'm looking for a book on Agile, I would have a few expectations.  This place and the people working here exceed those expectations.

When I return to Washington DC tomorrow night, I'll take with me the first hand confirmation that Agile workspaces (and companies) are so much more inviting than those with cube farms or offices.

Zero Cost Effect

I had dinner with a colleague the other night.  I inadvertently quoted something verbatim from Dan Pink's book, Drive. My colleague said if I liked Dan Pink's work, I should read something from Dan Ariely.  So, I started on Predictably Irrational:  The Hidden Forces That Shape Our Decisions. Wow, this book is crazy!  I'm not going to go into any more details in the post other than a comparison of an experiment detailed in the book and something I've seen in the real world. In the book, the author described an experiment on 34 Halloween trick-or-treaters. As soon as the children knocked on the door, they received 3 Hershey's (each weighing about 0.16 oz.) and were asked to hold the Hershey’s they had just received in their open hand in front of them. Each child was then offered a choice between a small (1 oz.) and a large (2 oz.) Snickers bar, under a Cost Condition and under a Free Condition.  In the Free Condition, they could simply get the small 1 oz. Snickers bar (for free) without giving up anything or they could exchange 1 of their 3 Hershey's for the 1 large Snickers bar.  In the Cost Condition, the children could exchange 1 of their .16 oz. Hershey's for the small (1 oz.) Snickers bar or exchange 2 Hersheys for the large (2 oz.) Snickers bar.  They could also choose to do nothing but all of the kids chose to make an exchange.

Experiment Results

In the Free Condition, in which the small Snickers bar is free, demand for it increases substantially (relative to the Cost Condition).  The results demonstrate the attractiveness of zero cost.  People gravitate more toward options that do not require giving up anything.

Example of this on a project

At work, I've had a Product Owner (PO) who wanted to add items from the Backlog to the Sprint.  During sprint planning, the team basically added a buffer, to account for unforeseen events.  I know people are going to crucify me for this, but basically, the Product Owner always seemed to want to shift priorities of work mid-Sprint.  Rather than killing the Sprint, we added a buffer.  This would allow new work to be entertained without totally derailing the work already being completed.  Yes, we could have used Kanban and all of this could have been avoided.  But, Kanban wasn't an option.

So, what happened?  I offered the PO a deal.  I could allow him to add a certain amount of work to the Sprint for free. When I did this, he usually asked for smaller deliverables (relative to other items on the backlog that were ready to work).  But, when I said some work would have to come off the table to pay for the new work, he always went big.  He would choose larger deliverables relative to other items on the backlog that were ready to work.

All I can say is we truly are predictably irrational.


Yes, the links to the books are affiliate links.

My Own Agile Game

Because I will be speaking at the Great Lakes Software Excellence Conference (#glsec) on April 16, I will be unable to attend Agile Games 2011 (#agilegames).  Realizing my session was for 50 minutes, I wanted to include a game as part of my talk.  Seriously, can you image listening to me talk for 50 minutes straight?  When I've seen other speakers who included collaborative play or human interaction in their presentations, it made the session so much more enjoyable.  So, I contacted Brian Bozzuto of BigVisible to ask if he could help me with a game on servant-leadership.

Brian made some recommendations and here is my final idea.  I call it Simon Says versus Red-Light-Green-Light. I'll admit, I find it hard to believe someone else has not documented this "game versus game" as an exercise to help people understand the concept of empowerment or servant-leadership.  If you know of someone who has documented this game, please let me know so I can give them credit.

 

Command and Control Management

Game: Simon Says (Modified) The Goal: Participants want to get from one side of the room to the next, via instructions from you (Simon).  Participant must be navigated around obstructions and follow Simon's instructions (regardless if instructions help the participant get closer to the goal or not.)

  1. Line up a group across the room from you.
  2. Tell the players that they should all obey you if you first say the words "Simon says." (all directions will begin with "Simon says")
  3. Tell them the goal of the game is to get across the room in the shortest possible path.
  4. Begin by saying something like, "Simon says, participant 1, take 3 steps forward."
  5. Look to make sure he or she has taken 3 steps forward.
  6. Give another order such as, "Simon says, participant 2, take 1 step to the left."
  7. Continue giving orders. Having the players navigate toward the goal and around obstructions.
  8. Give a few players direct paths to the goal and a few players crazy instructions that do not help them reach the goal.

Servant-Leadership

Game: Red Light Green Light (Modified) The Goal: Participants (cars) want to get from one side of the room to the next, via self-direction and verbal input.  You will act as the stoplight. Someone will act as the obstructionist, who will block cars with whatever is available.  When stopped, the obstructionist will block cars.  The stoplight will then ask the cars if they want obstructions removed or if they want to continue on.

  1. Line up a group across the room from you (the Stoplight).
  2. Tell the cars that they should all obey the instructions to stop or go by the verbal queues of red light and green light.
  3. Tell them the goal of the game is to get across the room in the shortest possible path.
  4. Begin by saying "Green light", allowing cars to approach the goal.
  5. Give the order "Red light."
  6. Have an obstructionist block the cars in some way.
  7. Ask the cars if they wish you to move any obstructions or if they wish to continue on. (just ask if they need help)
  8. Give stop-go orders until the the last car reaches the goal.

That's it!  That's my comparison between a traditional top-down management environment versus an empowered environment with the assistance of a servant-leader.  If you have any comments or suggestions, I would love to hear them.

HT: Brian Bozzuto

Getting PMI Agile PDUs Early

Let's say you're interested in the upcoming Agile Project Professional (APP) certification from PMI.  You look to see the eligibility requirements and notice you'll need 21 hours of Agile Project Management Training.  If you're determined to get the PMI APP and looking to do this on the cheap, start watching webinars now. I can guarantee there will be a lot of training opportunities in the near future.  Check out a future location to find upcoming Agile PDUs. Once it is fully rolled out, it should be an excellent resource to find PDUs to meet your PMI needs. PMI Agile PDUSo back to the intent of getting the training.  After I read (and recently reread) Dan Pink’s book, Drive: The Surprising Truth About What Motivates Us, it made me stop and question why people wanted to get the PMP or APP.  Are we trying to discover better ways to deliver value to customers or just trying to get a piece of paper and a few extra letters after our names?  Dan breaks it down to pursuing the mastery of performance-based objectives versus learning-based objectives (ie. getting a passing score on a certification exam versus learning new approaches to deliver value to customers).

Regardless, information is information and I want to do what I can to help people discover it.

One of the approaches I really enjoy using is Kanban.  Today I stumbled upon a free Kanban webinar.  Though you do have to enter some contact information, it's free.  You have the option of downloading it or viewing a playback.  So, regardless if you're looking to bank those PMI Agile PDUs or not, enjoy 1 free hour of training.  By the way, I am in no way affiliated with the provider.   I just like free webinars.

HT: ASPE Events HT: Agile PDUs

Link to Drive is an Amazon affiliate link Drawing by Pictofigo

 

 

My Zombie PM Book on Amazon

When I realized that I could publish my thoughts on a blog, I found it very cathartic.  Writing a book posed its own set challenges.  When I was halfway done with the book, I saw the forest through the trees.  This idiom personified what I was trying to communicate about project management.  I found that I had become a writing zombie.  I thought of those who came before me, putting pen to paper.  They had ideas. But, how many were able get their works published and released to the general public?  What roadblocks stopped them from making their dream a reality?

To just accept the status quo without question is one of the first steps to becoming a zombie.  Traditionally, a writer gets approval from a publisher, they plan out and write their book, someone edits the work, the book gets printed, and hopefully people buy it.  To me, the book publishing process sounded a lot like traditional project management.  Regardless of the process, I think you should always ask yourself why.  Why are you following the process?  If a process doesn’t seem to make sense, perhaps it should be changed. In my case, I decided to change the process to meet my needs, taking a more agile approach.

First, I picked a publish date and decided I would focus on whatever I thought would have the greatest value first.  I took my inspiration from Seth Godin who said to just pick a date and ship.  Next, I decided that I would publish more content at scheduled intervals, until the body of work was completed.  The book will be released in a series of sections or chapters rather than the entire book at once.  After fifteen years in the project management industry, I’ve learned that it’s possible to deliver more value sooner, by establishing a series of deadlines and delivering something at each deadline.  Lower the risk of not reaching the overall goal, by ensuring delivery of something on a regularly basis.

One of my favorite books, Agile Project Management with Scrum by Ken Schwaber, has 9 chapters and 155 pages.  When I purchased the book at a Borders bookstore back in 2005, it cost me $39.99.  Though I recognize the value in reading a physical book cover to cover, I would now be willing to purchase chapters of an electronic version of a book, if the author was willing to offer it.  Give me the chapters of greatest value first, at a price relative to its overall cost.  And from that, I had the basis of the book.  I intend to offer it at a very reasonable cost ($2.99) and in multiple formats.  Starting with an electronic form allows me to keep costs down and will allow it to be iterated into a better body of work.

I want everyone to know that I don't see myself as an author.  I probably don't use the best sentence structure or verb tense.  But, I want you to know that the barrier of entry in the publishing world has come down.  If you've ever been inspired to write something, just do it!  I feels great.

Direct Link to the $2.99 Book on Amazon:  Zombie Project Management(Also available on Amazon UK)

Links to both my book and Ken Schwaber's book are both affiliated links.  What can I say, I need to feed my coffee habit.