Agile methodology

Incremental testing is used in agile development methods and hence, every release of the project is tested thoroughly. This ensures that any bugs in the system are fixed before the next release.

Advantages

It is possible to make changes in the project at any time to comply with the requirements.

This incremental testing minimizes risks.

Disadvantages

Constant client interaction means added time pressure on all stakeholders including the client themselves, software development and test teams.

Scrum workflow:

User Stories → Product Backlog → Sprint Planning → Sprint Backlog → Sprint (1 – 3 weeks and
daily scrum meetings) → Product → Sprint Review and retrospective Meeting

Scrum Team:

Scrum Team involves,

  1. Product Owner

  2. Scrum Master

  3. Development Team

  4. QA Team

Product Owner:

  • Product Owner is the First Point of Contact.
  • He will get input from the customers.
  • Defines the feature of the product.
  • Prioritize the features according to the market value.
  • Adjust features or priority every iteration, as needed.
  • Product Owner can Accept or Reject the work result.
  • He will define features of the product in the form of User Stories or Epics.

Scrum Master:

  • Scrum Master has the main role of facilitating and driving the Agile Process.
  • He acts like a manager/team lead for Scrum Team.
  • He leads over all the Scrum ceremonies.

Developers and QA:

  • Develop and test the software.

Product Backlog: Contains a list of all requirements (like user stories and epics). Prepared by Product
Owner.

Epic: Collection of related user stories. Epic is nothing but a large (high level) requirement.

User Story: A feature/module in a software. Define the customer needs. It is nothing but the phrasing.
of the requirement in the form of a story.

Definition of Ready (DOR):

If the below points are ready or clear regarding User Stories, is DOR.

  •   User Story is clear.
  •   User Story is testable.
  •   User Story is feasible.

Definition of Done (DOD):

It is achieved when,

  • The story is developed completely.
  • Testing (QA) complete
  • Regression around the story is complete.
  • The story meets and satisfies the acceptance criteria.
  • The feature is eligible to be deployed in production.

Task: To achieve the business requirements development team, create tasks

Sprint/Iteration: Period/time to complete (means development and testing) the user stories,
decided/selected by the Product Owner and Team. It is usually for 2-4 weeks of time.

Different ceremonies perform in the Scrum:

  1. Planning Meeting
  2. Review Meeting
  3. Retrospective Meeting
  4. Backlog Grooming Meeting

Sprint Planning Meeting: This is the meeting with the team, to define what can be delivered in the
Sprint and its duration.

development team, scrum master, product owner ==> Involve entire team
to discuss that how much work the team can complete from the product backlog. That body
of work then becomes the sprint backlog.

Scrum Meeting/Scrum Call/Standup Meeting:

This happens every day.
Points to be discussed in Daily stand-up meetings:

  1. What are we going to do today?
  2. What have I done yesterday?
  3. Any blockers/issues, due to which we are not able to proceed.

Sprint Review:

development team, scrum master, product owner ==> Iteration review is a time to
showcase the work of the team. They can be in a casual format like "demo Fridays."

Sprint Retrospective Meeting: Conducts after completion of Sprint only. The entire team including.
the Product Owner and Scrum Master should participate.
They discuss majorly on 3 things,

  1. What went well?
  2. What went wrong?
  3. Improvements are needed in the upcoming sprint.

Scrum Board/Task Board: It is showing the status of the story.
Scrum Board contains points like,

  1. User Story: It has the actual business requirement.
  2. To Do: Tasks that can be worked on.
  3. In Progress: Tasks in progress.
  4. To Verify/Testing: Tasks pending for verification or testing.
  5. Done: Completed tasks.

Zero sprint

Zero Sprint can be defined as the preparation step of the first sprint in Agile. There
are some activities that are required to be done before actually starting the project. These
activities are considered as the Zero sprint; the examples of such activities are – setting the
environment for development, preparation of backlogs etc.

Spike

Spike is the type of story that can be taken between the sprints. Spikes are commonly
used for the activities related to the design or technical issues such as research, design,
prototyping, and exploration. There are two types of spikes – functional spikes and technical
spikes.

Burn up and Burn Down chart:

A burn-down chart shows the amount of work remaining on a
project (the remaining effort), whereas a burn-up chart shows how much work has been completed
and the total scope of the project.

Velocity and Capacity:

Velocity is based on actual points completed, which is typically an average of
all previous sprints. Velocity is used to plan how many products backlog items the team should bring
into the next sprint. Capacity is how much availability the team has for the sprint.

Ideal Size of Scrum team is 7 to 9 resources.

Ideal duration of Sprint is 2-4 weeks.

Requirements are defined in Scrum as User Stories.