Project Based Work

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.

3 Keys to Working With Virtual Teams

“Go West, young man,” wrote Horace Greeley.

I live in the west.  Smack dab in the middle of the Rocky Mountains.  I don’t tote around a six-shooter, but I do drive a Jeep, like to go camping, often wave a fly in the air trying to catch fish and otherwise enjoy playing in the mountains or the high deserts of Southern Utah.

After you escape the bigger cities and get off the Interstate, there’s a lot of wide-open country—towns are about thirty miles apart.  It’s the distance a buggy or a horse and rider could travel in a day (and the distance I can cover in my Jeep in about 30 minutes).  My world is a little smaller than the early settlers in Utah.

However, organizations doing project based work have a world that has become even smaller.  The vast array of technological tools available today are getting better and better at making virtual project teams effective, allowing people to be accessible without being in the same building, the same country, or even the same continent.

Some of the benefits of building virtual teams include:

  • Organizations can hire the best people for the job regardless of geographic proximity
  • The overhead expenses related to brick-and-mortar office space can be reduced
  • Global project teams make it possible for work to be virtually done around-the-clock

The benefits of working with virtual teams can be pretty substantial, but there are some considerations that need to be taken into account before jumping in with both feet.  If you’re considering working with virtual teams, let me suggest the following regarding people, process, and technology:

People:

  • Trust yourself and your employees
  • Clearly communicate roles, responsibilities, and expectations
  • As a team, understand how productivity will be measured

Process:

  • Build a communication plan that takes into account the diverse geographical relationship of the team
  • Define an electronic records archiving policy
  • Establish an electronic communications standard

Technology:

  • Use collaborative workspaces to manage project content
  • Deploy and use an online “chat-like” capability
  • Use Internet-based meetings with both voice and video

Project management solutions have come a long way in the last few years, making it possible for organizations to manage projects and teams from anywhere with an Internet connection.  When looking for a technology solution, it’s important to consider a few things like foreign language capability, platform independence, collaboration and communication capabilities, as well as scalability of the network and online access.  The right solution will help address many of the people and process requirements of working with a virtual team.

Do you have experience working virtually with a project team?  Please share what you’re doing to promote efficiency and effectiveness with a global team.

0 Comments »

As Soon As Impossible

Faster than ASAP?As Soon As Impossible Gantt

Enterprise Project Management Software is helping teams accomplish their Project Based Work more efficiently than ever. Most Projects are designed to be done As Soon As Possible (ASAP). The PPM Software that teams use may even have email alerts to expedite Tasks that can start early.

But a colleague recenty posed an interesting challege: "Is there a way to easily reset the start date of successor tasks when a task completes early, essentially setting planned dates to the projected dates? I thought this would be down by looking at recalculate timeline, but this does not seem to do it."

The Handoff Date

Imagine a Project with Task A, Task B1, and Task B2 (successor of B1)

ASAI1

The @task "Handoff Date" is a Task level attribute that notes the earliest date that Task could be started. When a Task (A or B1) has no predecessors, its Handoff Date is equal to its Projected Start Date. When a Task (B2) has predecessors (B1), its Handoff Date remains null while its Predecessors are < 100% complete.

ASAI2

Once all of a Task’s predecessors (B1) are complete, @task populates Handoff Date of the successor Task (B2) with the Actual Completion Date of the predecessor (B1).

ASAI3

At this point, the @task Event Handler would kick in and send emails, if configured to do so; however, most of our clients do not use the email Event Handlers (gets too spammy).

Do The Impossible

I fall in the "Revise Planned Dates as I get Smarter" camp myself, so — heresy or not — if you are also interested in synchronizing the successor Plan Dates, I have a solution. Change the successor Task Constraints to FIXT, and the Planned Start Date to the predecessor Handoff Date. The effect is that AtTask stretches the successor earlier in time, visually highlighting the opportunity to compress the timeline.

ASAI4

If you like this approach, you could also create a Task report with a filter that restricts to Tasks where Actual Start Date is null (not started), Handoff Date is not null (could start), and Handoff Date is earlier than Planned Start Date (could start earlier than Planned). Run the report daily, and do the impossible, as above. Our clients liked it so much that we even used the AtTask API’s to automate it for them.

0 Comments »

Making The Best Use Of Consulting �� Part 2

Continuing on from my first blog post on Making The Best Use of Consulting, I would like to conclude with the next 5 suggestions I have for using consultancy time when implementing PPM software.

