6-7 minutes<\/p>\n
Empirical process control is a core Scrum principle and distinguishes it from other agile frameworks. The Scrum Guide puts it well:<\/p>\n
\u201cScrum is not a process or a technique for building products; rather, it is a frame work within which you can employ various processes and techniques. Scrum makes clear the relative efficacy of your product management and development practices so that you can improve.\u201d<\/p>\n
Both SCRUM and LeSS Framework adopt an empirical approach (or sometimes called empiricism) to adapt to the changing requirements of the customer. Empiricism is the act of making decisions based on what is experienced. The empirical approach means working in a fact-based, experience-based, and evidence-based manner, and in particular, progress is based on observations of reality, not fictitious plans based on a large number of upfront requirements.<\/p>\n
With empirical process control, we don\u2019t fix the scope of the product nor the processes of how to build it. Instead in short cycles, we create a small shippable slice of the product, inspect what and how we create it and adapt the product and the way we build it, with built-in mechanisms for transparency to enable clear inspection. I<\/p>\n
n short, we can learn and improve upon past mistakes and experiences. The three pillars of Scrum that uphold every implementation of empirical process control are Transparency, Inspection, and Adaptation as shown in the Figure below:<\/p>\n
Transparency in Scrum can be realized by scrum tools such as Product Backlog, Task Boards and Burndown charts, Daily Stand-ups, Retrospectives, Definition of Done, Sprint Reviews, etc. These are used to transfer the flow of work through a cross-functional team. This is one of the key advantages in SCRUM \u2013 allowing visibility with regards to the progress of work and team. This means when the team is achieving its goal, those responsible for it can be recognized and appreciated for the efforts.<\/p>\n
Scrum artifacts must be frequently inspected and progress towards a goal to detect undesirable variances. Inspection in Scrum can be realized by scrum activities such as:<\/p>\n
Use of a common Scrum board and other information to make clear of the current status of the project for everyone<\/p>\n
Collection of feedback from the customer and other stakeholders during the Develop Epic(s)<\/p>\n
Create Prioritized Product Backlog, and Conduct Release Planning processes<\/p>\n
Inspection and approval of the Deliverables by the Product Owner<\/p>\n
The customer in the Demonstrate and Validate the Sprint process<\/p>\n
In an Agile world, we always embrace and Adapt changes, so that we can constantly improve. Adaptation means that we change what does not work or what could work better. It means that we constantly run small experiments, keep what is working and change when we fail. We use the results from our inspections to decide which experiment to run next, for example:<\/p>\n
Empirical Process Control vs Defined Process Control<\/p>\n
Why is Scrum based on empirical process control? Because central to the insight of Scrum is that product development is too complex a domain\u2014and with too much variation between product groups\u2014for an elaborate set of \u201ccanned\u201d defined process control formulas.<\/p>\n
As shown in the Figure below, an empirical process control expects the unexpected, while defined process control expects every piece of work to be completely understood in the upfront.<\/p>\n","protected":false},"excerpt":{"rendered":"