Online Project Management

Browse our posts by category or by author. Subscribe to RSS feeds by author, category, or all posts. We love comments, so let us know what you think.

Strategically Thinking About Managing Work in the Cloud

There’s a lot of talk about working in the “cloud” these days. If you’re like me, you have some personal storage in the cloud, a handful of the apps you use every day are in the cloud and your company is always looking for new ways to work in the cloud.

Earlier this month, Mark Thiele suggested, “As an IT community we are still stuck in the past relative to the strategic nature of cloud. Many of us are looking at the adoption of cloud as just another technology, and are leaving the decisions on how to adopt, own, and manage the cloud up to engineers.” Managing the cloud “…is not an engineering decision—it’s a strategic one,” says Thiele.

I agree. What’s more, managing work in the cloud just makes strategic sense to me—particularly with distributed teams. I know of a number of project managers that regularly work with teams spread throughout the country, and the world for that matter, who deal with time zones, languages and the communication issues associated with the every day. The cloud makes it possible, but they’ve all developed strategies that make it work.

The world has become a pretty small place since I started my career—the technology that allows me to interact with colleagues instantaneously from around the world continues to blow my mind.  Computers, cell phones, VOIP, and video conferencing allow me to work from almost anywhere in the world.  Although my adult children harass me about growing up when dinosaurs ruled the earth, we did get a lot of work done without cell phones, personal computers, or SKYPE

As convenient as things are now, there are some unique challenges to working in a global project environment.  Organizations regularly working with teams from around the world need to consider their strategy for dealing with cultural, language, geographic, and time differences that can sometimes make working with global teams problematic.

  • The Challenge of Different Time Zones: Collaborating with teams in South America, China, the UK, and Cincinnati can sometimes be problematic.  For example, as I write this at 7:45 am local time, it’s 11:45 pm in Tokyo, 2:45 pm in London, 12:45 pm in Rio, and 10:45 pm in Beijing.  The challenges of putting together a project team meeting with a globally diverse workforce are sometimes as basic as determining what time to hold the meeting.
  • A Possible Solution: Nobody on the project team should be asked to regularly stay up until 2:00 am just to make it more convenient for you.  Everyone on the project team should be able to share the burden of an inconvenient meeting time once in a while.  A simple solution is to try to hold team meetings when everyone is at work, which might be early in the workday where you are and later in the workday where part of the team is located—at least everyone should take turns meeting at inconvenient times.
  • The Challenge of Bringing the Team Together: Sometimes it’s important to bring the team together, which has the potential to be pretty expensive.
  • A Possible Solution: At @task, we have global project teams that work out of Europe and Asia.  Although we don’t get together often, we do get together.  Online project management tools help organizations collaborate and work together in different countries, timezones, and languages—but the need to get together doesn’t completely go away.  Personally meeting together as a team once or twice a year is important for building morale and team esprit de corps.
  • The Challenges of Different Languages: The nuances of different languages beg for miss-communication.  Even where your particular language is spoken as a second language, it’s critical that communication be clear.  We need to be cautious, particularly where the lion’s share of communication is written, where body language and facial expression are not available to aid understanding.
  • A Possible Solution: Video conferencing is a good option, but at the very least, make sure emails contain all the information necessary to communicate your ideas clearly.  I try to address all my emails with a salutation and a name to remind me that I am actually communicating with a real person.  Even amongst my co-workers, where English is our native language, we sometimes misunderstand and misinterpret an abrupt email.
  • The Challenges of Cultural Differences: If part of what defines us is our shared experiences, taking time for global team members to become better acquainted, and share experiences to create a team culture is important.  This is true even if your team only spreads across your own country.
  • A Possible Solution: Take the time for global project teams to become familiar with each others varied customs and cultures.  It might be as simple as sharing a regional dish for lunch.  In this regard, a little effort goes a long way.

