© 2012 About Me Doing agile since 1999 Start ups / Enterprises Planigle - Consulting and Training Qcue – VP, Engineering.

Slides:

Advertisements

Similar presentations

Iteration Planning.

Advertisements

Walter Bodwell Planigle. An Introduction – Walter Bodwell First did agile at a startup in 1999 Got acquired by BMC in 2000 and spent the next 8 years.

Why Use Test Driven Development (TDD)?.  Why the need to change to TDD.  Talk about what TDD is.  Talk about the expectations of TDD.

Implementation Strategies to Help Improve Systems Rollout Diana Cox, IT Services University of California Center of Excellence for Enterprise Risk Management.

Taking a Waterfall Project Agile REF: Paul Geberth GCSS-J Project Manager Establishment of an Agile Project.

Agile Samurai Principles. Agile Development Deliver Value Every Iteration Break big problems into smaller ones Focus on most important issues Deliver.

What Is Agile? Agile is a group of software development methodologies Scrum Extreme Programming (XP) Lean Etc. Key Characteristics: Small increments Adaptive.

Walter Bodwell Planigle. An Introduction – Walter Bodwell 18 years in software First did agile at a startup in 1999 Went back to waterfall (after acquisition)

Agile Project Management

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.

Effective Tools for Productive People Lessons Learned for Successful Adoption eRoom Terry Barash Ford Motor Company.

Database Development Keep It Agile, Not Fragile Dev Nambi, Senior Software Engineer, Microsoft.

Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.

Optimizing Your Clarity Support Team.

© 2009 GroundWork Open Source, Inc. PROPRIETARY INFORMATION: Information contained herein is not for use or disclosure outside of GroundWork Open Source,

By John Boal  Continuous Integration [CI] ◦ Automating the build process ◦ Build the entire system each time any new.

CONTINUOUS DELIVERY / CONTINUOUS INTEGRATION. IDEAS -> SOLUTIONS Time.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Extreme Programming.

Gaining Support for a Sustainable Agile Transformation Dennis Stevens, VP Enterprise Engagements LeadingAgile November 12, 2013.

Continuous Delivery Ajey Gore Head of Technology ThoughtWorks India.

Michael Burnside Blog: Software Quality Assurance, Quality Engineering, and Web and Mobile Test.

Software Development Landscape

IS2210: Systems Analysis and Systems Design and Change Twitter:

Opening Keynote Presentation An Architecture for Intelligent Trading  Alessandro Petroni – Senior Principal Architect, Financial Services, TIBCO Software.

© BJSS Limited Going Agile UK TMF - April 2011 Mark Crowther, Test Consultant.

Extreme programming overview Agenda  Extreme programming goals  Extreme programming values  Extreme programming practices  The Extreme programming.

One XP Experience: Introducing Agile (XP) Software Development into a Culture that is Willing but not Ready Joe Bergin * Fred Grossman * David Leip **

Creating a Maintainable Software Ecosystem Jeremy D. Miller November 27th, 2007.

資工 4A 陳怡秀 Microsoft Visual Studio’s Journey to Continuous Delivery.

Release and Iteration Planning September 13, 2008.

 CS 5380 Software Engineering Chapter 8 Testing.

Real World Software Development Management and Solutions Joel Semeniuk April 5, 2011.

Extreme/Agile Programming Prabhaker Mateti. ACK These slides are collected from many authors along with a few of mine. Many thanks to all these authors.

Dr. Tom WayCSC Testing and Test-Driven Development CSC 4700 Software Engineering Based on Sommerville slides.

Engineering  Turning ideas into reality  Creating something useful from other things using science and math.

C O N F I D E N T I A L 22-Oct-15 1 StarCite Engineering Weekly Meeting StarCite Engineering Feb 9, 2009.

Putting the “Engineering” in Software Engineering: Technology Infrastructure in Process Improvement Adam Kolawa, Ph.D. CEO, Parasoft.

1 FROM DEVELOPERS TO ENGINEERS ENGINEERING ROLE IMPLEMETED AT EXPEDIA August 26, 2015.

New Ideas for IA Readings review - How to manage the process Content Management Process Management - New ideas in design Information Objects Content Genres.

1 Planning – Agile Style Highsmith, Ch 7 All kinds of iterations! CSSE579 Session 3 Part 1.

AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.

Agile Engineering. Agile - Engineering en·gi·neer·ing enjə ˈ niriNG/ noun the branch of science and technology concerned with the design, building, and.

What Is Agile? Agile is a group of software development methodologies Scrum Extreme Programming (XP) Lean Etc. Key Characteristics: Small increments Adaptive.

January 24, 2009 Agile Product Management Making Things Happen Walter Bodwell Planigle.

UHCS 2005, slide 1 About Continuous Integration. UHCS 2005, slide 2 Why do you write Unit Test ? Improve quality/robustness of your code Quick feedback.

Principles of Software Engineering: Why Study Software Engineering? COSI 120b, Spring 2005.

Agile Methods Presentation By: Jason Abbett. Definition A process to rapidly develop software Many kinds of agile methods but few are practiced.

Extreme Programming. Extreme Programming (XP) Formulated in 1999 by Kent Beck, Ward Cunningham and Ron Jeffries Agile software development methodology.

CS223: Software Engineering Lecture 5: Software Development Models.

Phoenix Scrum User Group Simplifying Scrum Online May 21 st 2009.

Integrating the Code during the Development Alexander Vakrilov Telerik Corporation

A way to develop software that emphasizes communication, collaboration, and integration between development and IT operations teams.

Globus online Delivering a scalable service Steve Tuecke Computation Institute University of Chicago and Argonne National Laboratory.

1 Punishment Through Continuous Delivery If it hurts, do it more often…

Internal developer tools and bug tracking Arabic / Hebrew Windows 3.1Win95 Japanese Word, OneNote, Outlook

Coming up: What is Agile? XP Development Dan Fleck 2010 Dan Fleck 2010.

The Challenges of Developing Games and Other High-Resolution Graphics Applications February 2007.

Software Development.

Real Metrics for Real Decisions

Johanna Rothman Create Technical Excellence Chapter 9

WEBINAR: Becoming Agile In Software Testing: The Government Edition

X in [Integration, Delivery, Deployment]

Teaching slides Chapter 1.

WEBINAR: Integrating SpiraTest with JIRA

AutomIQ Inc. Proprietary & Confidential – DO NOT DISTRIBUTE

Testing and Test-Driven Development CSC 4700 Software Engineering

Coming up: What is Agile?

Agile Development – a new way of software development?

Presentation transcript:

© 2012 About Me Doing agile since 1999 Start ups / Enterprises Planigle - Consulting and Training Qcue – VP, Engineering

© 2012 Case Study: Qcue SAAS Small team (DevQAOps) Deploy every weeknight (for 2 years) Automation and monitoring are key Lots of small issues Few big issues

© 2012 Agenda Why do it? Prerequisites Getting Good At It

© 2012 Value Before Continuous Deploy A lot of the literature focuses on going “all the way” You get a lot of value before that And it is much easier!

© 2012 Customer Benefits Can turn around fixes / small features quickly Able to give feedback incrementally

© 2012 Engineering Benefits Easy to narrow down what caused the problem Easy to fix Known stability

© 2012 What if I don’t do SaaS? Deploy to an internal server instead Use data typical of production QA, Prod Mgmt, etc. can use it Everything else can still apply

© 2012 Downsides Every deploy can crash and burn Have to be vigilant If done poorly, can spend all your time recovering

© 2012 Prerequisites – Testing Unit tests Integration tests Ability to see what it will look like in production

© 2012 Prerequisites – Deployment Automated build Notification on failure Promote last build that passes

© 2012 Prerequisites – Monitoring Web site / User monitoring Application / Guts monitoring Log monitoring

© 2012 Prerequisites – Processes What if deployment fails? What if your server crashes? What if data is corrupted? What if a critical error gets deployed?

© 2012 Getting Good At It / Tips and Tricks Defects are the first priority Identify / fix the root cause Identify / repair holes in testing / monitoring Small stories help Code reviews / pair programming Retrospect often and change Don’t be disruptive Communicate early and often!

© 2012 What if it is TOO BIG? Break into increments Make it admin only A few customers at a time

© 2012 What if it is too risky? Identify risky areas Vary process by riskiness Anyone can block the deploy

© 2012 Messaging to Customers Release and Marketing can be distinct Fine grained vs. large grained communication

© 2012 Resources Walter Bodwell Planigle