Summary on Agile
Its an  iterative approach to managing software development projects that focuses on continuous releases and incorporating customer feedback with every iteration.

Each iterative phase consist of -Database, back end, front end, and testing.

Int his Product owners prioritize work and Development teams select work:-product owner doesn’t push work to the team, development team can only accept work as it has capacity for it.

Mechanisms agile programs use to organize, run, and structure work in an iterative way. 

1) RoadMap - outlines how a product or solution develops over time.
 Composed of  areas of functionality, and include timelines that communicate when a feature is available

2)Requirements - Each functionality in the roadmap breaks down into a set of requirements. Agile requirements are lightweight descriptions of required functionality,

3)  Backlog -
The backlog sets the priorities for the agile program.he product owner prioritizes the work on the backlog for the engineering team. The development team then uses the prioritized backlog as its single source of truth for what work needs to be done.

4) Agile Delivery Vehicles - Agile can be implemented using various frameworks (like Scrum and Kanban) to deliver software. Scrum teams use sprints to guide development, and Kanban teams often work without fixed work intervals

5)  Agile Metrics -
Work in progress (WIP) limits keep the team, and the business, focused on delivering the highest priority work.

About Agile Ceremonies

1. Sprint Planning -

Attendees:

• Required: development team, Scrum master, product owner

When: At the beginning of a sprint.
Duration: Usually an hour per week of iteration, for example, a 2-week sprint kicks off with a 2-hour planning meeting.
Agile Framework: Scrum. (Kanban teams also plan, of course, but they are not on a fixed iteration schedule with formal sprint planning.)

product owner has a prioritized product backlog. They discuss each item with the development team, and the group collectively estimates the effort involved. The development team then makes a sprint forecast outlining how much work the team can complete from the product backlog. That body of work then becomes the sprint backlog.

2.Daily Stand-Up
Attendees:

• Required: development team, Scrum master, product owner
• Optional: team stakeholders

When: Once per day, typically in the morning.
Duration: No more than 15 minutes.
Agile Framework: Scrum and Kanban.
Purpose: Stand-ups are designed to quickly inform everyone of what’s going on across the team.

• What did I complete yesterday?
• What will I work on today?

3. Iteration Review

Attendees:

• Required: development team, Scrum master, product owner
• Optional: project stakeholders

When: At the end of a sprint or milestone.
Duration: 30–60 minutes.
Agile Framework: Scrum and Kanban

Iteration review is a time to showcase the work of the team.
Dmonstrate work finished within the iteration, and get immediate feedback from project stakeholders.


4.Retrospective

Attendees:

• Required: development team, Scrum master, product owner

When: At the end of an iteration.
Duration: 60 minutes.
Agile Framework: Scrum and Kanban.Use retrospectives to find out what’s working so the team can continue to focus on those areas. Also, find out what’s not working and use the time to find creative solutions and develop an action plan.