Confirmed users
1,193
edits
Scrum/Guide: Difference between revisions
Jump to navigation
Jump to search
→Sprints
| Line 48: | Line 48: | ||
** This should be something that the team can fall back on. The team should feel confident in saying, "Funding dried up, but at least the last release does XYZ and does it completely." | ** This should be something that the team can fall back on. The team should feel confident in saying, "Funding dried up, but at least the last release does XYZ and does it completely." | ||
** The product created by a Sprint will not do everything, but it should provide a complete user experience | ** The product created by a Sprint will not do everything, but it should provide a complete user experience | ||
*** For example, imagine a product that allows users to share media. At the end of one Sprint, photo support is completed but video support is not. The sortware released at the end of this Sprint should allow the user to create an account, log in, and click "Post a photo" to post a photo. No link for posting | *** For example, imagine a product that allows users to share media. At the end of one Sprint, photo support is completed but video support is not. The sortware released at the end of this Sprint should allow the user to create an account, log in, and click "Post a photo" to post a photo. No link for posting videos should be provided, because in this imagined situation video upload is not completed yet. | ||
*** It would make little sense to build, say, photo upload support before building user login. That would create an incomplete user experience. | *** It would make little sense to build, say, photo upload support before building user login. That would create an incomplete user experience. | ||