|
Cockburn Scale
The Cockburn Scale, also known as the Project Classification Scale, is a method of describing how much formal process a software project requires. The scale was described in Alistair Cockburn's book ''Agile Software Development''. According to the author, the scale can be applied to other types of project, not only those that employ Agile Agile may refer to: * Agile, an entity that possesses agility Project management * Agile software development, a development method * Agile construction, iterative and incremental construction method * Agile learning, the application of incremen ... methodologies. Definition The Cockburn Scale categorizes projects according to "criticality" and "size". Process criticality is defined as the worst probable effect of an unremedied defect: * Loss of Life (L) * Loss of Essential Money (E) * Loss of Discretionary Money (D) * Loss of Comfort (C) Process size is defined as the size of the project's development staff. It is an open-ended scale, but ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Project Management
Project management is the process of leading the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. The primary constraints are scope, time, and budget. The secondary challenge is to optimize the allocation of necessary inputs and apply them to meet pre-defined objectives. The objective of project management is to produce a complete project which complies with the client's objectives. In many cases, the objective of project management is also to shape or reform the client's brief to feasibly address the client's objectives. Once the client's objectives are clearly established, they should influence all decisions made by other people involved in the project – for example, project managers, designers, contractors, and subcontractors. Ill-defined or too tightly prescribed project management objectives are detrimental to decision-ma ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Alistair Cockburn
Alistair Cockburn ( ) is an American computer scientist, known as one of the initiators of the agile movement in software development. He cosigned (with 17 others) the Manifesto for Agile Software Development. Life and career Cockburn started studying the methods of object oriented (OO) software development for IBM. From 1994, he formed "Humans and Technology" in Salt Lake City. He obtained his degree in computer science at the Case Western Reserve University. In 2003 he received his PhD degree from the University of Oslo. Cockburn helped write the Manifesto for Agile Software Development in 2001, the agile PM Declaration of Interdependence in 2005, and co-founded the International Consortium for Agile in 2009 (with Ahmed Sidky and Ash Rofail). He is a principal expositor of the use case In software and systems engineering, the phrase use case is a polyseme with two senses: # A usage scenario for a piece of software; often used in the plural to suggest situations whe ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Agile Software Development
In software development, agile (sometimes written Agile) practices include requirements discovery and solutions improvement through the collaborative effort of self-organizing and cross-functional teams with their customer(s)/ end user(s), adaptive planning, evolutionary development, early delivery, continual improvement, and flexible responses to changes in requirements, capacity, and understanding of the problems to be solved. Popularized in the 2001 ''Manifesto for Agile Software Development'', these values and principles were derived from and underpin a broad range of software development frameworks, including Scrum and Kanban. While there is much anecdotal evidence that adopting agile practices and values improves the effectiveness of software professionals, teams and organizations, the empirical evidence is mixed and hard to find. History Iterative and incremental software development methods can be traced back as early as 1957, Gerald M. Weinberg, as quoted ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
