tag:blogger.com,1999:blog-6199523239435234790.post9198463708577257772..comments2023-05-05T08:54:18.646-07:00Comments on Athena TV: Weaving the TapestryGHhttp://www.blogger.com/profile/10291497113580475203noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-6199523239435234790.post-75147009653229979902013-08-16T17:55:38.009-07:002013-08-16T17:55:38.009-07:00Thanks for the links! I'm intrigued.Thanks for the links! I'm intrigued. GHhttps://www.blogger.com/profile/10291497113580475203noreply@blogger.comtag:blogger.com,1999:blog-6199523239435234790.post-7353629579995085132013-08-03T08:41:39.683-07:002013-08-03T08:41:39.683-07:00Ah, I didn't get notified by a reply!
So here ...Ah, I didn't get notified by a reply!<br />So here it goes.<br /><br />The overview of the whole thing is somewhat described in http://en.wikipedia.org/wiki/Agile_software_development<br /><br />A typical SCRUM board for us is something like:<br />http://www.mountaingoatsoftware.com/system/asset/file/29/MockedTaskBoard.jpg<br /><br />When you transcend into this whole mindset and start to think about software as delivering value to people (I see entertainment as value too), you'll end up with thoughts that are well described by Liz Keogh: http://lizkeogh.com/2012/06/01/bdd-in-the-large/<br /><br />There are several books I'd recommend, but most relate way too heavily to software. There is however one that might be worth checking out, as it's unique in many ways: http://commitment-thebook.com<br /><br /><br />p.s.: is there a way to get notified of replies? :D<br /><br /><br />Anonymoushttps://www.blogger.com/profile/06265278274185419578noreply@blogger.comtag:blogger.com,1999:blog-6199523239435234790.post-43861880764285929472013-07-20T18:46:46.010-07:002013-07-20T18:46:46.010-07:00Marton, thank you for the insight and I would love...Marton, thank you for the insight and I would love to read up on that methodology, do you have any pointers for where to start?GHhttps://www.blogger.com/profile/10291497113580475203noreply@blogger.comtag:blogger.com,1999:blog-6199523239435234790.post-3502179850357494302013-07-20T12:28:49.499-07:002013-07-20T12:28:49.499-07:00This resembles my line of work. I create software....This resembles my line of work. I create software. My success lies in embracing and understanding uncertainty. What we have is a vision, or a set of goals we believe we'd like to achieve. We start off somewhere and iteratively discover our domain (using user stories, index cards, boards, etc). We build the product bit-by-bit, capability-by-capability, and we re-evaluate our understanding of the pursued outcome and the steps we've taken so far. Sometimes we pivot the vision, sometimes we discard solutions.<br /><br />I wonder how much you (could) use from Agile / Lean methodologies we use in software development. If you have the time to read up on it a bit, I'd love to read a post of your findings.Anonymoushttps://www.blogger.com/profile/06265278274185419578noreply@blogger.comtag:blogger.com,1999:blog-6199523239435234790.post-73777417981893345192013-07-20T12:06:07.637-07:002013-07-20T12:06:07.637-07:00Fascinating analysis, thanks! I recall an early va...Fascinating analysis, thanks! I recall an early variation of this on Smallville, where acts I-IV resolved the freak-of-the-week, and act V dealt with advancing the Clark/Lana/Lex arcs. As you point out, this is now a more difficult, interwoven process.DougMhttps://www.blogger.com/profile/02801228578783289083noreply@blogger.com