The 12 principles behind the agile manifesto adapted to web operations

Walking once again through the twelve principles behind the Agile Manifesto, I realized how tailored they are for software development projects. Yet experience has shown that agile practices are not strictly limited to development projects, but to all areas involved in bringing a software product to the users.

Here is my version of the twelve principles adopted to fit to web platforms. Find my changes in italics:

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

Welcome changing requirements,even late in
development even after deployment. Agile processes harness change for
the customer’s competitive advantage.

Deliver Upgrade working software systems frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.

Business people and developers all technical staff must work
together daily throughout the project lifetime of the platform.

Build projects platforms 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 technical
team is face-to-face conversation.

Working software A working platform is the primary measure of progress success.

Agile processes promote sustainable development work environments.
The sponsors, developers technical staff, 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.

At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.

I think it’s helpful to broaden the adaptability of the agile principles as defined by the agile manifesto.