Practical:

Stay current on new thinking and approaches (e.g., Scaling Agile, Design Thinking, Product Line Management).

Fit the practice to the culture of Equinix.

​Build a foundation of Scrum and Kanban.

​Select a framework with sufficient training, consulting and support available.

Focus on measurable outcomes and not activities (always answer why we are doing what we are doing).

Bring "business-centricity" and operational excellence to our work

Tactical:

Build cross-functional, teams to manage dependencies and streamline decision-making.

Provide a path to resolve cross-cutting dependencies across architecture, security and performance

Values:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

That is, while there is value in the items on
the right, we value the items on the left more.

Principles:

1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support their needs and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity--the art of maximizing the amount of work not done--is essential.
11. The best architectures, requirements and designs emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective, then fine tunes and adjusts its behavior accordingly.​

History:

Nearly 20 years ago, 17 software developers came together in Snowbird, Utah to propose a new way of developing software “by doing it and helping others do it." Through this work, the signers of the Agile Manifesto understood how much of an impact these principles would help them in the field of software development—but they had no idea how quickly their ideas would spread beyond their industry.

What are the Scrum values?​

​Courage: Agile Team members have the courage to do the right thing and work on tough problems.​
Focus: Everyone focuses on the work of the sprint and the goals of the Agile Team.
Commitment: People personally commit to achieving the goals of the Agile Team.
Respect: Agile Team members respect each other to be capable, independent people.
Openness: The Agile Tram and its stakeholders agree to be open about all the work and the challenges with performing the work.

Tell us what Agile means to you!​ [this links to an Elovoro Form: What does Agility mean? (office.com)]

Rubrik and/or Form to collect Info