Here's how to do it.
This time, in our new blog post series on hybrid project management: rolling out Can Do in five tried-and-true steps
If you want to implement hybrid project management with Can Do andJira® in your company, we have a specific recommendation for the rollout: Use a variation of the iterative approach and first introduce the new PM software to a small group. In this third post on the Can Do rollout, we’ll show you a suitable five-phase approach for doing so.

As we explained in our last blog post: Based on our practical experience, neither the all-encompassing “Big Bang” approach nor an iterative approach—where the software is rolled out company-wide but only “in small increments”—is the right strategy for rolling out Can Do. Instead, it has proven most effective to establish a “task force” for the Can Do rollout. This is a group of employees who are first tasked with gaining their own experience with Can Do. Based on this experience, the group then optimizes the specific use of Can Do within the company and applies the knowledge gained during testing.
If you want to introduce hybrid project management with Can Do andJira® , you’ll encounter broad support across all roles in your projects. After all, its benefits have project-wide implications, such as:
So you’ll have no trouble finding interested people in your company whom you can get excited about a pilot implementation of Can Do. We’ve had very good results so far by initially assigning this task to 1 to 3 groups of 5 to 15 employees each.
To avoid any misunderstandings: The priority installation described here for a pilot group is not intended as a “trial run,” but rather as the first step in transforming your project management into a modern hybrid approach. To get to know Can Do in advance, please take advantage of our live demo, which is tailored entirely to your specific use case.
So once you’ve found your team of dedicated employees who want to participate in the introduction of hybrid project management , you can begin the phased rollout of Can Do:
In this phase, things get technical—after all, installation comes before use. First, you decide whether to run Can Do “on-premises”—that is, installed on your own server—or in the cloud. Then, your admin(s) will be trained on operating and supporting Can Do. Together with the Can Do experts, you’ll put together a team and define the roadmap—including goals and milestones. This phase also involves the Can Do Migrator, which ensures that the software integration is largely automated.
The first phase takes about a week.
This step is one of the most important in the transition to hybrid project management with Can Do—because it lays the foundation for all the features Can Do provides for your projects. Both basic tools, such as budget planning, and Can Do-exclusive features, such as its proprietary AI for skill management, can only function smoothly if they have access to the appropriate data. The second phase, therefore, focuses on the accurate establishment of valid master data. This includes, among other things:
In addition, starting in the second phase, key users for the Can Do application are trained over an extended period, and the necessary interfaces are created. These ongoing project strands span phases 2 through 4.
The second phase takes about one to two weeks.
Now you can put your core competencies to work to drive the rollout of hybrid project management forward: It’s all about planning, strategy, and optimization! In the third phase, Can Do is “fed” with your projects (or your portfolios in the case of multiproject management). So, in Can Do, you’ll plan, among other things,
With this new planning approach, you’ll simultaneously optimize the management of your projects and multi-project portfolios in Can Do.
The third phase lasts about two to four weeks, depending on the scope of the project and the size of the portfolio.
Can Do is now being put into regular operation in the units that are using it first. Project team members are assigned in Can Do Staffing; project progress tracking and time tracking are handled in Can Do; and users gain experience with features such as the fully customizable dashboard and tools like risk analysis.
During this phase, Can Do is adapted and optimized to meet your company’s project management requirements. This is an ongoing, increasingly granular process.
The fourth phase is completed after two to four weeks.
The time has finally come! Your company’s entire project management team will soon be able to benefit from hybrid project management —because the rollout across the organization is now beginning. The agile rollout of Can Do includes, among other things, further data setup, ongoing training, and the creation of use-case-oriented instructional videos to serve as a permanent knowledge base for admins and users.
The fifth phase lasts approximately two to six months.
It’s clear: every company has a different use case and a unique project environment. That’s why, while our 5-phase rollout for hybrid project management is a good guideline for estimating your own rollout, “your” rollout will certainly differ in the details. If you’d like to learn more about how to best prepare yourself and your company for the Can Do rollout and then implement it, we recommend scheduling an appointment so we can advise you on the optimal way to introduce Can Do. Just get in touch!
Our blog provides well-founded and practical content on project management, resource management, and the use of AI in businesses. Our goal is to equip professionals and decision-makers with tools, strategies, and inspiration to manage their projects and resources more efficiently and successfully.
This time, in our new blog post series on hybrid project management: rolling out Can Do in five tried-and-true steps
The final post in our blog series on the rollout of Can Do: the first workshop, the requirements specification, and why ...
1 min read
Why scheduling often becomes a project risk, and how modern project management methods and AI enable more reliable ...