Working in the cloud allows us to work globally, but it should also encourage us to think about how we use cloud-based tools strategically. Simply having the ability to collaborate on projects, tasks and issues with team members from around the world isn’t enough—we need to think about how to do it best. How do we use our cloud-based tools to maximize the contribution of everyone on the team—regardless of their location?

What do you think? Is project management in the cloud tactical or a strategic play?

0 Comments »

How Do You Leverage Social Media For Project Success?

I’m a big advocate of leveraging the social media metaphor as well as social media tools to make teams more effective and engaged. Over the last few months I’ve written a lot about how the social media metaphor is a great way to encourage collaboration among the team, but there are other ways we can leverage social media within the project management process.

A Network of Subject Matter Experts

When I first started following the project management world online I was literally blown away by how many brilliant project managers willingly shared their smarts with the rest of us via Twitter updates, blogs and even podcasts. If you have a question there’s an incredibly active community of really smart project managers on the #pmot hashtag and most recently the #pmchat hashtag to name just two.

Some of the smartest project managers I know are very active bloggers. It doesn’t matter if you want to read about Agile methods or more traditional approaches, there are guys like Derek Huether and the Agile Scout as well as more traditional project managers like Robert Kelly, Josh Nankivel and Todd Williams (and there are dozens of other like Liz Harrin, Deanne Earl, Mike Meikel…the list goes on).

Podcasts have become very popular over the last year or so with anything from the fifteen minute PMChat podcasts Robert Kelly is doing to podcasts like Raechel and I do with TalkingWork that are about an hour. Anyone wanting to learn more about how to be a better project manager has lots of opportunities to do so.

I’m also a big fan of the online project management communities like Gantthead, ITToolbox, Projects@Work and PMHut. These are great places to keep up to date on news, articles and current project management thought.

Capturing and Leveraging Best Practice

Wikis have a lot of potential for capturing, cataloging and sharing best practices. There are also tools like Dropbox, Evernote and other cloud based filing systems that have great potential for sharing lessons learned—many of which are free or very little cost. What are some of the ways you are using these tools to facilitate effective project learning?

Online Survey Tools, Facebook and Forums

I’ve successfully used Survey Monkey and Facebook to get feedback from colleagues, but Forums are another very powerful way to participate in the project management conversation as well as learn and meet new people. What are the forums you turn to when you need answers?

We’ve only scratched the surface—how are you leveraging social media?

0 Comments »

Doctor’s On Demand

Traveling as much as I do often doesn’t leave much time to prioritise essential chores and appointments. I recently sought some medical help for a troubled knee injury and visited the local doctor’s surgery. It was Monday and I asked if they had an appointment the same week. The receptionist looked at me, laughed, and said "Come on Sir, be realistic". The earliest they could offer me was later the next week. Because of work travel commitments I left the surgery 5 minues later, some-what disgruntled, with an appointment for 6 weeks hence! All I want to do was see a doctor.

It was at this point I came to realise that I’ve come to expect far too many things ‘on demand’ these days. Whether it be my favorite TV programme from last night, a 24 hour supermarket for my soda fix, free WiFi somewhere other than McDonalds, or simply some medical attention. For some things, however, we should expect no less than instantaneous.

In business we seem to have become acustomed to waiting too. Two weeks for a project report, a week for the next status meeting, or hours for someone to return a call. Why should we have to wait when the information we so often capture is right at our finger tips?

I visit many companies looking to transform the way their project management practices work simply because the pain of waiting for project status information is no longer acceptable. Often, in order to produce the necessary project reporting information, the reporting cycle starts up to two weeks before the actual delivery date. By the time the report data is gathered, collated, formatted, and distributed its already started to become stale. Its no longer current. The amount of effort required to pull all of this information together, especially for larger project management practices, can sometimes be the equivalent of several full time resources. The processes to achieve this are manual and labour intensivie. There’s nothing instantaneous about it.

But with the coming forth of on-demand project management software all of this is changing.

