OO and Agile, or how to get your life in order

Introduction

OO or object oriented can be a resource that works within agile, agile is a methodology for get your work in order, can be described as an iterative or incremental to adapt the satisfaction for the clients to deliver the software product in a more efficient and easily way you product.

What is agile?

The methodology believes that as much as a project may seems look like another no project is equal, so the requirements have to be configured so suit the project

These requirements are separated in boxes, to specify features for the release. Iterative is the way this work so the approach is to build a deliver after each iteration.

The most popular agile methods were created and designed since 1994 with Rational Unified Process. Nowadays this specifications were collected and corrected collectively collected as the Agile methodologies , this was the Agile Manifesto, published in 2001.

Why do I need agile?

Agile helps you to build iterations to deliver it to clients or testing, every iteration can be determinate up to the developers or clients, the ones I know can last between a couple of days or weeks but in fact the iterations involves some areas to work simultaneously:

• Planning
• Design
• Coding
• Unit testing
• Acceptable testing

With object oriented similarities

Object oriented methodologies make a bigger difference when you work on a large scale, so this made the code since the 90’s maintainable and a way better to explain and understand it.

At the end the object oriented perspective at the same time as agile helps you to improve your performance and forget about developing problems to start and retrieving better work product. As you can see both methodologies help you and as the previous description I make reference to both and can apply to the both of them.