TL;DR: The effects of working in an agile style is described and the problem it addresses and the way in which it addresses the problem are introduced.
Abstract: In a previous article (2001), we introduced agile software development through the problem it addresses and the way in which it addresses the problem. Here, we describe the effects of working in an agile style.
TL;DR: The waterfall model is considered before the other models because it has had a profound effect on software development, and has additionally influenced many SDLC models prevalent today.
Abstract: This history column article provides a tour of the main software development life cycle (SDLC) models. (A lifecycle covers all the stages of software from its inception with requirements definition through to fielding and maintenance.) System development lifecycle models have drawn heavily on software and so the two terms can be used interchangeably in terms of SDLC, especially since software development in this respect encompasses software systems development. Because the merits of selecting and using an SDLC vary according to the environment in which software is developed as well as its application, I discuss three broad categories for consideration when analyzing the relative merits of SDLC models. I consider the waterfall model before the other models because it has had a profound effect on software development, and has additionally influenced many SDLC models prevalent today. Thereafter, I consider some of the mainstream models and finish with a discussion of what the future could hold for SDLC models.
TL;DR: The transition from a plan-driven to an agile software development process affects not only the development team members, but also other teams, departments, and management.
Abstract: The transition from a plan-driven to an agile software development process affects not only the development team members, but also other teams, departments, and management. Any new process will likely attract developers excited to try it while repelling those opposed to change. Thus, how an agile process is introduced into an organization significantly affects its ultimate success.
TL;DR: The second edition of CMMI Distilled, updated for CMMI version 1.1, includes more material in layman's language to meet a wider variety of reader's needs, but has not lost any of the technical content that made the first edition so successful.
Abstract: Capability Maturity Model IntegrationSM (CMMI) has rapidly become a preferred means of improving organizational processes in industry and government. Building on a decade of work with process improvement models, including the Capability Maturity Model® (CMM®) for Software and the Systems Engineering Capability Model, a team of over two hundred engineering and process improvement experts worked for three years to create this broader, more agile instrument for guiding, integrating, and appraising improvement activities. CMMI provides a single, integrated framework for improving processes throughout an organization, enhancing the quality and efficiency of the organization as a whole.The CMMI Product Suite is rich in detail and guidance, but correspondingly large and somewhat complex. The sheer volume of information it presents can seem overwhelming. CMMI Distilled reduced that complexity with a fresh and approachable introduction to the key elements of CMMI and integrated process improvement.This new edition of CMMI Distilled, updated for CMMI version 1.1, includes more material in layman's language to meet a wider variety of reader's needs, but has not lost any of the technical content that made the first edition so successful. Written for those new to model-based process improvement, it also offers insights that can help even battle-scarred process improvement veterans and experienced systems, software and quality engineers perform better. CMMI® Distilled, Second Edition is especially appropriate for executives and managers who need to understand why process improvement is valuable, why CMMI is a tool of choice, and how to maximize the return on their efforts and investments.The three authors have been involved with CMMI since its inception, and they bring a wealth of their own experience and knowledge to this book. They highlight the pitfalls and short cuts that are all too often learned by costly experience. Above all, they provide a context for understanding why CMMI is the fastest growing process improvement framework in the world. 0321186133B06272003
TL;DR: This comparative summarizes the steps an organization would have to go through in order to make the best possible choice when selecting the right software development life cycle (SDLC).
Abstract: Organizations that are developing software solution are faced with the difficult choice of picking the right software development life cycle (SDLC). The waterfall model is a sequential design process, often used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases. The V-model represents a software development process which may be considered an extension of the waterfall model. Instead of moving down in a linear way, the process steps are bent upwards after the coding phase, to form the typical V shape Agile Modeling is a practice-based methodology for modelling and documentation of software-based systems. It is intended to be a collection of values, principles, and practices for modelling software that can be applied on a software development project in a more flexible manner than traditional Modelling methods. This comparative summarizes the steps an organization would have to go through in order to make the best possible choice.