Timeline for When does a prototype become alpha software?
Current License: CC BY-SA 3.0
20 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 8, 2014 at 14:31 | review | Close votes | |||
| Sep 9, 2014 at 0:04 | |||||
| Sep 8, 2014 at 9:19 | answer | added | Ian | timeline score: 0 | |
| Sep 7, 2014 at 3:35 | comment | added | Hot Licks | Keep in mind that software is the only engineering "discipline" (if we can use that term) where it's not only common but usual to ship the prototype. | |
| Sep 5, 2014 at 12:11 | vote | accept | gotohales | ||
| Sep 4, 2014 at 20:26 | comment | added | DA01 | @Jayfang that is an excellent point. | |
| Sep 4, 2014 at 12:33 | comment | added | Jason A. | A hint to solution lies in last line your question "... in the UX process?" Organisations that have a UX Process separate from S/W Development Process generate this Prototype / Alpha conundrum. This may help explain variety of answers below. | |
| Sep 4, 2014 at 12:03 | answer | added | kaiser | timeline score: 2 | |
| Sep 4, 2014 at 11:58 | comment | added | Bergi | Wouldn't this question be a better fit on Software Engineering than here? | |
| Sep 3, 2014 at 23:41 | answer | added | Izhaki | timeline score: 4 | |
| Sep 3, 2014 at 23:08 | comment | added | gotohales | @Izhaki I've seen both. Sometimes eager developers will try to implement our prototypes by plugging them directly into their dev environments, other times clients will continuously widen the scope of the prototype to try and evolve it into a finished product. | |
| Sep 3, 2014 at 22:39 | comment | added | Izhaki | When you say that a prototype becomes an MVP, do you mean they actually get deployed, or do you mean their scope is fairly comprehensive? | |
| Sep 3, 2014 at 22:27 | answer | added | FranMowinckel | timeline score: 2 | |
| Sep 3, 2014 at 20:56 | comment | added | DA01 | I think it's less about finding the 'point where we call it alpha' and more about 'using a development process that accommodates this from the start'. Agile would be the first thought...as Agile processes tend to be better suited for this than waterfall. Also look at LEAN UX. | |
| Sep 3, 2014 at 20:46 | comment | added | gotohales | @DA01 I suppose the hope is that along the way someone has found a decent process or set of standards for how and when to make the transition, naturally always with a bit of room for variance given the differing situations you mentioned. | |
| Sep 3, 2014 at 20:25 | history | tweeted | twitter.com/#!/StackUX/status/507263128493891584 | ||
| Sep 3, 2014 at 20:18 | answer | added | nightning | timeline score: 77 | |
| Sep 3, 2014 at 20:02 | comment | added | DA01 | I think the only answer is "when it makes sense to do so." It's going to vary wildly depending on the team, product, company, process, etc. | |
| Sep 3, 2014 at 19:50 | answer | added | Roman Reiner | timeline score: 0 | |
| Sep 3, 2014 at 19:30 | answer | added | tillinberlin | timeline score: 7 | |
| Sep 3, 2014 at 19:00 | history | asked | gotohales | CC BY-SA 3.0 |