Value Driven Agile Adoption

Slide 1: Value-Driven Agile Adoption Ahmed Sidky, Ph.D. Certified Scrum Master Director of Business Technology, X2A Consulting A Quick Introduction • Originally a Developer • Earned a Ph.D. in Agile • Agile Coach and Trainer • Conferences – XP – Agile – ABC – Agile Egypt, India

Slide 2: Expectation-Driven Tutorial (EDT) EXPECTATIONS ??? Why adopt Agile Industry Results* Customer “Exceeding expectations for both the project delivery timeline and scope” - Small Business Executive Satisfaction Speed 25-50% reduction in Time To Market “Lean Agile has really fostered a team spirit! Everyone has been willing to pitch in and get the project done unlike most projects where everyone seems to Team Morale wait for work to be 'passed over the wall” - Business Services Tech Delivery Team Member Cost 10-30% cost reduction Defects 20-65% reduction in number of defects * Source: IBM Expert interviews, ThoughtWorks experts interview, Forrester, Literature research

Slide 3: The Challenge How to adopt agile practices • What does it mean to be agile? • How do we know we are ready? • What is the first step? • Which practices or methods should we adopt? • Do we need an agile coach ? Exercise Agile Adoption Simulation

Slide 4: Get into groups Please get into groups of 6-7 members Divide each group into 2 Teams Team representing the Team representing the agile coaches company adopting agile

Slide 5: For the next 15 minutes Get familiar with the set of cards representing 40 different agile practices. Coaches Ignore the different colors on the cards Create an imaginary or real company that will adopt agile. Use the template handed out – it contains 8 aspects of a company that should be discussed by the group to get familiar with Company your new imaginary company. For the next 30 minutes You are hired by the company team to identify the set of agile practices they need to adopt because they want to be “agile”. You can hand the company as Coaches many cards as you wish and as frequent as you see appropriate. As the hiring company, you have the right to accept or reject any practice Company suggested by the coaching team.

