What is the most important Agile ceremony in Agile?

The most important Agile ceremony in Agile: (Sprint Planning )

  • The most important Agile ceremony depends on the Agile methodology. 
  • The most important ceremony is Sprint Planning.
  • Sprint planning held at the beginning of each sprint and is where the team identifies what tasks can be delivered in the sprint and how that work will be achieved. 
  • The development team, scrum master, and product owner meet to plan work, discuss work in progress, gather feedback, and more.

Other Agile ceremonies that help to empower teams of all sorts include:

  • Daily Stand-up meeting: To discuss progress and identify blockers.
  • Sprint Review: Meeting held at the end of the sprint to review the work completed and what works remain.
  • Sprint Retrospective: In this meeting they talk about What went well, what went wrong and what to improve for next sprint.


Comments

Post a Comment

Popular posts from this blog

What is CI, CD & CT?

Image
 CI (Continuous Integration): Developer frequently commit to a shared common repository using a version control system such as GIT. A Continuous integration pipeline can automatically run builds, store the artifacts, run Unit test, and even conduct code reviews using tools. We can configure the CI pipeline to be triggered every time there is a commit/merge in the code. CI workflow:
Read more

Difference between White box and Black box tests?

 White Box Testing : In white box testing the tester should know the internal logic of the code Its is mostly done by developer. The testing of software is started after the detailed design document. It is also called Clear box testing.       White box test design techniques: Control flow testing' Data flow testing Branch testing Types of White box testing: Path testing Loop testing Condition testing
Read more

What is the difference between Use Case, Test Scenario and Test Case?

Image
  Use Case:         Use Case describes the functional requirements, which help us to understand the client needs.         It is written by Product Owner / Business Analyst. Test Scenario:         Based on the Use Case ,Test Scenario is created and it is Tester responsible.         Test Scenario --- "What to Test"         Example : Validate the functionality of Login Button. Test Case:         Test Case describes Test steps/ Procedure.         Test Case --- "How to Test"         Step by step actions to be performed to verify the functionality.         It is prepared by Test Engineer. Example:   TC1: Click the submit button without entering Username and Password TC2: Click the submit button with valid credentials. Simple diagrammatic representation:           Here Test D...
Read more