Vantaggi
- Leadership and project management were often reactive and inconsistent, creating frequent scope shifts and unclear priorities. - Decision‑making bottlenecks and poor stakeholder alignment led to repeated rework and avoidable delays. - Communication from some PMs and leaders could be aggressive and non‑collaborative, which impacted team morale and made the environment stressful over time. - Limited governance for handovers, testing and deployment increased operational risk and manual effort. Concrete examples - Frequent last‑minute scope changes without updated acceptance criteria caused multiple UAT cycles to be reopened. - No clear escalation path or consistent sprint planning cadence; priorities changed mid‑sprint several times. - Leadership feedback tended to focus on blame rather than root‑cause resolution, which discouraged open problem‑solving. Suggestions for improvement - Establish clear decision rights and a stable sprint roadmap to reduce mid‑sprint churn. - Implement consistent acceptance‑criteria and API contract reviews before development starts to cut down UAT rework. - Introduce structured feedback and people‑management training for PMs and leaders to foster respectful, solution‑oriented communication. - Strengthen governance for deployments and handovers to reduce manual processing and operational risk. If you value structured delivery, clear governance and collaborative leadership, raise questions in interviews about sprint cadence, decision‑making authority and how the company supports people managers. You will get strong hands‑on experience, but be prepared to escalate governance and process issues early if you join.
Svantaggi
PM's who handled the project, hampered the engagement with client by inconsistent leadership, unclear priorities and process instability, which made it difficult to sustain delivery momentum and maintain team morale
