Scrum is one of the most popular frameworks for implementing agile.

 With Scrum, the product is built in a series of fixed-length iterations called sprints that give teams a framework for shipping software on a regular cadence.

Scrum calls for four ceremonies that bring structure to each sprint:

• Sprint planning: A team planning meeting that determines what to complete in the coming sprint.
• Daily stand-up: Also known as a daily Scrum, a 15-minute mini-meeting for the software team to sync.
• Sprint demo: A sharing meeting where the team shows what they’ve shipped in that sprint.
• Sprint retrospective: A review of what did and didn’t go well with actions to make the next sprint better.

Three Essential Roles for Scrum Success 

1) The Product Owner -

• Build and manage the product backlog.
• Closely partner with the business executives and the development team to ensure everyone understands the work items in the product backlog.
• Give the development team clear guidance on which features to deliver next.
• Decide when to ship the product with the preference toward more frequent delivery.

2) The Scrum Master
They coach the team, the product owner, and the business executives on the Scrum process and look for ways to fine-tune their practice of it. An effective Scrum master deeply understands the work being done by the team and can help the team optimize their delivery flow. As the facilitator-in-chief, they schedule the needed resources (both human and logistical) for sprint planning, stand-up, sprint review, and the sprint retrospective.

3) The Scrum Development Team Team members have differing skill sets, and they cross-train each other so no one person becomes a bottleneck in the delivery of work. Strong Scrum teams approach their project with a clear “we” attitude.

 

 

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.

  
 

Salesforce Apex Code Corner: Dynamic Visualforce Page In Apex Salesforce

Salesforce Apex Code Corner: Dynamic Visualforce Page In Apex Salesforce: Hi Guys , We can create Visualforce Pages dynamically . Just need to write the script in Apex Class and avoiding on Visualforce Page. He...

Amit Blog 4Salesforce: CLI | command line interface salesforce |

Amit Blog 4Salesforce: CLI | command line interface salesforce |: Requirements for the batch process 1) Data Loader 2) JRE Step 1) Encrypting Passwords 1: Create the Key File Execute above comma...

Amit Blog 4Salesforce: Pre-Chat form for Live Agent | Post Chat / Pre Cha...

Amit Blog 4Salesforce: Pre-Chat form for Live Agent | Post Chat / Pre Cha...: Pre-Chat Form in Live Agent In live Chat this is very common to collect some information about customer like name ,email and phone numbe...