Did you ever think regards a small concept that called ‘Standardization’? -Or what Standardization
Is all about? Followed a short definition from Wikipedia:
Standardization or standardisation is the process of implementing and developing technical standards based on the consensus of different parties that include firms, users, interest groups,standards organizations and governments Standardization can help to maximize compatibility, interoperability, safety, repeatability, or quality.
Think of buying 1.5 liter bottle from a store, or asking someone at your street what is the current time – All has the accepted common format that expect to receive as an answer.
In our business, Standardization could be achieved by many ways. One example is defining the overall R&D process under ISO. This means, that most or common R&D organization are acting the same & using the same processes. Although, different organization, are using different coding languages or different set of validation tools, all will (should) deliver the end project or product by using the same Standardization.
On Scrum, different organizations implement different approaches. Followed some examples:
Roles: product owner, scrum master vs. scrum role & R&D legacy roles (Team Leader & R&D managers)
Estimation: some are not using any estimation, some use weekly or daily while other uses hourly time estimation.
Maturity: In some organization developer are also conducting the testing instead QA while on other places QA is a different department.
Sprint duration: can be varied from 1 week up to 14 weeks.
So, instead of standardization we turn to use the best practice in which is the most common scrum implementation for the organization. Yet, most common means that is accepted by most organization but not by all organization.