Page 1407 - (ISC)² CISSP Certified Information Systems Security Professional Official Study Guide
P. 1407

Build projects around motivated individuals. Give them the
                    environment and support they need, and trust them to get the job

                    done.

                    The most efficient and effective method of conveying information
                    to and within a development team is face-to-face conversation.

                    Working software is the primary measure of progress.

                    Agile processes promote sustainable development. The sponsors,
                    developers, and users should be able to maintain a constant pace
                    indefinitely.

                    Continuous attention to technical excellence and good design

                    enhances agility.

                    Simplicity—the art of maximizing the amount of work not done—is
                    essential.

                    The best architectures, requirements, and designs emerge from
                    self-organizing teams.

                    At regular intervals, the team reflects on how to become more
                    effective, then tunes and adjusts its behavior accordingly.

               The Agile development approach is quickly gaining momentum in the

               software community and has many variants, including Scrum, Agile
               Unified Process (AUP), the Dynamic Systems Development Model
               (DSDM), and Extreme Programming (XP).


               Software Capability Maturity Model

               The Software Engineering Institute (SEI) at Carnegie Mellon
               University introduced the Capability Maturity Model for Software, also
               known as the Software Capability Maturity Model (abbreviated as SW-

               CMM, CMM, or SCMM), which contends that all organizations
               engaged in software development move through a variety of maturity
               phases in sequential fashion. The SW-CMM describes the principles
               and practices underlying software process maturity. It is intended to
               help software organizations improve the maturity and quality of their
               software processes by implementing an evolutionary path from ad hoc,
               chaotic processes to mature, disciplined software processes. The idea
   1402   1403   1404   1405   1406   1407   1408   1409   1410   1411   1412