One of the most commonly used SDLCs is SCRUM.
Q. What is scrum?
-Scrum is a process framework that has been used to manage complex product development based on empirical knowledge which comes from experience and making decisions based on what is known.
-Scrum is a process framework that has been used to manage complex product development based on empirical knowledge which comes from experience and making decisions based on what is known.
- Any empirical process control has 3 pillars :
1- transparency
2- inspection
3- adaptation
1- Transparency means that the process aspects must be clear for those who are working on the product.
They must share a common language referring to the process.It means that Those performing the work and those accepting the work product must share a common definition of “Done”.
Ex. Scrum teams may share there definition of "Done" as sprint has completed and accepted.
2- Inspection means that scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances.
Inspections are most beneficial when diligently performed by skilled "Inspectors" at the point of work.
3- Adaptation means that if an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted.
Adjustment must be made as soon as possible to minimize further deviation.
Q.what does scrum team consist of ?
- The scrum team consists of a Product Owner, the Development Team, and a Scrum Master.
Scrum Teams deliver products iteratively and incrementally.
Incremental deliveries of “Done” product ensure a potentially useful version of working project is always available.
1- The Product Owner is the sole person responsible for managing the Product Backlog.
Product Backlog management includes:
a- Clearly expressing Product Backlog items.
b- Ordering the items in the Product Backlog to best achieve goals and missions.
c- Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next.
b- Ordering the items in the Product Backlog to best achieve goals and missions.
c- Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next.
2- The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint.
Only members of the Development Team create the Increment.
Q.what is the optimal development team size ?
- Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint.
- Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint.
Fewer than three Development Team members decrease interaction and results in smaller productivity gains.
Having more than nine members requires too much coordination, generates too much complexity for an empirical process to manage. The Product Owner and Scrum Master roles are not included in this count unless they are also executing the work of the Sprint Backlog.
3- The Scrum Master is a servant-leader for the Scrum Team.
The Scrum Master helps everyone to maximize the value created by the Scrum Team.
Q.what is scrum event ?
- based on inspection and adaptation scrum prescribes four formal scrum events:
1- Sprint planning.
2- Daily scrum.
3- Sprint review.
4- Sprint retrospective.
Q.what is scrum event ?
- based on inspection and adaptation scrum prescribes four formal scrum events:
1- Sprint planning.
2- Daily scrum.
3- Sprint review.
4- Sprint retrospective.
- each event in Scrum is a formal opportunity to inspect and adapt something.
These events are specifically designed to enable transparency and inspection.
Any failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt.
Q.what is a scrum sprint?
- The heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, and potentially releasable product Increment is created.
Sprints best have consistent durations throughout a development effort. A new Sprint starts immediately aftert the conclusion of the previous Sprint.
Sprints contain and consist of the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective.
During the Sprint:
- No changes are made that would endanger the Sprint Goal.
- Scope may be clarified and re-negotiated between the Product Owner and Development team as more is learned.
During the Sprint:
- No changes are made that would endanger the Sprint Goal.
- Scope may be clarified and re-negotiated between the Product Owner and Development team as more is learned.
- Each Sprint may be considered a project with no more than a one-month horizon. Like projects, Sprints are used to accomplish something.
Each Sprint has a definition of what is to be built, a design and flexible plan that will guide building it, the work, and the resultant product.
Q.what is sprint cancellation?
- A Sprint would be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change.
In general, a Sprint should be cancelled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense.
Q.what is sprint planning?
- The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team.
- Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
- Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
The Scrum Master ensures that the event takes place and that attendants understand its purpose. The Scrum Master teaches the Scrum Team to keep it within the time-box.
Sprint Planning answers the following:
- What can be delivered in the Increment resulting from the upcoming Sprint?
- How will the work needed to deliver the Increment be achieved?
1- What can be delivered in the Increment resulting from the upcoming Sprint?
- The Development Team works to forecast the functionality that will be developed during the Sprint.
- The Development Team works to forecast the functionality that will be developed during the Sprint.
The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that if completed in the Sprint, would achieve the Sprint Goal.
The entire Scrum Team collaborates on understanding the work of the Sprint.
The input to this meeting is the Product Backlog, the latest product Increment, projected capacity of the Development Team during the Sprint, and past performance of the Development Team.
The number of items selected from the Product Backlog for the Sprint is solely up to the Development Team. Only the Development Team can assess what it can accomplish over the upcoming Sprint.
Q.what is sprint goal?
After the Development Team forecasts the Product Backlog items it will deliver in the Sprint, the Scrum Team crafts a Sprint Goal. The Sprint Goal is an objective that will be met within the Sprint through the implementation of the Product Backlog, and it provides guidance to the Development Team on why it is building the Increment.
2-How will the work needed to deliver the Increment be achieved?
- Having set the Sprint Goal and selected the Product Backlog items for the Sprint, the development team decides how it will build this functionality into a “Done” product Increment during the Sprint.
After the Development Team forecasts the Product Backlog items it will deliver in the Sprint, the Scrum Team crafts a Sprint Goal. The Sprint Goal is an objective that will be met within the Sprint through the implementation of the Product Backlog, and it provides guidance to the Development Team on why it is building the Increment.
2-How will the work needed to deliver the Increment be achieved?
- Having set the Sprint Goal and selected the Product Backlog items for the Sprint, the development team decides how it will build this functionality into a “Done” product Increment during the Sprint.
Q.what is sprint backlog?
The Product Backlog items selected for this Sprint plus the plan for delivering them is called the Sprint Backlog.
- The Sprint goal is created during the Sprint Planning meeting.
The Sprint Goal gives the development team some flexibility regarding the functionality implemented within the Sprint.
The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.
Q.what is daily scrum?
- The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. This is done by inspecting the work since the last Daily Scrum and forecasting the work that could be done before the next one. The Daily Scrum is held at the same time and place each day to reduce complexity.
During the meeting, the Development Team members explain:
- What did I do yesterday that helped the Development Team meet the Sprint Goal?
- What will I do today to help the Development Team meet the Sprint Goal?
- Do I see any impediment that prevents me or the Development Team from meeting the sprint goal?
- Daily Scrums improve communications, eliminate other meetings, identify impediments to development for removal, highlight and promote quick decision-making, and improve the Development Team’s level of knowledge. This is a key inspect and adapt meeting.
Q.what is sprint review?
- A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value.
This is a four-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.
The Sprint Review includes the following elements:
- Attendees include the Scrum Team and key stakeholders invited by the Product Owner.
- The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”.
- The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved.
- The Development Team demonstrates the work that it has “Done” and answers questions about the Increment.
- Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated release of the product.
This is a four-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.
The Sprint Review includes the following elements:
- Attendees include the Scrum Team and key stakeholders invited by the Product Owner.
- The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”.
- The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved.
- The Development Team demonstrates the work that it has “Done” and answers questions about the Increment.
- Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated release of the product.
Q.what is sprint retrospective?
-The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning.
This is a three-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.
The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning.
This is a three-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.
The purpose of the Sprint Retrospective is to:
- Inspect how the last Sprint went with regards to people, relationships, process, and tools.
- Identify and order the major items that went well and potential improvements.
- Create a plan for implementing improvements to the way the Scrum Team does its work.
Q.what is product backlog?
- The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product.
The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.
- The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for
delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment.
delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment.
Q.what is increment?
- The Increment is the sum of all the 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 it must be in useable condition and meet the Scrum Team’s definition of "Done." regardless of whether the Product Owner decides to actually release it.
Good job
ردحذف