Difference between revisions of "Management Information Systems"
(Created page with "==Agile Methodology== ===What Is Agile?=== Agile software development is based on an incremental, iterative approach. Instead of in-depth planning at the beginning of the proj...") |
|||
| Line 6: | Line 6: | ||
Agile refers to any process that aligns with the concepts of the Agile Manifesto. In February 2001, 17 software developers met in Utah to discuss lightweight development methods. They published [http://agilemanifesto.org/ the Manifesto for Agile Software Development], which covered how they found “better ways of developing software by doing it and helping others do it” and included four values and 12 principles. The Agile Manifesto is a dramatic contrast to [https://www.pmi.org/pmbok-guide-standards the traditional Project Manager’s Body of Knowledge (PMBOK)] guide and standards. | Agile refers to any process that aligns with the concepts of the Agile Manifesto. In February 2001, 17 software developers met in Utah to discuss lightweight development methods. They published [http://agilemanifesto.org/ the Manifesto for Agile Software Development], which covered how they found “better ways of developing software by doing it and helping others do it” and included four values and 12 principles. The Agile Manifesto is a dramatic contrast to [https://www.pmi.org/pmbok-guide-standards the traditional Project Manager’s Body of Knowledge (PMBOK)] guide and standards. | ||
| + | |||
| + | |||
| + | ====12 Principles of Agile Methodology==== | ||
| + | |||
| + | The Agile Manifesto lists [http://agilemanifesto.org/principles.html 12 principles] to guide teams on how to execute with agility. These are the principles: | ||
| + | |||
| + | *Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. | ||
| + | *Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage. | ||
| + | *Deliver working software frequently, from a couple of weeks to a couple of months, with preference to the shorter timescale. | ||
| + | *Business people and developers must work together daily throughout the project. | ||
| + | *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. | ||
Revision as of 13:38, 28 May 2018
Agile Methodology
What Is Agile?
Agile software development is based on an incremental, iterative approach. Instead of in-depth planning at the beginning of the project, Agile methodologies are open to changing requirements over time and encourages constant feedback from the end users. Cross-functional teams work on iterations of a product over a period of time, and this work is organized into a backlog that is prioritized based on business or customer value. The goal of each iteration is to produce a working product.
In Agile methodologies, leadership encourages teamwork, accountability, and face-to-face communication. Business stakeholders and developers must work together to align the product with customer needs and company goals.
Agile refers to any process that aligns with the concepts of the Agile Manifesto. In February 2001, 17 software developers met in Utah to discuss lightweight development methods. They published the Manifesto for Agile Software Development, which covered how they found “better ways of developing software by doing it and helping others do it” and included four values and 12 principles. The Agile Manifesto is a dramatic contrast to the traditional Project Manager’s Body of Knowledge (PMBOK) guide and standards.
12 Principles of Agile Methodology
The Agile Manifesto lists 12 principles to guide teams on how to execute with agility. These are the principles:
- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
- Deliver working software frequently, from a couple of weeks to a couple of months, with preference to the shorter timescale.
- Business people and developers must work together daily throughout the project.
- 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.
