Sprint Review

At the end of a sprint cycle, two meetings are held: the “Sprint Review Meeting” and the “Sprint Retrospective”. This section describes the Sprint Review Meeting and next section describes the Sprint Retrospectives. One must understand that the objectives of both meetings are very different. At the Sprint Review Meeting: Attended by Product Owner, ScrumMaster, team […]

Read More

Daily Scrum

Each day during the sprint, a project team communication meeting occurs. This is called a Daily Scrum (meeting) and has specific guidelines: Plan the next 24 hours All members of the development team come prepared with the updates for the meeting. The meeting starts precisely on time even if some development team members are missing. […]

Read More

Sprint Planning

At the beginning of the sprint cycle , a “Sprint planning meeting” is held. Select what work is to be done Prepare the Sprint Backlog that details the time it will take to do that work, with the entire team Identify and communicate how much of the work is likely to be done during the current […]

Read More

Product Increment

The Increment is the sum of all Product Backlog Items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be “Done” which means that it should be in a useable condition and meet the Scrum Team’s definition of Done. It […]

Read More

Sprint Backlog

The list of the tasks to be executed by the Scrum Team in upcoming Sprint is called the “Sprint Backlog”. This is the second artifact in Scrum. It is common practice that the Sprint Backlog is represented on a task board which provides a constantly visible depiction of the status of the user stories in the […]

Read More

Product Backlog

“What” needs to be done in Scrum are called Backlog. Product Backlog is everything that is yet to be done and not necessarily the activities that the team has fallen behind. The product backlog is an ordered list of requirements that is maintained for a product. It consists of features, bug fixes, non-functional requirements, etc.—whatever needs to […]

Read More

Scrum Artifacts

In archaeology, the term “artifact” refers to an object that was made by a human. The Latin roots of the word artifact roughly translate to “Work of Art.” So, an artifact is something that we make, either a tool that solves a problem, or a work of art that inspires us. Scrum describes three primary […]

Read More

What is a Sprint?

A sprint  is the basic unit of development in Scrum. The sprint is a “timeboxed” effort; that is, it is restricted to a specific duration. The duration is fixed in advance for each sprint and is normally less than 30 days, although two weeks is typical. Once agreed, the timelines of the Sprint “deadline” cannot […]

Read More

Agile Manifesto

In February 2001, following 17 software developers met at the Snowbird, Utah resort, to discuss lightweight development methods. Agile Manifesto- Kent Beck Mike Beedle Arie van Bennekum Alistair Cockburn Ward Cunningham Martin Fowler James Grenning Jim Highsmith Andrew Hunt Ron Jeffries Jon Kern Brian Marick Robert C. Martin Steve Mellor Ken Schwaber Jeff Sutherland Dave […]

Read More

Scrum Events

Prescribed events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum. All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose […]

Read More
Call Now Button
WhatsApp chat