cloud computing vector. backing up and storing business data via cloud computing. vector illustration.

Download our comparison of MS Project versus ITM Platform

Industy standards that consolidate at certain historical moments are often more strongly influenced by the human tendency to conservatism than by the value they bring.

It may seem like a bold statement, but there is a plethora of literature on it. It will be clearer with an example: the QWERTY keyboard came from a salesman trick: agents who sold typewriters demonstrated the amazing ease of use by typing the word "typewriter" using only keys in the upper row of the keyboard.

However, many people still believe that the QWERTY keyboard was created after extensive studies on the relationships between English vocabulary letters and, therefore, is optimized for English speakers.

 

This is the case of MS Project, which appeared in the era of the personal computer and propelled the digital consolidation of project management methodologies in hundreds of thousands of organizations. Just as QWERTY has never been replaced by an alternative keyboard due to the resistance of the typographers (first) and the millions of users (after) who were already accustomed to a certain configuration, the continuity in using MS Project is not due to a rational comparison between alternatives evaluated on an equal footing, but the enormous power of continuity.

What both products have in common is the combinatorial use to generate a superior result to its parts. The integration of characters and components creates a coordinated meaning. In this situation, replacing all functions with different access modes in an alternative generates major issues in the transition.

But there is the difference between the two examples. While QWERTY has captured 100% of users, Microsoft Project only has 67% of the market share in project management, and 15% in portfolio management, according to Statista.

How does MS Project market share compare to QWERTY? Data

This rate will go down for one simple reason: MS Project is a product anchored in the past. There are many reasons to dismiss it in favor of a solution based on a contemporary digital paradigm, that is: collaborative, distributed and connected.

So, what are the main reasons for leaving behind MS Project?

The question could also be formulated in the opposite direction: What reason is there to continue using MS Project? It is fundamentally a desktop program and is for personal use? Is it that it’s comfortable? Or a false perception of the balance between advantages and disadvantages?

Let's review the motivations for replacing MS Project with a SaaS solution like ITM Platform:

MS Project is single user (ITM Platform is multi-user)

In MS Project, the working model is a project manager who creates the project plan, saves it to a file on a local hard drive ... and makes changes manually.

"In ITM Platform, your team can be an army permanently connected." 

Overcoming the native limitations of MS Project as a desktop solution is very costly even for small teams. While ITM Platform is worth $ 1,000 USD per year to support teams of up to 7 people, that same amount can only serve 1.5 people with the most affordable version of MS Project online.

In addition, since MS Project does not have project approval mechanisms and state changes, anyone can make changes to .mpp files on a shared server without prior discussion, without approval flows or notifications to the parties involved.

On the contrary, ITM Platform works from a network model, so users do not work on files, but in environments: shared project ecosystems common to each organization. This model has important implications:

  • Users have differentiated access profiles, so they make modifications exclusively in their area of ​​responsibility;
  • No action by other users goes unnoticed: the system generates notifications about changes made to projects and tasks, as well as allowing contextual communications.
  • In short, thanks to the ability of team members to report hours and progress, the distance between planning and execution is much shorter and more efficient than MS Project.

ITM Platform is designed for strategic planning - MS Project is not

MS Project focuses on improving its timeline; ITM Platform in alignment with business objectives

When considering this aspect, the history of project management as a discipline is of particular importance. With its expansion beyond the fields of engineering to assert itself as an organization management model, the demands on the priority aspects with which software must comply have changed.

MS Project has not responded to those needs, having preferred to concentrate on the complexity of planning aspects.

In contrast, ITM Platform allows you to introduce business objectives, study different scenarios and make decisions based on actual data for which projects to execute.

MS Project requires expensive installations - ITM Platform is cloud based

"ITM Platform is a tool for organizations; MS Project is software for the personal use of project managers." 

This distinction has nuances: MS Project Server is the version for organizations that Microsoft offer. However, the process of moving from the personal to the organizational version can cost between $ 10,000 and $ 20,000. In addition, the on premises installation requires MS, SQL and Sharepoint servers as a starting point, as well as advanced technical expertise in those fields.

