The Project Work Performance Domain in traditional project management focuses on processes, resource management, and fostering a learning environment. For a project manager transitioning to a Scrum Master, it's important to understand how these elements translate into a Scrum context, where collaboration, team effort, and adaptability are key.
Potential dangers for project Managers, just picking out two from my experiences
- Sole Responsibility for Project Work: As a project manager, there's a tendency to take sole responsibility for project processes and resource management. In Scrum, these responsibilities are shared among the team, emphasizing collaboration and collective ownership.
- Over-Reliance on Formal Status Reports: Traditional project management often relies on formal status reports to track progress. In Scrum, progress is monitored through empirical evidence and direct team collaboration, rather than formal reports.
Useful Experiences and Skills:
- Process Optimization: Your skills in establishing and managing project processes can be valuable in helping the Scrum Team define and refine their workflow, contributing to continuous improvement.
- Resource Efficiency: Your experience in managing physical resources efficiently can aid in optimizing the team's use of tools and materials, contributing to the team's overall effectiveness.
Steps you can take as Project Manager to transition to a professional use of the Scrum framework:
- Foster Team Collaboration: Shift from managing project work individually to facilitating collaborative efforts within the Scrum Team. Encourage team members to take collective ownership of processes and resource management.
- Adopt Empirical Progress Tracking: Transition from formal status reports to tracking progress through Scrum artifacts like the Product Backlog, Sprint Backlog, and Increment. Use these artifacts to provide transparency and foster stakeholder engagement.
- Embrace Adaptive Change Management: Move away from formal change control processes. Instead, focus on incorporating stakeholder feedback into the Product Backlog and adapting the work as needed, without the need for additional formalities.
Conclusion:
The transition from traditional project management to a Scrum Master involves rethinking how project work is approached. It's about shifting from individual responsibility to collaborative team efforts, using empirical methods for progress tracking, and adopting a more adaptive and responsive approach to change management.
Next step:
Consider how you can apply your expertise in a way that enhances team collaboration and adaptability.
Exploring this project management aspect within Scrum reveals a complex relationship between project management skills and agile practices which we only just touched upon. Project Managers can bring valuable expertise to a Scrum team, but realizing its full potential only happens when the skills are adapted and applied to each unique Scrum Team’s context.
I hope you find value in these short articles and if you are looking for more clarifications, feel free to take contact.
Don't want to miss any of these blog posts? Have the “From PM to PSM” series weekly in your mailbox.
Wishing you an inspiring read and a wonderful journey.
Scrum on.
Steven
