What’s Wrong With Traditional Approaches ?

It’s easy to see the problems with the waterfall method for software development. It assumes that every requirement can be identified before any design or coding occurs.

Can you tell a team of developers everything that needed to be in a software product before any of it was up and running ?

Can you require users to validate the design of a product even before any prototype or model was introduced to them ?

Can you require users to be experts on functional and technical specifications ?

chart1

Agile development is not a single methodology, it’s a manifesto

Many developers have lived through the nightmare of a project with no practices to guide it. The lack of effective practices leads to unpredictability, repeated error, and wasted effort.

Customers are disappointed by slipping schedules, growing budgets, and poor quality. Developers are disheartened by working ever-longer hours to produce ever-poorer software.

agile development

Please click here for further detail on Agile Manifesto .

At Agilisoft, 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.

Combining agility and long-term planning with JIRA.

Jira is a flexible and scalable project management tool for software development teams.

At Agilisoft, we use JIRA for bug tracking, issue tracking, and project management. JIRA works in a wide range of industry sectors (Among the 30,000 companies that currently use JIRA, you will find NASA, Ebay, BMW, Adobe, SalesForce, Cisco, and Linkedin).

What we like about JIRA is the huge flexibility it offers to customize every workflow and adapt it to the needs of our development teams.

JIRA offers great plugins like agile boards for KANBAN or SCRUM. For the users it’s simple and for administrators detailed enough. Flexibility is the biggest advantage of this software tool.