Dilbert6. Have a clear understanding of what you do
Understanding what you do goes so much further than knowing what you want (discussed in my last post). When I say what ‘you’ do, I don’t mean YOU, I mean your organization. In order to understand this you have to have done your homework (read: requirements gathering) and to have worked with all the key stakeholders and users of the PPM software to understand what their individual, team, and process requirements are. The Consultant will help with this, but if you can’t articulate the requirements, the project will take much longer.

7. Dedicate the right resources and their time
There are two very important points here. First, the right resources. The right System Administrator will have a good mix of technical knowledge and business knowledge. A user champion or key user likewise. In addition to these you may well need to have a Project Manager to manage the implementation. Sounds funny, but it is a project after all. Second, time. The System Admin and Project Manager roles will need to spend significant time with the Consultant, most notably the System Admin, to really understand what it is that’s being done. This doesn’t end when the Consultant leaves either. The System Admin will then become the owner of the tool, and will need to know the in’s and out’s of the configuration, and the Project Managers job typically won’t finish until all user groups have been trained and are ready to use it.
Dilbert
8. Make all resources available for training
If you want the implementation to progress smoothly, I suggest you give everyone plenty of notice as to when they will be required for training with the new PPM software. The number one cause of delay for an implementation project, in my opinion, would come from not having the right people trained ready to use the tool when it’s set for rollout. If you’ve paid someone to come in and train your Pilot team then having the users prepared and briefed on their responsibilities will be important.

9. Prepare information and data
Once you have your newly configured PPM software ready to go, you need something to put in it. Don’t underestimate how long it can take to prepare the information and data ready to populate the system. As soon as you make contact with your Consultant ask them “What information would you like me to gather together?” because you can be doing this whilst all of the early requirements analysis and configuration is going on. Often information on project based work is spread across numerous locations; document repositories, e-mails, share folders, in peoples heads! and it can be found in various formats; project plans, spreadsheets, paper.

Dilbert10. Have a plan
Just like any other project, implementing Project Management tools will require a project plan. A consultant will certainly help to construct that plan, providing best practice and experience, playing an important role in defining the timeline, but inevitably there will be more work to do than just the time you purchased the Consultant for. Make sure you have planned what will be done when the Consultant leaves.  It’s your project. The first four weeks of the implementation are like open heart surgery, the next four months are like intensive care!

My 10 suggestions are by no means an exhaustive list of the only things you have to do to make the best use of a Consultant’s time, but if you take on board each of the points discussed and plan accordingly, you stand a much greater chance of seeing immediate value from your engagement.

0 Comments »

What makes a successful implementation?

NY Skyline from airplaneFrom the airplane window…
I was just sitting here looking out the airplane window and thinking about how great the week went.  It may seem silly, but despite all the chatter and noise, these are some of my most reflective times.  So what has my attention today you ask?

I am on the way home from what I personally and professionally consider a very good week.  So it has me thinking – what made this a successful implementation?

Well it wasn’t…
Project management implementations (processes and tools) can be tricky.  There is opportunity to fail in many ways; due to methodology, processes, support/buy-in, the list is endless.  So let’s rule out a few things that might come to mind about a successful implementation.  

It wasn’t the business they are in.
 
I have worked with all kinds of industries and I have seen good and bad in every arena.
It wasn’t how well adopted their project management methodology is.
No, they still have much work to do to get buy-in and educate their users and their business.
It wasn’t the people.
Don’t get me wrong – great people make for a great week and that helps for a personally great implementation, but not professionally.

What makes a successful implementation…
Success, to the place I am just leaving, may not be realized for many months or even longer.  The implementation we did is only a "slice of life" and it is just the start of their journey.  (More about the Slice of Life in a future blog)
But what makes a great partner and PPM software tool is the ability to grow, mature, and realize your potential on that journey.  To me, the same things that made this a great initial implementation will serve them well while they are on their way.  There are many things, but here are the ones on my mind today.

Determination:  Ever watch the story of Rudy?  I recommend it if you haven’t.  Rudy had desire to accomplish something and nothing was going to hold him back.  It took him years but he held on to the goal.  Well this customer has that determination.  The implementation team wants to provide a value to their business, to see the implementation go well, and to mature as an organization and they realize it doesn’t end after processes or tools are in place.  

