Scrum Sprint Demo: A Comprehensive Guide
Key Takeaways: The sprint demo showcases completed sprint work, allowing the Product Owner to validate against acceptance criteria. It clarifies completed work, improves estimation, and informs the team's velocity. The focus is on demonstrable value, not technical details or problems (those belong in the retrospective). Accepted features are then integrated (released) according to a sustainable schedule.
(This section is based on Scrum: Novice to Ninja by M. David Green. Available in stores and as an ebook.)
The sprint demo, held at the sprint's conclusion, is a crucial ritual. The development team demonstrates completed work, while the Product Owner assesses completion against acceptance criteria, accepting or rejecting each story. This provides a clear picture of sprint progress and refines future estimation.
Sprint Demo Objectives:
The primary goal is to understand the sprint's output and the product's updated state post-integration. Accepted stories determine the team's velocity, improving future sprint backlog estimations.
Guests at the Sprint Demo:
While guests are welcome observers, their presence shouldn't disrupt the demo's objectives or timebox. They are observers, not participants, unless feedback is actively solicited.
Timeboxing the Sprint Demo:
Time allocation depends on the number and complexity of completed stories. A half-day is common for two-week sprints. The Scrum Master ensures adherence to the allocated time.
Combining the Demo and Retrospective:
Often, teams schedule the retrospective on the same day to minimize productivity disruption. However, this prioritizes Scrum artifacts over tangible product development – a trade-off requiring careful consideration.
Preparation for the Sprint Demo:
The demo showcases all "done" stories, regardless of release status. Each contributing team member should be prepared to explain their work. A pre-demo meeting with the Product Owner ensures alignment with acceptance criteria and prepares for demonstrations. The Scrum Master coordinates preparation and ensures the demo fits within the timebox.
Product Owner-Driven Demos:
While engineers can present, having the Product Owner conduct live testing is beneficial. Engineers know the "happy path," but the Product Owner identifies edge cases and prioritizes acceptance criteria, ensuring comprehensive testing and stakeholder engagement.
Demonstrating a Story:
The Scrum Master guides the process, systematically reviewing each story. The Product Owner reads the story and acceptance criteria while the demo is set up, ensuring everyone understands expectations. The demo focuses on the functional addition to the product, demonstrating each acceptance criterion's fulfillment. Inadequate acceptance criteria identified during the demo result in new stories for future sprints.
Avoiding Detailed Discussion of Issues:
While valuable, detailed discussions of development challenges should be deferred to the retrospective. Focusing on the product prevents the demo from becoming bogged down in technical details.
Tallying Points and Velocity:
The Scrum Master calculates the sprint's velocity based on points assigned to accepted stories. Rejected or incomplete stories are tracked and their status updated. Reports summarizing the sprint's progress are often generated.
Releasing the Stories:
Releasing integrates completed features into the live product. Release methods vary; some teams release immediately, while others group stories for larger releases. Continuous integration supports immediate release, eliminating post-demo release steps.
Continuous Integration:
With continuous integration, engineers shouldn't abandon a story until it's released and tested. This might require dedicated time for maintenance and improvement.
Release Scheduling:
Release schedules should align with the team's sustainable pace and the Product Owner's objectives, not arbitrary deadlines. Avoid rushing to meet deadlines at the expense of quality; prioritize critical features if necessary.
Frequently Asked Questions (FAQs)
(The FAQs section has been omitted for brevity, as it largely repeats information already covered in the main text.)
The above is the detailed content of Scrum Rituals: Sprint Demo. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Common problems and solutions for PHP variable scope include: 1. The global variable cannot be accessed within the function, and it needs to be passed in using the global keyword or parameter; 2. The static variable is declared with static, and it is only initialized once and the value is maintained between multiple calls; 3. Hyperglobal variables such as $_GET and $_POST can be used directly in any scope, but you need to pay attention to safe filtering; 4. Anonymous functions need to introduce parent scope variables through the use keyword, and when modifying external variables, you need to pass a reference. Mastering these rules can help avoid errors and improve code stability.

To safely handle PHP file uploads, you need to verify the source and type, control the file name and path, set server restrictions, and process media files twice. 1. Verify the upload source to prevent CSRF through token and detect the real MIME type through finfo_file using whitelist control; 2. Rename the file to a random string and determine the extension to store it in a non-Web directory according to the detection type; 3. PHP configuration limits the upload size and temporary directory Nginx/Apache prohibits access to the upload directory; 4. The GD library resaves the pictures to clear potential malicious data.

There are three common methods for PHP comment code: 1. Use // or # to block one line of code, and it is recommended to use //; 2. Use /.../ to wrap code blocks with multiple lines, which cannot be nested but can be crossed; 3. Combination skills comments such as using /if(){}/ to control logic blocks, or to improve efficiency with editor shortcut keys, you should pay attention to closing symbols and avoid nesting when using them.

AgeneratorinPHPisamemory-efficientwaytoiterateoverlargedatasetsbyyieldingvaluesoneatatimeinsteadofreturningthemallatonce.1.Generatorsusetheyieldkeywordtoproducevaluesondemand,reducingmemoryusage.2.Theyareusefulforhandlingbigloops,readinglargefiles,or

The key to writing PHP comments is to clarify the purpose and specifications. Comments should explain "why" rather than "what was done", avoiding redundancy or too simplicity. 1. Use a unified format, such as docblock (/*/) for class and method descriptions to improve readability and tool compatibility; 2. Emphasize the reasons behind the logic, such as why JS jumps need to be output manually; 3. Add an overview description before complex code, describe the process in steps, and help understand the overall idea; 4. Use TODO and FIXME rationally to mark to-do items and problems to facilitate subsequent tracking and collaboration. Good annotations can reduce communication costs and improve code maintenance efficiency.

In PHP, you can use square brackets or curly braces to obtain string specific index characters, but square brackets are recommended; the index starts from 0, and the access outside the range returns a null value and cannot be assigned a value; mb_substr is required to handle multi-byte characters. For example: $str="hello";echo$str[0]; output h; and Chinese characters such as mb_substr($str,1,1) need to obtain the correct result; in actual applications, the length of the string should be checked before looping, dynamic strings need to be verified for validity, and multilingual projects recommend using multi-byte security functions uniformly.

ToinstallPHPquickly,useXAMPPonWindowsorHomebrewonmacOS.1.OnWindows,downloadandinstallXAMPP,selectcomponents,startApache,andplacefilesinhtdocs.2.Alternatively,manuallyinstallPHPfromphp.netandsetupaserverlikeApache.3.OnmacOS,installHomebrew,thenrun'bre

TolearnPHPeffectively,startbysettingupalocalserverenvironmentusingtoolslikeXAMPPandacodeeditorlikeVSCode.1)InstallXAMPPforApache,MySQL,andPHP.2)Useacodeeditorforsyntaxsupport.3)TestyoursetupwithasimplePHPfile.Next,learnPHPbasicsincludingvariables,ech
