Agile methodology

[12126107906]

AGILE methodology is a practice that promotes continuous iteration of development and testing throughout the software development lifecycle of the project. Both development and testing activities are concurrent unlike the Waterfall model. I hope we got an idea of Agile!!! Now, we can step on to Agile Testing.

[12131123807]

The Agile methodology is a way to manage a project by breaking it up into several phases. It involves constant collaboration with stakeholders and continuous improvement at every stage. Once the work begins, teams cycle through a process of planning, executing, and evaluating. Continuous collaboration is vital, both with team members and project stakeholders
Agile software development principles
The Manifesto for Agile Software Development is based on twelve principles:[23]

Customer satisfaction by early and continuous delivery of valuable software.
Welcome changing requirements, even in late development.
Deliver working software frequently (weeks rather than months)
Close, daily cooperation between business people and developers
Projects are built around motivated individuals, who should be trusted
Face-to-face conversation is the best form of communication (co-location)
Working software is the primary measure of progress
Sustainable development, able to maintain a constant pace
Continuous attention to technical excellence and good design
Simplicity?the art of maximizing the amount of work not done?is essential
Best architectures, requirements, and designs emerge from self-organizing teams
Regularly, the team reflects on how to become more effective, and adjusts accordingly

[12111163010]

          Agile methodology is a type of project management process, mainly used for software development, where demands and solutions
   evolve through the collaborative effort of self-organizing and cross-functional teams and their customers.

            Four values of Agile

           individuals and interactions over processes and tools
           working software over comprehensive documentation
           customer collaboration over contract negotiation
           responding to change over following a plan.

[KD]

From your question, I assume by agile tools, that you are asking for agile tools for project management. Companies choose these tools based on their licensing budgets, existing platforms and technologies that suit their environment. For example, if the company is working with Microsoft products, then they may get some trial licenses for Microsoft foundation server and eventually start using it. Here are some of the tools that are popular in agile project management.
 Atlassian Jira/Jira Agile- This is one of the more popular tool names that I know of. This tool is used for product development tracking, organizing issues, assign work and team activities. Jira handles majority of tasks as issue types. User stories, bugs, epics, new features are among the few issue types that can be tracked, managed and shared in an agile project.
Axosoft OnTime Scrum- This is a HTML-5 based tool that provides management dashboards, burndown charts along with time tracking for coding and testing.
Microsoft visual team foundation server- This works in collaboration with the visual studio as an application life cycle management server. The tool aids in management of tasks among team members that can be used in an agile environment. Developers using visual studio for development in C#, Java or other platforms would definitely prefer using this to distribute their tasks.
Telerik TeamPulse- This is another popular tool that helps manage requirements, bugs and can work with Microsoft TFS that supports Kanban and scrum. The product offers a feedback portal, product owners can prioritize their backlog while project managers plan their sprints. This can be used in tandem with TFS, where developers use TeamPulse for tasks and integrate with visual studio with TFS.
Rally- I have had personal experience using this tool for an agile project. We used a Kanban style board for managing the tasks along with the required user stories for each sprint. Rally has excellent ease of use, one can create their user story, bug, epic or task and assign the size and severity and ownership. Based on the style used the priority of the user story, task or bug is decided and pulled in or out of the current sprint.

[12117192212]

-JIRA tool is used for:- JIRA is a tracking tool that is used for Agile testing as well as project management. It is developed for bug tracking, issue tracking and project management to software and mobile development processes. Some of the key features include capture, assign, and set priorities to do work.

[12103112907]

Agile methodology approaches the product development that is aligned with the values. It aims to deliver the right product, with incremental and frequent delivery of small chunks of functionality, through small cross-functional self-organizing teams, enabling frequent customer feedback and course correction as needed.
And it challenges to face the traditional ?waterfall Model? approaches of delivering large products in long periods of time, during which customer requirements frequently changed, resulting in the wrong products being delivered. Agile Methodology promotes continuous iteration of development and testing throughout the software development life cycle of the project.
Agile is about being responsive to the market and to the customer by responding quickly to their needs and demands and being able to change direction as the situation demands.  In agile methodology we have to work on the provide sprints or iterations. The iteration provides the information about what to work and delivering a working product to the customer, getting feedback and making changes based on the feedback.

[12215203601]

Active Collab
JIRA Agile
Agile Bench
Pivotal Tracker
Telerik TeamPulse
VersionOne
Planbox
LeanKit

[12215202401]

  Agile Methodology

#Provides continuous and incremental shippable product/software in every sprint
#Change requests can be handled even at the final stage
#Continuous client team (stakeholders) and technical team coordination is required
#No documentation is required
#Gathered requirements are converted into epics then user stories then into different tasks and then these tasks are assigned to developers

[12201187801]

 Agile software development refers to software development methodologies centred around the idea of iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. The ultimate value in Agile development is that it enables teams to deliver value faster, with greater quality and predictability, and greater aptitude to respond to change. Scrum and Kanban are two of the most widely used Agile methodologies.
                                                           Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. Agile methods or Agile processes generally promote a disciplined project management process that encourages frequent inspection and adaptation, a leadership philosophy that encourages teamwork, self-organization and accountability, a set of engineering best practices intended to allow for rapid delivery of high-quality software, and a business approach that aligns development with customer needs and company goals. Agile development refers to any development process that is aligned with the concepts of the Agile Manifesto. The Manifesto was developed by a group of fourteen leading figures in the software industry, and reflects their experience of what approaches do and do not work for software development.

                                                                    Scrum is a subset of Agile. It is a lightweight process framework for agile development, and the most widely-used one. A ?process framework? is a particular set of practices that must be followed in order for a process to be consistent with the framework. (For example, the Scrum process framework requires the use of development cycles called Sprints, the XP framework requires pair programming, and so forth). ?Lightweight? means that the overhead of the process is kept as small as possible, to maximize the amount of productive time available for getting useful work done.

[12219239203]

Agile implemented for wherever fast delivery required. Here no documentation given importance but the working code will form as documentation.
The Agile Manifesto is a document that identifies four key values and 12 principles.
Agile software development emphasizes four core values.
1.   Individual and team interactions over processes and tools
2.   Working software over comprehensive documentation
3.   Customer collaboration over contract negotiation
4.   Responding to change over following a plan
 The key 12 principles of Agile Software
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 behaviour accordingly.