Lean Software Development Tips and Tricks Augusto “Gus” Evangelisti - PaddyPower PLC

Slides:



Advertisements
Similar presentations
Introduction to Lean. Benefits of Lean Why go Lean? Improvements in: –Customer service –Quality and efficiency –Staff morale –Internal communication and.
Advertisements

Implementation Strategies to Help Improve Systems Rollout Diana Cox, IT Services University of California Center of Excellence for Enterprise Risk Management.
Steve Collins Richland County IT Manager Agile.  Have Fun  Learn About Agile  Tell Some Stories.
LEAN A QUICK INTRO. QUALITY RESPONSIBILITY SKILLS PRICE LABOUR DIVISION STANDARDS CRAFT PRODUCTION MASS PRODUCTION LEAN PRODUCTION.
Archana Mehta. Spot a Failing project Costs a lot more than it should Its takes longer than anyone expected The product doesn’t do what it was supposed.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
If you want to survive in marketing, it’s time to know agile. Dan Naden VersionOne Community Manager.
Creating a learning culture Barriers Some of the main cultural barriers are embedded in: the beliefs of individuals, teams, and the organization People.
Intro to Scrum. What is Scrum? An answer to traditional “fixed cost / strict requirements” contracts which had very high rates of failure Recognizes the.
Non-Coding Activities a Development Team Needs a.k.a ”I don’t code, am I no longer useful?” Maaret Pyhäjärvi| | Twitter: maaretp Test Granlund.
C O R P O R A T I O N January 15, 2014 Confidential: © Victiva Corporation.
8 lessons learned from becoming agile ESTONIA Marko Taipale.
25 Mar 10 – WDM 204 – Session Two. Cape Area Management Program (CAMP) Sponsored by the Cape & Islands Workforce Investment Board.
Extreme Programming Team Members Gowri Devi Yalamanchi Sandhya Ravi.
© AgiliX Agile Development Consulting Agile Demystified Cesario Ramos.
Software SYSTEMS DEVELOPMENT
Agile Methodologies for Project Management By – Komal Mehta.
INSPIRING DIGITAL COMMUNICATION TIPS & TRICKS FOR ENTREPRENEURS By Sarah Lamb #TAGITComms.
James A. Whittaker Principal Architect Visual Studio Team Test Microsoft blogs.msdn.com/james_whittaker.
Failures – Love ‘em or lose János Tóth-Égetö / Software Consultant Softhouse Consulting.
Agile Software Development What is Agile? And How are we implementing Agile?
Presentation copyright © AccuRev, Inc. May be used with permission only. Contact for permission. Damon Poole – CTO, AccuRev.
Copyright © 2008 Pearson Prentice Hall. All rights reserved. 1 1 Professor Donald P. Linden LEAD 1200 CRN Workforce Development and Critical Thinking.
PBI Summit August 23, 2013.
The UX Connection Driving Innovation on an Agile Project Hugh Beyer Cohealo.
The Agile Mindset Linda Rising
Overall Presentation Goal Learn about challenges of adopting Scrum in large enterprises and some rules of thumb. Share experiences and.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
10-January-2003cse Context © 2003 University of Washington1 What is a development project? CSE 403, Winter 2003 Software Engineering
Visibility: How to Educate Your Stakeholders and Be Visible in a Good Way: Joe Todora, DCS Sullivan County Where there’s danger be a stranger… There are.
Webinar Series 2015 ©Pollyanna Pixton Team Ownership: How do we help it happen? Presented by Pollyanna Pixton.
Prototyping a High Quality Student Employee Cameron Goble Technical Training Consultant.
2009 Your Opinion Our Future SurveyClarify and Prioritize Clarify & Prioritize Tool Root Cause The 5 Why’s Control & Employee Impact 4 Block Cost & Ease.
C N H | K E Y C L U B | Updated by: Member Relations Committee California-Nevada-Hawaii District | Key Club International August 2013 Presented.
The Importance of Feedback. Why get customer feedback Feedback is crucial for company improvement…positive feedback is great but it is usually the negative.
Step back step up.  On both sides of the business model Step up? Step back? how and when ?
T Iteration demo T Iteration Demo Team Balboa I1 - Iteration
CS CS 5150 Software Engineering Lecture 2 Software Processes 1.
University School of Agility SAFe Leadership Presented by: Berkana Enterprise Consulting Mac Felsing, SPC/CSM The College of William & Mary Mason School.
The Entrepreneur’s Bootcamp Jeff Hoffman ColorJar

