How cloud computing affects projects

“Human knowledge has been changing from the word go and people in certain respects behave more rationally than they did when they didn’t have it. They spend less time doing rain dances and more time seeding clouds.”
Herbert Simon

Cloud computing – that server in the sky – has gotten a lot of press recently. Organizations are investigating its power to offer less expensive client services, to more tightly couple dispersed organizations, and to integrate open source applications with proprietary ones to improve the comprehensiveness of services. Cloud computing is also touted as a way to save money and be more green because less energy and natural resources are used.  In fact, I just got back from the Microsoft Worldwide Partner conference in DC where every presentation had something about “the cloud” and how you needed to be “all in.”

Tim O’Reilly, CEO of founder and CEO of O’Reilly Media, talked with operations personnel at OSCON 2010 about cloud coordinating services during the relief efforts after the Haiti earthquake. He discussed using information services provided through Ushahidi (Tufts University) to take source data from SMS, creating interactive maps using Google Earth, provide instantaneous translation with software developed in close to real-time, and connecting people through Skype.  

How will cloud computing change development and project management?

From a project management perspective, several things about business change in a cloud environment. Costing, for example, reflects service agreements rather than hardware and software purchases. Maintenance and troubleshooting becomes more difficult because it is the responsibility of the service provider. How queries are written against stored data changes because of the way that databases are handled in the cloud. Comfort in data security services from providers becomes a huge deal. Developers need proficiency in dynamic programming languages such as Python, Perl, Ruby etc.

Architectures change as Lew Tucker, Sun’s CTO of Cloud Computing cautions, “Different parts of an application might be in many places in the cloud. For example, a presentation layer might be on Facebook, storage could be on Amazon.com’s S3, and application logic could run somewhere else entirely. "

Nikita Ivanov,  CEO of GridGain Systems – Cloud Computing Software suggests that The best way to think about cloud computing is as a data center with an API. In his blog, he presented a provocative list of real-life challenges and observations about cloud computing from which I have selected a couple major ones for consideration by project managers and developers:

  1. You will spend weeks and months fine tuning your application and developing additional functionality; plan accordingly
  2. With 1000s of remote nodes, things that worked in 10s of nodes often “mysteriously” don’t work on the “cloud” scale.
  3. Debugging problems require pretty deep understanding of distributed computing; learning curve is very steep; trial and error is often the only solution
  4. Cloud(s) are implemented based on hardware virtualization – make sure your grid middleware can dynamically provision such images on demand.

Cloud computing requires a platform that can manage the dynamics of the application including troubleshooting performance issues. There are currently no great approaches to identify quickly the root cause of application performance issues in the Cloud. Existing tools and solutions are limited in the way they capture information reports Andreas Grabner in the post, “Challenges of Monitoring, Tracing and Profiling your Applications running in The Cloud”.

To cloud or not to cloud, that is the question. There is certainly potential value added to applications and organizations using the capabilities of cloud computing. However, before making the plunge into territory that will significantly change the way you do application development and manage projects, I strongly recommend educating yourself on process and procedures and get advice from experts.  There are several good places to start and Microsoft has some good resources to help you get started.

Please share your thoughts and experience with computing in the cloud.

 

 

Project Manager Tips for Successful Negotiating

What do you do when you cannot get what you need or want by simply asking (or using brute force — as appealing as that might be)?  Negotiation is one way to get most of what you want when you run into this situation.  Negotiation may involve a simple two-person dialogue (I want Joe Smith to head up testing on the new product before its release; you want Joe to stay with testing the current product; the boss says work it out between yourselves.) Your intelligent scheduling software will not assign Joe full-time to both jobs. So, negotiating an agreement is required.

Negotiation comes into play for simple decision making such as where to go for lunch or what time to should we meet to complex decisions about product pricing, developing a new approach, selecting a team leader, or putting together names for a lay-off list. As project manager, you are negotiating for your team and yourself.

