Bug for Software Developers-Funny Pic


Haha…We know to fix our bugs properly…  😀


Work Pressure-Funny Pic

Work_Pressure_Funny Pic

Dedicated to all Programmers who face so much pressure everyday and that helps them to bring out the Diamond in them.

Happy Programming. 😀 Hope you don’t feel so much pressure in your work today.

Agile Software Development Tool-Agilefant

Agilefant is an open source tool for managing agile software development. It brings together the perspectives of daily work, long-term product and release .

It has become quite popular in the industry where  Agile Methodology is used for Software Development.

Some of its features are:

  • Backlog Management
  • Product Management
  • Iterations
  • Dailywork
  • Timesheets

The UI is easy to understand and even a newcomer becomes comfortable using it.

Visit the website for more info and downloads.


What is Agile Software Development?

An iterative and incremental (evolutionary) approach performed in a highly collaborative manner with just the right amount of ceremony to produce high quality software in a cost effective and timely manner which meets the changing needs of its stakeholders.
Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.
Core principles
–“Fits just right” process
–Continuous testing and validation
–Consistent team collaboration
–Rapid response to change
–Ongoing customer involvement
–Frequent delivery of working software

Agile can mean different things to different people, so it can be helpful to create some common ground to avoid misunderstandings.  As IBM Rational has worked with companies who are undertaking Agile Development, we’ve made some key observations:

Agile software development can be significantly different from one organization to another.  Agile is not a “one size fits all” proposition

Agilists do a lot more testing, in fact they often write a test before they write sufficient production code to fulfill that test, then they iterate

Agilists work very closely together and ideally work closely with their stakeholders

Changing requirements are seen as a competitive advantage, as long as you can act on them, not as something that you need to prevent

Agilists deliver working software every iteration, providing concrete evidence of actual progress on the project.  Daily builds, or even multiple times a day are highly desirable

Shorter iterations are desirable, from as short as one-to-two weeks, 4 weeks as a common recommendation, although up to 8 weeks will occur at scale