Does Agile Manifesto Need Changes?

Download
Share  Add to  Flag Embed
Views:
 
Category: Education
     
 
License:   Some Rights Reserved

Presentation Description

This presentation was made by Vikrama Dhiman at Scrum India Noida Meetup on March 26. The meet up was hosted by Kronos, Noida. The topic of the meet up was 'Does Agile Manifesto need Changes' and this presentation does stick the neck out and say things that are generally avoided. Vikrama Dhiman currently works with WizIQ Courses.

Comments

Presentation Transcript

Agile Manifesto:

Agile Manifesto Does IT Need Changes? Scrum-India Meetup, Noida edit

We’ll talk about 2 edits ...:

We’ll talk about 2 edits ... Let’s Get Started

What is Agile Manifesto?:

What is Agile Manifesto? Individuals & Interactions OVER Processes & Tools Working Software OVER Comprehensive Documentation Customer Collaboration OVER Contract Negotiation Responding to Change OVER Following a Plan While there is value in the items on the right, We value the items on the left more.

Edit Number 1:

Edit Number 1 But First … Let’s Get to Know Each Other And Now … Let the Rant Start

Rant … :

Rant … Individuals & Interactions OVER Processes & Tools Working Software OVER Comprehensive Documentation Customer Collaboration OVER Contract Negotiation Responding to Change OVER Following a Plan While there is value in the items on the right, We value the items on the left more. ? ? ? ?

Rant …:

Rant … Under all conditions: Individuals & Interactions Working Software Customer Collaboration Responding to Change Processes & Tools Comprehensive Docs Contract Negotiation Following a Plan

Edit Number 1:

Edit Number 1 Individuals and Interactions over Processes and Tools Really? Like Always?

Edit Number 1 :

Edit Number 1 Focus on Individuals & Interactions AND Frame Right Policies Right People & Right Processes Know what Process to Follow and which ones to Change

Edit Number 1:

Edit Number 1 Working Software over Comprehensive Documentation Why is Working Software so Important anyways?

Edit Number 1:

Edit Number 1 Understand Business Value and Focus on Achieving That Maximize Business Value

Edit Number 1:

Edit Number 1 Customer Collaboration over Contract Negotiation

Edit Number 1:

Edit Number 1 Stakeholders as well as the Product Dev Team should Walk the Talk Fire Bad Customers, Hire Good Customers

Edit Number 1:

Edit Number 1 Responding to Change over Following a Plan

Edit Number 1:

Edit Number 1 Find the Right Balance b/w Changes & No Changes Listen and Respond to the Market Do not change too frequently or too late

Edit Number 2:

Edit Number 2 Face to face goes out of the window – in fact it will become useless The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. “ Really???

Edit Number 2:

Edit Number 2 Lack ambition Highly connected Low attention spans Self directed Individualistic Tolerant of diversity Financially responsible Stronger work ethic

Edit Number 2:

Edit Number 2

Edit Number 2:

Edit Number 2 3 Stories: Linux OS 37 Signals, RoR goodagile

Edit Number 2:

Edit Number 2 Enable teams to find their communication methods and balance

What Questions Do You Have … :

What Questions Do You Have … vikramadhiman.com