Pages

Saturday, 13 May 2023

What is empiricism in scrum agile?

Empiricism is a fundamental principle of Scrum Agile. It is a theory of knowledge that emphasizes the role of experience and evidence in the formation of ideas and beliefs. In the context of Scrum Agile, empiricism refers to the idea that knowledge comes from experience and making decisions based on what is observed and measured.

There are three pillars of empiricism in Scrum Agile:

Transparency: The Scrum team and stakeholders must have a shared understanding of what is being worked on and how progress is being made. This requires transparency in all aspects of the work, including the work itself, the progress made, and any obstacles encountered.

Inspection: Regular inspection of the work and progress made helps the team and stakeholders identify any issues or deviations from the plan. This allows the team to make adjustments and improvements to the process in order to achieve the desired outcome.

Adaptation: Based on the inspection results, the Scrum team should be able to adapt their plan and make changes to improve the outcome. This requires a willingness to experiment and learn from the results in order to continuously improve the process and achieve better outcomes.






Thursday, 8 September 2022

What is agile manifesto?

It is a document that identifies the four values and twelve principles that can be used when developing software or a product using agile scrum methodologies.

This methodology is diametrically opposed to the traditional waterfall approach, which allows the development team to deliver software/applications on a regular basis.

Four values of agile manifesto

1. Individual interaction over process and tools

2. Working software over comprehensive document

3. Customer collaboration over contract negotiation

4. Responding to change over following a plan



Twelve principles of agile manifesto

1. Satisfying customers through early and continuous delivery of valuable work.

2. Breaking big work down into smaller tasks that can be completed quickly.

3. Recognizing that the best work emerges from self-organized teams.

4. Providing motivated individuals with the environment and support they need and trusting them to get the job done.

5. Creating processes that promote sustainable efforts.

6. Maintaining a constant pace for completed work.

7. Welcoming changing requirements, even late in a project.

8. Assembling the project team and business owners on a daily basis throughout the project.

9. Having the team reflect at regular intervals on how to become more effective, then tuning and adjusting behavior accordingly.

10. Measuring progress by the amount of completed work.

11. Continually seeking excellence.

12. Harnessing change for a competitive advantage.

 

What is NFR in scrum agile?

 In Scrum Agile , NFR stands for Non-Functional Requirements . 📌 What are Non-Functional Requirements (NFRs)? These are the system quali...