Archive for category project management

Scrum Project Management

Here is an amazingly good video that describes the Scrum development methodology in less than ten minutes. I highly recommend it to anyone who wants to get a quick and effective introduction to a new and now proven project management and software development methodology. We have started to use scrum in some of our R&D projects. We decided to use Agile/scrum to develop two new product modules that require a highly iterative creative approach. We continue to use traditional PMBOK type project management for feature enhancements and core product development. After some debate we concluded it is better to initially apply Scrum to “blue sky” type R&D projects. What we learn from these new projects can then be applied to our feature enhancement and core product development efforts. I will be able to share our experiences regarding these new methodologies in about six months when we are closer to the end of these pilot projects.

1 Comment

The 2009 Chaos Report – Is Project Success Really that Rare?

The Standish Group released its widely quoted report (available for purchase here) on project success in April 2009. The latest report is based on a survey of more than 300 organizations and 30 interviews. A summary of the findings is shown in the figure below.

SuccessRateGraph

The news is not very positive. According to this report the number of IT projects that failed has actually increased since 2006, successful projects are also alarmingly harder to find. Here is a far smaller and less official survey on software project success rates.

From our own experience and all the anecdotal evidence I have gathered projects are often late and over budget but they are mostly successful. In my opinion the Standish Group’s survey is overly pessimistic on the success rate of IT projects. I find nothing on the Internet that explains Standish Group’s survey approach or confirms these findings. It would be better if they provided more details as to how they assess project success and how they can backup their claim of a negative trend in worldwide IT project performance.

The report did not highlight any new reasons for the higher project failure rates. There are many more capable and highly qualified project managers today than in 2006, there are better tools, an abundance of easily accessible information on project management lifecycles and methodologies, and better collaboration between all project contributors/stakeholders. I simply cannot see how the end results can be this bad.

2 Comments

Unlocking the cloud

Here is an interesting perspective on cloud computing from the Economist. The article contends that customers subscribing to an on-demand service should be wary of data ownership and the data migration difficulties they will face when moving their data from one SaaS (software as a service) vendor to another. The author positions open source as a liberating technology and sees cloud computing as new attempt by software vendors to lock-in customers.

This is the first time I ever heard anyone argue against cloud computing. To tout on-premise open source systems as liberating technologies and to call SaaS and cloud computing as a step back is simply out of touch with what is occurring in the marketplace. At the heart of its argument against cloud computing is the lack of standards for moving data from one service provider to another. However, the same can be said for migrating data from one on-premise solution to another, whether open-source or not. For example, have you ever tried moving data from an Oracle application into a Microsoft or SAP application? No common standards exist today that would automate the migration of any form of enterprise data from one solution provider to another.

However, the process of importing data has become a relatively painless, inexpensive and a low risk activity for most forms of data. Data in most modern enterprise applications (on-premise or on-demand) is represented in XML or can easily be exported to XML, now a ubiquitous standard for data representation and data exchange. Using XML, just about every cloud service provider (and even legacy application providers) have the tools and the expertise to migrate data from the customer’s current formats and systems. There may of course be some minor challenges to overcome and the migration may require investment in a few days of consulting services but I do not at all see how data migration results in vendor lock-in.

One thing that customers need to make sure of is data ownership. Tenrox project management software and workforce management customers own their data, whether they are on-demand or on-premise. This assures our customers that they are totally free to move to another service provider.

Cloud computing has tremendous benefits for the customer. The service provider takes care of all the details of software maintenance, bug fixing, data backups, 24/7 availability, 99.9% up time, data security audits and certifications, bandwidth, worldwide access, and much more. This frees internal IT to spend time on more strategic work such as IT project portfolio and resource optimizations, data analysis, portal/report development, and activities that are directly related to the company’s core business.

2 Comments

Applying Occam’s Razor Principle to Product Design – Lessons learned from our Project Management Software design experiences