On the other hand, the deployment of ITM Platform in an organization is much more agile, since it does not require any type of installation (clarification: we offer on-premises installation for the organizations that demand it, but it is a marginal option among our customers). Including all parameterization and initial training, our customers begin to use ITM Platform in terms of between two days and two weeks.

Build a PMO in a week ... or in an eternity

"ITM Platform is an ideal tool to create a project management office." 

For adoption facilities and portfolio management capabilities, ITM Platform is an ideal tool for organizations that already manage projects from the initiative of individual project managers and that are about to create a project management office. While MS Project Server requires a remarkable economic and human effort to simply deploy the tool, ITM Platform is a catalyst for centralized management, thanks to the ability to focus on the methodological aspects that really matter.

MS Project does not offer control over basic integration components

The management of basic components of project integration - such as costs and billing of projects - are done outside of MS Project, so anyone who only accesses the .mpp file has no visibility to these modifications.

On the other hand, ITM Platform's solution includes cost management, making it an excellent candidate for integrations with ERP systems. Another example of the holistic ITM Platform approach is risk.

MS Project has a closed philosophy - ITM Platform an open philosophy

In the era of online business productivity, where most players integrate solutions through API to achieve more ambitious automation flows, Microsoft maintains a closed philosophy that only allows to connect their own solutions with each other: Excel, Access, and so on. Even so, the possibilities to connect MS Project are deficient. It is impossible, for example, to receive custom notifications in Outlook when modifications are made to projects.

On the contrary, ITM Platform strives to coexist with the systems of all our clients: we don’t want to bring about traumatic changes.

Not only do we have a complete API for developers from any organization to connect their ERP, accounting or CRM systems; there are also integrations with JIRA and Slack, as well as an upcoming presence in Zapier.

MS Project is rigid - ITM Platform is flexible

According to Mark Corker, president of Seradex Web Services, software complexity and the repercussions of preprogrammed options to readjust dates in dependency tasks have the counterproductive result that 99% of MS Project projects have no reliable dates.

On the contrary, ITM Platform is based on a flexible software model: resilient adaptation goes from the technology to the user, and not the other way around. That's the reason why ITM Platform is enjoyed not just by project managers, but also by CFOs, CEOs, CIOs, IT Analysts, and a long etcetera.

Receive the latest blogs directly into your inbox

 

analytics and e-management of data on dashboard. graphs, diagramsOne of the most complex goals for a project manager is to manage all project components in a coordinated and unified manner. This is known as project integration.

Integration is probably the most crucial area of ​​knowledge: it is no coincidence that it’s the first of the 10 areas recognized by the PMBOK. In fact, it is most directly concerned with project governance and the project manager's ability to "be everywhere."

ITM Platform is a project management software specifically designed to help make integration not an impossible task. Its navigation menu puts all the components of the project in one easy to view panel, so that it is possible to access them and control them with a simple click.

Project home, ITM Platform

Test the ITM Platform project menu and start integrating seamlessly

In this article we review how to solve the most important aspects of project integration with ITM Platform. You can continue reading about project integration in this article.

1. Project Approval

Every project begins with its approval, which, according to PMBOK, should be reflected in an Act of Constitution of the Project.

How to do it in ITM Platform

ITM Platform allows you to configure the flow of approval status’ of the project, adapting it to the realities of each organization.

the flow of approval status’ of the project

In addition, when creating a project, it is mandatory to indicate the approval status, which by default is listed as "pending".

The Constitution Act can be uploaded in the project documents section so that the responsible person can review the documentation before making the decision.

Request a demo session to see how ITM Platform can fit your organization

2. The project management plan

Project planning with ITM Platform can begin with the design of a schedule, but goes much further.

How to do it in ITM Platform

  • Gantt or Kanban: For predictive projects or for agile teams. Both project planning and portfolio/program aspects are fully compatible with both methodologies.

  • Purchases, revenues and budgets: Once the project budget has been entered, ITM Platform is responsible for tracking each invoice, measuring the distance between the estimated budget and actual expenditure. In the purchases tab,

  • Risk management: In the risk view it is possible to plan and consult the risks associated with the project, which can be evaluated with our risk assessment matrix.

