Timeline for Does an increment always involve a working prototype?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 8, 2020 at 10:03 | comment | added | Christophe | @Flater I see ! Thanks for pointing it out :-) | |
| Jun 8, 2020 at 9:41 | comment | added | Flater | @Christophe: I'm agreeing with you :) I agree with your answer but its phrasing left me worried that since an increment is being defined by its distinction from a prototype, it's important to realize that prototypes get mislabeled as commonly as increments do (since "unfinished" for a customer is not always the same as "unfinished" to a developer). I was just adding an asterisk, not trying to contradict your (IMO) correct answer. | |
| Jun 8, 2020 at 9:39 | comment | added | Christophe | @Flater I agree that the boundaries are in some conditions, and especially in the very first sprints somewhat fuzzy. But it’s a question of mindset: a prototype is something purposely unfinished and therefore of lower quality grade. Prototype featured do not necessarily comply with definition if done. Using this word for increments therefore might mislead and create a mental bias. If people see the product as a prototype, they might let some things not completely done with the intent of later rework and the risk of forgetting it. This is why I recommend not to use it. | |
| Jun 8, 2020 at 9:29 | comment | added | Flater | Note that it's not uncommon for "prototype" to be misused and applied to what is an increment. For example, if your current sprint goal is achieved but it functionally doesn't make sense yet (e.g. you display stored data, but users cannot cannot input this data yet, maybe because that input feature is the next sprint's goal), that's still an increment since this feature's development (i.e. the displaying of the stored data, the current sprint goal) is finished. Just because the customer doesn't consider that finished doesn't mean that it's not "done" in the scrum team sense. | |
| Jun 8, 2020 at 0:51 | comment | added | Christophe | @KansaiRobot a working software system. Because a documentation is of no value if it would be released. And a documentation is not a usable product. | |
| Jun 8, 2020 at 0:49 | comment | added | KansaiRobot | As I commented to the other answer, perhaps my understanding of the word "prototype" is wrong. I thought "usable condition" meant prototype as opposed to say.. just documentation. So in simple words what should I have at the end of a sprint? A working software system? (even without the full functionality) | |
| Jun 8, 2020 at 0:47 | history | edited | Christophe | CC BY-SA 4.0 |
added 186 characters in body
|
| Jun 8, 2020 at 0:41 | history | answered | Christophe | CC BY-SA 4.0 |