+ Log in or register to post
Results 21 to 30 of 41
Thread: Playtesting in Detail
Monday, 12th November, 2012, 03:27 PM #21
Superhero (Lvl 15)
Overview of D&D Rules Cyclopedia.
Of course, not everything should or will be a rules module.
Spoiler:There's no such thing as stories or storytelling. RPG roleplaying is game system mastering
- EN World
- has no influence
- on adverts that
- are displayed by
- Google Adsense
Monday, 12th November, 2012, 04:49 PM #22
A 1e title so awesome it's not in the book (Lvl 21)
Bear in mind a RC Mystic = Monk in AD&D parlance.
Originally Posted by Arkhandus
Monday, 12th November, 2012, 04:49 PM #23
Grandfather of Assassins (Lvl 19)
"There is no survival without order, there is no evolution without chaos."
"You have to see past the RAW to understand the rules of the game."
"And rules are OVERRATED by the way!
Monday, 12th November, 2012, 04:57 PM #24
Waghalter (Lvl 7)
I actually found this part of the article the most interesting. And potentially disturbing.
Building a product plan really shouldn't be the most challenging and exciting part of the business for the customer advocate.In parallel with all this, I'm working closely with our business team to build a product plan for the game. That's probably the most exciting and most challenging part of the process.
Its also interesting to see the misuse of Agile :-). Nice to see one buzz word being misapplied in a completely different industry with totally different design parameters and process :-).
Monday, 12th November, 2012, 05:08 PM #25
Defender (Lvl 8)
Monday, 12th November, 2012, 06:00 PM #26
Orcus on an Off-Day (Lvl 22)
Monday, 12th November, 2012, 06:08 PM #27
Waghalter (Lvl 7)
Last edited by Bravesteel; Monday, 12th November, 2012 at 06:31 PM.
A Harper holds peaceful sharing of the lands above all other goals.
Monday, 12th November, 2012, 06:13 PM #28
This scenario is a little different, as Mike is really a kine of "technical" person himself (technical in this instance meaning game designer/developer) and there may be a strong temptation to cross-pollinate and "get his hands dirty in the code", so to speak. But I've seen a few ex-programers move into the role and leave the more technical side behind them; it gives them a sometimes more insightful understanding of the process if they can resist the temptation mentioned above.
Monday, 12th November, 2012, 06:29 PM #29
Lama (Lvl 13)
Product Owner is a formal Scrum role that encompasses all aspects of "decide what product to create and the order in which it's going to be built." There's no "Customer Advocate" role in Scrum, but it's easy to see how a product owner would include advocating for the customer in his job.From my background, Product Owner and Customer Advocate are different roles. I'm still figuring out what I think about the roles being merged.
Utlimately, in a product company, the product owner is responsible for creating a commercial success. It's a good fit for Mearls' position.
I got the strong impression a few years ago that WotC's internal development shop (the one that took over the DDI tools) was using Scrum, so there's a good chance that R&D's use of Scrum migrated from the software team. That's a pretty typical progression--a software team uses Agile, which makes their work process more visible to the rest of the organization, which then adopts the non-programming aspects of Agile, typically with something Scrum-like.
Monday, 12th November, 2012, 06:30 PM #30
Myrmidon (Lvl 10)
I thought it was a great translation of agile methodology for a non IT implementation.