Prepare for Negotiations:
Decide what you want from the negotiations and the minimum you can live with. In between what you want and can live with are the things that you have to trade in negotiations. Ask yourself what the other person wants and what they have to trade — be realistic and acknowledge the justness of their needs. If possible, breakup the total need into small bites of activity or resources. Sometimes small agreements can be achieved without a total victory.

Outside of the specific resource or activity under negotiations, consider what else you have available to “trade”. For example, think about a basketball team that needs a strong forward. The team may put up money, other players, or draft choices to negotiate the release of a player they want. Be flexible on parameters that do not matter to achieving your goal. Start times, hours, days, location, reporting chain, end time, cost, and long-term ownership are all possible areas of negotiation.

Strategies for Negotiations:
Sonshi’s “Intelligent Approaches to Conflict Resolution and Competition” provides wise advice to the beginning negotiator summarized as: 

  • Negotiation is mostly about listening.
  • Negotiation requires give and take. If you can figure out a way to give the other person something important to them while getting what you want, you have a win-win situation.
  • “Be human. Don’t try be clever. In fact, don’t display cleverness. Talk softly and be pleasant. You’re trying to have him be on your side. Share your troubles and problems if need be. You’re not trying to outsmart anyone here — you’re trying to obtain an amicable agreement with another person. When she realizes she is not going against a ruthless opponent but rather someone who’s a real person, she’ll drop her guard and work with you. Isn’t that what you want in the first place?”
  • “If time is of the essence to you, you are at a great disadvantage. Where you must obtain a resolution with the other party by a certain date, she may not be in such a rush. Because of this fact, she can walk away from the negotiation table causing you to give up something valuable just to reach an agreement. Therefore, make sure you’re not constrained by time. Even if you are, do not display it.”

In terms of negotiation strategy, Anatol Rapoport, a mathematical psychologist offered a simple and provably effective negotiation strategy called tit-for-tat. This was used to solve the famous Prisoner’s Dilemma used in game theory to optimize conditions that facilitate cooperation between two parties with conflicting goals. (For more information, see History of Tit for Tat)  According to tit-for-tat, two players have two choices: either cooperate or defect. The best strategy to a successful negotiation is to begin by cooperating (perhaps on one of those little items you identified when breaking down the bigger task). Then on your next move, you do whatever the other person did – so if they cooperate, you cooperate again. If they defect – that is refusing to make an offer – you retaliate by removing your offer or something else of value to the other person.

In studying successive evaluation of the tit-for-tat strategy, four rules emerged:

  • Never be the first to defect
  • Retaliate only after the other party has defected
  • Be prepared to forgive after carrying out just one act of retaliation
  • Adopt this strategy only if the probability of meeting the same player again exceeds 2/3

Sample dialogue – your project needs senior QA and test from a matrix organization. The manager says he can’t meet your project schedule:

(YOU)Make an offer: “The project begins May 1, but I can wait until September 1 to get Joe’s help”.
(THEM) Cooperative response: “Joe is on a project until December”
(THEM) Defecting response: “I can’t ever imagine Joe having any time available in the foreseeable future”

(YOU responding to cooperative response): “Mary Sue in QA my other project can be made available to help you from September through December.”

(YOU responding to defecting response): “Your department needs to hire another QA. my project has high management visibility and I would hate to report that we can’t make schedule because of failure to do QA.”

A couple final thoughts on successful negotiating techniques:

  • Think out of the box. There may be several ways to get what you both want.
  • Do not be afraid to invite an objective third party – one without a stake in the decision – to participate in the discussion. They may have new ideas that are not clouded by preconceived notions of “how this needs to be done” and will be less emotionally involved in the give and take.

If you really want to get better at negotiation I suggest taking a course  - here is the one that I took:
Karrass seminar on Negotiating – http://www.karrass.com/kar_eng/effectivenegotiating.htm

 

Project Management Collaboration and Communication Tools

