The James Webb Space Telescope (JWST) will use an event-driven system architecture to provide efficient and flexible operations as initiated by a simplified, high-level ground command interface. Event-driven operations is provided through the use of an on-board COTS JavaScript engine hosted within the payload flight software. After presenting the overall software architecture, we summarize the trade study that led to the selection of a commercial JavaScript interpreter and review our experiences developing scripts over the past year. Our script development approach is based upon the process successfully used at Space Telescope Science Institute for the last six Hubble Space Telescope science instruments. The major characteristics of our process are 1) coordinated development of the operational scripts and the flight software, 2) an incremental buildup of the operational requirements, and 3) recurring integrated testing. Our iterative script implementation process addresses how to gather requirements from a geographically dispersed team, and then how to design, build, and test the script software to accommodate the changes that are inevitable as flight hardware is built and tested. The concurrent development of the operational scripts and the flight software enables early and frequent "test-as-you-will-fly" verification, thus reducing the risk of on-orbit software problems.