Investing in agile Transformation.

1. Investing in Agile
Transformation, the Future of
Enterprise Survivability
Hemanta Chandra Bhatt
25-Jan-2020

2. Investing
 Investing = saving?
 Investing via fundamental and technical analysis
 The long and short of Investing
 Returns – margins and beyond
 ROI – returns versus investment

3. Agile?

4. Manifesto
On February 11-13, 2001, at The Lodge at Snowbird ski resort in the Wasatch mountains of Utah, seventeen people met to talk, ski, relax, and
try to find common ground—and of course, to eat. What emerged was the Agile ‘Software Development’Manifesto.

5. Method?
 Agile methodologies
 Scrum, XP, FDD, TDD, ASD, DSDM, Pragmatic Programming, Crystal, Lean, RAD,
Kanban, Scrumban, Scrumbut
 Scaled Agile – SoS, SAFe, LeSS, IXP, Nexus, DAD
 Meaning of the term agile:
 Able to think and understand quickly
 Able to move quickly and easily

6. Enterprise Survivability
 Survivability
 Survive to stay where you are
 Grow to move up the ladder
 Change in culture is key to survival
 Bring the change on your own
 Change willingly when the wind blows
 Change only when forced to
 “Culture eats strategy for breakfast”

7. Agile Transformation
 Agile mindset
 More than the method
 For agile transformation for future survivability:
 100% alignment of strategy, capabilities and culture
 Appropriate organizational structure and roles
 Right person for the right role
 Authority before accountability
 True empowerment through genuine trust
 Balance between delegation and micro-management

8. Investing in Agile Transformation
 Agile as a strategic management tool
 Levers for agile transformation
 People and Mindset
 Process and Method
 Technology and Automation

9. Agile Principles
 Customer focus, involvement and feedback
 Iterative and incremental change for delivering working software
 Empowered team with high degree of communication and collaboration
 Work as per defined and agreed rhythm
 Technical excellence and simplicity in approach
 Regular introspection and improvement

10. Twelve Principles of Agile (1-3)
Our highest priority is to satisfy the customer through early and continuous
delivery of valuable software.
Welcome changing requirements, even late in development. Agile processes
harness change for the customer's competitive advantage.
Deliver working software frequently, from a couple of weeks to a couple of
months, with a preference to the shorter timescale.

11. Twelve Principles of Agile (4-6)
Business people and developers must work together daily throughout the
project.
Build projects 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 team is face-to-face conversation.

12. Twelve Principles of Agile (7-9)
Working software is the primary measure of progress.
Agile processes promote sustainable development. The sponsors, developers,
and users should be able to maintain a constant pace indefinitely.
Continuous attention to technical excellence and good design enhances
agility.

13. Twelve Principles of Agile (10-12)
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.

14.  Hemanta Chandra Bhatt is a business excellence and process
management professional with over two decades of experience. He is
currently working as the Head of Quality with a Hughes Group company.
Hemanta is a Master Black Belt and M. Tech. in Quality from the Indian
Statistical Institute. Hemanta is also a life member of Indian Society for
Quality and Quality Council of India. He is deeply passionate about
improving business systems and processes. He is also deeply interested in
economics, finance and investing.