It seems I cannot go anywhere these days without seeing people talking on cell phones, texting, taking phone pictures and sharing them – sometimes many of these at once. People want to use every free minute to communicate with someone. And, before you ask; yes, this is the pot calling the kettle black. I am wired and I stay in contact with clients, team members and family 24/7.   And it is not just being a PM that requires this connectivity.

At work, I appreciate and recommend tools like SharePoint to facilitate collaboration and communication (see Collaboration tools for virtual project teams). However, as the capabilities of these tools continue to expand, the line between our personal and work lives blurs.

Dean Halstead, Microsoft Collaboration Architect for U.S. Federal Government Sales Team presenting to the Gov 2.0 summit in 2009 offered this list of commonly used content sharing capabilities that may crossover between project life and home life:

  • Blogs with collaborative comment capabilities
  • Video and multimedia sharing
  • Podcasting
  • Social networking
  • Syndicated web feeds (RSS)
  • Mashups
  • Social bookmarks and news
  • Microblogging
  • Cloud Tagging

(Note: If you are like me, some of the words are new and I had to look them up on the internet – you should too)

Many organizations wrestle with the desire to use some of these tools to improve communication on projects while trying to control privacy, confidentiality and make the best use of time available. Privacy is often handled through firewalls or intranets that provided a barrier to web-based tools for communication. However, advances in tool capability now allow intranets to offer these communication and collaboration tools inside the organization or project.

SharePoint, for example, offers tools for video sharing through its interactive media manager and podcast kit — available as free downloads. Mashups – combining content from multiple sources – can be created from SharePoint’s Business Data Catalogue connector, XML Mashup, Visual Studio and SharePoint Designer. And, the SharePoint Community Kit (another free download) supports social bookmarking and sharing news. Not to mention instant messaging. How much real-time information is too much? (You might enjoy reading Daniel Tenner’s perspective on this from Technology, “The questionable value of the real-time web”)

There is more …
In 2009, Google announced the release of Google Wave. Initially by invitation only, the software is now available to anyone. Described by CNET as "the e-mail of the future," Google Wave blends e-mail, instant messaging, photo sharing, and potentially connections to the world of social networking. According to Google, a wave helps make communication better by integrating formatted text, photos, videos, maps, and more. Because a wave is shared within a group, members can reply anywhere in a message, edit content and add participants to the discussion at any point in the process. A playback feature lets newcomers rewind the wave to see who said what and when.

Google Wave is an attempt to "combine conversation-type communication and collaboration-type communication. As summarized by Mashable, Google Wave offers innovative features one could imagine using to improve communication and collaboration on projects including:

  • Wiki functionality: Anything written within a Google Wave can be edited by anyone else, because all conversations within the platform are shared. Thus, you can correct information, append information, or add your own commentary within a developing conversation.
  • Natural language: Google Wave can autocorrect your spelling, even going as far as knowing the difference between similar words, like “been” and “bean.” It can also auto-translate on-the-fly.
  • Drag-and-drop file sharing: No attachments; just drag your file and drop it inside Google Wave and everyone will have access.

Also take a look at all the new Instant messaging products (I think they still classify as that!).  One that I have used is Trillian Astra from Cerulean Studios.  It brings together IM (from multiple sources), Video chat, Audio chat, Social Networks (like Myspace and Facebook), Twitter, Skype and email.  It is kind of a one stop communicator.

And, even Microsoft’s communicator now lets you go beyond IM and do VOIP calls or even integrate calendar and Net meetings.

Deciding which tools and capabilities will facilitate communication and collaboration on your project
Before jumping on any new technology bandwagon, remember that new processes require training and distract staff from ongoing tasks. As project manager, you need to do a realistic cost/benefit analysis before you commit that delineates who will use the technology, how they can use it within the context of the project, and understand what – if any – communication or collaboration technologies could be lost in the transition.

Like every new technique or technology that comes along, we must decide which tools to incorporate and what processes to use to “improve” our team collaboration.  Those that never try new technology will turn around one day to find they are still typing status reports on a typewriter!

 