Prepared:  You can want to do something all day but unless you take steps to accomplish the goal, it won’t be realized.  This customer has done many things to realize their goals and prepare the path to success.  They have incorporated a PMO into their business, established processes, brought in a great project management tool, and educated themselves to bring it together.  While they would be the first to tell you they have only just started, I can tell you that their preparation has them going in the right direction.

Communications:  Project management, methodology, and project based work doesn’t happen in the PMO office or even in a tool.  The ability to communicate with each other is critical.  The PMO has to understand the departments, end users, and the executives; but the reverse is also true.  The more two-way communications there is the better.  It opens the path to decisions.

Decision:  To me, this is the success criteria this is most often missed.  If you can’t decide which direction to turn it means you are either on the same path you have been on or maybe stopped all together.  I am even okay with turning the wrong direction – at least you will have ruled out one of the options and you now know to go another direction.  This customer had tough decisions to make but they pulled together, discussed, and made those decisions.  

I realized as I sat looking out the airplane window that what made this a successful implementation was not that the week is over, the tool is in place, or that I did a good job.  What made this successful and gratifying is that I can look at this organization and know that they are doing all the things they need to do to realize long-term success.  To compare them to Rudy – they have moved out (from home), started Jr. College, and helping the grounds crew at ND Stadium.  

(you really should see Rudy)

0 Comments »

The Power Sweep and Strategic Execution

In my dad’s mind there was only one football team: the Green Bay Packers, one quarterback: Bart Starr and one coach: Vince Lombardi. 

There was nothing fancy about the way Lombardi’s Packers played football.  They relied on a play called the Power Sweep to "power" their way to five NFL championships during the nine years Lombardi was head coach.  In the Power Sweep (which was later called the Lombardi Sweep) both guards pulled to the outside and blocked down-field while the halfback would "run to daylight"—or in other words, to wherever the opposing team wasn’t.  Let’s just say it wasn’t glamorous, it wasn’t glitzy, but it worked.  It helped the Packers dominate the NFL from 1959-1967.

Executing the play well required everyone on the field to work together for the same strategic objective.  "It’s my number one play because it requires all eleven men to play as one to make it succeed," said Lombardi, "and that’s what ‘team’ means."

Successful work management requires the same kind of teamwork and focus on strategy.  A strategic approach that not only addresses how project based work is done, but also which projects get done is the project management Power Sweep.  In other words, it’s about doing the right projects, not just doing projects right.

Lombardi focused on a few very effective plays, like the Sweep, to lead his team.  Answering these four simple questions for every project—and ensuring that every member of the team, from stakeholder to individual contributor, understands how their efforts contribute to achieving strategic execution—puts you well on your way to creating your own Power Sweep:

  1. What are the high-level objectives of the project?
  2. What are the estimated costs—and the anticipated rewards?
  3. Does it align with the mission, vision, and values of the organization?
  4. What are the risks associated with pursuing the project?

The Packers were consistent winners because there was no question in anyone’s mind what the objectives were.  "Winning isn’t everything, it’s the only thing," said Lombardi.  Taking a strategic approach to working on the right projects will put you in the end zone. 

0 Comments »

How’s My Portfolio?

TSN Turning PointMyPie

Our local sportscaster uses the phrase "TSN Turning Point" to highlight the pivotal play that enabled the win. In my Project Based Work, I use it to refer to that pivotal event when someone I’ve been coaching thinks of their own solution in a way I wouldn’t have. I always like to make a big deal of it, both to encourage them for taking ownership, and to celebrate their progress.

Chris Connoly, one of my @task clients, sent me just such a TSN Turning Point, and has given me permission to share it here.

My My My

@task has many "My" features built in to help users with Work Managment, such as My Tasks, My Reports, and My Issues. However, where Chris works, the emphasis is on the PORTFOLIO portion of the Project Portfolio Management Software, which doesn’t really mesh with the "My" concept. Here’s his story, and his solution:

We have all of our projects grouped into Programs and then Portfolios, and we have Program Managers and Portfolio Managers.  It’s very easy to create project reports based on the Portfolio Manager or Program Manager since they are only one level up.  However, it seems pretty much impossible to pull out task information based on those managers.

Since most of the information that we want to report on is generated in task reports, not being able to have a "My Program" or "My Portfolio" on task reports is actually a huge problem. And it annoys me that I can see who the Managers are in the view, and group by them, but not include them in a filter.

[One option would be to] create a filter that uses project IDs with an "IN", and then just include all the project IDs that you want. Not exactly useful for a large number of projects, and still doesn’t take care of the "My" part.

So what I ended up doing was creating calculated custom data fields at the project level (in my ever expanding "For System Use Only" section) for "Program Manager ID" and "Portfolio Manager ID", and using "Program.Owner.ID" and "Portfolio.Owner.ID" as the formulae.

I can now just use DE:project:Progam Owner ID=$$USER.ID for my filter, and I have the My Program filter, [without] even having to use text mode.

An Elegant Solution

In short, Chris was able to use @task’s Custom Parameters feature to point "up" to the data that he wanted, effectively extending the data model to suit his needs. I’ve always admired AtTask’s stance that (I’ll paraphrase) "We can’t think of everything, so we’ve included Custom Data so you can tailor @task to what you need". That’s a collabrative invitation that works.

 

0 Comments »

3 Keys to Redefining Work Management Success

Completing projects on time and on budget has proven to be a pretty valid measure of IT project success—but should it be the primary measure?  I believe that pushing a project to completion on time is not the only objective—ultimately the project also needs to deliver business value.  Along with the worthy objectives of finishing projects on time and within budget constraints, here are some other objectives that should be considered:

  1. It should be about doing the right projects, not just doing them right.  Delivering business value and satisfying customers is becoming more important than ever—and it starts with the evaluation of which potential projects will meet those needs and provide that value in the first place.  Hopefully this has always been important, but organizations are realizing that they have to do more than give lip service to meeting customer expectations while meeting organizational goals.  It must become a primary measurement of how we determine the success or failure of any IT project.
  2. Project teams need to completely understand and address the business needs of every project.  Although everyone would agree that "quality" is very subjective, if everyone on the team doesn’t have a thorough understanding of the cost of defects and rework, it doesn’t matter what work management tool you use, it won’t help.  Edward Deming used to talk about how organizations must build quality into the product, it can’t be inspected in.  Quality assurance needs to be a part of every process from start to finish.  Smart organizations are looking at defects and their root causes through the project life-cycle to develop methodologies that improve the quality of their final deliverables.
  3. The final product needs to be stable, compatible, and easily maintainable.  It’s just too expensive for organizations to maintain software that’s incompatible with current systems or unreliable.  Because staff and maintenance budgets are at a premium, software that isn’t will be abandoned for something that is.

The way organizations measure the success of project based work is changing.  Managers who leverage project management tools to meet these new objectives are able to better address business needs and ultimately increase their value within their organizations.

How does your organization measure success?

0 Comments »

Who really needs Project Management?

As I write this on the day of my second anniversary as a Consultant with AtTask I cast my mind back over the last 2 years of travels to all the customers I’ve been onsite to work with. In that time I’ve visited 27 companies, across 11 countries and 3 continents.

I reflect on who I’ve visited and what I’ve done to assist each company. As I thought about it more (and did a quick count) I realised that 60% of the customers I worked with ended up using project management software only in their IT departments. A further 30% used it to specifically run a Project Management Office not part of an IT department, or in another company department altogether. Only 10% used project management software throughout the entire company, in all departments, which led me to think… ‘Who really needs Project Management?’

The simple, and obvious answer, is everyone!

So why is it that 90% of the time its confined to just the IT department or Project Management group? I’ve heard many reasons, none of which I agree to be limiting factors for not going company-wide… "IT guys are the only ones that will pick it up"… "nobody else really does project management in the company except IT or the PMO"… "the IT department are the only ones looking for better ways of working"… "I only interact with people within my own department"… add you own to the list.

Of the companies I’ve been to, including our own, who use an enterprise project management software tool, across its entire organisation, the benefits and efficiencies gained have been huge. I’ve observed increased communication between departments, greater levels or collaboration, consistency across both project based work and ad hoc work, more valuable time recording, reduced time spent gathering and creating reports, openness, accountability, and overall more effective work management.

Enterprise Project Management software is so much more than a Gantt chart or a task list. When you think about how it encompasses help desks, timesheets, financial and resource management, and even just general work management, you begin to realise that the possibilities are endless. Marketing does projects. Finance manages monthly projects. Sales lead on to projects. So why not bring them all together?

I appreciate my statistical analysis is by no means comprehensive, but when I think about where I might be in 2 years from now I hope its not somewhere that believes Project Management ends with the PMO or IT department.

0 Comments »

Face The Interfaces

Mirror MirrorInterfaces