3. Monitoring and control of project work

The control of project work has several fronts:

  • From the team tab you can assign project responsibilities to the team, while from the Gantt / Kanban tabs you can track progress in the tasks.

  • From the Follow-up tab of the project menu you can add quick progress evaluations for the whole project.

  • The budget tab allows you to compare the estimated budget with actual values

Start monitoring your projects with ITM Platform

 The budget tab

  • The dashboard offers a panoramic view of the most important indicators of the various components and is a working tool that our clients use continuously for internal reports and to support decision making.

Project cost/Actual cost

4. Beyond the project menu

Certain processes of integration more related to the administration of the organization live outside the project view.

  • Communication: ITM Platform has a contextual communication network that enables the exchange of information at any scale: notifications throughout the organization, project discussions or task discussions.

  • Stakeholders: This is one of the most differentiated features of ITM Platform. The external clients section connects projects with their profitability, facilitating a project-oriented customer relationship analysis.

Receive the latest blogs directly into your inbox

 

coding and programming mobile applications for devices An area of ​​knowledge is, according to PMBOK (Project Management Body of Knowledge), "an identified area of ​​project management defined by its knowledge requirements and described in terms of its processes, practices, initial data, results, tools and techniques that compose them. " In fact, all project management processes contained in the PMBOK are divided into 10 areas.

Start integrating the components of your projects with ITM Platform and keep control over activities, resources, costs, suppliers, customers, risks and much more.

In addition to the famous 6 phases of project management, the PMBOK contains 10 areas of knowledge:

  • Project integration

  • Project scope management

  • Project time management

  • Project cost management

  • Project quality management

  • Project Human Resource Management

  • Project Communication Management

  • Project Risk Management

  • Project Procurement Management

  • Project Stakeholder Management

In this article, we review the first area of ​​knowledge: Project integration.

The management of PMBOK project integration brings together the processes and activities necessary for the project to exist beyond its parts. Without integration, the project is nothing more than a value proposition with a goal; Once the components are identified and defined to integrate them around the scope to be produced, the project is sufficiently defined to be accepted.

Integration, however, should not be confused with initiation: in fact, it is a beginner's mistake to integrate the components only when defining the project: integration must be maintained throughout the project life cycle, along with the six management processes in this area of ​​knowledge.

The 4 keys to improvement in this area of ​​knowledge are:

  • Gain ​​acceptance

  • Create an attack plan

  • Be willing to make concessions and rectifications

  • Learn from mistakes and successes in project closure

Obtain acceptance

Integration management will be effective if we gain the support of all team members and, above all, stakeholders. Getting acceptance from the start of the project ensures that we have the support and funding to succeed. To do this, we start by creating a Project Plan and a Preliminary Reach Statement.

The Project Plan marks the beginning of the project and includes the necessary approvals and corrections. In addition, it authorizes the project manager to direct and organize the resources, which will be reflected in this letter, being well defined in their roles and responsibilities.

In the Preliminary Scope Statement we indicate the scope of the project, we define the reasons for undertaking this initiative, the objectives, the possible limitations, the possible solutions and identify the important stakeholders affected by this project. This document defines the project itself, as well as the strategy that must be followed for the change control process.

With these two documents we will be able to guarantee that the resources are coordinated and programmed in the form and time that are needed.

Create an attack plan

We begin by identifying the activities that will be necessary to effectively execute, manage and monitor the project. It will be necessary to have a project management software that allows for planning and supervision of the project at any time and from anywhere.

With a Gantt, we can visualize the project tasks and the assigned resources. In addition, we will get daily status updates, necessary to effectively manage the project.

As the project progresses, so that reporting and monitoring among all team members is more accurate and timely, we should emphasize that everyone updates the completion status of their tasks. Otherwise, its use is very easy and intuitive.