Occam’s Razor principle by a 14th century English philosopher states that “plurality should not be posited without necessity” or “when there are multiple approaches to solving a problem just use the simplest approach”. Seems like such an obvious statement but so much of the products we build and use today totally ignore this principle. The following best practices are based on the mistakes we made and lessons learned in building a project management software application.

Applying Occam’s rule to product design and development could go something like this:

  1. Design features that are simple to use
  2. Provide just one way of performing a function
  3. Don’t oversimplify

1) Design features that are simple to use

If you can implement a feature using several design options choose the simpler one. However, for most product development teams choosing the simpler design is easier said than done.
Here’s why:

  • There is a tendency to try and build an all in one comprehensive solution

    Since a variety of internal and external stakeholders participate in the analysis phase, designers often keep adding complexity to satisfy the many parties and differing agendas involved. Therefore, often a product that was intended to automate a simple function or provide a simple service turns into a complicated device that can “do it all”, right out of a science fiction movie. 

  • Developers are naturally biased towards paying much more attention to handling extreme cases and boundary conditions at the expense of basic patterns of usage

    I have seen the negative impact of this firsthand at Tenrox. The complexity of software developed is increased by a factor of ten when developers try to cover all possible scenarios. Let me provide an example, a few years ago our R&D team redesigned Tenrox Project Workforce Management’s rate engine so that it could support a variety of cost and billing scenarios. When the new software was released, to our surprise, a few large customers with simple cost and billing rules reported significant performance issues with the new rate engine. After some analysis we discovered that these customers were using standard hourly rates, and yet the rate engine’s new design, which had absolutely nothing to do with hourly rates had been overcomplicated and slowed down a simple calculation that was working just fine before. Of course, the engineers went into emergency mode and had to come up with short and long term fixes to their overly engineered design. It takes considerable senior executive attention to reduce this bias and it is an ongoing battle in our product management and R&D teams.

  • Iterative reviews focused on what is missing complicate product design

    After working with our R&D team on several product releases over a fifteen year period we have identified this as a recurring pattern to avoid. Here is an example. We met about a year ago to redesign our software’s budgeting feature. The designers had come up with what they thought was a simple elegant solution that they claimed would address 95% of the requirements we had encountered. The meeting started on a positive note and everyone participated in the design review. A few people made suggestions of small things they thought were missing. Eventually there were many more ideas, new, even some commonly observed, usage patterns the designers had not considered. Within minutes the simple design was thrown out the window, and a complex multi headed beast of a budgeting feature design reared its ugly head. We all walked away from the meeting a little more tired, uncomfortable with the outcome. R&D ran with the feedback and put a few good developers to the development task. Six weeks later we were invited to another meeting to get a more in-depth view of the design, including some design mockups. The meeting was a disaster; the feature had become so complicated that virtually everyone agreed that the entire design should be killed. After wasting six weeks of development time, the designers went back to the drawing board and re-designed the feature from scratch. The second revision had fewer features than the initial design they proposed! But it was just the right combination of automation and ease of use. Our third design review meeting was an overwhelming success and the new budgeting interface was a hit.

2) Provide just one way of performing a function

As any product evolves, especially of the software type, we keep on adding more and more new functions. For example, in a version one, you can only create a project from the setup page. But based on customer feedback, by version 5, you can create a project while on a dashboard page, from the project manager summary page, from the customer page, while creating a portfolio… However, if you look at the products that are often viewed as amazingly simple yet effective designs such as the iPod or Google ‘s user interface the user is given very few choices of performing the same function. I had our R&D team hang pictures of the classic iPod with just five buttons in all their meeting rooms so they are constantly reminded of the importance of this bare bones “get it done” philosophy.

3) Don’t oversimplify

