Skip to content

Agile manifesto

June 8, 2011

Among the these principles, Four of these principles directly cover XP’s (extreme programming) four values of feedback, communication, courage, and simplicity; these and the remainder are also largely used repeatedly in the agile manifesto and its supporting principles.

Customer Satisfaction:- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Deliver working software frequently, from a couple of weeks to a couple of months,
with a preference to the shorter timescale.

Changing Requirements :- Welcome changing requirements, even late in development. Agile processes harness
change for the customer’s competitive advantage.

Working :-Business people and developers must work together daily throughout the projectGive them the environment and support they need, and trust them to get the job done.

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

Work Speed :- Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Practice continuous improvement – A key element of using iterations is to allow for learning to take place. Testers should be part of retrospectives (and if you’re not consistently adapting based on the results of retrospectives, you’re not agile enough.) Testers should also treat their career as a profession by continually learning more about testing practices, tools, and the system itself.

Simplicity :- Agile testers can help push back against an insistence on overly-elaborate features. Testers can also help the customer understand how to incrementally deliver value. They must learn an appropriate balance of iterative testing– just enough to provide the right confidence in delivering software.

Self-organize – In a true agile team, everyone has the capability to act as a tester. Agile teams know how to shift focus as needed; from time to time, At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.  The best architectures, requirements, and designs emerge from self-organizing teams.

Enjoy – The ability to help drive the process and be a true, equal contributor to a team can be extremely gratifying for an agile tester.


From → Agile Testing

Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: