Monday, May 12, 2008

Principles behind the Agile Manifesto

Some of the principles behind the Agile Manifesto are:

  1. Customer satisfaction by rapid, continuous delivery of useful software
  2. Working software is delivered frequently (weeks rather than months)
  3. Working software is the principal measure of progress
  4. Even late changes in requirements are welcomed
  5. Close, daily cooperation between business people and developers
  6. Face-to-face conversation is the best form of communication (Co-location)
  7. Projects are built around motivated individuals, who should be trusted
  8. Continuous attention to technical excellence and good design
  9. Simplicity
  10. Self-organizing teams Regular adaptation to changing circumstances

Agile Software Development Model

Agile software development is a conceptual framework for software development that promotes development iterations throughout the life-cycle of the project.
There are many agile development methods; most minimize risk by developing software in short amounts of time. Software developed during one unit of time is referred to as an iteration, which typically lasts from one to four weeks. Each iteration passes through a full software development cycle: including planning, requirements analysis, design, coding, testing, and documentation. An iteration may not add enough functionality to warrant releasing the product to market but the goal is to have an available release (without bugs) at the end of each iteration. At the end of each iteration, the team re-evaluates project priorities.
Agile methods emphasize face-to-face communication over written documents. Most agile teams are located in a single open office sometimes referred to as a scrum. At a minimum, this includes programmers and their "customers" (customers define the product; they may be product managers, a business analyst, or the clients). The office may include software testers, interaction designers, technical writers, and managers.
Agile methods also emphasize working software as the primary measure of progress. Combined with the preference for face-to-face communication, agile methods produce very little written documentation relative to other methods. This has resulted in criticism of agile methods as being undisciplined.

Tuesday, April 29, 2008

Logica CMG Interview 22 April 2008

Bug life cycle?
How to choose the tool
Problems during the testing
What did u do to solve them
How to map the requirements to d test cases (traceability matrix)
What would u do if u find a bug
What if the developer denies the bug
What bug tracking tool did u use
What r the different data it contained
What were your core responsibilities