This is perhaps the hardest rule of all. Let me explain with an example. Developing a timesheet application seems pretty straightforward these days and is considered by most to be a simple application to buy or develop. That is until you get into the details of the varying department specific time tracking user interface and timesheet policy enforcement requirements, cost allocation, billing, leave time and overtime calculations, and approval processes that have to be accounted for and automated. Not to mention the complexities of integrating a timesheet with payroll, accounting, project management software, and CRM applications.  We are often faced with prospects who try to oversimplify such requirements, choose an under-powered product or do not make the proper investments, and pay a very heavy price when these issues resurface in the tail end of the implementation.

However, even if your product can and must handle complex functions, always focus on the most common use of a function. If you need to implement complex or boundary scenarios they can not impact the average use of the function.

In a future blog, I will apply Occam’s Razor principle to making IT investments.

1 Comment

A Primer on Just-in-Time Resourcing

A Primer on Just-in-Time ResourcingSM, Enabling the Concept of Just-in-Time Resourcing (JITR) with Project Workforce Management is a white paper I co-wrote with Randy Mysliviec CEO of RTM Consulting. Just-in-Time Resourcing  (JITR) can offer significant advantages and immediate benefits to professional services agencies, consulting companies and other expanding technology firms needing improved resource planning. “Stop gap” and other measures can compound the problems in handling large scale fluctuations in labor sourcing and management. Find out how JITR addresses the need for optimal resource supply for growing businesses, and how to enable JITR through project workforce management software.

You can register and download it here.

No Comments

Obama project management

Reporters and people alike have come to admire these distinct qualities in Obama: his generally calm and friendly demeanor, his message of respectful disagreement and yet cooperation, … trying to find common goals and rivals coming together to achieve these goals. Of course, all of this is quite a radical shift from the type of message we have seen from both sides of the political spectrum. So much of what Obama stands for (and hopefully will stand for throughout his presidency) can be applied to how we run our businesses, and projects.

Just like many of you, throughout my career, I have had my differences with some people. Whenever, I or any of my rivals chose to firmly disagree, argue, stand our ground or take a dogmatic position on an issue we all ended up losing somehow. This is specially true in any type of partnership. Hard ideological positions create nothing but obstruction, or worse destruction.

As an example, take the senator that single-handedly blocked the confirmation of Hillary Clinton on January 20th, knowing full well that she would be easily confirmed the next day whether he likes it or not. What is the point of obstructing and delaying what is an inevitable outcome? Instead, he could have simply stated his objections, understand that he has to work with this new team and get on with doing his job. Possibly spending some of that time and energy on the credit crisis instead. These are the politics of the future. As a friend of mine said, chances are when he runs for reelection he will be replaced by voters with someone who gets that this mindset change must occur.

So all of this got me thinking. How would Obama manage projects? I look forward to reading your thoughts on situations such as below and how you think an Obama type character would handle them.

- Dealing with a difficult customer: A customer that refuses to pay any invoices due because the project is late. The customer has changed project scope several times but does not think the scope changes are the root cause of the delays in achieving the milestones. He does not agree that the customer's team bares any responsibility whatsoever for the project's issues. The customer is absolutely convinced that his internal resources are doing a fine job and all the blame lies with your team.

Internal Politics: Your team and your projects are doing fine. So the "boss" and other project managers constantly raid your team for emergencies and try to take your resources away to fight fires. When you confront them they explain how urgent their issues are and how they absolutely have to "borrow" these resources. You know, of course, that it is only a matter of when not if that your projects will start to be yellow and red flagged as a result of these workforce planning (or lack there of)  issues.

How would an Obama-type leader handle these project management challenges?

, , ,

No Comments

Ten Predictions for Project Management Trends in 2009 Part 3

We covered the following 2009 trends for project management in the Part 1 and Part 2

- #10 The increasing correlation between project management and operational excellence

- #9 The CFO and the project manager friendship

- #8 The rise of the Project Workforce

- #7. Dispersed customers, projects and teams kill politics

- #6. Finding the right talent gets a lot easier

- #5. Emphasis shifts from project management to workforce management

Let’s look at the last four trends.

