#scrum_master_certification

[worldofagile]

Transitioning to Scrum | World Of Agile

Conventional, long standing advice regarding transitioning to Scrum or any Agile process has been to start with a pilot project, learn from it and then spread agile throughout the organization. This approach is the frequently used start-small pattern in which an organization selects typically one to three teams, gets them successful and then expands Scrum from there.

[worldofagile]

Scrum is not a magic-wand solution to solving all problems. In fact, if you do things incorrectly then the problems will multiply. It is better for organizations to understand Scrum and Agile correctly and apply only where required. “One-size-fits-all” is not a great approach.

[worldofagile]

Most people consider Daily Scrum is presumed to be a Status Meeting where Scrum Master takes status from the teams. One of the most common reasons for this is because people have used Project Manager as an entity for years and assume that Scrum Master is a renaming of the Project Manager role and Daily Scrum to be a new name for “Status Meeting”.

[worldofagile]

Most people feel that every Sprint MUST make an Increment which HAS to be sent to production and given to the end-users for using. This is actually not true. Sometimes, it is not possible to produce Incremental “production-ready” outcome every Sprint

[worldofagile]

Sprint Review is not a gate checking forum. It is a working session where Scrum Team and Stakeholders collaborate on how better to achieve the Product Goal.

[worldofagile]

The anti-pattern is a commonly-used process, structure of pattern of action that, despite initially appearing to be an appropriate and effective response to a problem, has more bad consequences than good ones. Here is one such pattern where many Scrum Masters become overprotective of their teams. A Scrum Master’s good intentions can become an impediment for the Scrum team’s progress and prevent the team from becoming independent.

[worldofagile]

The anti-pattern is a commonly-used process, structure of pattern of action that, despite initially appearing to be an appropriate and effective response to a problem, has more bad consequences than good ones. Here is one such pattern where people think that Scrum Master is the solver of all impediments and end up making him/her an administrator or a secretary.

[worldofagile]

This article explains Workshops for Rich Agile Communication. Typically, a workshop would last from 2 or 3 hours to a whole day.