IT Agility Sum Up: Agile Principles I

Agility within and of itself is a strategy.

Agility is not only the ability to create the change, but also the capability to adapt to the changes. Within an IT, organizational agility should be defined as the speed in which the organization can enable the enterprise's goals and objectives as IT strategy is an integral element of business strategy. Agile is a culture as well! It is important to recognize that moving to Agile may require a significant culture change that affects the entire business. It certainly is NOT just a "development thing.”

             The Principles to Achieve IT Agility

• What is the Hardest Agile Principle to Follow - Upon well-known twelve Agile principles, some say, the hardest one for most people to get over is “individuals and interactions over processes and tools.” People are creative beings. What is the process? A process is a perception that the logic steps being identified as of now will help to create the product better; keeping in view of the facts that people learned and the related tools they have at hand. So are people always over the process, or doesn't process bring the order from chaos?

• Is Agile a set of Principles or Practices? Agile originally started out as a revolution against rigid, dogmatic practices, but the ironic is that the way some people practice Agile has come full circle back to that rigid adherence to the mechanics of how practices are implemented and have lost sight of the original intent of Agile. So here is an interesting debate: Is agile a set of principles or practices?

• The Agile “Simplicity Principle” - How to Dig it Through : “Agile principle -Simplicity--the art of maximizing the amount of work not done” is essential for Agile project success. Simplicity is also a general principle to run the digital business today. Contextually, how do you define and apply it to run project and business more successfully?

• Agile Principle Digging Through: Why is it Important to Build a Self-Organizing Team: Creating a self-organizing team is one of the hardest challenges in Agile - or rather the challenge lies in transitioning a team from its current behaviors towards one that is self-organizing. “The best architectures, requirements, and designs emerge from self-organizing teams.” Why is this Agile principle important in practice, how is self-organization related to the best architecture and structure? And how shall you apply these Agile principles to running a digital organization?

• Agile Principle Digging Through: Is Document still Valuable? One of the important points in Agile Manifesto is "Working software over comprehensive documentation." So according to this, the product is given more priority than documentation, but do we still need documents? By stating explicitly that we value the working software rather than the documentation, we will now question whether the documentation is valuable.

The “Future of CIO” Blog has reached 1.3 million page views with about 2600+ blog posting in 59+ different categories of leadership, management, strategy, digitalization, change/talent, etc. The content richness is not for its own sake, but to convey the vision and share the wisdom. Blogging is not about writing, but about thinking; it’s not just about WHAT to say, but about WHY to say, and HOW to say it. It reflects the color and shade of your thought patterns, and it indicates the peaks and curves of your thinking waves. Unlike pure entertainment, quality and professional content takes time for digesting, contemplation and engaging, and therefore, it takes the time to attract the "hungry minds" and the "deep souls." It’s the journey to amplify your voice, deepen your digital footprints, and match your way for human progression.

Posted in: Agile,Principle/Practice