One of the happy paradoxes of good Enterprise Project Management Software is that the more information users find and believe, the more information users believe they will find.

That extra information often lives in other tools; and rightly so. But to be effective, it often needs to be visible along side our Project Based Work. For those of us managing such Project Management Tools, this leads to an inescapable truth: eventually, we’ve got to face the Interfaces.

A Spectrum of Options

Modern PPM Software offers a plethora of choices when it comes to data integration. Recently, I had a client ask me to help them decide which route made the most sense for them. So I took the opportunity to build up this Interface Options matrix in Excel:

The Requirement section:

  • Has a Description of the overall objective (e.g. To Push @task Hours to an External System Twice per Day)
  • Lists each Option in increasing degree of technical difficulty (e.g. Manual Push/Pull by User, Email Pull to User, Email Pull to [Email] Agent, Webservice to WebService, or WebService to Database)

The Interface Steps section:

  • Lists the functional steps in the interface
  • Notes for each Option which resource has responsibility for each step

The Comparison section:

  • Lists the difficulties in the interface (e.g. Reliances, Manual Efforts, Programming Efforts, Costs of Developing, Costs of Operating)
  • Uses a somewhat subjective (but rather telling) High (Red) / Medium (Orange) / Low or None (Greeen) score of each Option against those difficulties
  • Boils each Option down to its most appropriate use

The Cost Estimate section:

  • Runs over 2 years (to allow for a more fair comparison)
  • Lists the assumptions for Hardware, Development, and Operating Costs
  • Computes the total costs for each Option

Upon Reflection

Once I set up my Interface Options, it was easy to use the same criteria for a second requirement (e.g. To Pull Cost Information from an External System into @task Twice Per Day). Having the two options on two tabs in Excel let me flick between the two scenarios. While doing so, I noticed some interesting comparisons, and it forced me to rethink a few assumptions.

Now that it’s set up, I think that my Interface Options matrix will help me provide better estimates more quickly. You are welcome to download it and change it for your own use.

0 Comments »

Small, Incremental, and Attainable

From 1967 to 1976 East Germany’s Roland Matthes dominated the 100 and 200 meter backstroke setting nine world records.  In 1976 when John Naber won four Gold Medals, a Silver Medal, and set four new World Records (including a new record for the 100 and 200 meter backstroke) at the Montreal Olympic Games, I was on my high school swim team and John Naber became a personal hero.

Naber is the perfect example of what author Robert Collier was describing when he wrote, "Success is the sum of small efforts, repeated day in and day out."  As a teenager, I had the opportunity to hear Naber speak about his Olympic success. Let me share with you how he toppled the dynasty Roland Matthes had created over the preceding nine years.

Matthes held the record for the 100 meter backstroke of 56.30 seconds and the 200 meter backstroke of 2:01:87, which he set at Munich, Germany in 1972 and Belgrade, Yugoslavia in 1973 respectively.  As Naber described it, he was several seconds slower than Matthes, which in swimming terms might as well be minutes among Olympic athletes.  Undaunted, Naber set his sites on winning the Gold and setting a new world record at the 76′ Games.  Doing this required setting goals that would push him to stretch, but were also realistic and attainable.  In a nutshell, this is what he did:

  1. He determined how many seconds he needed to cut off of his time in order  to set a new World Record and divided it by four (the years he had to prepare for the Olympics).
  2. He calculated how much faster he would need to be each month and each week to meet the yearly goals.
  3. He then considered the number of days and workouts each day to determine how much faster he would need to be every day and every workout.
  4. Finally, he calculated how much faster he would need to be within every set of every workout, and thought "I can do this."

By subdividing the goal into small, incremental improvements he was not only able to beat Matthes for the Gold, but was also able to set a new World Record for the 100 meter backstroke of 55.49.  What’s more, his 200 meter World Record of 1.59.19 was the first under two minutes and along with his 100 meter record, stood for seven years.

Naber’s story is meaningful because it demonstrates that sometimes, in my opinion most of the time, gradual and steady progress contributes to monumental outcomes.  I believe the same is true for project based work.  Project management tools, including PPM software enable project managers and teams to make efficiency improvements that impact project success.  Although there are some immediately apparent and substantial gains that can be achieved with the right project management software, there are many small and incremental efficiencies that can provide exponential gains in productivity.

What are some of the small improvements in efficiency you’ve found that have a substantial impact in project success?

2 Comments »

© 2011 AtTask, Inc. All rights reserved.