Agile Software Development:
an Executive Briefing


Tathagat Varma
thoughtleadership.in

Standish Group

Untitled Slide

Chaos Report 2015

Agile Manifesto, 2001

4 Values

Individuals and Interactions

Working Software

Customer Collaboration

Responding to Change

12 Principles

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.

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.

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.

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.

Agile in Practice

Agile Mindset

Self-organizing Teams

Empowering Culture

Partnering customers

Deliver value

Continuous feedback

Adaptive Planning

Seek progress

Scrum: An Agile Framework

Roles

Recap

• Businesses need high agility to address uncertainty and rapid changes
• An agile mindset of problem-solving and continuous improvement is required
• Agile methods provide good guidance to get started at team-level
• However, a culture and framework that promotes self-organization is key to sustain an enterprise-level adoption