Be willing to make concessions

One of the biggest challenges that we will face in implementing the project is the management of people. The interests and opinions may be overlapping between managers of different departments and on multiple occasions they may ask to make changes in the planning of our project.

For us to be effective we must be willing to make concessions, although we may not always be able to give them what they ask of us. Above all is the project, which must meet the objectives and requirements set out in the Project Plan.

We must ensure that the team is doing its part of the project correctly and make sure that the work is completed according to the requirements in the Preliminary Reach Statement. We must monitor and control project work by measuring and balancing project progress; and carrying out corrective or preventative actions, to ensure compliance with all objectives.

It is important that we follow the established process for change control as defined in the Preliminary Reach Statement, and when a change request is made, make sure it goes through the appropriate channels before it becomes part of the plan.

Each change request must be evaluated individually and we would only implement validated and approved changes that will help us to achieve the project objectives.

Learning from mistakes and also successes

At the beginning of the project we clearly defined all the activities, and at the end of the project all we have to do is verify that the activities are all completed and that the final product or service meets the expectations of the client and the interested parties. It is desirable that we obtain written approval of the completion of the project.

Once the project is finished, it is about learning from any mistakes and successes. We organize a formal meeting with the team members and have a brainstorming session, listing one by one all the errors observed during the project. We also make a list of things that went well.

The weaknesses that we have encountered, the threats of the environment suffered, the strengths that we have detected as a team and the opportunities that we have known or did not take advantage of, everything learned in this experience, will serve us for the next project in which we will be more effective.

Receive the latest blogs directly into your inbox

 

meditating businessman balancing work and personal life, heart and tool When evaluating different tools, soft virtues such as the ability to adapt to different situations are often overlooked.

The concept of resilience has been popularized from its origin in psychology and environmental sciences to have multiple uses.

It is said that someone is resilient when he manages to overcome adverse situations. A resilient material regains its shape when the external pressure ceases; A plant, when it survives a period of drought. A resilient organization is one that manages to reorient its business model to the pressures from the market.

 

However, resilience is seldom mentioned as an advantageous feature for software products that can tolerate stressful situations. Given that B2B software is reaching new degrees of specialization, it may seem strange.

Let us explain the model of Software as a Service with ITM Platform.

Let's begin to consider resilience as a priority factor when evaluating different business software alternatives, in particular SaaS solutions.

SaaS B2B software suffers from a widespread problem: adoption rates by end users. Friction is, in this sense, the biggest barrier to return on investment.

What characterizes resilient software? What does it mean to be able to tolerate and survive adverse circumstances? Somehow, the stress test moves from the user to the tool itself. In the most difficult situations for a company, such as the adoption of a new management software, the tool has features that allow it to adapt and respond positively to a variety of uses by users.

More specifically, we look at an example from the project management industry. A project management software, for example, will be resilient if:

  • it covers different styles, methodologies and organizational processes, without forcing specific behaviors on the part of the users that require previous training

  • assumes in its system the dichotomy of agile versus predictive

  • allows for managing operations in addition to the projects themselves

  • is able to coexist with the intensive use of other products in linked areas of the core business

  • manages to increase its value from the appearance in other software environments (e.g. apps and integrations)

In the case of ITM Platform, for example, its resilient features include, but not limited to, the following factors:

  • ITM Platform is a very useful tool for expert project managers, because it welcomes, in its core, most of the aspects that should be considered in the integration of projects. However, it does not require specialized knowledge, to the point that it has an excellent reception in organizations that are taking the first steps in their orientation to projects.

  • Instead of covering a very specific niche, ITM Platform offers a competitive combination of complete but easy-to-use features. It is not necessary to take advantage of everything the machine can do to get going.

  • As far as the user experience is concerned, the navigation menus opt for maximum visibility of the benefits, instead of requiring a very precise knowledge of the platform

  • There are multiple access routes for the most essential functions

These points are just some examples of why I consider resilience to be a very valuable principle in assessing the ease of maintaining software use when circumstances change, motivations to use software, and coexistence with other business information systems.

