Overview of SCRUM

Our new approach to systems development is based on both defined and black box process management. We call the approach the SCRUM methodology (see Takeuchi and Nonaka, 1986), after the SCRUM in rugby -- a tight formation of forwards who bind together in specific positions when a scrumdown is called.

As will be discussed later, SCRUM is an enhancement of the iterative and incremental approach to delivering object-oriented software initially documented by Pittman9 and later expanded upon by Booch. It may use the same roles for project staff as outlined by Graham, for example, but it organizes and manages the team process in a new way.

SCRUM is a management, enhancement and maintenance methodology for an existing system or production prototype. It assumes existing design and code which is virtually always the case in object-oriented development due to the presence of class libraries.
SCRUM will address totally new or re-engineered legacy systems development efforts at a later date.
Software product releases are planned based on the following variables :
·  Customer requirements - how the current system needs enhancing.
·  Time pressure - what time frame is required to gain a competitive advantage.
·  Competition - what is the competition up to, and what is required to best them.
·  Quality - What is the required quality, given the above variables.
·  Vision - what changes are required at this stage to fulfill the system vision.
·  Resource - what staff and funding are available.
These variables form the initial plan for a software enhancement project. However, these variables also change during the project. A successful development methodology must take these variables and their evolutionary nature into account.