The term ‘On-Demand’ refers more specifically to the sales and delivery model by which software customers are purchasing products. Marc Benioff, founder and CEO of Salesforce.com, changed the way we thought about software when in 1999 he started, and what has since become, the first $1billion On-Demand Software Company. No longer do we think of project management software as a huge piece of software that requires teams of technically trained developers, months to install and set up on numerous servers and systems, behind firewalls that can only be accessed from the office. With On-Demand software we not only receive the software as a service but we can get to the information when we want, from wherever we want, and as quickly as we want.

The power of an online project management tool comes because it can be accessed from anywhere in the world, not only does the information reporting become on-demand, but the information input also becomes on-demand. As information becomes more visbile and accessible, more people see the benefit of sharing information. As this happens reporting information becomes more accurate, reliable and current. Functionality of on-demand project management software is such that most reports can be created at the click of a button, and some don’t even require you to be that involved!

Now that we can get a project health checks on-demand what a shame I can’t get an actual health check as fast.

0 Comments »

Two Ways to Improve Project Communication

Although Alexander Graham Bell considered his most famous invention, the telephone, to be an intrusion on his real work as a scientist, I don’t think you’d find very many people today who would be willing to give up their cell phone.

We live in a world of instantaneous communication.  Cell phones, the Internet, text messaging, social media—all keep us connected and communicating, right?

There are times when I feel like technology has made communicating more accessible, but does it really make communication easier?  For project communication to be effective, we need to be thoughtful in how we utilize technology.  It’s important to remember that we may be writing an email or updating a status report, but the person on the other end of that email or status report is a person.  It’s probably just the nature of technology, but sometimes I think it’s a good idea to remember what makes effective communication, effective.

Here are a couple of techniques that aren’t original with me, but might help you improve the quality of your project communication:

The Sundown Rule: 

Unless you work at Walmart, you’ve probably never heard of it.  According to their corporate website: "It’s really just a twist on ‘why put off until tomorrow what you can do today?’  Observing the Sundown Rule is very simple.  Whether it’s a request from a store across the country or a call from an associate down the hall, we do our very best to give our customers, and each other, same-day service."

I work with a colleague who did a college internship in Bentonville, AK at Walmart’s corporate headquarters.  He said the Sundown Rule is the real deal.  It didn’t matter who he reached out to during the day, he would typically get a response before the sun set.

Would you treat email or other project correspondence among your project team members a little differently if you knew the expectation was a response before the end of the day?

No Email Fridays:

I heard about U.S. Cellular’s No Email Friday rule a couple of years ago.  COO Jay Ellison thought it would make life a little easier and lighten the load for employees, but instead it initially caused a fire-storm.  In an article written by Sue Shellenbarger of The Wall Street Journal, she quotes  Kathy Volpi, a marketing director who said, "I thought, ‘He just doesn’t understand how much work we have to get done, and how much easier’ it is when using email."

With the exception of responding to urgent matters, normal email is considered taboo.  The initiative was designed to encourage more face-to-face communication with customers and co-workers, raise productivity, or provide a break from the ever-filling email inbox. 

It looks like it’s been a success.

Even Ms. Volpi, now U.S. Cellular’s director of product management and marketing, has become a fan.  According to Shellenbarger, "Gradually, she realized that reading and responding to all the email she was sending was probably a burden to co-workers.  Now, she makes a point of visiting co-workers on Fridays.  Business, she says, isn’t only about emailing ‘cold reports’ and being efficient, she says, ‘It’s about human beings and interaction.’"

Would either of these techniques work within your organization?  I don’t know.  There are so many project collaboration and communication features incorporated into many traditional or online project management solutions, that completely eliminating that type of communication might be problematic.  However, regardless of the project management software or work management tools you use, everyone can step out of their cubes for a few minutes and have a real conversation occasionally.

