1. SPS Accounts:
    Do you find yourself coming back time after time? Do you appreciate the ongoing hard work to keep this community focused and successful in its mission? Please consider supporting us by upgrading to an SPS Account. Besides the warm and fuzzy feeling that comes from supporting a good cause, you'll also get a significant number of ever-expanding perks and benefits on the site and the forums. Click here to find out more.
    Dismiss Notice
Dismiss Notice
You are currently viewing Boards o' Magick as a guest, but you can register an account here. Registration is fast, easy and free. Once registered you will have access to search the forums, create and respond to threads, PM other members, upload screenshots and access many other features unavailable to guests.

BoM cultivates a friendly and welcoming atmosphere. We have been aiming for quality over quantity with our forums from their inception, and believe that this distinction is truly tangible and valued by our members. We'd love to have you join us today!

(If you have any problems with the registration process or your account login, please contact us. If you've forgotten your username or password, click here.)

NWN Postmortem at Gamasutra

Discussion in 'Game/SP News & Comments' started by NewsPro, Dec 5, 2002.

  1. NewsPro Gems: 30/31
    Latest gem: King's Tears


    Joined:
    May 19, 2015
    Messages:
    3,599
    Likes Received:
    0
    (Originally posted by Mollusken)

    An article with reflections to the development and release of Neverwinter Nights has been posted at Gamasutra. It's written by Scott Grieg, Ray Muzyka, James Ohlen, Trent Oster and Greg Zeschuk (all from BioWare), and here's an excerpt.

    With the NWN team growing at the end to upwards of 75 people, communication of the goals of the project, and the day-to-day development decisions, became a critical necessity. We formed a tight communication network, with the leads in each area summarizing daily challenges, potential pitfalls, and areas of concern. Each significant code change required consultation with the various people responsible for the systems that would be touched - a fundamental change required a quick meeting between three to five people simply to make sure everyone who was affected would be aware of how the change would affect them. While this might superficially seem like an inefficient way to work, it did result in a number of benefits for the project and the team. First, the constant communication to achieve difficult goals brought the entire team together, and when difficult problems arose there were always a few knowledgeable people with a familiarity with the problem that could be consulted.

    Read the whole article here.
     
Sorcerer's Place is a project run entirely by fans and for fans. Maintaining Sorcerer's Place and a stable environment for all our hosted sites requires a substantial amount of our time and funds on a regular basis, so please consider supporting us to keep the site up & running smoothly. Thank you!

Sorcerers.net is a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to products on amazon.com, amazon.ca and amazon.co.uk. Amazon and the Amazon logo are trademarks of Amazon.com, Inc. or its affiliates.