Ing. Viktor Tomaško, PMP, PMI-ACP

When I took over a massive global data migration project, all reports showed it was strictly green, and leadership was completely satisfied with the progress. However, a deep initial analysis revealed a harsh reality: finance was entirely out of control with unclear budget coverage, planning was done ad-hoc, documentation was non-existent, and developers worked in silos without alignment. Stakeholders were deeply frustrated, and communication was stuck in endless status calls where nothing got resolved.

The hardest part wasn't just fixing the project – it was facing severe pushback from management when I changed the status from green to amber. As an external consultant saving their investment from a multi-million collapse, I was suddenly under intense political pressure. The project objectively required a red status, but an immediate escalation would have created resistance before the organization was ready to absorb the reality. The challenge was not only identifying the problem, but creating enough alignment to enable corrective action. Navigational and political finesse was required to prove we were heading toward a cliff. Even if a miracle had delivered the project under original terms, the complete lack of processes, change requests, and documentation would have caused severe compliance failures during any external audit.

Instead of applying superficial methods, I started with an intense assessment of the budget, contracts, vendors, and real team capacity to create a truthful forecast for management. We paused the active delivery for one month to stabilize the baseline. Daily synchronizations directly linked to realistic milestones were set up with developers. Regular face-to-face sessions with all key stakeholders were established to fully understand their concerns. After budget, scope, and all compliance topics were clarified and properly documented, we proceeded with a rigorous cutover plan featuring clear ownership and a strategy for the operational transition – including financial and resource analysis to ensure all markets received necessary post-deployment support. In the end, the project was successfully delivered on time and within the allocated budget while effectively keeping stakeholder concerns under control and expectations aligned.

Not every project ends in celebration, in fact, many of them do not. Real life is far from theory in books and a lot of transformations and projects fail. In one startup company we hit a brick wall for a combination of reasons that clearly highlight what happens when agility is forced rather than lived and when leadership is disconnected from execution layer.

• Very limited initial analysis: The transformation was rolled out to all teams without proper understanding of the core operational context, clear responsibilities and existing company culture.
• The Cultural Gap: We overlooked the cultural diversity of the teams. Merging people from multiple countries with vastly different work habits and communication styles created a massive blind spot. Agile principles must be carefully evaluated and their adoption tailored to specific cultures.
• Forced structural collision: Management tried to forcefully integrate rigid project management into a company that was supposed to run as an agile product organization – creating operational schizophrenia.
• Missing executive backing: Top management wanted "agile results" on paper, but completely refused to change their own directive behavior or cede any real decision-making power.
• Degradation of Scrum Masters: Under extreme pressure from above, Scrum Masters were forced into becoming micro-managers and meeting cheerleaders. People who challenged this interpretation of agility gradually lost influence or left the organization.