Jaime Capitel
Senior Content Strategist
ITM Platform

Receive the latest blogs directly into your inbox

 

technology, used for electric circuits. suitable for use on web apps, mobile apps and print media.Making organizational changes in any process, work methodology or project management system is, in itself, a very difficult project to manage. When it comes to internal management, the cost of a failed project is very high, so the margin of error is small. To make matters worse, the response of the people involved in the process makes it difficult to predict and difficult to design change plans that are followed closely.

In fact, it is common for any change, that is outside the organizations’ comfort zone, to cause diverse attitudes among workers and managers, making it difficult to contribute to change in a coordinated and organized way.

 

Some of these attitudes could be summarized in the following sentences:

  • "Our employees are prepared for change in the organization, there is nothing to worry about."

  • "Our company is different. Team members will be able to follow directions while exercising their autonomy. So it is not necessary to intervene in the management of change. They, know how to act better than anyone else."

  • "Things are fine as they are. The changes you want to introduce mean an additional workload that adds to what we already have, so the change cannot be positive."

  • "Workers do not have to be involved in change. We have not even been involved in the choice of new software tools."

All these statements can be refuted with the right arguments. Next, we are going to analyze valid arguments to answer them.

Complementary training programs

Undoubtedly, all the workers in your company are qualified for the work that they perform, so they can take care of it. However, the introduction of new working methodologies requires additional preparation and a strategic vision. So it is desirable to have complementary training programs provided by the company both before the introduction of the changes and during their implementation. These training programs achieve a two objectives at once. On the one hand, they will help the change develop properly, without undertaking useless additional work, since the appropriate orientation will allow for all the efforts and dedicated time to be oriented to achieve an efficient change according to the established plans. On the other hand, providing this training during the change will increase the motivation of the workers.

It is important to learn from real cases in other organizations

The problems that arise in your company have probably been experienced in other contexts, especially if there are similarities in market niche, economic sector, technological development, and so on. Although each company is unique, there are common situations and frequent problems, especially towards certain challenges characteristic of business development. For example, internationalization has very different resistance to change from the introduction of performance evaluation, the opening of a new line of business or the acquisition of another company. In any case, there is no alternative to the analysis of comparable cases. With change management there is no room for experimentation. The successes or failures of other organizations will help avoid mistakes and in turn gain precious time.

Conformity is the main enemy of progress

To be able to improve it is necessary to be open to change. Undoubtedly, at the beginning all changes are an additional effort, but this is necessary to increase efficiency and productivity, essential requirements to remain competitive.

Workers are the main engine of the company...

...Those in charge of taking the company forward. If they don’t feel involved or motivated with the work they do and with the company, it is a serious problem that is above the difficulties to implement a system or project management solution. Regardless of the organizational model, workers must be motivated. Of course, an adequate motivation also contributes to the success in the implementation of any work system.

Try ITM Platform for free

So what can we do when there is resistance to change management both by managers and employees? Here are some tips:

It directs the change towards a clear improvement

It identifies the main obstacles to growth and proposes a process of change that achieves more mature and robust management, with clear benefits.

Adjust the exchange rate to your corporate strategy and culture

Before any change, it is best to evaluate exactly its magnitude and where the efforts should be directed. There is nothing worse than making "changes in change", on the fly, because it generates a sense of distrust, of not knowing exactly what is being done, and produces demotivation of employees. If they have tried to change something, this change must appear to be definitive, it must seem that it has been done right at first. Improvising will convey a lack of leadership.

Explain what change really means

Probably, in the initial moments there is a certain resistance. It is normal and is simply based on a certain fear of any change that may occur. Explaining exactly the magnitude of the changes will help to reassure employees or managers and will predispose them to accept them to the best degree.

Demonstrates the advantages of new project management systems using data

If they understand that the change is necessary and that the return will be greater once they have been applied, they will be more willing to perform the initial overexertion.

Using these tips, managing change in your company will be much simpler. What are you waiting for to give a return to your project management?

Receive the latest blogs directly into your inbox