Building Agile teams

In our experience, we get to talk about agility with our clients when it is no longer necessary to explain anything and the results say it all.

We managed to talk about agile teams by describing the sum of Values ​​and Principles, plus the Roles and Artifacts, and also the Ceremonies of the methodology. All of this is multiplied by the Attitude of its members.

Let’s review it briefly, then.

Essence: Teamwork – Collaboration

– Business managers and developers work together on a daily basis.

– Communication between the developers and the rest of the team is face-to-face conversation.

– The team reflects on how to be more effective periodically.

– Projects are developed around motivated individuals.

– The best architectures, requirements and designs emerge from self-organizing teams.


“We value individuals and interactions over processes and tools”

Essence: Software working – Quality

– Running software is the measure of progress.

– All of those involved must be able to maintain a constant rhythm indefinitely.

– Continuous attention to technical excellence and good design improves agility.

“We value working software over comprehensive documentation”

Essence: Close Relationship with the client – Client

– Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

– We deliver functional software frequently, and we prefer to do it in short periods of time.

– Simplicity, or the art of achieving maximum granularity of work, is essential.

“We value customer collaboration over contract negotiation”

Essence: Quick response to change – Team agility

– We accept requirements to change, even at late stages of development.

– Agile processes benefit from continuous change to provide competitive advantage to the customer.

“We value responding to change over following a plan”

I will continue sharing simply thoughts about agility…

Ing. Mariana Duobaitis