I have to admit that sometimes it’s easier for me to ping a colleague 10 feet away with an Instant Message that it is to get out of my chair and actually go talk to him or her.  I wonder how many of us have forgotten how to really talk to each other as we IM, text, and email our way through life?  Give these two approaches a try and see if they will work for you and your project team.  You might be surprised at how effective your daily communication becomes when you incorporate a little face-to-face time once in a while.

1 Comment »

“That Which Doesn’t Kill Us…”

It was the 19th-century German philosopher Friedrich Nietzsche who said, "That which doesn’t kill us makes a stronger."

I look at project challenges this way. Over the years I have come to appreciate that regardless of the project management methodology, the PPM software, or the training of the project manager, there are some pretty common challenges that need to be addressed by every project leader. The nature of the project doesn’t even really matter; if you neglect the following, the odds are against your success:

  1. Unrealistic Deadlines: The success of some projects might depend on a hard deadline, but most projects don’t. Creative and flexible planning can remove the stresses of unrealistic deadlines.
  2. Scope Changes: Although most of us would agree that you can’t always stop change, you can make stakeholders aware of what scope changes cost. Changes in schedule, cost, and even the quality of the product can add up fast.
  3. Failing to Manage Risk: Ignoring risk doesn’t make it go away. Acknowledging risk and addressing it early will at least minimize expensive issues later. Risk and efforts to mitigate risk should be identified before the project has even begun.
  4. Poor Team Communication and Collaboration: With all the technology available today, there is almost no excuse for poor project communication. The right PPM software makes collaboration easier—and online project management software makes it possible for teams spread throughout the world to effectively collaborate.
  5. Stakeholders Who Aren’t Engaged: Keeping stakeholders informed of project status is only a start. The real challenge involves helping stakeholders see the value of becoming real project advocates.
  6. Undefined Project Goals and Objectives: To maximize the value of every project, each project should be tied to some kind of strategic objective. Once identified, it’s critical that everyone understand the strategic value of any particular project in process. Most people want to be part of something bigger than themselves. It’s always been a puzzle to me why so many organizations neglect to share their vision with the workforce.

Are there any of these common challenges you face? What do you do to overcome them?

0 Comments »

PPM Performance Testing For PMs

Food for Thought

It was over 20 years ago, around 8 pm. Three Business Analysts and two fellow coders crowded around my desk with the sinking realization that it was going to take an all-nighter to pull off our deliverable. Just then, the senior PM poked her head in with a concerned look and a "What can I do to help?" We shot a round of blank looks at each other, but before we could even formulate a polite reply, she nodded quickly, and said: "Right: I’ll go get some food."

Surely, figuring out what the team needs to keep them going efficiently is one of the most important skills a PM can offer.

But what happens when your team’s Online Project Management itself isn’t keeping up? The prospect of assessing the performance of sophisticated Web-based PPM Software is pretty daunting, even if you are a technical PM.

This spreadsheet can help you performance test your On-Demand Project Management environment and keep your team going:



Peek Performance

The spreadsheet has several practical features: 

  • a cell (B2) of the maximum allowable time for any test (e.g. 120 seconds)
  • a cell (B5) to define the Date and Reason for the tests
  • a column (C) to define and describe three tests
  • a column (D) to define two physical locations for each tests (e.g. Office, Offsite)
  • a column (E) to define four different types of connections (e.g. LAN, Proxy, etc.)
  • a grid (F3:K16) to record the results of the tests across two environments and three browsers
  • three graphs — one per test — with fixed Y-axis scales that illustrate the test results
  • two lines across all graphs dividing acceptable, borderline, and unacceptable performance

You too can take your own Performance Testing. Download the spreadsheet, update the ranges above to suit your tests, and then each time you want to test: 

  • duplicate the tab and date it
  • update the Date and Reason (B5)
  • clear the results grid (F3:K16)
  • run the tests and enter the new results (F3:K16)
  • use the tabs to "flip" between the tests, effectively animating the graphs

The performance tracking spreadsheet is simple to use and easy to understand. If certain aspects of your Project Management Software are not running as quickly as your team needs them to, you — as PM — can take the initiative to quantify what’s really happening, initiate a solution with your vendor, and keep your team going efficiently.

