Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon Reflections
White Dwarf 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 Nest
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, OSR, & D&D Variants
*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!
EN Publishing
Twitter
BlueSky
Facebook
Instagram
EN World
BlueSky
YouTube
Facebook
Twitter
Twitch
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, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Upgrade your account to a Community Supporter account and remove most of the site ads.
Community
General Tabletop Discussion
Promotions/Press
The D&D 4th edition Rennaissaince: A look into the history of the edition, its flaws and its merits
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="humble minion" data-source="post: 9573877" data-attributes="member: 5948"><p>Professional software developer since 2002 here.</p><p></p><p>In (slight) defense of my profession, I probably should point out that software DOES somehow successfully get released from time to time! Looking back, I can only think of a very small number of projects I've ever worked on that could have been derailed by the loss of two people, and this is in teams numbering 5 to 90, in tiny family businesses or major banks. IF you have someone who is a knowledge silo, you break your back to share that knowledge - you assign someone to shadow them, you assign other people their work in order to share the experience, you make them run training sessions on the material, you hire in experts. </p><p></p><p>A bit more in the weeds though. The 4e books were released in June 2008. I'm a little fuzzy on recollection, but I vaguely recall that the initial intent was for the online tools to be available at release time (please correct me if I'm wrong). The murder took place in July 2008, a month after the release of the 4e paper books. The application should have almost been ready for release at this time, but instead, it was in such a state is was utterly abandoned, with WotC/Hasbro believing that it was so hopelessly irretrievable that they simply wrote off the no-doubt-significant sunk costs. At this tie they should have been deep into fixing the final few bugs, doing last-stage testing of scaling, security, performance, etc, writing documentation and tutorials. If they were at that stage, then the murder would not have resulted in the cancellation of the project. Delay sure, but the thing would have been close enough to finished to be shipped eventually. But this was clearly not the case.</p><p></p><p>Now, as I know VERY well, production delays happen, deadlines slip, and I can't imagine that, given later tragic events, the development team had been working at prime efficiency for some time.</p><p></p><p>But.</p><p></p><p>A project doesn't get into this sort of state overnight. If, on the target release date, your code is still so incomplete that the companty junks it all rather than even try to finish, the problems go back a year, at least. Where was the project manager during this process? Why hadn't additional people been brought on 12, 18 months earlier? (Yes, I know more bodies aren't a cure-all, but the project was clearly just SO far behind that they were basically a necessity, although not the only one by a long shot) Why weren't they aware that 1-2 people were irreplaceable knowledge silos and take immediate steps to fix that? Why weren't the WotC decisionmakers getting frequent updates and demos of the software, so they could twig that something was wrong? Hell, once it became clear that the software wouldn't be ready in time for the paper release, why didn't they bring in an expensive top-of-the-line sort of hired gun to try to push the thing out in a hurry? I mean, this is D&D for freak's sake - you're telling me that you couldn't find a few software geeks who'd jump at the chance?</p><p></p><p>There is a level of very basic project management competence on display here. Now, I admit I've long forgotten whether this software was developed in-house by WotC employees or whether they contracted out. If the latter, it's kinda more explicable. Subcontractors fib about stuff all the time to clients, although WotC should have had someone on site full-time if they were even remotely legit (they did with BG3 I'm pretty sure). </p><p></p><p>This project was a very big deal for WotC - I mean, how often do you release a new D&D edition, and you've been promising the online tools since day 1? But it seems to have been treated with almost neglect. I sometimes wonder whether the computer side of things was pushed on an unwilling WotC development team by WotC/Hasbro higher-ups, and then deprived of resources by people who thought that the paper game should have been the focus. This possibility might explain what happened, but of course it's complete speculation on my part. </p><p></p><p>Regardless, this whole project was very clearly in deep, deep trouble long before the murder, and the loss of personnel was only a small part of why it failed.</p></blockquote><p></p>
[QUOTE="humble minion, post: 9573877, member: 5948"] Professional software developer since 2002 here. In (slight) defense of my profession, I probably should point out that software DOES somehow successfully get released from time to time! Looking back, I can only think of a very small number of projects I've ever worked on that could have been derailed by the loss of two people, and this is in teams numbering 5 to 90, in tiny family businesses or major banks. IF you have someone who is a knowledge silo, you break your back to share that knowledge - you assign someone to shadow them, you assign other people their work in order to share the experience, you make them run training sessions on the material, you hire in experts. A bit more in the weeds though. The 4e books were released in June 2008. I'm a little fuzzy on recollection, but I vaguely recall that the initial intent was for the online tools to be available at release time (please correct me if I'm wrong). The murder took place in July 2008, a month after the release of the 4e paper books. The application should have almost been ready for release at this time, but instead, it was in such a state is was utterly abandoned, with WotC/Hasbro believing that it was so hopelessly irretrievable that they simply wrote off the no-doubt-significant sunk costs. At this tie they should have been deep into fixing the final few bugs, doing last-stage testing of scaling, security, performance, etc, writing documentation and tutorials. If they were at that stage, then the murder would not have resulted in the cancellation of the project. Delay sure, but the thing would have been close enough to finished to be shipped eventually. But this was clearly not the case. Now, as I know VERY well, production delays happen, deadlines slip, and I can't imagine that, given later tragic events, the development team had been working at prime efficiency for some time. But. A project doesn't get into this sort of state overnight. If, on the target release date, your code is still so incomplete that the companty junks it all rather than even try to finish, the problems go back a year, at least. Where was the project manager during this process? Why hadn't additional people been brought on 12, 18 months earlier? (Yes, I know more bodies aren't a cure-all, but the project was clearly just SO far behind that they were basically a necessity, although not the only one by a long shot) Why weren't they aware that 1-2 people were irreplaceable knowledge silos and take immediate steps to fix that? Why weren't the WotC decisionmakers getting frequent updates and demos of the software, so they could twig that something was wrong? Hell, once it became clear that the software wouldn't be ready in time for the paper release, why didn't they bring in an expensive top-of-the-line sort of hired gun to try to push the thing out in a hurry? I mean, this is D&D for freak's sake - you're telling me that you couldn't find a few software geeks who'd jump at the chance? There is a level of very basic project management competence on display here. Now, I admit I've long forgotten whether this software was developed in-house by WotC employees or whether they contracted out. If the latter, it's kinda more explicable. Subcontractors fib about stuff all the time to clients, although WotC should have had someone on site full-time if they were even remotely legit (they did with BG3 I'm pretty sure). This project was a very big deal for WotC - I mean, how often do you release a new D&D edition, and you've been promising the online tools since day 1? But it seems to have been treated with almost neglect. I sometimes wonder whether the computer side of things was pushed on an unwilling WotC development team by WotC/Hasbro higher-ups, and then deprived of resources by people who thought that the paper game should have been the focus. This possibility might explain what happened, but of course it's complete speculation on my part. Regardless, this whole project was very clearly in deep, deep trouble long before the murder, and the loss of personnel was only a small part of why it failed. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
Promotions/Press
The D&D 4th edition Rennaissaince: A look into the history of the edition, its flaws and its merits
Top