- #4. Uncertainty is the new normal

The unceasing uncertainty we have all felt about our jobs, our homes, the economy and the world in the last two years is going to be with us for the foreseeable future. The credit crisis, terrorism, climate change, and prolonged wars will continue to directly and indirectly impact our lives, our psyche. However, with human being’s remarkable ability to adjust to any situation we are starting to get used to it! When this whole war/economic mess started I remember how shocked and surprised I was every time I turned on the TV. Now, I do not watch as much predictably bad news anymore, and if when I do, I know it will be bad … so it does not really bother me nearly as much as it used to.

- #3. The rapidly increasing service web

The business model of virtually every large monolithic company is under attack. The web has enabled small, fast moving, low cost global competitors to emerge virtually overnight. This is even more true in the enterprise software space. Small companies with deep expertise in a particular problem area are able to build and offer Web service based solutions that solve the customer’s pain point a factor of time-cost faster than the ERP/established vendor alternative. With ever improving collaboration, Web service and integration technologies this trend will only accelerate in 2009.

- #2. Enterprise software technology cross-pollination gains momentum

Web services and new technologies continue to create a powerful seemingly perpetual wave of innovation in productivity tools. One of the more recent developments that is starting to gain further momentum has been is the surge in hybrid software technologies. Here are some examples (with varying degrees of success):

  • ERPs offering and embedding analytics
  • Project management vendors embedding business process management capabilities (true enterprise class workflow engines)
  • Project management and workforce management (not just time tracking but also workforce planning, time for payroll, leave time and other integrated HR/labor related functions/services) hybrid applications
  • Accounting systems offering CRM and other enterprise solutions

Generally, hybrids that create large monolithic all or none propositions do not provide compelling value. Vendors with such solutions seek vendor lock-in as their ultimate goal and only pay lip service to the true goal of standards-based pluggable solutions that are based on Web services allowing the customer to pick and choose the services that best address their needs. However, modular Web Services oriented hybrid technologies that can be quickly implemented are on the increase and offer a compelling alternative to the legacy application models.

- #1. Leadership matters

Above all, I think one of the most important lessons of the last several years has been the critical importance of the leader. It does not matter who is on the bus, what great technologies one has access to, how many best practices you are fully versed in, it is all for nothing if the people that lead your organization and projects lack the leadership skills and intuition to make the right decisions. An incompetent leader can lead the best team, the best technologies and the organization with the most abundant resources to total and shameful failure. The primary reason we are in the mess we are in now is extremely poor ignorant leadership at some of the largest public and private institutions throughout the world. We have learned, the hard way, that choosing a bad leader or project manager can be hazardous to us, to our way of life. I think, in 2009 every single one of us, whether we are executives, members of a board of directors, members of a committee, voters … will pay a lot more attention to who we pick as our leaders, representatives and our project managers.

These are my predictions about what to expect for project management in 2009. It should be helpful to consider these trends in your business plans so you can leap ahead of your competition.

What are your thoughts about how project management practices and technologies will change in 2009?

, , , ,

No Comments

Ten Predictions for Project Management Trends in 2009 Part 2

In Part 1 of this blog we looked at following three trends for 2009:

- #10 The increasing correlation between project management and operational excellence

- #9 The CFO and the project manager friendship

- #8 The rise of the Project Workforce

Now let’s look at the next three trends.

- #7 Dispersed customers, projects and teams kill politics

The flat world and access to a global talent pool has significantly changed the inner workings and team dynamics of virtually all organizations. There are many disadvantages to working with remote dispersed team members, which most of us are doing today. We tend to be happier, more loyal to the team, learn faster, and accomplish more as a team when we work physically close to each other. On the other hand, there are less emotions and politics with a dispersed team; people tend to pay more attention to getting the work done, than playing office politics; and their performance ultimately dictates how they are evaluated. In today’s increasingly dispersed teams office politics is certainly on the decline.

- #6 Finding the right talent gets a lot easier