But food’s always appreciated, too.

0 Comments »

Sufferin’ SaaS-afras! Where can I Test?


ExSaaSperation

Online Project Management is a great fit for Software as a Service (SaaS). Teams can perform their project based work in different locations and timezones, but still collaborate in a loosely coupled way. And as vendors improve the underlying PPM Software, everyone instantly benefits when the production website is upgraded. What more could you want?

Well, when a major new release that changes the user interface is coming down the pipe…how about a place to test?

DiSaaSter

About a year ago, AtTask wisely decided to give its @task ondemand customers a beta site so they could test new features against known data. The weekly beta refresh worked so well that some customers also use it for training purposes. Views, reports and other objects copy across automatically, and because the data is in a separate environment, it’s a safe place for new users to get some practise.

However, the next version of @task (R14) is a major look-and-feel release.  Suddenly, those customers have few options for training new users:

  • There is no Test environment as such, where the current release points to a copy of their data
  • Beta is different enough that it could cause confusion
  • Even if they’d agree to pay for a data restore, they can’t copy their data back into the ondemand environment, since the primary keys would collide
  • They could create what’s called a Testdrive with sample canned data, but then none of their dashboards, their reports, their data — their business, really –  would be included

But fortunately, there’s an easy solution.

SaaSisfaction

The trick is to build a Test environment within Production. Seriously!

  • Create a special Group called Training Data, and a special Access Level called Trainee, with rights to see Home Group data only
  • Set all new users’ Home Group to Training Data, and their Access Level to Trainee
  • Create several Projects, Tasks, and Issues that belong to the Training Data Group; or better yet, keep several side-by-side versions; or best of all, prepare them in Kickstarts, so you can delete and reload them each time a fresh class of new users shows up
  • Have the new users log in: all they will see is the Training Data
  • As new views, reports, dashboards and so on are added to the Production environment, they can be instantly made available to the Trainees — no migration required
  • Because it’s really Production, the Test environment will get the same care and attention as real data does as far as uptime, performance, support and backups (whereas beta can be down unexpectedly or intentionally for days…true story…)
  • When training is complete, simply upgrade their Access Level and change their Home Group to graduate them into Production

It sounds a bit daunting at first, but by leveraging @task’s security model, you can provide a safe, refreshable Test environment within Production that stays current with your business as it evolves. Who knows? If enough of us adopt the approach, it could become the defacto standard.

If you decide to try it, please let me know how it goes.

0 Comments »

Adapt and Improvise: Agile, Waterfall, and the PMBOK

A recent article published by TechRepublic and written by Rick Freedman, Adaptive Project Framework: A new level of agile development, caught my eye the other day.  As I was reading, I couldn’t help but think of Clint Eastwood as Gunnery Sergeant Tom Highway in the movie Heartbreak Ridge

Without spoiling it for anyone interested in watching an old Clint Eastwood movie (1986), Highway is a hard-nose gunnery sergeant who gets stuck training a bunch of "indulged" Marines who wind up in Granada.  Although the movie is predictable (and the language is what you’d expect in a Marine barracks), Gunny Sergeant Highway says something that I think is applicable to Freedman’s article.  When asked why his squad advanced on an enemy position despite being outnumbered and without support, he says, "We’re Marines, sir.  We’re paid to adapt, to improvise."

According to Freedman, when teaching Agile Project Management classes, the first thing he does is write two words on the board.  "The first word is adaptive," he says.  "I emphasize with my students that adapting the project approach to the specific effort at hand is a fundamental concept that underlies all agile methods."

I couldn’t agree more.

"The second word is hybrid," he continues.  "I assure my students that, while some agile proponents are almost religious in their insistence that Project Management Institute (PMI)-style, traditional methodologies have no place in an agile environment, my philosophy is that almost every project, every client, and every organization will require us to incorporate some traditional methods into our agile approach.  It’s my experience that very few organizations desire, or are prepared for, a complete migration from traditional tools, such as project plans and Gantt charts, to a total agile approach founded around the idea that, if you’re running a traditional product development life-cycle and applying PMI standards, everything you know is wrong."

