Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon Reflections
Columns
Weekly Digests
Weekly News Digest
Freebies, Sales & Bundles
RPG Print News
RPG Crowdfunding News
Game Content
ENterplanetary DimENsions
Mythological Figures
Opinion
Worlds of Design
Peregrine's Next
RPG Evolution
Other Columns
From the Freelancing Frontline
Monster ENcyclopedia
WotC/TSR Alumni Look Back
4 Hours w/RSD (Ryan Dancey)
The Road to 3E (Jonathan Tweet)
Greenwood's Realms (Ed Greenwood)
Drawmij's TSR (Jim Ward)
Community
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Resources
Wiki
Pages
Latest activity
Media
New media
New comments
Search media
Downloads
Latest reviews
Search resources
EN Publishing
Store
EN5ider
Adventures in ZEITGEIST
Awfully Cheerful Engine
What's OLD is NEW
Judge Dredd & The Worlds Of 2000AD
War of the Burning Sky
Level Up: Advanced 5E
Events & Releases
Upcoming Events
Private Events
Featured Events
Socials!
Twitch
YouTube
Facebook (EN Publishing)
Facebook (EN World)
Twitter
Instagram
TikTok
Podcast
Features
Top 5 RPGs Compiled Charts 2004-Present
Adventure Game Industry Market Research Summary (RPGs) V1.0
Ryan Dancey: Acquiring TSR
Q&A With Gary Gygax
D&D Rules FAQs
TSR, WotC, & Paizo: A Comparative History
D&D Pronunciation Guide
Million Dollar TTRPG Kickstarters
Tabletop RPG Podcast Hall of Fame
Eric Noah's Unofficial D&D 3rd Edition News
D&D in the Mainstream
D&D & RPG History
About Morrus
Log in
Register
What's new
Search
Search
Search titles only
By:
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Community
General Tabletop Discussion
*TTRPGs General
A brand new EN World in development
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Sammael" data-source="post: 5833495" data-attributes="member: 4475"><p>In today's world, there is no such thing as a finished software product. Iterations are the current thing, and I think they can work here as well (I won't dwell too much on the theory of agile development, just try to give some practical advice):</p><p></p><p>1. Set up a <em>fixed</em> time period for an iteration. From my prior experience, 1 week is too short, 4 weeks is too long. 2-3 weeks is ideal, but the important thing is that each iteration must last the exact same amount of time.</p><p></p><p>2. Compile a list of stuff that needs to be done. Divide it into tasks. Each task should be fairly easy to implement.</p><p></p><p>3. Set up a goal for each iteration and then choose a number of tasks from the list that lead to that goal. The goal should be some functionality that's visible to the future users of ENW.</p><p></p><p>4. Resist the temptation to do tasks that are not on your "to do" list. </p><p></p><p>5. Make daily progress reports (internal or external).</p><p></p><p>6. At the end of the iteration, you should have come close to fulfilling your goal. Try to create a demo of sorts, or, better yet, deploy a new (alpha, beta, RC) version of the site for people to see and try.</p><p></p><p>7. As people test the site, new issues <em>will</em> arise. Add them to your list of tasks to do.</p><p></p><p>8. At some point, decide which features will have to be included for the new site to be rolled out. This is the Release Candidate (RC) version. From that moment on, institute "feature lock." No new features can be added (resist the temptation) until you've ironed out as many bugs as possible.</p><p></p><p>9. Deploy the new ENW, while continuing to work on the remaining features.</p><p></p><p>10. Remember, it's perfectly fine to roll out software that doesn't do 100% of the stuff that you think it should do. Google does this <em>all the time</em>.</p><p></p><p>11. Rolling the software out will result in the most valuable thing there is - <strong>user feedback</strong>. Analyzing user feedback will help shape the future of the project - perhaps you'll realize that one of your initial ideas won't be well accepted, but you'll get a different idea that users will appreciate more. Discarding old ideas and embracing new ones is natural in software development.</p><p></p><p>Hope some of this helps <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p></blockquote><p></p>
[QUOTE="Sammael, post: 5833495, member: 4475"] In today's world, there is no such thing as a finished software product. Iterations are the current thing, and I think they can work here as well (I won't dwell too much on the theory of agile development, just try to give some practical advice): 1. Set up a [i]fixed[/i] time period for an iteration. From my prior experience, 1 week is too short, 4 weeks is too long. 2-3 weeks is ideal, but the important thing is that each iteration must last the exact same amount of time. 2. Compile a list of stuff that needs to be done. Divide it into tasks. Each task should be fairly easy to implement. 3. Set up a goal for each iteration and then choose a number of tasks from the list that lead to that goal. The goal should be some functionality that's visible to the future users of ENW. 4. Resist the temptation to do tasks that are not on your "to do" list. 5. Make daily progress reports (internal or external). 6. At the end of the iteration, you should have come close to fulfilling your goal. Try to create a demo of sorts, or, better yet, deploy a new (alpha, beta, RC) version of the site for people to see and try. 7. As people test the site, new issues [i]will[/i] arise. Add them to your list of tasks to do. 8. At some point, decide which features will have to be included for the new site to be rolled out. This is the Release Candidate (RC) version. From that moment on, institute "feature lock." No new features can be added (resist the temptation) until you've ironed out as many bugs as possible. 9. Deploy the new ENW, while continuing to work on the remaining features. 10. Remember, it's perfectly fine to roll out software that doesn't do 100% of the stuff that you think it should do. Google does this [i]all the time[/i]. 11. Rolling the software out will result in the most valuable thing there is - [b]user feedback[/b]. Analyzing user feedback will help shape the future of the project - perhaps you'll realize that one of your initial ideas won't be well accepted, but you'll get a different idea that users will appreciate more. Discarding old ideas and embracing new ones is natural in software development. Hope some of this helps :) [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*TTRPGs General
A brand new EN World in development
Top