Project Management

Agility and Project Leadership

by
A contrarian and provocative blog that goes beyond the traditional over-hyped dogma of "Agile", so as to obtain true agility and project leadership through a process of philosophical reflection.

About this Blog

RSS

Recent Posts

Has Scrum outlived its usefulness? Should Scrum just go away?

The rise of Agile’s SAFe is like a bad episode of the movie Groundhog Day

Marcel Proust’s recursive novel: Why the concept of iteration in Agile is shortsighted

Forecast for 2015: The beginning of the end of Agile?

Google considered the best US company to work for due to HR agility

Categories

Date

Crowdsourcing, Social Media and Agility

linkedin twitter facebook Request to reuse this  

There has been a lot of hype recently about the effectiveness of crowdsourcing that runs parallel to the hype around social networking, which is no surprise since each feed each other.  A crowdsourcing project typically gets launch through some kind of social media platform like Facebook or Twitter, and if its popular enough it can go “viral” (to use another hyped term).  A great recent example of a crowdsourcing project was the infamous Doritos commercial that aired on the Super Bowl.

 
 
This contest allowed consumers to submit their own Doritos commercials that could then be voted upon by the general public to select five finalists in which monetary prizes are given out.  Obviously this went viral and generated nearly a million social media comments.
 
But what if your a project manager tasked with managing a crowdsourcing project?  How would you go about managing such a project, especially if you don’t have a brand like Doritos and their deep pockets of funding?
 
I think before you even consider crowdsourcing a project, you need to have some preliminary items to think through:
  • Industry Domain: I think the first order of business is to understand that crowdsourcing projects work best for industry domains such as marketing, advertising, industrial design and open source software projects.  You would not want to crowdsource the design and construction of a implantable medical device or pharmaceutical drug.
  • Crowd (big/massive team) Management: Crowds will engage with your project for fame, notoriety, money or all of the above.  You have to make sure you have the right incentive and furthermore, the added burden of making sure no one is gaming the system or feels as though they are not adequately being rewarded for their contributions.
  • Real-Time Communication Management (e.g., social and/or mainstream media): Real-time feedback and communication is absolutely critical in this type of project.  Going “viral” is a double edge sword, since just as positive comments on Facebook or Twitter can bring you tremendous momentum, bad press can take you down just as quickly and can mean a PR nightmare for your project and organization.
In this type of situation, you will have to do Agile and beyond.  Your crowd will have to be self-organizing.  There is no choice, since you are not picking the crowd but rather hoping you generate enough of a crowd to get the talent you need.  This will be achieved by having a large enough crowd such that it will suffice to get the talent you need by sheer scale, dumb luck or a combination thereof.
 
I think you will get iterations, but they will not be the well defined Sprints we are accustomed to, but rather waves of self-correcting iterations provided by the crowd.  And rather than remove impediments as a typical ScrumMaster would do, your job will be to provide the right kinds of inducements, rewards or hype to keep the crowd active and moving forward.
 
Rather than fall to a traditional communication plan or attempt daily stand up meetings, you will have to be a master social media communicator that knows how to nip bad PR in the bud before it goes viral and ensure your updates or status gets linked (“Liked”) and forwarded (“Retweeted”) through the social network.
 
