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
*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
*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
*Pathfinder & Starfinder
The biggest issue with the new Character Builder:
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="Lokiare" data-source="post: 5388225" data-attributes="member: 83996"><p> <ul> <li data-xf-list-type="ul"></li> </ul><p>Well since I don't have access to that book can you summarize a few of the methods mentioned?</p><p></p><ul> <li data-xf-list-type="ul"></li> </ul><p>Since features differ in scope and time this method would yield variable numbers that wouldn't match the actual time needed. A work break down structure breaks the work down to its smallest part and then allows you to estimate each part, when added up they give you a very accurate view of how long it will take.</p><p></p><ul> <li data-xf-list-type="ul"></li> </ul><p>Estimating stories? seriously? for this to be even remotely accurate they'd have to compare projects and assignments that were almost exactly the same in scope and time to find out how long it would take. This would be really inaccurate. Updating predictions is not a planning model, it is part of the process of working in a team/project environment (if your smart). They can still update a WBS every week, so basically that part doesn't change anything.</p><p></p><p> </p><p></p><p>The heart of the issue? It is not tangential to shipping successful software. It is essential! unless of course the management doesn't care if they have to work their developers 24/7 for the last few weeks to try to hit a deadline because the project wasn't properly planned and the developers abandoned tried and true methods to try a shortcut that then turned out to be a long cut...</p><p></p><p>To summarize my point: When using an agile method an exceptional group of developers can put out decent software on time. A standard group will invariably fail. Using a factory method both the exceptional group and the standard group will put out decent software on time.</p><p></p><p>I'm also not insulting "agile" development. It has its place. Things that need to be out in a short time, that will never need updates should use "agile" development. As far as the software WotC is developing is concerned they will constantly have to update the rules system and add new ways of doing things as long as they keep putting out new books, so a factory model would be a much better way in the long run...</p></blockquote><p></p>
[QUOTE="Lokiare, post: 5388225, member: 83996"] [LIST] [/LIST] Well since I don't have access to that book can you summarize a few of the methods mentioned? [LIST] [*] [/LIST] Since features differ in scope and time this method would yield variable numbers that wouldn't match the actual time needed. A work break down structure breaks the work down to its smallest part and then allows you to estimate each part, when added up they give you a very accurate view of how long it will take. [LIST] [*] [/LIST] Estimating stories? seriously? for this to be even remotely accurate they'd have to compare projects and assignments that were almost exactly the same in scope and time to find out how long it would take. This would be really inaccurate. Updating predictions is not a planning model, it is part of the process of working in a team/project environment (if your smart). They can still update a WBS every week, so basically that part doesn't change anything. The heart of the issue? It is not tangential to shipping successful software. It is essential! unless of course the management doesn't care if they have to work their developers 24/7 for the last few weeks to try to hit a deadline because the project wasn't properly planned and the developers abandoned tried and true methods to try a shortcut that then turned out to be a long cut... To summarize my point: When using an agile method an exceptional group of developers can put out decent software on time. A standard group will invariably fail. Using a factory method both the exceptional group and the standard group will put out decent software on time. I'm also not insulting "agile" development. It has its place. Things that need to be out in a short time, that will never need updates should use "agile" development. As far as the software WotC is developing is concerned they will constantly have to update the rules system and add new ways of doing things as long as they keep putting out new books, so a factory model would be a much better way in the long run... [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Pathfinder & Starfinder
The biggest issue with the new Character Builder:
Top