Agafonov Slava Digest about software

Manifesto for Agile Software Development

Agile Manifesto Development What about Agile Methodologies? Is Agile (SCRUM) still popular in big software projects? Do we still have to implement bicycle with new name for software development process? I think nope, because  we are uncovering better ways of developing

software by doing it and helping others do it Through this work we have come to value: Individuals and interactions  over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
 

It is still up to date with Agile Manifesto Development

We follow these 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 a
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.
 

Agile Manifesto Development

Summary:
The Agile Manifesto was written in February of 2001, at a summit of seventeen independent-minded practitioners of several programming methodologies. The participants didn't agree about much, but they found consensus around four main values. Supplementing the Manifesto, the Twelve Principlesfurther explicate what it is to be Agile.

Individuals and interactions over processes and toolsAgile Manifesto Development

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

Comments (2) -

  • Agafonov Viacheslav

    7/26/2011 9:40:16 AM | Reply

    Thanks Udayan, here the list of your poll:

    Which of the 12 principles behind the Agile Manifesto do you think is most important?

    1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

    2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

    3.Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

    4.Business people and developers must work together daily throughout the project.

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

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

    7.Working software is the primary measure of progress.

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

    9.Continuous attention to technical excellence and good design enhances agility.

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

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

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

Pingbacks and trackbacks (1)+

Add comment

Loading

Copyright © 2018 - Design by FS