Agile Retrospective Onebit Brownbag, September 18th 2015 

Are we Agile? Based on Onebit Culture Test, we’re not Agile! ( This is our own survey result, engineers…. ) 

Why Agile? “Perfection is not attainable, but if we chase perfection we can catch excellence.” -Vince Lombardi Perfection is a fallacy that leads to over planning, procrastination and failure to ship; agile is about focusing on delivering the best thing possible in a set time period. 

Where do we start? - SCRUM? - Extreme Programming? - Kanban? - Pair programming? - Something else? 

One of my favorite Agile Quote “If you adopt only one #agile practice, let it be retrospectives. Everything else will follow.” – Woody Zuill (@woodyzuill) 

Why Retrospective? “Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning.” – Albert Einstein As agile organizations, teams and team members, we must constantly question what could be better in order to continually improve. 

Goals of Retrospective Insanity, it’s said, is doing the same things and expecting different results. - To help them solve problems and improve themselves! - Team decides and drives its own actions toward their improvement goals. - Respond quickly, and inspect and adapt! - Understand the root cause of problems. Not the symptoms 

Benefits of Retrospective ● Actions from, by and for the team ● Stakeholders can be involved ● No Handover Team will be the one who analyze, define actions and execute it. ● Team control their own destiny! 

Values of Retrospectives - Dare to share! - The result depends on the team - Focus on learning and understanding instead of blame. You may critique anything, but you may never criticize anyone - Trust each other, and assume that everybody is doing the best job they can - Focus on clearly defined problems - Follow up on and evaluate progress. Why it worked, why others didn’t. 

Pre-requisites of Retrospective (1) ● The need for ritual Usually, we never stop to reflect during projects. Let’s make it a ritual! ● Naming the process Make people inside and outside the process understands it. Retrospective is quite simple right? ● Prime Directive Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand. 

Pre-requisites of Retrospective (2) ● Avoid dark side of retrospectives Avoid retrospective to be complaint session. Express your thoughts or problems as wishes instead of accusations ● Retrospective Facilitator Facilitator should have a clear idea what is the expected result from retrospectives. Become a good facilitator takes time. 

Retrospective Structures 1. Set the stage Prepare teams for the work they’ll do in the retrospective 2. Gather Data Create shared picture about what happened previously. 3. Generate insights Evaluate data and make interpretations 4. Decide what to do Decide what the team need to focus and team members must agree the decision or conclusion. Use timebox method for step 1-4 5. Close the retrospective 

Let’s Play!