I’ve been a project manager for six years working exclusively with Waterfall methodologies. My current company is shifting toward Agile, and I’m struggling to understand how to manage documentation and stakeholder expectations when there isn't a fixed long-term plan. What are the best practices for a PM to adapt to the Scrum Master role without losing control of the project's overall delivery timeline?
3 answers
Transitioning is less about changing your tools and more about shifting your mindset toward iterative delivery. In Waterfall, you’re used to front-loading requirements, but in Scrum, you embrace change through the Product Backlog. Start by facilitating effective Daily Stand-ups and ensuring the team is protected from outside distractions. You don't "control" the timeline anymore; instead, you track Velocity to provide data-driven forecasts to your stakeholders. Focus on the Definition of Done to ensure quality remains high without needing a massive sign-off phase at the very end of the project life cycle.
This is a common hurdle. Are you finding that your stakeholders are still demanding a rigid Gantt chart even though the team is trying to work in two-week Sprints? It’s hard to be Agile when leadership still expects Waterfall-style reporting.
Focus on the ceremonies. Mastering the Sprint Planning and Retrospective sessions will naturally help you move away from the rigid documentation of your previous Waterfall projects.
I agree with Jessica. The Retrospective is especially vital because it allows the team to self-correct, which is a major shift from the PM-led "lessons learned" at the end of Waterfall projects.
Michael, that is the "Water-Agile-Fall" trap. To fix this, I recommend using a Release Burn-up chart. It provides the visual progress leadership craves while allowing the scope to remain flexible. You must educate them on how 'Value' is delivered incrementally rather than all at once.