Question

In a ScrumMaster with a traditional Project Manager perspective. Do you think it would be easy to transition to be a Scrum Master? Who do you think has the most power, the Scrum Master, Product Owner or the team? What do you think of the low-tech technique of “wall documentation”? Must contain more than 300 words

Answer 1

Scrum master is basically a facilitator of a project team working with agile methodology. The Scrum methodology gives the power to teams to self-manage and self-organize their work, as per the agile principles. Scrum master keeps a track of the project performance as per the agile standards. A project manager can become a scrum master if he undergoes and qualifies the CSM certification. CSM certification is a comprehensive program and hence the transition of project manager to scrum master can be quite tedious.

Product owner owns the product, project team executes the project while the scrum master acts as mediator between the product owner and project team. In my views, the product owner is the most powerful. This is so because he owns the product and plans the product execution accordingly. He can make the scrum master change the project execution. He has full rights over the project team. However, in reality, the product owner, the scrum master as well as the product team must complement and support each other. There must be amicable relationship between these 3 entities, so as to make the product development and execution, a successful one. If the scrum master is absent, the project facilitation and transition to different agile levels will become difficult. If the project team is absent, project development will not be possible. Similarly if there is no product owner, the scrum master and the project team will have no work as there will be no product.

Wall documentation technique is a method used by the project team, to document the various steps of the project effectively. This technique helps in requirement and objective refencing and keeping the main points in observation and consideration. There is a common wall in the project area. Here the common understanding about the project features and requirements has been enlisted. Any team member having confusion, can reference the wall and have a clarity about project execution. In my views, it is a nice way to make the overall team, have a common understanding about the project.