Agile John Brunning, Senior Associate John.Brunning@fieldfisher.com 020 7861 4280 04 September 2014 Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com
What we will cover What is Agile? Agile vs Waterfall Managing the Risks Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 1
What is Agile? Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 2
What is Agile? Group of software development methodologies Requirements and solutions evolve through collaboration Agile Manifesto Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 3
The Agile Manifesto key concepts Customer satisfaction by rapid, continuous delivery of useful software Working software is delivered frequently (weeks rather than months) Working software is the principal measure of progress Even late changes in requirements are welcomed Close, daily cooperation between business people and developers Face- to- face conversation is the best form of communication (co- location) Projects are built around motivated individuals, who should be trusted Continuous attention to technical excellence and good design Self- organising teams Regular adaption to changing circumstances Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 4
Types of Agile Methodology Scrum extreme / Pair Programming Lean Software Development Feature Driven Development est Driven Development DSDM (Dynamic Systems Design Method) Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 5
Example of Agile: A Scrum Cycle Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 6
Agile vs Waterfall Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 7
The Waterfall Model/Modular Approach Requirements Design ImplementaGon VerificaGon Maintenance Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 8
An analogy V Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 9
Key Bene=its and Challenges Key Bene2its Iterative rather than big bang Working code delivered each iteration Ability to address changing business requirements Early and frequent customer feedback Ability to identify and mitigate problems early V Key Challenges No contractual requirements Pricing agile contracts Incentivising performance Managing the process Big shift from traditional waterfall approach Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 10
Contractual Risk Models Supplier Risk Waterfall Hybrid? True Agile Customer Risk Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 11
Managing the Risks Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 12
Contracting for Agile Requirements Pricing Governance Acceptance Performance Changes Termination Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 13
Requirements No contractual detailed requirements High level scope + constraints speci=ied Documentary deliverables Non- contractual prioritised list of requirements Delivery of Core Requirements? Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 14
Pricing T&M Fixed price Fixed price per iteration Fixed price per unit of effort Target pricing Caps/incentive mechanisms? Combination? Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 15
Process, Governance and Communication Describe process rather than the result Communication lines identi=ied Project teams to make decisions Approvals given orally Consideration for multi- location/offshoring Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 16
Acceptance and warranty Iterative Testing De=inition of completed Only completed software tested Some development may not be used Final sign- off based on previous acceptances Warranty Period Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 17
Monitoring Performance Burndown Charts and Project Velocity used to monitor performance Service Levels - amount delivered versus amount agreed to be delivered Quality measured through defects found after each iteration Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 18
Termination and Changes Termination possible after each iteration Changes to requirements for free (with caveats!) Formal change procedure for high level objectives Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 19
Any Questions? John Brunning, Senior Associate John.Brunning@=ield=isher.com 020 7861 4280 Brussels / Düsseldorf / Hamburg / London / Manchester / Munich / Palo Alto /Paris / Shanghai / =ield=isher.com 20