I have to agree with Freedman.  Sometimes I think we forget that the entire project management process is about getting work done—not the particular work management methodologies that are used.  I like his suggestion that we should consider "hybrid" approaches to the process.  There are some things that agile methodologies do very well, but to say that everything in the PMBOK is a bunch of hogwash would be like suggesting that there is no need for a hammer because we now have a nail-gun (or vice-verse).  I don’t know a carpenter who would make either of those outlandish claims.

If getting work done, or rather getting the right work done, is the ultimate aim of the project management process, using whatever method makes the most sense for the type of work undertaken just makes sense to me.  After all, it’s people that get work done anyway, the particular approach used is to make it possible for people to be successful, isn’t it?

With that said, I think our job as project managers is to adapt and improvise depending upon the particular work challenges we’re faced with.  Some projects might require sophisticated online project management software while another might require a simple task list—or PPM software that incorporates traditional waterfall or agile methodologies.

If you haven’t read Freedman’s article I suggest you give it a look.  He also introduces a new book written by Robert Wysocki that looks interesting, Adaptive Project Framework.  It’s a book I’ve put on my summer reading list.

How do you incorporate different project management methodologies into your work management strategy?

2 Comments »

Improving Project Communication: Two Rules You’ve Probably Never Heard Of

Although Alexander Graham Bell considered his most famous invention, the telephone, to be an intrusion on his real work as a scientist, I don’t think you’d find very many people today who would be willing to give up their cell phone.

We live in a world of instantaneous communication.  Cell phones, the Internet, text messaging, social media—all keep us connected and communicating, right?

There are times when I feel like technology has made communicating more accessible, but does it really make communication easier.  For project communication to be effective, we need to be thoughtful in how we utilize the technology.  It’s important to remember that we may be writing an email or updating a status report, but the person on the other end of that email or status report is a person.  It’s probably just the nature of technology, but sometimes I think it’s a good idea to remember what makes effective communication, effective.

Here are a couple of techniques that aren’t original with me, but might help you improve the quality of your project communication:

The Sundown Rule: 

Unless you work at Walmart, you’ve probably never heard of it.  According to their corporate website: "It’s really just a twist on ‘why put off until tomorrow what you can do today?’  Observing the Sundown Rule is very simple.  Whether it’s a request from a store across the country or a call from an associate down the hall, we do our very best to give our customers, and each other, same-day service."

I work with a colleague who did a college internship in Bentonville, AK at Walmart’s corporate headquarters.  He said the Sundown Rule is the real deal.  It didn’t matter who he reached out to during the day, he would typically get a response before the sun set.

Would you treat email or other project correspondence among your project team members a little differently if you knew the expectation was a response before the end of the day?

No Email Fridays:

I heard about U.S. Cellular’s No Email Friday rule a couple of years ago.  COO Jay Ellison thought it would make life a little easier and lighten the load for employees, but instead it initially caused a fire-storm.  In an article written by Sue Shellenbarger of The Wall Street Journal, she quotes  Kathy Volpi, a marketing director who said, "I thought, ‘He just doesn’t understand how much work we have to get done, and how much easier’ it is when using email."

With the exception of responding to urgent matters, normal email is considered taboo.  The initiative was designed to encourage more face-to-face communication with customers and co-workers, raise productivity, or provide a break from the ever-filling email inbox. 

It looks like it’s been a success.

Even Ms. Volpi, now U.S. Cellular’s director of product management and marketing, has become a fan.  According to Shellenbarger, "Gradually, she realized that reading and responding to all the email she was sending was probably a burden to co-workers.  Now, she makes a point of visiting co-workers on Fridays.  Business, she says, isn’t only about emailing ‘cold reports’ and being efficient, she says, ‘It’s about human beings and interaction.’"

