Editing Agile software development (section)

====Scrum master as a contributor====
In the Scrum framework, which claims to be consistent with agile values and principles, the ''scrum master'' role is accountable for ensuring the scrum process is followed and for coaching the scrum team through that process. A common pitfall is for a scrum master to act as a contributor. While not prohibited by the Scrum framework, the scrum master needs to ensure they have the capacity to act in the role of scrum master first and not work on development tasks. A scrum master's role is to facilitate the process rather than create the product.<ref name="agileconnection.com">{{cite web|last1=Berczuk|first1=Steve|title=Mission Possible: ScrumMaster and Technical Contributor|url=http://www.agileconnection.com/article/mission-possible-scrummaster-and-technical-contributor?page=0%2C1|website=www.agileconnection.com|access-date=2014-06-14}}</ref>

Having the scrum master also multitasking may result in too many context switches to be productive. Additionally, as a scrum master is responsible for ensuring roadblocks are removed so that the team can make forward progress, the benefit gained by individual tasks moving forward may not outweigh roadblocks that are deferred due to lack of capacity.<ref>{{cite web | url=https://aristeksystems.com/blog/how-not-to-burn-your-budget-with-agile-scrum/| title=How to Implement Agile Scrum | accessdate=2022-01-04}}</ref>