The Art of Verbal Communication

“I took myself down to the Tally Ho Tavern,
To buy me a bottle of beer.
I sat me down by a tender young maiden,
Who’s eyes were as dark as her hair.
And as I was searching from bottle to bottle,
For something un-foolish to say.
That silver tongued devil just slipped from the shadows,
And smilingly stole her away.
“*

  *lyrics from Silver Tongued Devil by Kris Kristofferson


Many of us wish we could be that “silver tongued devil” – someone skilled at getting what they want through the power of words–an expert in The Art of Verbal Communication. Verbal communication is an essential project management skill. Whether it is instructing team members, chatting in the break area, interviewing users, persuading clients, or presenting to management, I find these skills come into play almost every day of my working life. (And of course in my personal life!)

How you say it matters
Two people saying exactly the same thing can deliver two very different messages depending on how they express the message. Take tone, for example. A quiet tone with little variation in pitch or volume tends to be calming. If the quiet tone goes on too long though, it may become a narcotic putting the audience to sleep or encouraging them to look around for other action.

Your tone reflects your attitude and influences interpretation of your communication. Upbeat, positive tones increase agreement and comfort. It is okay to sound a little excited about a good idea or a new product. However, sarcastic, condescending, or monotone inflections are downers that discourage people and drive them away from your message.

Eye contact and smiling are powerful adjuncts to how you say something. Verbal communication, accompanied by looking at the audience or into the other person’s eyes and smiling, unconsciously moves the communication outcome in the direction of agreement.
And don’t forget that body language matters in verbal communication. Arm position, hand movements, smooth or jerky actions all integrate to create one verbal communication event. Now body language is a big subject that deserves its own post. However, for a good introduction to body language and its role in the art of verbal communication, check out “Understanding body language” from Changing Minds and “Body Language – Understanding non-verbal communication” from MindTools.

Repetition
Verbal communication beyond “social chitchat” benefits from repetition. NO – Not saying the exact same thing several times, but communicating the same message in different ways. In his book, What the Dog Saw (2009), Malcolm Gladwell talks about why some pitchmen are successful in selling ideas and products, “You have to explain to customers – not once or twice but three or four times with a different twist each time. You have to show them how it works and why it works… and how it fits into their routine.”

For project managers communicating with clients, stakeholders or potential customers, this means you follow the words of Dale Carnegie, “tell what you are going to say, tell them, then tell them that you’ve said.”

Get feedback
A unique virtue of oral verbal communication is the ability to get instant feedback from your audience. You should use the verbal and nonverbal feedback to shape or redirect your verbal communication. If people are looking directly at you, nodding their heads, and making agreeable noises, your presentation is having the desired effect. On the other hand, if the person or audience is looking away, texting on their Blackberries, or folding their arms over their chests and looking like they want to bite something, it is time to change verbal tactics. (You think?)

The most important thing you can do to improve the effectiveness of your verbal communication is to ask for feedback. This sounds real easy, but it isn’t and most people don’t do it. Ask in a way that shows you really want to know and paraphrase or restate comments or questions to make sure you are focusing on what the audience wants and needs from you.

Deal with filters
Based on previous life experiences, beliefs and values, people develop filters through which they interpret what they see and hear. Perception is reality. Project managers must keep this fact in mind when choosing words to speak and listening to words spoken. You may not understand or even need to know why your message is not being received as intended. However, it is essential that you know when there is a disconnect from what you expect – and take action to ameliorate it.

Summary
Follow the simple suggestions above:

  • Make your tone of voice upbeat and positive
  • Say the same thing in different ways,
  • Pay attention to your body language and your target audience
  • Choose words carefully and do not use words that are loaded with extra meaning
  • And, most importantly, GET FEEDBACK!

If you have other tips on communication please share your thoughts with other project managers via comments. Thanks!

Follow

Get every new post delivered to your Inbox.

Join 354 other followers