I’m In Charge, Now What?! John Onderdonk, KYSM-FM, San Antonio College Mark Maben, WSOU-FM, Seton Hall University Erica Szczepaniak, WSOU-FM, Seton Hall.
Trust, Ownership and Motivation. Contents Trust, Ownership & Motivation How does it feet to be Trusted? What Trust Looks Like What must you do to be Trusted?
Project management methodologies Waterfall vs. agile vs. half-arsed agile.
Read to Learn Describe the kinds of market research a company may use. Identify the steps in developing a new product.
Principles of Software Engineering: Why Study Software Engineering? COSI 120b, Spring 2005.
Lean Software Development (Can Çetin)
Phoenix Scrum User Group Simplifying Scrum Online May 21 st 2009.
Show Me the Money Getting Results From the Whole Organization Means It ’ s Not Just About the Environment.
Collaboration culture of trust leadership practices problem solving decision making considering risk applications step up, step back.
BizSmart Lunch & Learn Webinar Launching A Minimum Viable Product Speaker: Paul Rhodes, Green Gorilla Apps Date: Tuesday 23rd February Time: 12.30pm With.
Top lean six sigma consulting strategies for businesses Lean Six Sigma Manufacturing Consulting By: Group50.com.
Beginning Software Craftsmanship Brendan Enrick Steve Smith
Collaboration culture of trust leadership practices problem solving decision making considering risk applications step up, step back.
Pull: A Formula for Producing Brand Advocacy Through Software.
Collaborative leadership workshop Accelinnova.com/pdtclassdev.html.
Creating Ambassadors (disciples) Leadership Conference 2016.
Code Simplicity: Software Design In Open Source Projects Max Kanat-Alexander
Getting Started with Flow
Why are Starbucks so successful?
Agile in the Wild The many ways to Apply Agile (not just Scrum and Kanban)
Johanna Rothman Create Technical Excellence Chapter 9
Johanna Rothman Start Somewhere Chapter 17
LEAN A QUICK INTRO.
Scrum Science NGSS: Engineering, Technology, Applications of Science
Be Collaborative. Be Innovative. Be Agile.
Applied Software Project Management
Principles of Customer Service
Our thinking impacts continuous improvement
Extreme Programming Explained by Kent Beck
Presentation transcript:

Lean Software Development Tips and Tricks Augusto “Gus” Evangelisti - PaddyPower PLC

Lean principles Eliminate Waste Optimize The Whole Focus On Customers Energize Workers Learn First Deliver Fast Build Quality In Keep Getting Better (Mary and Tom Poppendiek)

Tip #1: Easy Identify waste

The Waste Snake

What you need Whiteboard/A3 Sheet Post-its Curious team

Tip #2: easy Ask “Why?”

Software is a liability Resolving problems with very little software is of great value

Let me tell you a story US Army: “We need a cost effective fighter jet that can reach speed of mach3” Many companies tried, one succeeded let me tell you a story

Thunderchief Vs Eagle

That means Refuse solutions to unknown problems understand what the real problem is (asking “why?”) and then resolve that (Gojko Adzic)

What you need Courage Trust Empathy Curious team

Tip #3: Medium See the whole

Have you ever seen this?

What’s the solution?

That means Focus on the full flow Remove barriers, collaborate, be cross functional, remove silo departments, whole team responsibility and accountability, fight suboptimization.

What you need Curious team Empathy No barriers No politics One goal, one direction

Tip #4: Difficult Have zero tolerance for defects

Bugs are waste The worst kind of waste! Don’t write them in the first place! Focus on prevention TDD/BDD Implement fast feedback loops

If a bug slips through Fix it immediately We don’t need to log categorize, sort, triage, asses, fight over BUGS We need to fix them so that our customers are happy A bug management tool is another backlog, ditch it, we’ve done it and we’re happy!

Collaborate and prevent

What you need Curious team Empathy No barriers No politics Passion for our craft

Tip #X: Easy Don’t ask for permission, beg for forgiveness!

What do these things have in common?

They were failures

What does this mean? The wrong answer is the right answer to a different question (Paul Sloane) Experiment, try new things, things you’ve never done before, accept failure and learn from it. Only people that don’t innovate never fail. You can only improve trying new things, you can only innovate trying new things, don’t be afraid of failure

So? Fail often Fail cheap How can I fail cheap? Prototyping, spiking, getting fast feedback, speaking to the customers, getting out of my building and speaking about my idea.

What you need Curious team Courage Desire to learn

Read More These readings inspired me: Lean Software Development - An agile toolkit (Mary and Tom Poppendiek) Impact Mapping (Gojko Adzic) The Lean Mindset: Ask the Right Questions (Mary and Tom Poppendiek) The Innovative Leader(Paul Sloane) More to come on:

Tip #6: Easy Use communities of practice to innovate

Tip #7: Difficult Stop predicting, be predictable #NoEstimates

Questions?