Slide 6: Please Remember Do not justify to the company team why you picked a certain practice Coaches After the coaching team hands you a practice, do not discuss it with them, Company just accept it or reject it Results • How many practices did the successfully adopt? • ` • How many practices did you reject? Group representing the • Overall Satisfaction? company adopting agile

Slide 7: As a team … Write three things you learned about adopting agile. Write three hardships you have identified about adopting agile. Changing the way we think about agile adoption SIDKY AGILE MEASUREMENT INDEX

Slide 8: Understanding Agile Software Development Defines in detail how this is Agile implemented in practice Practices Agile Defines a set of ways Principles to meet the values Agile Values Defines the set of most important beliefs of what is truly important The need to respond to constant The fundamental reason change for a “new” paradigm A Value-based roadmap to agility Sidky’s Agile Measurement Index (SAMI)

Slide 9: Level 5 Encompassing Establishing a vibrant and all-encompassing environment to sustain agility Level 4 Adaptive Responding to change through multiple levels of feedback Level 3: Integrated Developing high quality, working software in an efficient and integrated manner Level 2: Evolutionary Deliver software early and continuously Level 1: Collaborative Enhancing communication and collaboration Level 5 Encompassing Establishing a vibrant and all-encompassing environment to sustain agility Level 4 Adaptive Responding to change through multiple levels of feedback Level 3: Integrated What practices will help enhance communication and collaboration Developing high quality, working software in an efficient and integrated manner for this team in this company. Level 2: Evolutionary Deliver software early and continuously Level 1: Collaborative Enhancing communication and collaboration

Slide 10: Understanding Agile Software Development Defines in detail how this is Agile implemented in practice Practices Agile Defines a set of ways Principles to meet the values Agile Values Defines the set of most important beliefs of what is truly important The need to respond to constant The fundamental reason change for a “new” paradigm Agile Principles A. Embrace change to deliver customer value B. Plan and deliver software frequently Agile Principles C. Human centric 5 A B C D E D. Technical excellence 4 Agile Levels 3 2 E. Collaboration with Business People 1 Empty Agile Levels with Agile Principles

Slide 11: Embrace Change Principles of an Plan and Deliver Collaboration with to Deliver Human Centric Technical Excellence agile process : Software Frequently Business People Customer Value Level 5 Encompassing Establishing a vibrant and all-encompassing environment to sustain agility Level 4 Adaptive Responding to change through multiple levels of feedback Level 3: Integrated Developing high quality, working software in an efficient and integrated manner Level 2: Evolutionary Deliver software early and continuously Level 1: Collaborative Enhancing communication and collaboration Embrace Change Principles of an Plan and Deliver Collaboration with to Deliver Human Centric Technical Excellence agile process : Software Frequently Business People Customer Value Level 5 Encompassing Establishing a vibrant and all-encompassing environment to sustain agility Level 4 Adaptive Responding to change through multiple levels of feedback Level 3: What practices will help enhance Integrated communication and collaboration for this team in this company Developing high quality, working software in an efficient and integrated manner from a planning perspective. Level 2: Evolutionary Deliver software early and continuously Level 1: Collaborative Enhancing communication and collaboration

Slide 12: Understanding Agile Software Development Defines in detail how this is Agile implemented in practice Practices Agile Defines a set of ways Principles to meet the values Agile Values Defines the set of most important beliefs of what is truly important The need to respond to constant The fundamental reason change for a “new” paradigm Embrace Change Plan and Deliver Collaboration with to Deliver Human Centric Technical Excellence Software Frequently Business People Customer Value Test Driven Development Level 5 Low Process Frequent Face-to-face Paired Programming Ceremony Agile Project Estimation Ideal Agile Physical interaction between Encompassing Setup developers & Users No/minimal number of (Collocated) Cockburn Level -1 or 1b people on team Collaborative, Client Driven Representative, Authorized, Daily Progress Tracking Iterations Committed and Smaller and More Meetings Level 4 Knowledgeable Frequent Releases (CRACK) Customer Adaptive Customer (4-8 Weeks) Agile Documentation (from Immediately Accessible Agile Modeling) Satisfaction Adaptive Planning Feedback Customer contract revolves User Stories around commitment of collaboration, not features Continuous Integration Self Organizing Risk Driven Iterations Teams Continuous Improvement Level 3: (i.e. Refactoring) Integrated Maintain a list of all Frequent face-to-face Have around 30% of remaining features communication Cockburn Level 2 and (Backlog) between Level 3 people on team the team Automated Unit Tests Software Configuration Continuous Delivery Management Level 2: (Incremental-Iterative Customer Contract Evolutionary development) Tracking Iteration through Evolutionary Requirements Working Software reflective of Evolutionary Development Planning at different levels No Big Design Up Front (BDUF) Coding Standards Reflect and tune Collaborative teams Knowledge Sharing Tools Level 1: Process Collaborative Planning (Wikis, Blogs) Customer Commitment to Collaborative Empowered and work with Developing Team Motivated Teams Task Volunteering not Task Assignment

Slide 13: Using the Sidky Agile Measurement Index (SAMI) CREATING A ROADMAP TO AGILITY Embrace Change Principles of an Plan and Deliver Collaboration with to Deliver Human Centric Technical Excellence agile process : Software Frequently Business People Customer Value Level 5 Encompassing Establishing a vibrant and all-encompassing environment to sustain agility Level 4 Adaptive Responding to change through multiple levels of feedback Level 3: Integrated Developing high quality, working software in an efficient and integrated manner Level 2: Evolutionary Deliver software early and continuously Level 1: Collaborative Enhancing communication and collaboration

Slide 14: The whole picture THE AGILE ADOPTION FRAMEWORK The Agile Adoption Framework • To guide and assist organizations adopting agile practices • Sidky Agile Measurement Index (SAMI) – Organize the Practices based on value • 4 Stage Process – Steps to guide the process with a focus on potential and readiness

Slide 15: The Agile Adoption Framework 4-Stage Process Stage 1 Stage 2 Stage 3 Stage 4 Discontinuing Factors Project Level Assessment Organizational Assessment Reconciliation The Agile Adoption Framework 4-Stage Process Stage 1 Stage 2 Stage 3 Stage 4 Discontinuing Factors Project Level Assessment Organizational Assessment Reconciliation

Slide 16: Embrace Change Plan and Deliver Collaboration with to Deliver Human Centric Technical Excellence Software Frequently Business People Customer Value Test Driven Development Level 5 Low Process Frequent Face-to-face Paired Programming Ceremony Agile Project Estimation Ideal Agile Physical interaction between Encompassing Setup developers & Users No/minimal number of (Collocated) Cockburn Level -1 or 1b people on team Collaborative, Client Driven Representative, Authorized, Daily Progress Tracking Iterations Committed and Smaller and More Meetings Level 4 Knowledgeable Frequent Releases (CRACK) Customer Adaptive Customer (4-8 Weeks) Agile Documentation (from Immediately Accessible Agile Modeling) Satisfaction Adaptive Planning Feedback Customer contract revolves User Stories around commitment of collaboration, not features Continuous Integration Self Organizing Risk Driven Iterations Teams Continuous Improvement Level 3: (i.e. Refactoring) Integrated Maintain a list of all Frequent face-to-face Have around 30% of remaining features communication Cockburn Level 2 and (Backlog) between Level 3 people on team the team Automated Unit Tests Software Configuration Continuous Delivery Management Level 2: (Incremental-Iterative Customer Contract Evolutionary development) Tracking Iteration through Evolutionary Requirements Working Software reflective of Evolutionary Development Planning at different levels No Big Design Up Front (BDUF) Coding Standards Reflect and tune Collaborative teams Knowledge Sharing Tools Level 1: Process Collaborative Planning (Wikis, Blogs) Customer Commitment to Collaborative Empowered and work with Developing Team Motivated Teams Task Volunteering not Task Assignment Embrace Change Plan and Deliver Collaboration with to Deliver Human Centric Technical Excellence Software Frequently Business People Customer Value Test Driven Development Level 5 Low Process Frequent Face-to-face Paired Programming Ceremony Agile Project Estimation Ideal Agile Physical interaction between Encompassing Setup developers & Users No/minimal number of (Collocated) Indicator Sheet Cockburn Level -1 or 1b people on team Nominal Values ID Statements Collaborative, Client Driven V W X Y Z Representative, Authorized, Daily Progress Tracking Iterations Strongly Neither Agree Committed and D1 Your manager does not micro-manage you or your work. Smaller and More Tend to Disagree Meetings Tend to Agree Strongly Agree Disagree nor Disagree Knowledgeable Level 4 Frequent Releases Your manager encourages you to be (4-8 Weeks) creative and does not Strongly Neither Agree (CRACK) Customer AdaptiveD2 Customer what to do exactly. dictate to you Disagree Tend to Disagree Agile Documentation (from Agree nor Disagree Tend to Strongly Agree Immediately Accessible Agile Modeling) Satisfaction Adaptive Planning Your manager gives you the authority to make decisions Strongly Neither Agree D3 Feedback Tend to Disagree Tend to Agree Strongly Agree Customer contract revolves without referring back to him/her. Disagree Usernor Disagree Stories around commitment of …… …… …… …… …… …… …… collaboration, not features Continuous Integration Self Organizing Risk Driven Iterations Teams Continuous Improvement Level 3: (i.e. Refactoring) Integrated Organizational Characteristic of all Maintain a list Assessment Table for Collaborative Planning of Frequent face-to-face Have around 30% remaining features communication Cockburn Level 2 and Characteristic (Backlog) determine: between Assessment Level 3 people on team To Indicators to be assessed the team Method Whether or not a collaborative or a command-control Automated Unit Tests relation exists between managers and subordinates. Management The management style is an indication of whether or Interviewing D1, D2, D3, Software Configuration Style not management trusts Delivery Continuous the developers and vice- Management versa. Level 2: (Incremental-Iterative Customer Contract Manager Evolutionary Whether development) or not management is supportive of or Tracking Iteration through Evolutionary Interviewing …… reflective of Evolutionary Buy-In Requirements resistive to having a collaborative environment Working Software Development Planning at different …… …… …… …… levels No Big Design Up Front (BDUF) Coding Standards Reflect and tune Collaborative teams Knowledge Sharing Tools Level 1: Process Collaborative Planning (Wikis, Blogs) Customer Commitment to Collaborative Empowered and work with Developing Team Motivated Teams Task Volunteering not Task Assignment

Slide 17: Embrace Change Plan and Deliver Collaboration with to Deliver Human Centric Technical Excellence Software Frequently Business People Customer Value Test Driven Development Level 5 Low Process Frequent Face-to-face Paired Programming Ceremony Agile Project Estimation Ideal Agile Physical interaction between Encompassing Setup developers & Users No/minimal number of (Collocated) Cockburn Level -1 or 1b people on team Collaborative, Client Driven Representative, Authorized, Daily Progress Tracking Iterations Committed and Smaller and More Meetings Level 4 Knowledgeable Frequent Releases (CRACK) Customer Adaptive Customer (4-8 Weeks) Agile Documentation (from Immediately Accessible Agile Modeling) Satisfaction Adaptive Planning Feedback Customer contract revolves User Stories around commitment of collaboration, not features Continuous Integration Self Organizing Risk Driven Iterations Teams Continuous Improvement Level 3: (i.e. Refactoring) Integrated Maintain a list of all Frequent face-to-face Have around 30% of Identify practices whose adoption remaining features (Backlog) communication between Cockburn Level 2 and Level 3 people on team depend on characteristics that the team Automated Unit Tests can not be changed. Software Configuration Continuous Delivery Management Level 2: (Incremental-Iterative Customer Contract Evolutionary development) Tracking Iteration through Evolutionary Requirements Working Software reflective of Evolutionary Development Planning at different levels No Big Design Up Front (BDUF) Coding Standards Reflect and tune Collaborative teams Knowledge Sharing Tools Level 1: Process Collaborative Planning (Wikis, Blogs) Customer Commitment to Collaborative Empowered and work with Developing Team Motivated Teams Task Volunteering not Task Assignment Embrace Change Plan and Deliver Collaboration with to Deliver Human Centric Technical Excellence Software Frequently Business People Customer Value Test Driven Development Level 5 Low Process Frequent Face-to-face Paired Programming Ceremony Agile Project Estimation Ideal Agile Physical interaction between Encompassing Setup developers & Users No/minimal number of (Collocated) Cockburn Level -1 or 1b people on team Collaborative, Client Driven Representative, Authorized, Daily Progress Tracking Iterations Committed and Smaller and More Meetings Level 4 Knowledgeable Frequent Releases (CRACK) Customer Adaptive Customer (4-8 Weeks) Agile Documentation (from Immediately Accessible Agile Modeling) Satisfaction Adaptive Planning Feedback Customer contract revolves User Stories around commitment of collaboration, not features Continuous Integration Self Organizing Risk Driven Iterations Teams Continuous Improvement Level 3: (i.e. Refactoring) Integrated Maintain a list of all Frequent face-to-face Have around 30% of Identify practices whose adoption remaining features (Backlog) communication between Cockburn Level 2 and Level 3 people on team depend on characteristics that the team Automated Unit Tests can not be changed. Software Configuration Continuous Delivery Management Level 2: (Incremental-Iterative Customer Contract Evolutionary development) Tracking Iteration through Evolutionary Requirements Working Software reflective of Evolutionary Development Planning at different levels No Big Design Up Front (BDUF) Coding Standards Reflect and tune Collaborative teams Knowledge Sharing Tools Level 1: Process Collaborative Planning (Wikis, Blogs) Customer Commitment to Collaborative Empowered and work with Developing Team Motivated Teams Task Volunteering not Task Assignment

Slide 18: Embrace Change Plan and Deliver Collaboration with to Deliver Human Centric Technical Excellence Software Frequently Business People Customer Value Test Driven Development Level 5 Low Process Frequent Face-to-face Paired Programming Ceremony Agile Project Estimation Ideal Agile Physical interaction between Encompassing Setup developers & Users No/minimal number of (Collocated) Cockburn Level -1 or 1b people on team Collaborative, Client Driven Representative, Authorized, Daily Progress Tracking Iterations Committed and Smaller and More Meetings Level 4 Knowledgeable Frequent Releases (CRACK) Customer Adaptive Customer (4-8 Weeks) Agile Documentation (from Immediately Accessible Agile Modeling) Satisfaction Adaptive Planning Feedback Customer contract revolves User Stories around commitment of collaboration, not features Continuous Integration Self Organizing Risk Driven Iterations Teams Continuous Improvement Level 3: (i.e. Refactoring) Integrated Maintain a list of all Frequent face-to-face Have around 30% of remaining features communication Cockburn Level 2 and (Backlog) between Level 3 people on team the team Automated Unit Tests Software Configuration Continuous Delivery Management Level 2: (Incremental-Iterative Customer Contract Evolutionary development) Tracking Iteration through Evolutionary Requirements Working Software reflective of Evolutionary Development Planning at different levels No Big Design Up Front (BDUF) Coding Standards Reflect and tune Collaborative teams Knowledge Sharing Tools Level 1: Process Collaborative Planning (Wikis, Blogs) Customer Commitment to Collaborative Empowered and work with Developing Team Motivated Teams Task Volunteering not Task Assignment Embrace Change Plan and Deliver Collaboration with to Deliver Human Centric Technical Excellence Software Frequently Business People Customer Value Test Driven Development Level 5 Low Process Frequent Face-to-face Paired Programming Ceremony Agile Project Estimation Ideal Agile Physical interaction between Encompassing Setup developers & Users No/minimal number of (Collocated) Cockburn Level -1 or 1b people on team Collaborative, Client Driven Representative, Authorized, Daily Progress Tracking Iterations Committed and Smaller and More Meetings Level 4 Knowledgeable Frequent Releases (CRACK) Customer Adaptive Customer (4-8 Weeks) Agile Documentation (from Immediately Accessible Agile Modeling) Satisfaction Adaptive Planning Feedback Customer contract revolves User Stories around commitment of collaboration, not features Continuous Integration Self Organizing Risk Driven Iterations Teams Continuous Improvement Level 3: (i.e. Refactoring) Integrated Maintain a list of all Frequent face-to-face Have around 30% of remaining features communication Cockburn Level 2 and (Backlog) between Level 3 people on team the team Automated Unit Tests Software Configuration Continuous Delivery Management Level 2: (Incremental-Iterative Customer Contract Evolutionary development) Tracking Iteration through Evolutionary Requirements Working Software reflective of Evolutionary Development Planning at different levels No Big Design Up Front (BDUF) Coding Standards Reflect and tune Collaborative teams Knowledge Sharing Tools Level 1: Process Collaborative Planning (Wikis, Blogs) Customer Commitment to Collaborative Empowered and work with Developing Team Motivated Teams Task Volunteering not Task Assignment

Slide 19: The Agile Adoption Framework 4-Stage Process Stage 1 Stage 2 Stage 3 Stage 4 Discontinuing Factors Project Level Assessment Organizational Assessment Reconciliation Embrace Change Plan and Deliver Collaboration with to Deliver Human Centric Technical Excellence Software Frequently Business People Customer Value Test Driven Development Level 5 Low Process Frequent Face-to-face Paired Programming Ceremony Agile Project Estimation Ideal Agile Physical interaction between Encompassing Setup developers & Users No/minimal number of (Collocated) Cockburn Level -1 or 1b people on team Collaborative, Client Driven Representative, Authorized, Daily Progress Tracking Iterations Committed and Smaller and More Meetings Level 4 Knowledgeable Frequent Releases (CRACK) Customer Adaptive Customer (4-8 Weeks) Agile Documentation (from Immediately Accessible Agile Modeling) Satisfaction Adaptive Planning Feedback Customer contract revolves User Stories around commitment of collaboration, not features Continuous Integration Self Organizing Risk Driven Iterations Teams Continuous Improvement Level 3: (i.e. Refactoring) Integrated Maintain a list of all Frequent face-to-face Have around 30% of remaining features communication Cockburn Level 2 and (Backlog) between Level 3 people on team the team Automated Unit Tests Software Configuration Continuous Delivery Management Level 2: (Incremental-Iterative Customer Contract Evolutionary development) Tracking Iteration through Evolutionary Requirements Working Software reflective of Evolutionary Development Planning at different levels No Big Design Up Front (BDUF) Coding Standards Reflect and tune Collaborative teams Knowledge Sharing Tools Level 1: Process Collaborative Planning (Wikis, Blogs) Customer Commitment to Collaborative Empowered and work with Developing Team Motivated Teams Task Volunteering not Task Assignment

Slide 20: Embrace Change Plan and Deliver Collaboration with to Deliver Human Centric Technical Excellence Software Frequently Business People Customer Value Test Driven Development Level 5 Low Process Frequent Face-to-face Paired Programming Ceremony Agile Project Estimation Ideal Agile Physical interaction between Encompassing Setup developers & Users No/minimal number of (Collocated) Indicator Sheet Cockburn Level -1 or 1b people on team Nominal Values ID Statements Collaborative, Client Driven V W X Y Z