It is much harder to find the matching resources you need when you limit yourself only to looking for talent in a local market. The flat world, Internet collaboration technologies have made it possible for organizations to tap large remote pools of talent at very competitive rates. For example, at Tenrox, we are increasingly leveraging specialized programmers working (probably) from their homes in Russia, Eastern Europe and at outsourcing shops in India. These resources are not replacing our full time staff; they complement our team by working on projects on a need basis. It allows Tenrox to remain flexible, not to over-hire, and yet quickly staff projects when required. With better collaboration technologies, improving quality of global resources, and our own improved knowledge of how to manage such projects, this process is becoming a lot easier and rewarding to execute.

- #5 Emphasis shifts from project management to workforce management

The project management discipline has traditionally emphasized the science of project management. Project managers and contributors are encouraged to follow strict templates, guidelines and steps to ensure a project is executed successfully. However, in spite of the increasing number of certified project managers and great project management tools, projects continue to show high failure rates, or high rates of disappointment by being too late, cost too much, or not fully meet their intended objectives. Numerous studies have looked at why projects disappoint. Many of these studies often conclude that better project management, communication, stakeholder involvement and change controls would have reduced failure rate. However, as books like Built to Last (Collins Business; 1 edition; November 2, 2004) suggest while best practices and better tools help there is nothing more important than picking the most qualified and best-fit resources to run the project (what Jim Collins called having the right people on the bus). Having the right people on the team makes everything easier; in fact, less process and less enforcement is needed since great team members innately know what needs to get done and just do it. As a result, more and more organizations are investing in cataloging their resources, understanding their resource’s capabilities and interests, and using more sophisticated workforce planning tools to find the best resources for their projects.

In the last and final part of this blog we will look at the top 4 project management trends in 2009.

, , , ,

1 Comment

Ten Predictions for Project Management Trends in 2009

2008 was an eventful prosperous year for the project management practice, project management service and solution providers:

  • Several independent vendors merged with larger entities; many more new small companies with innovative technologies emerged on to the scene. Given the poor macro picture, the amount of M&A and startup activity in this space shows how much interest there is and how much more there is to do, to improve in project management.
  • What do you mean you don’t do on-demand?! On-demand adoption surged in 2008 and is now the standard way to deploy project management software. In fact, the tables have turned. Vendors that do not offer on-demand solutions look out of place, out of touch with the market.
  • Project management continued to gain credibility as a legitimate profession that is very much in need given today’s complex project, workforce, market realities and regulatory requirements.
  • Working remotely, virtual offices, working from home, are now almost as accepted as working from the office in an increasing number of industries and work types. It is now common to find work arrangements that account for some work being done from home.

The stage has been set for some very exciting changes in the project management world. In a three part series, I discuss ten potential project management trends that may be more prominent in 2009.

- #10 The increasing correlation between project management and operational excellence

It used to be that senior company executives such as the CEO, CFO and board members would generally stay away from project management related decisions. The expectation was that CIO, COO and other operational executives would “take care of” ensuring that the company has effective project management practices. In fact, most executives generally regarded project management as something the “techies”, field level workers and mid level managers should worry about.

In today’s highly competitive flat world, the “Chinese wall” between executives and operations has broken down. In 2009, we will continue to see increasing sponsorship, collaboration, and direct involvement of senior executives in project management initiatives. Senior executives have come to appreciate the direct link between effective project management processes, best practices and tools and operational excellence. This task is no longer delegated away and deemed to be a tactical activity. Senior executives and board members view project management improvement initiatives as a strategic investment.

- #9 The CFO and the project manager friendship