Would either of these techniques work within your organization?  I don’t’ know.  There are so many project collaboration and communication features incorporated into many traditional or online project management solutions that completely eliminating that type of communication might be problematic.  However, regardless of the project management software or work management tools you use, everyone can step out of their cubes for a few minutes and have a real conversation occasionally.

I have to admit that sometimes it’s easier for me to ping a colleague 10 feet away with an Instant Message that it is to get out of my chair and actually go talk to him or her.  I wonder how many of us have forgotten how to really talk to each other as we IM, text, and email our way through life?  Give these two approaches a try and see if they will work for you and your project team.  You might be surprised at how effective your daily communication becomes when you incorporate a little face-to-face time once in a while.

2 Comments »

Global Project Teams: Unique Challenges for Project-Based Work

I am still amazed at how small the world has become since I started my career—the technology that allows me to interact with colleagues instantaneously from around the world continues to blow my mind.  Computers, cell phones, VOIP, and video conferencing allow me to work from almost anywhere in the world.  Although my adult children harass me about growing up when dinosaurs ruled the earth, we did get a lot of work done without cell phones, personal computers, or SKYPE.

As convenient as things are now, there are some unique challenges to working in a global project environment.  Organizations regularly working with teams from around the world need to consider the cultural, language, geographic, and time differences that can sometimes make working with global teams problematic.

  • The Challenge of Different Time Zones: Collaborating with teams in South America, China, the UK, and Cincinnati can sometimes be problematic.  For example, as I write this at 7:45 am local time, it’s 11:45 pm in Tokyo, 2:45 pm in London, 12:45 pm in Rio, and 10:45 pm in Beijing.  The challenges of putting together a project team meeting with a globally diverse workforce are sometimes as basic as determining what time to hold the meeting.
  • A Possible Solution: Nobody on the project team should be asked to regularly stay up until 2:00 am just to make it more convenient for you.  Everyone on the project team should be able to share the burden of an inconvenient meeting time once in a while.  A simple solution is to try to hold team meetings when everyone is at work, which might be early in the workday where you are and later in the workday where part of the team is located—at least everyone should take turns meeting at inconvenient times.
  • The Challenge of Bringing the Team Together: Sometimes it’s important to bring the team together, which has the potential to be pretty expensive.
  • A Possible Solution: At @task, we have global project teams that work out of Europe and Asia.  Although we don’t get together often, we do get together.  Online project management tools help organizations collaborate and work together in different countries, timezones, and languages—but the need to get together doesn’t completely go away.  Personally meeting together as a team once or twice a year is important for building morale and team esprit de corps.
  • The Challenges of Different Languages: The nuances of different languages beg for miss-communication.  Even where your particular language is spoken as a second language, it’s critical that communication be clear.  We need to be cautious, particularly where the lion’s share of communication is written, where body language and facial expression are not available to aid understanding.
  • A Possible Solution: Video conferencing is a good option, but at the very least, make sure emails contain all the information necessary to communicate your ideas clearly.  I try to address all my emails with a salutation and a name to remind me that I am actually communicating with a real person.  Even amongst my co-workers, where English is our native language, we sometimes misunderstand and misinterpret an abrupt email.
  • The Challenges of Cultural Differences: If part of what defines us is our shared experiences, taking time for global team members to become better acquainted, and share experiences to create a team culture is important.  This is true even if your team only spreads across your own country.
  • A Possible Solution: Take the time for global project teams to become familiar with each others varied customs and cultures.  It might be as simple as sharing a regional dish for lunch.  In this regard, a little effort goes a long way.

Managing project-based work with global project teams might be a little more complicated, but keeping expectations realistic among team members and stakeholders can lead to success.

If you work with global project teams, what are some of the things you are doing to facilitate collaboration and successful project management best practices?

0 Comments »

© 2011 AtTask, Inc. All rights reserved.