I’ve seen discussions on the topic of whether social media can be effective in project management.  I think when it is done as I have outlined above, is when it can be most effective.
This contest allowed consumers to submit their own Doritos commercials that could then be voted upon by the general public to select five finalists in which monetary prizes are given out.  Obviously this went viral and generated nearly a million social media comments.There has been a lot of hype recently about the effectiveness of crowdsourcing that runs parallel to the hype around social networking, which is no surprise since each feed each other.  A crowdsourcing project typically gets launch through some kind of social media platform like Facebook or Twitter, and if its popular enough it can go “viral” (to use another hyped term.  A great recent example of a crowdsourcing project was the infamous Doritos commercial that aired on the Super Bowl.
 
 
This contest allowed consumers to submit their own Doritos commercials that could then be voted upon by the general public to select five finalists in which monetary prizes are given out.  Obviously this went viral and generated nearly a million social media comments.
Posted on: February 23, 2012 12:12 AM | Permalink | Comments (1)

PMBOK v5 Draft - More Agile integration

linkedin twitter facebook Request to reuse this  

The PMBOK v5 Guide Exposure Draft was made available to the public on February 17, 2012 and is available for public review and comments/recommendations by PMI members.  What this means is that you have an opportunity to provide your feedback on the draft before it goes to final publication.

Here are some of the major changes I’ve seen:
  • They took out Chapter 3 (The Standard for Project Management) and placed it in the appendix since it is now an ANSI standard
  • The communications content that used to be part of Chapter 11 is now a new Chapter 13 titled “Stakeholder Engagement” which adds a new, 10th knowledge area called “Project Stakeholder Management”
  • The word “Plan” has been added to the knowledge areas in the Planning Process Group for items such as Scope, Schedule, Cost, and Stakeholder management much like it was in previous editions
  • There are now 47 processes in the 5th edition PMBOK Guide exposure draft as well as 614 input, tools and techniques and outputs which is about 15-20% more than the previous edition
The interesting sections for me were the continued addition of Agile terms and practices.  Take this section on the “Adaptive Life Cycles”, section 2.4.2.4:
 
Adaptive life cycles (also known as change-driven or agile methods) are intended to facilitate change and require a high degree of ongoing stakeholder involvement. Adaptive methods are also iterative and incremental, but differ in that iterations are very rapid (usually 2 to 4 weeks in length) and are fixed in time and resources. Adaptive projects generally perform all processes in each iteration, although early iterations may concentrate on planning activities.
 
Sound very Scrumish and from this we can see why stakeholder management was spawned off as a separate knowledge area that is included in all the process groups except closing since “to facilitate change and require a high degree of ongoing stakeholder involvement”.  Much as is advocated in Agile/Scrum is the need for constant customer engagement and feedback and this is now reflected in the draft version of the 5th edition PMBOK.
 
Rolling Wave Planning is more aligned with Agile in section 6.2.2.2:
 
Rolling wave planning is an iterative planning technique in which the work to be accomplished in the near term is planned in detail, while the work in the future is planned at a more general level. It is a form of progressive elaboration. Therefore, work can exist at various levels of detail depending on where it is in the project life cycle.
 
For example, agile project management, originating in software development, uses iterative planning as a progression of rolling wave planning. The agile project team utilizes CPM scheduling for each development cycle (iteration). Agile project management focuses on shorter development cycles and tangible results for each iteration; the focus is on creating value instead of completing activities.
 
And in Section 6.7 regarding Control Schedule:
 
If an agile approach is utilized, control schedule is concerned with:
Determining the current status of the project schedule by comparing the total amount of work delivered and accepted against predictions of work completed for the time elapsed,
Conducting retrospective reviews (scheduled lessons learned reviews) for correcting processes and improving, if required,
Reprioritizing the remaining work plan (backlog),
Determining the rate of delivery (velocity) and acceptance of work per iteration (agreed work cycle duration, typically two weeks or one month),
Determining that the project schedule has changed, and
Managing the actual changes as they occur.
  • Determining the current status of the project schedule by comparing the total amount of work delivered and accepted against predictions of work completed for the time elapsed,
  • Conducting retrospective reviews (scheduled lessons learned reviews) for correcting processes and improving, if required,
  • Reprioritizing the remaining work plan (backlog),
  • Determining the rate of delivery (velocity) and acceptance of work per iteration (agreed work cycle duration, typically two weeks or one month),
  • Determining that the project schedule has changed, and
  • Managing the actual changes as they occur.
 
Mike Griffiths of the PM blog “Leading Answers” who worked on the Agile sections of the PMBOK states it pretty well when he says “never have I worked so hard, to write so little, about agile”, since as can be seen from the sections above, the draft PMBOK is articulating Agile practices, but is trying very hard not to be perceived as advocating Agile as Agile is generally practiced and known.
 
In my view, I can actually understand this rationale.  Though I have seen studies that indicate that the majority if project managers who are studying the PMBOK for the PMP are in the IT industry, there are still many who are not and as a body of knowledge for general project management best practices, they need to be as agnostic as possible.
 
In any event, for those interested and with current PMI membership status I recommend you check it out.
In any event, for those interested and with current PMI membership status I recommend you check it out.The PMBOK v5 Guide Exposure Draft was made available for review on February 17, 2012  and is available for public review and comments/recommendations by members.  What this means is that you have an opportunity to provide your feedback on the draft before it goes to final publication.
 
Here are some of the major changes I’ve seen:
They took out Chapter 3 (The Standard for Project Management) and placed it in the appendix since it is now an ANSI standard
The communications content that used to be part of Chapter 11 is now a new Chapter 13 titled “Stakeholder Engagement” which adds a new, 10th knowledge area called “Project Stakeholder Management”
The word “Plan” has been added to the knowledge areas in the Planning Process Group for items such as Scope, Schedule, Cost, and Stakeholder management much like it was in previous editions
There are now 47 processes in the 5th edition PMBOK Guide exposure draft as well as 614 input, tools and techniques and outputs which is about 15-20% more than the previous edition
 
 
The interesting sections for me were the continued addition of Agile terms and practices.  Take this section on the “Adaptive Life Cycles”, section 2.4.2.4:
 
Adaptive life cycles (also known as change-driven or agile methods) are intended to facilitate change and require a high degree of ongoing stakeholder involvement. Adaptive methods are also iterative and incremental, but differ in that iterations are very rapid (usually 2 to 4 weeks in length) and are fixed in time and resources. Adaptive projects generally perform all processes in each iteration, although early iterations may concentrate on planning activities.
 
Sound very Scrumish and from this we can see why stakeholder management was spawned off as a separate knowledge area that is included in all the process groups except closing since “to facilitate change and require a high degree of ongoing stakeholder involvement”.  Much as is advocated in Agile/Scrum is the need for constant customer engagement and feedback and this is now reflected in the draft version of the 5th edition PMBOK.
 
Rolling Wave Planning is more aligned with Agile in section 6.2.2.2:
 
Rolling wave planning is an iterative planning technique in which the work to be accomplished in the near term is planned in detail, while the work in the future is planned at a more general level. It is a form of progressive elaboration. Therefore, work can exist at various levels of detail depending on where it is in the project life cycle.
 
For example, agile project management, originating in software development, uses iterative planning as a progression of rolling wave planning. The agile project team utilizes CPM scheduling for each development cycle (iteration). Agile project management focuses on shorter development cycles and tangible results for each iteration; the focus is on creating value instead of completing activities.
 
And in Section 6.7 regarding Control Schedule:
 
If an agile approach is utilized, control schedule is concerned with:
Determining the current status of the project schedule by comparing the total amount of work delivered and accepted against predictions of work completed for the time elapsed,
Conducting retrospective reviews (scheduled lessons learned reviews) for correcting processes and improving, if required,
Reprioritizing the remaining work plan (backlog),
Determining the rate of delivery (velocity) and acceptance of work per iteration (agreed work cycle duration, typically two weeks or one month),
Determining that the project schedule has changed, and
Managing the actual changes as they occur.
 
 
Mike Griffiths of the PM blog “Leading Answers” who worked on the Agile sections of the PMBOK states is pretty well when he says “never have I worked so hard, to write so little, about agile”, since as can be seen from the sections above, the draft PMBOK is articulating Agile practices, but is trying very hard not to be perceived as advocating Agile as Agile is generally practiced and known.
 
In my view, I can actually understand this rationale.  Though I have seen studies that indicate that the majority if project managers who are studying the PMBOK for the PMP are in the IT industry, there are still many who are not and as a body of knowledge for general project management best practices, they need to be as agnostic as possible.
 
In any event, for those interested and with current PMI membership status I recommend you check it out.
Posted on: February 22, 2012 10:59 PM | Permalink | Comments (0)

Being a Lean-er Startup

linkedin twitter facebook Request to reuse this  

Here'a a video by author Eric Ries on being a lean-er startup:

 

 

This movement seems to be catching on quite well, and interestingly, much like the early days of project management that was done informally and with very little structure that now has many methods and best practices associated with it, Mr. Ries is arguing that launching and managing a startup can be put on a more systematic and scientific basis with methods and best practices from Lean and other business processes.

Of course as anyone who has been involved with managing projects or with startup business ventures would know, that it is much as art as it is science, but I do applaud his efforts to put setting up a startup which is typically associated with chaos on a more firmer foundation.

It is very similar to an idea I have about reconciling the best PM practices with startup business ventures.

You can buy the book on Amazon:

Posted on: February 06, 2012 11:10 PM | Permalink | Comments (1)

The Cult of Agile

linkedin twitter facebook Request to reuse this  

Wikipedia defines a cult as "a new religious movement or other group whose beliefs or practices are considered abnormal or bizarre".  Images of Charles Manson or Jim Jones comes to mind with brainwashed individuals engaged in bizarre rituals and following their crazed leaders without question to murder or commit mass suicide.  So it may seem harsh for me to title this post as the "cult of Agile", but when I see blog post such as this one titled "Project Management: A Malady" or "Are Project Managers Living a Lie?" where in their over zealous efforts to promote Agile, they blast traditional project management, I can't help but to feel as though they are speaking as if from a cult.  As Tobian Mayer of Agile Anarchy posts:

Contrary to popular myth, Project Management is not a job, a profession or a career path. It is an illness, a disorder characterized by delusion, specifically a desire to control people and outcomes, and a belief that the future can be accurately predicted if only everyone did what they were supposed to do. Sufferers in the advanced stages of this illness resort to resentment, blame, and fear, and can often be seen pouring over spreadsheets and charts, pulling their hair out in dismay, or pounding their desk... Just as the alcoholic frequents bars and other drinking holes, seeking validation of his or her resentments towards the world, so the Project Manager attends PMI and other certification courses to be reminded, I am right!... Happily, there is a cure. It is a program of recovery called Agile, but because the nature of the program is a complete reassessment of one’s life and career, few are able to engage, seeking, as always a quick-fix solution.


Though I realize that much of this is a tongue-and-cheek jibe at traditional project management, I have seen such rhetoric hurled at traditional project management to advance Agile methods.

In general, I don't think it will help promote Agile in a constructive way, especially amongst those millions of project managers who are tasked with projects that are not always conducive to Agile methods or for those who would like to adopt and incorporate the practices into their day-to-day work.  It could turn them off to the practices, which would be the real loss since there are many benefits to using them.

Any seasoned project management professional (though the quote above and some within the community argue whether a PM is a true professional such as an accountant or lawyer, I believe we are professionals in the general sense) would know that there is no one size fits all to managing projects, but rather the ability to have a broad and deep understanding of the best practices in his/her industry and to apply the best one to their individual projects.
For me its like a sliding scale:  On one end you have pure Agile and on the other your have pure traditional project management.  And depending on your project, team, stakeholders, expectations, and organizational structure, you would see where your project fits within the scale and apply the best practices to make your project succeed.

In the end, all that matters is whether your project was done on time, within budget/scope and most importantly, to customer satisfaction.  No one will care whether you did Agile, traditional or voodoo magic.

Posted on: January 30, 2012 10:44 PM | Permalink | Comments (2)

When whole overseas industries become more Agile

linkedin twitter facebook Request to reuse this  

This very interesting article from the NY Times talks about how and why the US lost out to China for the manufacturing of the iPhone.  Though most would think it is cost that drives companies like Apple to transfer their manufacturing overseas, the article points out that it was only one of several major factors:

It isn’t just that workers are cheaper abroad. Rather, Apple’s executives believe the vast scale of overseas factories as well as the flexibility, diligence and industrial skills of foreign workers have so outpaced their American counterparts that “Made in the U.S.A.” is no longer a viable option for most Apple products.

The article goes on to talk about the incredible Agility of Chinese companies like Foxconn in China, where "Apple’s executives had estimated that about 8,700 industrial engineers were needed to oversee and guide the 200,000 assembly-line workers eventually involved in manufacturing iPhones. The company’s analysts had forecast it would take as long as nine months to find that many qualified engineers in the United States... In China, it took 15 days".

Furthermore, companies in China have many skilled workers who have highly specialized technical skills that are above most manufacturing level labor, but not necessarily at the level of a formal engineering degree at the university that just cannot be matched in the US.  They are also able to mobilize them very quickly with no issue both for the employer and employee, for the most part, to work 12 hour shifts, 6 days a week.

We can dispute in this country whether that work level will be sustanable and if it's worth the loss of personal life with family and friends that will take its eventual toll, but in my opinion I have no doubt much of this comes down to people in countries like China who are just more hungrier for financial success than we are in the US and Europe.  Whether this is good or bad in itself is missing the point that China other countries are and will continue to outpace us in manufacturing which is a catalyst for creating middle class jobs.

What this entails for those of us in the project management field, is that as we all know, the world is getting flatter, faster and more projectized for as the article points out,

The pace of innovation, say executives from a variety of industries, has been quickened by businessmen like Mr. Jobs. G.M. went as long as half a decade between major automobile redesigns. Apple, by comparison, has released five iPhones in four years, doubling the devices’ speed and memory while dropping the price that some consumers pay.

Your now going to have to deal with whole industries in other countries that are more agile, flexible and speedier with respect to how they dispatch and deploy their workforce, engineer their business processes, and manage their portfolio of projects.

We are in for some interesting times indeed.

 
In China, it took 15 days.
 
In China, it took 15 days.
Posted on: January 23, 2012 12:40 AM | Permalink | Comments (1)
ADVERTISEMENTS

'Human existence must be a kind of error. It may be said of it: "It is bad today and every day it will get worse, until the worst of all happens."'

- Arthur Schopenhauer

ADVERTISEMENT

Sponsors