Glossary term descrip­tion

Agile stands for a ver­sa­tile and highly flex­i­ble pro­ject man­age­ment. It is an iter­a­tive and incre­men­tal approach of man­ag­ing the design and build activ­i­ties for engi­neer­ing, infor­ma­tion tech­nol­ogy, and new prod­uct or ser­vice devel­op­ment in an inter­ac­tive man­ner.

The Agile devel­op­ment par­a­digm pro­vides oppor­tu­ni­ties to assess the direc­tion of a pro­ject through­out the entire devel­op­ment life­cy­cle. This is achieved through reg­u­lar, short cycles of work, known as sprints or iter­a­tions. At the end of each iter­a­tion, the teams pre­sent a poten­tially ship­pable prod­uct incre­ment. Agile activ­i­ties are described as "iter­a­tive" and "incre­men­tal" because of the rep­e­ti­tion of the work cycles, as well as the func­tional prod­uct incre­ments they yield.

At the end of each iter­a­tion, every aspect of devel­op­ment is con­tin­u­ally revis­ited and re-eval­u­ated. This includes require­ments, design, the value added to the busi­ness, the progress made, etc. The con­tin­u­ous re-eval­u­a­tion allows any­time to steer the devel­op­ment process into another direc­tion. The results of this "inspect-and-adapt" approach to devel­op­ment greatly reduce both, devel­op­ment costs and time to mar­ket.

Because teams develop prod­ucts at the same time they're gath­er­ing require­ments, they are less likely prone to get­ting lost or stuck in overly pre­dic­tive analysing and plan­ning details of the final prod­uct. While a teams' work cycle is lim­ited to short iter­a­tions with poten­tially usable prod­uct incre­ments, stake­hold­ers gain recur­ring oppor­tu­ni­ties to test the prod­uct under real world con­di­tions and cal­i­brate its details and fea­tures for suc­cess.

Thus, Agile devel­op­ment method­ol­ogy helps com­pa­nies build the right prod­uct. It pre­serves the prod­ucts' crit­i­cal mar­ket rel­e­vance and allows it to be as com­pet­i­tive as pos­si­ble.

SHORELESS is using the Agile approach for almost every aspect of its work. Whereas SHORELESS's method­ol­ogy of choice is Ticket Dri­ven Devel­op­ment . It greatly sup­ports our Agile pro­ject man­age­ment and Scrum , the pre­ferred frame­work for all our soft­ware devel­op­ment pro­jects.

Addi­tion­ally, Ticket Dri­ven Devel­op­ment ensures a high level of trans­parency to our teams and pro­ject stake­hold­ers at every stage of their pro­jects.