+91-7710033016 / +91-8291749529 support@effectivepmc.com

Agile is project development method which focuses on developing small increments of product instead of developing the entire product at one time. Agile is a time boxed, iterative approach. Agile is adopted using various methodologies such as Scrum, Lean, DSDM. Out of all Scrum is the most popular and widely used agile framework for completing complex projects.

Agile-Scrum methods of software development adopts an empirical process model, as against the defined process model used in the waterfall method.

In Scrum, the focus on Detail level planning is less. The decisions are made based on observation and experimentation rather than on detailed upfront planning. Scrum is founded on Empirical Process Control Theory, or empiricism. With Empiricism you expect the unexpected. With empiricism it is concluded that knowledge comes from experience and learning and Then you make decisions based on what is known.

Empirical process control relies on the three main ideas of transparency, inspection, and adaptation.

Transparency :

Transparency allows all facets of any Scrum process to be observed by anyone. This promotes an easy and transparent flow of information throughout the organisation and creates an open work culture. In Scrum, transparency is depicted through:

•             Artifacts

•             Project Vision Statement

•             Prioritised Product Backlog

•             Release Planning Schedule

•             Meetings – Sprint Review Meetings

•             Daily Standup Meetings

•             Information Radiators

•             Burn down Chart

•             Scrum board

Inspection :

Inspection in Scrum is depicted through:

•             Use of a common Scrum board and other information radiators

•             Collection of feedback from the customer and other stakeholders during the Develop Epic(s), Create Prioritised Product Backlog, and Conduct Release Planning processes.

•             Inspection and approval of the Deliverables by the Product Owner and the customer in the Demonstrate and Validate Sprint process.

Adaptation :

Adaptation happens as the Scrum Core Team and Stakeholders learn through transparency and inspection and then adapt by making improvements in the work they are doing. Adaptation in Scrum is depicted through:

•             Daily Standup Meetings

•             Constant Risk Identification

•             Sprint Reviews

•             Retrospectives