An increasingly project-based service-oriented economy has led to more complex customer engagements and billing arrangements. By instituting charge backs, even internal departments have to justify their costs, deliver services efficiently, and earn the business of other entities within the same organization. Consequently, for CFOs measuring project value and recognizing revenue in compliance with various GAAP (Generally Accepted Accounting Principles) cost accounting and revenue recognition regulations has become an even more daunting task. The intricacies of estimating project value have created unprecedented ties between financial executives and projects managers who have to collaborate to produce incontestable project value assessments that can withstand the various forms of potential financial and project audits the organization may be subjected to. Given the current trends, the CFO/project management alliance is likely to grow stronger in 2009.

- #8 The rise of the Project Workforce

As explained in my book The Rise of the Project Workforce (www.projectworkforcebook.com) more and more individuals choose the projects they want to work on rather than the company they work for. Similarly, more companies are adopting the Hollywood model for a larger percentage of their workforce. In this model a project team is quickly assembled to execute a well defined objective; the team is just as quickly discharged once the project (the movie) has been completed. This flexibility makes both the company and the workforce more agile in a rapidly changing competitive marketplace.

In Part II we will look at the next three trend predictions for project management in 2009.

, , , ,

1 Comment

When project management software isn’t your thing

From time to time we encounter prospects with the following modus operandi. The company:

  • Uses a small to mid market accounting application such as QuickBooks, ACCPAC or Great Plains for financial reporting
  • May be using Microsoft Project to build plans for projects that require planning
  • Has implemented spreadsheets (or a custom app) to track cost and billing information that is then manually keyed into the accounting system

The company’s management is aware that how they run their business can be much improved and there are tremendous cost avoidance, cost reduction and revenue increase opportunities if the right process improvements are made. The company has allocated the funds and resources to make the investment. Now the hard work begins.

After months of research, demos, questions and walkthroughs the decision is made to purchase a solution like Tenrox project workforce management. The full software cost including a multi-year on-demand agreement, integration and implementation costs are prepared by the vendor and reviewed by the company.

And here comes the doozy.

After reviewing the project deliverables, some of the members of the customer team in charge of the initiative insist that all project details be exported back into the accounting system. The rational being that financial types (CFOs, senior executives) want to have all the cost and detail information in the accounting system. Sounds pretty harmless doesn’t it?

The problem with this approach is that the accounting system is being used as a detailed project tracking system with too many GLs (general ledger accounts), too many segments, too many transactions, too much data. Also, if you look at any GL entry in the accounting system you will still not be able to easily trace it back to the exact time entry, expense entry, or project charge that created it, unless you add even more complexity to the GL transactions you create.

Here is a true story from one of our customers who experienced this (names are anonymous for privacy):

“Many years ago, I recall we attempted a similar initiative at XYZ. We decided that we wanted to know everything when we look at our financial reports:

  • who bought which products and services?
  • how much did the project cost us?
  • which customers, projects, products or services has the most margin?
  • how much expenses were incurred for a project, by an employee, etc.

We redesigned our GL accordingly and came up with a 3 page document that described the GL structure. I came into the office 2 days later and was passing by the desk of one of our accounting resources. The image of Mary (not her true name) has been with me since that day, I will never forget it.

Mary had an expense report in front of her and she was on the third entry. She looked exhausted and confused. I asked Mary if everything is ok. She said she was having a lot of trouble understanding what each GL segment meant what and which full GL should be used for every expense type. The combinations were too many! We tried various lists and formats to try and simplify their work without success. Our entire accounting team was frustrated and confused by the complexity.

We ultimately dumped our “smart” GL system and went back to a more simplified GL model that captured cost and revenue information at a high level for financial reporting.”

Before you roll out any project management system, you should be convinced of the following fundamental principles, or the project management initiative will fail before it ever sees daylight:

  1. Use your accounting application to do what it is created for; to report on financials
  2. Use your project management system to plan, budget and track detailed project and workforce actuals, cost and revenue
  3. Export client/project cost and revenue transactions to your accounting application with enough detail to manage your receivables, accounts payable and financial reporting. However, stay way from trying to reproduce in two systems detailed cost and revenue information that you already have access to in your project management solution.

, , , , ,

No Comments