Thinking if Scrum Framework will work for your Project?
Here is what you need to consider before making this decision. Can your project operate under a “Defined Process”, or will it require an “Empirical Process”?
What is the difference? A defined process control approach is used on projects when the output is predictable and no change in design, scope, structure is expected after the execution. However, an Empirical approach is used when the output is not predictable as the requirements keep evolving to suit the customer requirements, stakeholder expectations throughout the project cycle.
For example, if you are going to build an office space for a client with a clear and well-defined SOW which is supported by a Fixed Price Contract, go ahead, and jump-start your project under “Defined Process Controlled” methodology as the project will be able to operate in a well-defined structure of steps that are predictable at the planning stage of the project.
If you are considering Empirical Process Controlled environment for your project, you should first analyse the chances of your SOW (Scope of Work) to evolve during the project, what type of a contract that the client is offering (should be either Time & Material or Cost Reimbursement), possibility for scope changes, technicality changes, etc. If you are able to determine that your project should adapt to change after execution, then its wise to consider an agile framework, i.e., Scrum to suit the situation. Empirical Process Control is a core value of Scrum as the Scrum Guide suggests that it is a framework to employ different techniques and processes.
Empirical is defined as “verifiable through observation” which means, when you follow an empirical process, you should inspect the changes required, quality, and identify options of adaptation. This is where Scrum framework is useful in terms of adapting to the change required based on your observations, customer’s preference, market value, etc. as the products are planned to be delivered in small portions of usable outputs. This is usually the output of “Sprint Review” where the development team demonstrates the developed product for the sprint and obtains feedback from key stakeholders, after which the Scrum team decides the changes that are required and if convinced, the new required changes are added to the Product Backlog and prioritized based on Product Owner’s guidance.