CUSTOMER 1 COLLABORATION over contract negotiationMANIFESTOAGILE INDIVIDUALS and 2 INTERACTIONS over processes and tools RESPONDING to 3 CHANGE over following a plan WORKING 4 SOFTWARE over full documentation
1 DELIVER SOFTWARE 2 EMBRACE CHANGE SHOW OFTENAGILE 3 PRINCIPLES 4 WORK TOGETHER 5 PROVIDE ENVIRONMENT 6 CHAT FACE-to-FACE 7 MINIMIZE WASTE 8 MAINTAIN PACE 9 SEEK TECH EXCELLENCE 10 LOVE SIMPLICITY 11 SELF-ORGANIZE TEAMS 12 IMPROVE CONTINUOUSLY
TIME BOXED PLANNING Fixed Scope Time Cost Agile! TraditionalEstimated Cost Time ScopeFrom a plan driven approach to a value driven one.
SCRUMDEFINITION iterative, incremental methodology for project management often seen in agile software development.
SCRUM ROLES PRODUCT OWNER1 the voice of the customer TEAM MEMBER2 deliver the product SCRUM MASTER3 facilitator, mentor, coach EXTERNAL EXPERTS4 consultants, assessors, auditors
SCRUM TEAMS TeamProd. Owner ?" ?" Tech Lead Test engineers Int. designer Visual InterfaceScrum Master designer #" #" #" <># Developers Front-end dev. ?*# QA Lead
In this beginning stage the MYSCRUM? At this point the student Now the student isntstudent follows the begins to branch out. With learning from otherteachings of one master the basic practices people, but from his ownprecisely. He concentrates working he now starts to practice. He creates hison how to do the learn the underlying own approaches andtask, without worrying too principles and theory adapts what hes learnedmuch about the underlying behind the technique. He to his own particulartheory. If there are multiple also starts learning from circumstances.variations on how to do other masters andthe task, he concentrates integrates that learningon just the one way his into his practice.master teaches him. shu ha ri
“AGILE” ANTI-PATTERN “Agile” team Centralized QA IT OperationsCustomer Iteration 1 2 3 4 5 The “last mile” http://gotocon.com/dl/jaoo-aarhus-2010/slides/JezHumble_ContinuousDelivery.pdf
RELEASEFREQUENTLYBut wait, what doesfrequently mean to you?
RELEASE FREQUENTLYNumber of days withreleases1 release 3,5 releasesevery 2 every week!weeks IJ 2010 IJ 2012
CONTINUOUS DELIVERYConstant flow of new features into production
CONTINUOUS DELIVERYFlickr deploy ten times eachday...Why don’t you? http://code.flickr.com/ IJ 2010 IJ 2012 Flickr
PRODUCTION-READY SOFTWAREFast, automated feedback on theproduction readyness of yourapplication every time there is achange – to code, infrastructure, orconfiguration http://channel9.msdn.com/Events/ALM-Summit/2011/Continuous- Delivery
PRINCIPLES create a repeatable, build quality in reliable process for releasing software done means released automate almost everybody is everything responsible for delivery keep everything in continuous version control improvement (kaizen) http://gotocon.com/dl/jaoo-aarhus-2010/slides/JezHumble_ContinuousDelivery.pdf
Source control Perforce CI server Jenkins One-step build Ant Maven Continuous delivery pillarsAutomated testing JUnit QTP
ZERO* DOWNTIME RELEASE UPDATESTo upgrade from 1.1 to 2.0 Release 1.1 Release 1.2 Release 1.3 Release 2.0 Release 2.1 Initial Make 1.1 Migrate db Clean 1.1 app to 2.0 compat DB compatible with 2.0 DB DB Changes Release updated! DB Changes